If a Provision or Refresh operation has failed with the following error:
ERROR at line 1: ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1:
It is a strong indication that the snapshot required for the operation is inconsistent.
The purpose of this Knowledge Base Article (KBA) is not to root cause why there may be corruption. There are simply to many variables to cover all possibilities in a single KBA.
The purpose of this KBA is to help the customer take steps to accomplish successful completion of a Provision/Refresh operation.
In the case of an Oracle dSource, the initial Snapsync and snapshot captures a level 0 (full) RMAN backup of the source database inclusive of archive logs.
Subsequent Snapsync operations take incremental backups of the source database capturing only those Oracle data blocks which have changed since the previous Snapsync.
In general, Delphix recommends enabling Block Change Tracking (BCT) on a primary or standby source database.
BCT improves the performance of incremental backups by recording changed blocks in the block change tracking file.
During an incremental backup, instead of scanning all data blocks to identify which blocks have changed, RMAN uses this file to identify the changed blocks that need to be backed up.
This can greatly reduce the length of time it takes to complete an incremental backup.
In a situation where there has been an issue during one of the above processes (leaving an inconsistent copy of the data on the Delphix Engine), the corruption will propagate forward resulting in all subsequent snapshots being un-provisionable.
Applicable Delphix Versions
- Click here to view the versions of the Delphix engine to which this article applies
Major Release All Sub Releases 6.0 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11
18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199
To resolve this issue the customer should take a Full Backup (RMAN level 0) of the Source and Refresh/Provision from the new snapshot.
By default, the Delphix Engine will take an incremental backup, you will need to update the snapshot parameters to force a full backup.
This can be done by an admin account from the CLI as follows:
delphix > database delphix database > select <dSource> delphix database "dSource" > sync delphix database "dSource" sync * > set forceFullBackup=true delphix database "dSource" sync * > commit
It can also be done from the Delphix UI as follows:
You may want to consider using the Double Sync option for Oracle SnapSync. For more information, see Using the Double Sync option for Oracle SnapSync.