Exclude a table to create an empty but usable table on the target
instance.
The module lists the tables that are not copied during a system clone. By
default, the system excludes tables for logging, auditing, notifications, workflow
contexts, and license usage.
Note: Excluded workflow context data includes records stored in the wf_context
table, and in related tables with names starting with a prefix of wf_. This also
includes the workflow scheduler table. This prevents occurrence of workflow
timer syncing issues that might take place due to the length of the cloning
process if workflow contexts were included.
The system cannot exclude tables that extend the Task table and are also flattened
into it as part of the table per
hierarchy extension model. Since these extended tables are actually part
of the same physical database table, the system clones the data when it clones the
Task table. You can exclude tables that extend the Task table under two conditions.
Either the system stores the tables in their own physical tables as part of the
table per class extension model, or you exclude the Task table itself.
You can use wildcards to exclude several tables from cloning with one entry. For
example, sys_script.* excludes all tables starting with sys_script.
Note: The
wildcard has to include the dot '.' before the asterisk.
To preserve the existing data on the target instance, see Create a data preserver. Data on tables that reference the table,
such as business rules, is not excluded.
