Use this Knowledge Script to retrieve the number of redo logs that are not being archived, if archiving is turned on for a given Oracle database. The number of redo logs not archived is returned and compared against the thresholds you specify. The Knowledge Script retrieves the archive status for an Oracle database from the AppManager repository, which is updated during discovery. To enable archiving, you must rediscover the Oracle UNIX resources if the redo log archive is enabled after you discover resources.
When you enable data collection, the number of redo logs not archived is stored in the repository. You can set multiple thresholds for the number of redo logs not archived, with varying severities, and the job raises an event when any of these thresholds exceed the values you specified.
The account you use to run this script must have SELECT permissions for the following tables:
V_$LOG
V_$VERSION
Oracle Database folders. When you drop a script on an Oracle Database folder, a job executes on that database and checks for ARCHIVING log mode before proceeding to monitor that database. The job then collects the number of redo logs that have not been archived. This data is collected and stored in the repository if you have enabled data collection.
The default interval for this script is Every 10 minutes.
Set the following parameters as needed:
|
Description |
How to Set It |
|---|---|
|
Oracle Username |
Enter the username that this script needs to access the target databases. If you run this script on more than one database, configure each database with the same username. To use SYSDBA authentication, leave this parameter blank. The default is blank. |
|
Collect data for number of redo logs not archived? |
Set to y to collect data. If data collection is enabled, returns the number of redo logs not archived. The default is n. |
|
Raise event if threshold is exceeded? |
Select Yes to raise an event if the threshold exceeds the value you specified. The default is Yes. |
|
Threshold - Maximum number of redo logs not archived |
Specify a threshold for the maximum number of redo logs that have not been archived. The default is 6. |
|
Severity |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 5 (red event indicator). |
|
Raise event if threshold is exceeded? |
Select Yes to raise an event if the threshold exceeds the value you specified. The default is unselected. |
|
Threshold - Maximum number of redo logs not archived |
Specify a threshold for the maximum number of redo logs that have not been archived. The default is 4. |
|
Severity |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 15 (yellow event indicator). |
|
Raise event if threshold is exceeded? |
Select Yes to raise an event if the threshold exceeds the value you specified. The default is unselected. |
|
Threshold - Maximum number of redo logs not archived |
Specify a threshold for the maximum number of redo logs that have not been archived. The default is 2. |
|
Severity |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 25 (blue event indicator). |
|
Raise event if threshold is exceeded? |
Select Yes to raise an event if the threshold exceeds the value you specified. The default is unselected. |
|
Threshold - Maximum number of redo logs not archived |
Specify a threshold for the maximum number of redo logs that have not been archived. The default is 1. |
|
Severity |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 35 (magenta event indicator). |
|
Ignore agent’s blackout state and keep monitoring? |
Select Yes to collect data during the blackout window for scheduled maintenance that you set using the AppManager for UNIX AMAdminUNIX_ SchedMaint Knowledge Script. The default is unselected. |
|
Event severity for internal failure |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The is 5 (red event indicator). |