Using the ETSM applications to monitor tablespaces
The ORACLE_ETSM application supports the monitoring of both autoextensible and non-autoextensible tablespaces in the database except for those that are excluded from monitoring. ORACLE_ETSM automatically sorts tablespaces into logical application containers.
The ORACLE_ETSM application discovers and monitors the percent used (PctUsed) and space left (SpaceLeft) for all tablespaces, except those that are excluded from monitoring. It places the tablespaces in ETSM_<tablespaceType> applications according to types. For more information, see Defining tablespace types.
Click to view a short video on how to configure an Oracle ETSM instance for monitoring in a PATROL environment.
For autoextensible tablespaces, the SpaceLeft and PctUsed parameters consider the maximum size of a datafile and actual space available on the disk.
The ORACLE_ETSM uses the following approaches to monitor the ETSM (ORACLE_ETSM) application:
- Monitoring by exception
- Monitoring tablespaces for historic data
- Monitoring newly created tablespaces
- Activating the ETSM applications
- Defining tablespace types
- Using regular expressions to choose tablespaces
- Sorting tablespaces
- Viewing the ETSM reports
- Debugging the ETSM applications
- Excluding Tablespace from being monitored
- ETSM Menu
Note
When monitoring tablespaces with data files that reside in the ASM Storage, make sure the following is true::
export ORACLE_SID=xxxx
export ORACLE_HOME=/xx/xxxx/xxxxx/xxxxxx
export PATH=$PATH:$ORACLE_HOME/bin
sqlplus mon_account/password
SQL>select count(*) from v$asm_diskgroup_stat;
The returned value must not equal a 0 value.
ORACLE_ETSM correctly monitors the tablespaces when the following Oracle objects are used:
- dba_free_space
- dba_data_files
- dba_tablespace_usage_metrics
- dba_tablespaces
- dba_temp_files
- v$sort_segment
- v$temp_extent_pool
- v$tempstat
- v$tempfile
- v$tablespace
- v$filestat
Comments