Before adding data preservers or exclude records on the source instance, please review this checklist that summarizes the preflight checks that are performed by the system and that can prevent a clone from completing.
E.G., this clone was canceled because a database view was added to the list of data preservers:
Release or Environment
London, Madrid, New York
Before adding data preservers or exclude records on the source instance, please review this checklist that summarizes the preflight checks that are performed by the system, and that can prevent a clone from completing.
Don't create a data preserver on this table
|sys_counter_number||duplicate numbers would result|
|sys_attachment||the large table size in the target can cause a failure|
|any database view||
A database view is a virtual table that is built in real time when the table is displayed. The records don't exist in the system as a physical table.
In addition, these are rare database configuration issues that can prevent a clone from succeeding:
A table name that is in upper case must first be changed to lower case.
A schema mismatch error can occur if the COLUMN_TYPE of a table has been changed on the source or target instance within a few days of the clone, e.g., from "varchar(40)" to "mediumtext".
Please see this link for 'exclude table' constraints, which explains that the clone will fail during the clone Preflight check if the sys_user or sys_user_has_role tables are added to the clone exclude list. If the sys_properties table is added to the clone exclude list, the clone will complete but the target instance's configuration and UI properties will be incorrect.
Before adding a data preserver or exclude table, review the checklist above to ensure that the preflight checks will run smoothly and your clone will complete.