Dataguard transport time
Job details
| Name: |
Dataguard transport 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_min |
2 |
Warning status if redo log transport is more than x minutes delayed |
| alarm_delay_min |
5 |
Alarm status if redo log transport is more than x minutes delayed |
Job Summary
- Purpose: The purpose of this job is to monitor the transport time in Oracle Data Guard standby nodes. It provides insights into the delay in redo log transports to standby databases.
- Why: This job is important as it helps in determining if there are significant delays in redo log synchronization between the primary and standby databases. Timely detection of transport lags ensures data consistency and availability in disaster recovery scenarios. If these thresholds are reached, timely measures can be taken to prevent data loss or discrepancies.
- Manual checking: You can check this manually in the database by issuing the following SQL command:
select 60 * extract(hour from to_dsinterval(value)) + extract(minute from to_dsinterval(value)) as "Transport lag in min" from sys.v$dataguard_stats where name like 'transport lag';
Technical Details
| Attribute |
Description |
| Name |
Oracle Dataguard transport time noschema |
| Version |
1.0 |
| Company |
dbWatch.com |
| Group |
com.dbwatch.job |
| Artifact ID |
oracle_noschema_dataguard_transport_time |
| Category |
Cluster and Replication |
| Instance Requirement |
False |
| Express Install |
True |
| Compatibility |
Oracle Data Guard instances configured as physical standbys |
Configuration Parameters
- warning_delay_min : Triggers a warning status if the transport lag exceeds the specified minutes.
- alarm_delay_min : Triggers an alarm status if the transport lag significantly exceeds the specified minutes.
Schedule and Frequency
- The job is scheduled to run every 10 minutes by default.
Output Evaluation
- The JavaScript engine evaluates the transport lag and sets statuses based on predefined threshold values:
- Status 1 (Warning) is set if transport lag exceeds the warning threshold.
Reporting
- Report Title: Dataguard transport time status
- Description: Provides the status of transport time in Data Guard configurations.
- Schedule: The report is generated automatically every hour.
- Content: A table in the report shows the detailed transport lag times fetched from the job output, enriching diagnostics and monitoring of data synchronization statuses.