Use this Knowledge Script to set the various monitoring options available with AppManager for Oracle (UNIX). You can set the location where files reside whose filenames contain the names of databases to be “blacked out” (not monitored) while they are down due to scheduled activities such as maintenance. Enter a full path to a directory containing filenames whose names indicate which databases to exclude from OracleUNIX jobs.
To reset this script, you can enable one or more parameters but leave their values blank and then run the job. For example, if you enable the Set option for blackout monitoring? parameter but leave the next parameter, Full path to directory with database names to exclude, blank, the next time you run the job, you overwrite the previous value with a blank value. This is the recommended way to reset the blackout monitoring option or any of the clustering options.
This script also lets you specify whether to monitor tablespaces with temporary contents, and/or those with autoextensible datafiles.
NOTE:Use this script to specify monitoring options for running jobs in a clustered environment. AppManager for Oracle (UNIX) supports monitoring both RAC and non-RAC clustered environments. For details, see the topics below.
An Oracle RAC cluster consists of one database and multiple Oracle instances that share that common database. Each instance runs on a separate node. The Oracle RAC software knows which instances are active and which are inactive.
The following information must be supplied by the SetMonitoringOptions script to enable monitoring in a RAC environment:
Service name for the RAC cluster
Directory containing the tnsnames.ora file (only if this file is in the non-default location). The default location is $ORACLE_HOME/network/admin.
NOTE:AppManager for Oracle (UNIX) requires that you configure Transparent Application Failover (TAF). TAF is an Oracle configuration that allows a client to attempt to connect to an instance, and if that attempt fails, to attempt to connect to a different instance. TAF is configured by default during Oracle RAC installations, but in rare cases might subsequently have been manually disabled. In this scenario, you must reconfigure TAF to enable monitoring by AppManager for Oracle (UNIX). For more information, see the Oracle Net Services Administrator’s Guide.
You can also use Oracle in non-RAC clusters. In this kind of cluster, third-party cluster software (VERITAS, Sun Cluster, etc.) installed on the nodes controls which Oracle instances are active. This software makes a required resource available only on active nodes. The required available resource is a file, directory, or device that resides in the file system.
The full path to this resource must be supplied by the SetMonitoringOptions script to enable monitoring in a non-RAC environment.
Oracle Database folders. When you drop a script on an Oracle Database folder, a job executes on that database and monitors only that database.
The default interval for this script is Run once.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Set option for blackout monitoring? |
Select Yes if you should set blackout location upon executing this job iteration. By default, this parameter is not selected. |
|
Full path to directory with database names to exclude |
Specify the directory where files reside whose filenames include database names for databases that should not be monitored (databases to “black out”). The default is blank. |
|
Set option for monitoring temporary tablespaces? |
Select Yes if you should set the option for monitoring tablespaces with temporary contents upon executing this job iteration. The default is unselected. |
|
Monitor temporary tablespaces? |
Select Yes to monitor those tablespaces with temporary contents. Clear the box to skip monitoring such tablespaces. The default is Yes. |
|
Set option for monitoring autoextensible tablespaces? |
Select Yes to set the option for monitoring tablespaces with autoextensible datafiles upon executing this job iteration. The default is unselected. |
|
Monitor tablespaces with autoextensible datafiles? |
Select Yes to monitor those tablespaces with datafiles that autoextend. Clear the box to skip monitoring such tablespaces. The default is Yes. |
|
Set option for monitoring Oracle RAC? |
Select Yes to monitor computers running Oracle RAC upon executing this job iteration. The default is unselected. |
|
Service name for the RAC cluster |
Enter the service name identifying the Oracle RAC environment upon which the job will run. This allows the Oracle UNIX/Linux managed object to connect to Oracle on the host and determine which nodes are active. The default is blank. |
|
Directory containing tnsnames.ora file (if not in default location) |
Enter the path to the folder containing the tnsnames.ora file. This is normally what the $TNS_ADMIN environment variable is set to for Oracle to resolve service names. The default location is normally: $ORACLE_HOME/network admin. The default is blank. NOTE:The default location is used if a directory is not specified here. |
|
Set option for monitoring non-RAC cluster? |
Select Yes to monitor computers running as part of a cluster where Oracle RAC is not installed upon executing this job. The default is unselected. |
|
Path to a required available resource |
Enter the path to a resource (file, directory, device, etc.) that must be available to the computer running the Oracle UNIX/Linux managed object in order for jobs to execute successfully. This can be a resource that a node in a cluster requires in order for that node to have access to Oracle. The default is blank. |
|
Raise event if unable to set monitoring options? |
Select Yes to raise an event when the monitoring options could not be set. The default is Yes. |
|
Severity |
Set the event severity level, from 1 to 40, to indicate the importance of the event for successfully setting the monitoring options. The default is 15 (yellow event indicator). |
|
Raise event to display options currently set? |
Select Yes to raise an event providing a summary of the current settings for monitoring options. The default is unselected. |
|
Severity |
Set the event severity level, from 1 to 40, to indicate the importance of the event for successfully setting the monitoring options. The default is 40 (magenta event indicator). |