Apply Lag (ApplyLag) - Documentation for BMC PATROL for Oracle Database Monitoring 9.7
Displays the amount of time that the application of redo data on the standby instance lags behind the primary instance. The value for this parameter is set by querying the apply lag column from the v$dataguard_stats view. The ApplyLag parameter depends on the v$dataguard_stats view. So the parameter goes OFFLINE if the apply lag column in the v$dataguard_stats view returns a NULL value.
For example: When the recovery process at the standby instance has not been started or has been stopped the v$dataguard_stats view returns a NULL or no rows value for the apply lag column.
Default parameter attributes
Attribute | Default value |
|---|---|
Application class |
|
Command type | not applicable |
Platform | All |
Icon style | Graph |
Unit | Time in minutes |
Border range | Undefined |
Alarm1 range | Undefined |
Alarm2 range | Undefined |
Scheduling(poll time) | 10 mins |
Active at installation | Yes |
Parameter type | Consumer |
Annotated? | No |
Value set by |
|
BMC ProactiveNet Performance Management properties
Default value | |
|---|---|
| Monitor type | Oracle Database Dataguard Standby Instance Parameters |
| Key Performance Indicator | Yes |
| Monitor for abnormalities | Yes |
| Graph by default | Yes |
| Availability | No |
| Response time | No |
| Normal distribution | Yes |
| Statistical | Yes |
