This topic describes how to clean up the Incremental V2P configuration associated with an in-progress Incremental V2P or Finalize Incremental V2P operation. This operation is useful in situations where the user would like to:
-
abort an in-progress Incremental V2P or Finalize Incremental V2P operation, or
-
clean up an in-progress Incremental V2P or Finalize Incremental V2P operation in exceptional situation where it has run into irrecoverable error in order to reattempt the operation against the same source virtual database.
The V2P Cleanup operation deletes any temporary virtual database provisioned on the target host (if API parameter cleanupTargetContainer is set to true) and removes the configuration associated with the operation.
- Currently, V2P Cleanup operation is only supported for Incremental V2P configuration for Oracle datasets
-
Cleanup of datafiles exported to the ASM/Physical filesystem on the target host is not supported through V2P Cleanup operation and must be cleaned up either by using target storage specific commands or OS commands.
-
Refer to CLI cookbook: Cleaning up the Incremental V2P configuration for a VDB or a vPDB for the procedure to invoke.