Use this Knowledge Script to monitor the number of times that a process tries to write an entry in the redo log buffer for a scheduled interval of time. The job raises an event and than stores data if the number of tries is different for subsequent iterations of the script.
The number of retries should be low. A high number of retries can adversely affect system performance, as processes must wait for buffers. If a process has to make numerous attempts to write an entry in the redo log buffer, you might need to allocate more space to the redo log buffer.
You can set a threshold value for the maximum number of times a process can try to write an entry in the redo log buffer. If the number of retries exceeds the threshold, the job raises an event.
The account you use to run this script must have SELECT permissions for the following tables:
V_$SGASTAT
V_$SYSSTAT
V_$VERSION
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 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 redo log write attempts? |
Select Yes to collect data for charts and reports. When you enable data collection, the Knowledge Script returns the number of times that processes attempted to write entries to the redo log buffer. The default is unselected. |
|
Raise event if threshold is exceeded? |
Select Yes to raise an event if the number of times that a process tries to rewrite an entry to the redo log buffer exceeds the threshold you set. The default is Yes. |
|
Threshold - Maximum redo log buffer allocation retries |
Enter a threshold for the maximum number of times that a process might try to rewrite an entry to the redo log buffer before the job raises an event. The default is 50. |
|
Severity |
Set the event severity level, from 1 to 40, to indicate the importance of the event. The default is 5 (red 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 default is 5 (red event indicator). |