Clone results based on Exclusion and Preserver configuration - Support and Troubleshooting

Clone results based on Exclusion and Preserver configuration Description Clones will read exclude/preserver lists from the source instance during the early stage of the clone. If updates are made to the exclusion/preserver list before clone, the clone will honor it even if the clone does not take on-demand backup.

This article explains through six different scenarios the expected results of the data in a table based on the configuration of the Table Exclusion and Data Preserver when performing a clone.

Release or Environment All

Resolution Test parameters used:

source = clone source (ex. production instance) target = clone target (ex. test instance) sys_temp = custom table we will be preserving and excluding data Data Preservers are always setup on source under System Clone > Preserver Data Table Exclusions are always setup on source under System Clone > Exclude Data Default clone settings used as per screenshot: IMPORTANT: If 'Exclude audit and log data' is not checked, the list of table exclusions under 'Exclude Data' is ignored! (see KB0751430 )

Scenario #1 Table Exclusion: None Data Preserver: None Table Exclusion on source

Data Preserver on source

Results #1 All records in sys_temp table on target are deleted. All records in sys_temp table on source are copied to sys_temp table on target . Data on source

Data on target before clone

Data on target after clone

Scenario #2 Table Exclusion: None Data Preserver: Yes, plus 'Conditions' field is empty. Table Exclusion on source

Data Preserver on source

Results #2: All records in sys_temp table on target are preserved. Records in sys_temp table on source , which do not exist in sys_temp table on target (based on sys_id), are copied to sys_temp table on target . Data on source

Data on target before clone

Data on target after clone

Scenario #3 Table Exclusion: None Data Preserver: Yes, plus 'Conditions' field contains a value. Table Exclusion on source

Data Preserver on source

Results #3 Records in sys_temp table on target , found by Data Preserver, are preserved. Records in sys_temp table on target , not found by Data Preserver, are deleted. Records in sys_temp table on source , which do not exist in sys_temp table on target (based on sys_id), are copied to sys_temp table on target . Data on source

Data on target before clone

Data on target after clone

Scenario #4 Table Exclusion: Yes Data Preserver: Yes, plus 'Conditions' field is empty. Table Exclusion on source

Data Preserver on source

Results #4: All records in sys_temp table on target are preserved. No records are copied over from sys_temp table on source . Data on source

Data on target before clone

Data on target after clone

Scenario #5 Table Exclusion: Yes Data Preserver: Yes, plus 'Conditions' field contains a value. Table Exclusion on source

Data Preserver on source

Results #5 Records in sys_temp table on target , found by Data Preserver, are preserved. Records in sys_temp table on target , not found by Data Preserver, are deleted. No records are copied over from sys_temp table on source . Data on source

Data on target before clone

Data on target after clone

Scenario #6 Table Exclusion: Yes Data Preserver: None Table Exclusion on source

Data Preserver on source

Results #6 All records are deleted from sys_temp table on target . No records are copied over from sys_temp table on source .

Data on source

Data on target before clone

Data on target after clone

Additional Information Related knowledge base articles on cloning, excluding a table, and data preservers:

System clone

Exclude a table from cloning

Data preservation on cloning target instances

Exclude Option Checkboxes not Being Honored with Clone Request