Deactivating parameters-1

To reduce the impact on your system resources and enhance performance, you can deactivate parameters that are not commonly needed. A deactivated consumer parameter does not appear and does not go into an alarm or warning state. However, the collector parameter that sets the deactivated consumer parameter continues to send information to the deactivated consumer parameter. Further, the collector notates the system output window with an error each time it attempts to send information to a deactivated consumer parameter. Collector parameters might also set off unwanted recovery actions if they cannot find a deactivated consumer parameter. Consider the following before deactivating a parameter:

• If you disable only the alarms for a consumer parameter, the collector parameter continues to send data to the consumer parameter, and the consumer parameter continues to provide a view and history for that data. However, the consumer parameter no longer triggers any alarms, warnings, or recovery actions.
• If you deactivate a collector parameter, the collector parameter stops collecting data for the consumer parameters it sets.
• If you disable an application class, no parameters under that application class are displayed. During configuration, you select which Categories or application classes are enabled to monitor the instance.

 Parameters with their status set in code

The following parameters directly set their status, and their status changes when conditions change. These internal status changes overwrite whatever changes are made through PATROL Configuration Manager.

• Cannot Extend--the status for this parameter is set to OK when the parameter is set to active, and OFFLINE when the parameter is set to inactive.
• TempTSLeft and TempTSLeftPct--these parameters are set offline when all temporary tablespaces are excluded from monitoring.
• The parameters under the ORACLE_MTS, ORACLE_PQO, and ORACLE_REPLICATION application classes are offline or online, depending on whether the features associated with these application classes are active for the Oracle instance.
• The ListenerTraceSize and ListenerLogSize parameters under the ORANET_LISTENER application class are offline or online depending upon whether tracing or logging is on or off.

 Reactivate parameters with PATROL Configuration Manager

The following table lists parameters that you must reactivate through PATROL Configuration Manager if you deactivated them through PATROL Configuration Manager.

Parameters that you must reactivate with PATROL Configuration Manager

 

 ~|

 ~|

 

ORACLE_TBS_INSTANCE

AutoExtended

ORACLE_AVAILABILITY

CannotExtend

RSExtentsLeft

RSExtentsLeftPct

RSSpaceLeft

RSSpaceLeftPct

SystemTSLeft

SystemTSLeftPct