Resolving data replication errors in Instance Data Replication
-
- UpdatedJan 30, 2025
- 3 minutes to read
- Yokohama
- Instance Data Replication
Resolve errors and monitor the status of Instance Data Replication (IDR) replication sets.
Monitoring and diagnostic checklist
Check | Description |
---|---|
Monitor | |
Check connectivity | Test your IDR instance connectivity to determine the connectivity of your instance to the message queue. |
Check IDR monitoring dashboard to see if replication jobs are active | For the dashboard to properly display replication set information, these IDR scheduled jobs must be available and running
on your instance:
If any of these jobs are missing or not running, contact Customer Service and Support. Note: The system only creates the
IDRDeltaConsumerJob-<instanceid> when a consumer instance subscribes to a
producer instance that is outside the local datacenter. |
Producer replication set | |
Check activation of the producer replication set | If the status of your producer replication set is In Draft, click Activate. |
Check consumer subscription approval | Review the consumer access requests for your producer replication sets. A consumer replication set must request access before it can receive replication data. |
Check producer replication log errors | Identify IDR errors by viewing the metadata for messages between producer and consumer instances, payload error logs, and message logs. |
Consumer replication set | |
Check activation status of the consumer replication set | If the status of your consumer replication set is In Draft, click Activate. |
Check if you need to synchronize replication sets | A synchronization issue occurs when a producer instance doesn't send data or a consumer instance doesn't receive data. Synchronization errors appear in the Status field on the consumer instance as Replication Error. |
Check your consumer replication set status | Review the status of your consumer replication set and what that means for your replication. |
Error and status messages | |
Check replication or replication metadata log errors | Identify IDR errors by viewing the metadata for messages between producer and consumer instances, payload error logs, and message logs. |
Check status messages | Review these status messages with recovery information. |
On this page
Related Content
- Manage consumer access to replication data in Instance Data Replication
Approve or deny a request to grant access to the replication data in Instance Data Replication (IDR).
- Comparing replicated data between instances in Instance Data Replication
Find missing or mismatched records by comparing replication data between instances in Instance Data Replication (IDR).
- Deploying a replication configuration from one instance to another in Instance Data Replication
Copy a replication configuration from one instance to another through an update set in Instance Data Replication (IDR).
- Cloning with Instance Data Replication
Ensure that certain tables are preserved or excluded to clone your database from one instance to another successfully with Instance Data Replication (IDR).
- Monitoring replication status in Instance Data Replication
Monitor the status of active producer and consumer replication sets, scheduled jobs, seeding requests, and license or usage details through the Instance Data Replication (IDR) Monitoring Dashboard.
- Monitoring queues in Instance Data Replication
Monitor the replication record queue, message produced queue, message consumed queue, and the messages processed for all replications sets through the Instance Data Replication (IDR) Queue Dashboard.
- Preventing insert and update errors in Instance Data Replication
You can prevent insert and update failures in Instance Data Replication (IDR) by specifying a class name filter in the producer replication set.