Skip to main content
Delphix

KBA1635 How to Resolve: "Error: Cannot Provision From Snapshot Taken at 'TIME'"

Issue

When using a dSource which is an Oracle Standby host, you may receive one of the following faults:

5.1 and later:

Title: Cannot provision database from snapshot

Description: Snapshot "2017-12-18T19:39:57.396Z" of database "XXX" cannot be provisioned. The source database is in Real Time Apply mode and redo from the current online log on the primary may be needed in order to provision from the snapshot.

Action: Force a log switch on the primary or wait for the log to be archived and LogSync to fetch the log from the source. The CLI TimeFlow Log List command can be used to see which logs LogSync has fetched and which are missing.

Or in earlier releases:

Title: Cannot provision database from snapshot

Description: Snapshot "2015-07-16T22:16:20.923Z" of database "XXX" cannot be provisioned. The source database is in Real Time Apply mode and redo from the current online log on the primary may be needed in order to provision from the snapshot.

Action: Force a log switch on the primary or wait for the log to be archived and LogSync to fetch the log from the source. The CLI TimeFlow Log List command can be used to see which logs LogSync has fetched and which are missing.

And prior to 4.2:

Description: Cannot provision database ”XXX" from snapshot taken at "2015-03-07T04:14:12.340Z". SnapSync continued even though you cannot provision from the snapshot. If the source database ”XXX" is a standby database in Real Time Apply mode, then redo from the current online log on the primary may be needed in order to provision from the snapshot. SnapSync continued in order to make progress on the snaps.

Resolution

This fault is raised when a snapshot has been taken from an Oracle Standby database, but one of the archive logs needed to recover it has not yet been made available to the Oracle Standby host, for collection by the Delphix Engine.

As noted in the fault description in later versions, there are two ways to resolve this fault:

  • Wait for the Primary database to perform a log switch; or
  • Force a log switch on the Primary database

Once the archive log is copied to the Standby database, it will be made available to the Delphix Engine for collection, and the fault should resolve itself automatically.

Please note that versions of the Delphix Engine prior to 4.2 may also raise this fault for non-standby databases, or for standby databases that are not in Real Time Apply mode.

If this issue persists even once the archive log is available, consider using Timeflow Patching to manually locate and apply the missing log files.