Dataguard startup time
Job details
| Name: |
Dataguard startup time |
| Platform: |
Oracle |
| Category: |
Cluster and Replication |
| Description: |
Checks refresh date of scheduled jobs in refresh group(s). |
| Long description: |
|
| Version: |
1.0 |
| Default schedule: |
10m |
| Requires engine install: |
No |
| Compatibility tag: |
.[type=‘instance’ & databasetype=‘oracle’] |
Parameters
| Name |
Default value |
Description |
| warning_delay_sec |
60 |
Warning status if startup time is more than x seconds |
| alarm_delay_sec |
300 |
Alarm status if startup time is more than x seconds |
Job Summary
- Purpose: The purpose of this job is to monitor and check the startup time of Oracle Dataguard standby nodes.
- Why: This job is important because it helps ensure that Oracle Dataguard startup times are within acceptable limits, which is crucial for maintaining system availability and performance in replication environments. If startup times exceed specified thresholds, it could indicate potential issues that may impact the disaster recovery strategy.
- Manual checking: You can manually check the Oracle Dataguard startup time in the database by issuing the following SQL command:
select value from sys.v$dataguard_stats where name like 'estimated startup time'
Job Configuration
- “Dataguard startup time”: It checks for the startup time on Oracle Dataguard standby nodes categorized under ‘Cluster and Replication’.
- The default alarm threshold is set at 300 seconds, and the warning threshold is set at 60 seconds.
- This job has an automatic installation property if certain conditions on the database instance are met indicating it’s an Oracle database and specifically a physical standby.
Deployment and Compatibility
- The job is designed for instances identified as Oracle databases with the status of being a physical standby.
- A series of filters and compatibility settings ensure that the job runs only on appropriate Oracle database instances.
Job Details and Report
| Column Name |
Data Type |
| Details |
varchar |
The report will provide information in a simplified table format showing the Dataguard startup time.
Scheduling and Frequency
- Default schedule: The job is scheduled to run every 10 minutes.
- The monitoring status, based on execution, can be one of the following: normal (0), warning (1), or alarm (2), depending on the fetched startup time:
- If the startup time is above 60 seconds, a warning is issued.
- If above 300 seconds, it raises an alarm.
- Otherwise, it reports the actual startup time without any alerts.
Resolution and Maintenance
- Deeper investigation and tuning should be considered if startup times frequently exceed the warning or alarm thresholds. Adjustments may include reviewing the physical hardware, network conditions, or specific replication settings in Oracle Dataguard configurations.
- Continued monitoring and periodic reviews of this job’s outcomes are suggested to maintain optimal performance of the database replication system.