Configure large and very large tablespace categorization

Before you begin

1. In BMC Helix Operations Management, select Configuration > Monitor Policies > Create Policy.
2. Click Add Monitoring Configuration.
3. From the Monitoring Solution list, select Oracle Enterprise Database.
4. From the Monitor Profile and Monitor Type lists, select Oracle Environment Monitoring.
5. In the Monitor Type section, select the required monitor type.
6. In the Environment configurations section, click Add.
7. Add the required Environment configurations details.
   Important: To monitor Tablespaces, make sure you select the Tablespaces checkbox to enable tablespace monitoring under Monitoring Categories in the monitor policy.
   To monitor pluggable database tablespaces, make sure you select the Pluggable Database checkbox to enable tablespace monitoring under Monitoring Categories in the monitor policy.
8. Click OK.

To configure Oracle tablespace monitoring for large and very large sizes

1. In BMC Helix Operations Management, select Configuration > Monitor Policies.
2. On the Monitor Policies page, click Configuration and select Monitor Policies.
3. Click the action menu of the policy that you want to modify and select Edit.
4. In the Configuration Variables tab, click Add Configuration Variable.
5. On the Add Configuration Variable page, enter the appropriate variable in the Variable field. Global-level variables apply across all monitor types and environments. Environment-level variables apply only to a specific environment and monitor type. 
   1. For Environment-level:
      • /KOE/Oracle/<EnvType>/<EnvName>/LargeTablespaceSize
      • /KOE/Oracle/<EnvType>/<EnvName>/VeryLargeTablespaceSize
   2. For Global-level:
      • /KOE/Oracle/VeryLargeTablespaceSize
      • /KOE/Oracle/LargeTablespaceSize
6. In the Environment-level variable, ​​​​the <EnvType> ​​​stands for Environment Type. Replace <EnvType> with either Oracle Data Guard Database, Oracle Standalone Database, Oracle Real Application Cluster, or Real Application Cluster One Node Database monitor type.
7. In the ​Environmental Variable, ​​​​the <EnvName> stands for Environment Name. Replace <EnvName> with the name that you used in the Environment name field in the monitor policy.
8. Select the REPLACE operation.
9. In the Value field, specify the minimum tablespace size in MB.
10. Save the configuration variable.
11. Restart the PATROL Agent for the changes to take effect.

For example, if LargeTablespaceSize is set to 200 and VeryLargeTablespaceSize is set to 500, tablespaces between 200 MB and 500 MB are monitored under the Oracle Large Tablespace (KOE_INST_LARGE_TABLESPACE) application class, and tablespaces larger than 500 MB are monitored under the Oracle Very Large Tablespace (KOE_INST_VERY_LARGE_TABLESPACE) application class.

To configure Pluggable database tablespace monitoring for large and very large sizes

1. In BMC Helix Operations Management, select Configuration > Monitor Policies.
2. On the Monitor Policies page, click Configuration and select Monitor Policies.
3. Click the action menu of the policy that you want to modify and select Edit.
4. In the Configuration Variables tab, click Add Configuration Variable.
5. On the Add Configuration Variable page, enter the appropriate variable in the Variable field. Global-level variables apply across all monitor types and environments. Environment-level variables apply only to a specific environment and monitor type. 
   1. For Environment-level:
      • /KOE/Oracle/<EnvType>/<EnvName>/PluggableLargeTablespaceSize
      • /KOE/Oracle/<EnvType>/<EnvName>/PluggableVeryLargeTablespaceSize
   2. For Global-level:
      • /KOE/Oracle/PluggableVeryLargeTablespaceSize
      • /KOE/Oracle/PluggableLargeTablespaceSize
6. In the ​Environment-level variable, <EnvType> ​​stands for Environment Type. Replace <EnvType> with either Oracle Data Guard Database, Oracle Standalone Database, Oracle Real Application Cluster, or Real Application Cluster One Node Database monitor type.
7. In the ​​Environment-level variable, ​​​​the <EnvName> stands for Environment Name. Replace <EnvName> with the name that you used in the Environment name field in the monitor policy.
8. Select the REPLACE operation.
9. In the Value field, specify the minimum tablespace size in MB.
10. Save the configuration variable.
11. Restart the PATROL Agent for the changes to take effect.

For example, if PluggableLargeTablespaceSize is set to 200 and PluggableVeryLargeTablespaceSize is set to 500, tablespaces between 200 MB and 500 MB are monitored under the Oracle Pluggable Large Tablespace (KOE_INST_PLUGGABLE_LARGE_TABLESPACE) application class, and tablespaces larger than 500 MB are monitored under the Oracle Pluggable Very Large Tablespace (KOE_INST_PLUGGABLE_VERY_LARGE_TABLESPACE) application class.