Preventing insert and update errors in Instance Data Replication
-
- UpdatedJan 30, 2025
- 2 minutes to read
- Yokohama
- 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.
When you replicate a parent table and one or more child tables, you must add a sys_class_name filter to the parent table in the outbound entry of your producer replication set. If the sys_class_name filter is missing, insert and update failures appear in
in the following scenarios:- A failed insert occurs when a record in the child table is replicated because the system attempts two inserts with the same sys_id to the parent table. Adding the sys_class_name filter to the parent prevents the unique key violation during the INSERT into the parent table.
- A new record is added to a replicated child table on the producer instance. Instance Data Replication (IDR) initially creates the record in the parent table on the consumer, but not the child table. If the child record is changed on the producer instance, during replication a failed update occurs on the child table in the consumer instance because the record only exists in the parent table.
If the table is a parent, decide if you want to replicate any of its child tables.
- If you want to replicate one or more child tables, you must identify the sys_class_name value
for the parent table, and then add a corresponding sys_class_name filter to the parent
table.
For example, Task Type is the label for sys_class_name on the Task [task] table. To start replicating the incidents in addition to tasks, you must add [Task Type] [is] [Task] to the outbound entry for the Task [task] table.
- If you only want to replicate the parent table, the filter is optional.
- If the parent table is already being replicated, you must edit the parent and add the sys_class_name filter.
If the table is a child, decide if you want to replicate its parent.
- If you want to replicate the parent table as well, you must identify the sys_class_name value
for the parent table, and then add a corresponding sys_class_name filter to the parent
table.
For example, Task Type is the label for sys_class_name on the Task [task] table. To start replicating tasks in addition to incidents, you must add [Task Type] [is] [Task] to the outbound entry for the Task [task] table.
- If you only want to replicate the child table, the filter is optional.
- If one or more child tables are already being replicated, you must add the sys_class_name filter to the parent.
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.
- Resolving data replication errors in Instance Data Replication
Resolve errors and monitor the status of Instance Data Replication (IDR) replication sets.