The following sections describe the procedure to configure monitoring options with AppManager for Oracle (UNIX) for maintenance and other purposes.
NOTE:The following sections apply only to Oracle Unix Knowledge Scripts. They do not apply to Oracle RAC Unix Knowledge Scripts.
AppManager for Oracle (UNIX) allows you to set up an environment in which jobs will not be run on Oracle databases that are known to be down for maintenance or other purposes. The SetMonitoringOptions Knowledge Script lets you specify a “blackout” directory on the UNIX host where the AppManager for Oracle (UNIX) component is installed. This directory contains filenames with the names of Oracle databases on which no jobs should be run. These filenames must begin with the name of the database. After the name of the database, these filenames might contain additional characters, possibly to serve as a description. The first of these additional characters, if any, must be a character that is not valid in an Oracle database name (A-Z, 0-9, _, $, and # are all valid characters in an Oracle database name).
For example, you can use the SetMonitoringOptions Knowledge Script to set the folder /usr/oracle/blackout as the blackout directory. When the databases oradb817 and oradb920 are down over the next few hours, it creates the following empty files:
/usr/oracle/blackout/oradb817.maintenance /usr/oracle/blackout/oradb920.upgrade.
Although OracleUNIX jobs continue running on any other Oracle databases on this host whose names do not appear as part of the beginning of a filename in this folder, no jobs are run on oradb817 and oradb920. Once the maintenance period is over, you can remove these files from the blackout directory, and monitoring resumes.
In addition, you can set a parameter in the DatabaseDown Knowledge Script so that when it runs and finds the selected database is down, it can automatically create a file in the blackout directory identifying the database to exclude from monitoring. In these cases, you must manually remove the files denoting databases down for maintenance in order for jobs to proceed correctly on these databases.
You might not want to monitor tablespaces that have temporary contents or whose datafiles are autoextensible. In these cases, the SetMonitoringOptions Knowledge Script also includes options to enable or disable monitoring for these types of tablespaces. You can enable or disable monitoring while jobs associated with the TablespaceAvail Knowledge Script are currently running.