Retour
-
Titre
Cannot see in SQL PI when an Oracle instance ran out of TEMP space -
Description
Would the Oracle monitoring of SQL PI product expect to see data (i.e. how does the functionality work) in the following scenario?• The database ran out of TEMP space in Oracle in the instance on Nov-17 night around midnight.• A DBA watched the system and confirmed that this was caused by the INSERT INTO TABLENAME statement• SQL PI did not show that INSERT statement running on Nov-17 around midnight and the Files area in the tree did not show the systemtemp.dbf file listed• The only activity for this INSERT statement was around midnight on Nov15Should the user have seen the INSERT statement in SQL PI on Nov-17 when the datafile ran out of temp space?Should the user have seen the systemtemp.dbf data file in the tree if Nov-17 when the datafile ran out of temp space?. " -
Cause
The two most likely reason why a sql statement isn't seen in specific time range are:- The sql isn't captured by agent during the time.
- The data has been aggregated to 1 hour granularity, and the specific time range misses the records.
-
Résolution
The temp space issue was not seen because SQL PI filters out the files whose workload is less than 0.01. For this reason the specific file was not able to be displayed in the PI dashboard (the workload of the specific file is less than 0.01).This functionality is by desgin as PI does not intend to show all activity - just the top events. -
Informations supplémentaires
A debug jar intended to identify the root cause was provided to the user. In the debug jar, we displays all files whose workload is greater than 0 (the original jar only displays the files whose workload is greater than 0.01)