Tables that should not be added to the Clone exclude list - Support and Troubleshooting

Tables that should not be added to the Clone exclude list Issue Description When configuring a clone on the source instance, if any of the following tables are added on the clone exclude list and not preserved, the table will not be excluded on the target :

sys_user sys_db_object sys_dictionary sys_user_has_role sys_user_role sys_user_group sys_user_grmember sys_group_has_role sys_user_role_contains sys_group_has_skill sys_user_group_type sys_user_group_visibility customer_contact

This is due to the property "cid.clone.cannot.be.empty.tables.after.clone" which has a list of critical tables that should not be excluded. This property contains a list of tables that, if they are excluded, must also be preserved to avoid complications to the target instance. For example if you excluded sys_db_object and didn't preserve it, you would have no table records on the target instance.

Steps to Reproduce 1) Logon to your source instance. 2) Add any of the tables mentioned above on the clone exclude list.

3) Schedule your clone.

NOTE: The clone will complete but the table will not be excluded.

Resolution 1). Check if any of the tables from the below list is excluded but NOT preserved. sys_user sys_db_object sys_dictionary sys_user_has_role sys_user_role sys_user_group sys_user_grmember sys_group_has_role sys_user_role_contains sys_group_has_skill sys_user_group_type sys_user_group_visibility customer_contact 2) Add any missing tables to the preserver list.

Related Links Refer to KB0870989 for related information.