Excluded tables in Instance Data Replication
-
- UpdatedJan 30, 2025
- 1 minute read
- Yokohama
- Instance Data Replication
You can't replicate certain tables in Instance Data Replication (IDR). Child tables of tables in the exclusion list are also excluded.
Excluded tables
These tables are excluded from IDR:- Tables with the prefixes V_PREFIX, SYSX_, sys, ts_, ua_, usageanalytics_, wf_, ecc_,
clone_, jrobin_, rrd_, imp_, pf_, pfd_, idr_
sys_domain is an exception.
- Rotated tables, including syslog, sys_querystat, ecc_queue, ecc_event, cmdb_metric, sysevent
- Tables without a sys_id
- sso_federation
- saml2_update1_properties
- sso_properties
- digest_properties
- Instance
Child tables that extend these tables are also excluded from IDR and should not be included in replication sets because replication fails if they are included. For example, sc_cat_item extends sys_metadata, which is an excluded table. This makes sc_cat_item an excluded table due to inheritance.
Tables to avoid replicating:
- cmdb
- cmdb_ci
If you determine the CMDB tables must be replicated, you must use conditions to constrain the count of replicated records and ensure all required columns are included in the replication set.
On this page
Related Content
- Data privacy in Instance Data Replication
The ability of replication sets to host multiple remote consumers in Instance Data Replication (IDR) means that there are potential data privacy issues to consider.
- Adapter descriptions for Instance Data Replication
Adapters modify the producer data before inserting the data on consumer instances in Instance Data Replication (IDR).
- Domain separation and IDR
Instance Data Replication (IDR) functions at the data level, which means it does not explicitly support domain separation.
- Instance Data Replication properties
These system properties control the behavior of the Instance Data Replication (IDR) application.
- Instance Data Replication roles
Instance Data Replication (IDR) is installed with these roles.