This topic describes how to perform the following V2P operations to physical database stored on an Oracle Automatic Storage Management (ASM) diskgroup or a physical filesystem using the Delphix Engine command-line interface.

  • The V2P operation from a snapshot or a Timeflow point belonging to a non-multitenant Oracle database.

  • Incremental V2P operation of a non-multitenant Oracle virtual database (VDB).

The V2P operation provisions a temporary VDB from the snapshot or Timeflow point as specified in the CLI parameters and then performs an in-place conversion of the temporary VDB to a physical database in an ASM diskgroup or a physical filesystem. This temporary VDB is destroyed at the end of the V2P operation.

Prerequisites

You must specify the following parameters for the V2P operation:

  • For the V2P operation to ASM - the target ASM data diskgroup, or the diskgroup that will contain all the database files, or in case of the V2P operation to a physical filesystem – the directories that will contain oracle data files and log files.

  • The base mount point on the target server where temporary VDB data should be mounted.

  • Database name for the physical non-multitenant database.

  • Unique name for the physical non-multitenant database.

  • The target repository for the physical non-multitenant database. These can be listed with the /repository list command.

  • The instance name for the physical non-multitenant database.

  • The instance number for the physical non-multitenant database.

  • The snapshot or Timeflow point of an Oracle non-multitenant dSource or a VDB that needs to be exported to ASM or a physical filesystem. This will be referenced as the "container" in the Timeflow point parameters in step 6 below. You can run these commands to get the list of snapshots or Timeflow ranges:

    snapshot list database=dexample
    timeflow "dexample" timeflowRanges; commit
  • Optionally, in case of the V2P operation on ASM, the target ASM disk group for redo log files, number of RMAN channels and the RMAN file section size.

In the example CLI, the V2P operation detailed below, the following configuration parameters are being passed:

  • The snapshot that is being exported to ASM or a physical filesystem belongs to a non-multitenant database "dexample”.

  • The database name and instance name for the physical non-multitenant database are both "asmdb".

  • The database unique name for the physical non-multitenant database is "asmdb_uniq".

  • The instance number for the physical non-multitenant database, which is 1 in this example, being a single-instance database.

  • The target ASM data diskgroup is "+DATA" (in case of the V2P operation to ASM).

  • The dataDirectory is /v2p_db/data and the archiveDirectory is /v2p_db/archive (in case of the V2P operation to Physical Filesystem).

  • The base mount point on the target server is "/mnt/provision".

  • The target repository is "ora1914-asm-tgt/'/u01/app/oracle/product/19.14.0.0/dbhome_1'“

Procedure

  1. Execute the database export command.

    delphix> database export
  2. Set the database export parameters type, storage strategy type, ASM layout type and the target ASM data diskgroup, dataDirectory and archiveDirectory.

    For the V2P operation to ASM:

    delphix database export *> set type=OracleDBExportParameters
    delphix database export *> set storageStrategy.type=OracleExportASMStorageStrategy
    delphix database export *> set storageStrategy.asmLayout.type=OracleASMLayout
    delphix database export *> set storageStrategy.asmLayout.defaultDataDiskgroup=+DATA

    For the V2P operation to Physical Filesystem:

    delphix database export *> set type=OracleDBExportParameters  
    delphix database export *> set storageStrategy.type=OracleExportFilesystemStorageStrategy 
    delphix database export *> set storageStrategy.filesystemLayout.type=OracleFilesystemLayout  
    delphix database export *> set storageStrategy.filesystemLayout.dataDirectory=/v2p_db/data  
    delphix database export *> set storageStrategy.filesystemLayout.archiveDirectory=/v2p_db/archive 
  3. Set the transfer strategy type and base mount point.

    delphix database export *> set transferStrategy.type=OracleExportDBTimeflowPointTransferStrategy
    delphix database export *> set transferStrategy.mountBase=/mnt/provision
  4. For the Incremental V2P operation, set the finalization strategy type and optionally set incremental export parameters, which have the following preset defaults:
    delphix database export *> edit finalizationStrategy.incrementalExportParameters 
    delphix database export finalizationStrategy.incrementalExportParameters *> set backupFrequencyMinutes=30 
    delphix database export finalizationStrategy.incrementalExportParameters *> set rmanChannelsForIncrementalBackup=8 
    delphix database export finalizationStrategy.incrementalExportParameters *> set rmanFilesPerSetForIncrementalBackup=5 
    delphix database export finalizationStrategy.incrementalExportParameters *> set rmanFileSectionSizeInGbForIncrementalBackup=0 
    delphix database export finalizationStrategy.incrementalExportParameters *> back 
  5. Set the source config type to be a single instance non-multitenant Oracle, and set the database name, database unique name and target repository.

    delphix database export *> edit transferStrategy.sourceConfig
    delphix database export transferStrategy.sourceConfig *> set type=OracleSIConfig
    delphix database export transferStrategy.sourceConfig *> set databaseName=asmdb
    delphix database export transferStrategy.sourceConfig *> set uniqueName=asmdb_uniq
    delphix database export transferStrategy.sourceConfig *> set repository=ora1914-asm-tgt/'/u01/app/oracle/product/19.14.0.0/dbhome_1'
  6. Set the instance name and number. In case of a single-instance database, the instance number will be 1. The instance name that is specified will be the SID of the resulting physical database upon successful completion of the V2P operation.

    delphix database export transferStrategy.sourceConfig *> edit instance
    delphix database export transferStrategy.sourceConfig instance *> set instanceName=asmdb
    delphix database export transferStrategy.sourceConfig instance *> set instanceNumber=1
    delphix database export transferStrategy.sourceConfig instance *> back
    delphix database export transferStrategy.sourceConfig *> back
  7. Set the Timeflow point parameters. In the below example, the latest Timeflow point for the non-multitenant database is being specified for the V2P operation.

    delphix database export *> edit transferStrategy.timeflowPointParameters
    delphix database export transferStrategy.timeflowPointParameters *> set type=TimeflowPointSemantic
    delphix database export transferStrategy.timeflowPointParameters *> set container=dexample
    delphix database export transferStrategy.timeflowPointParameters *> set location=LATEST_POINT
    delphix database export transferStrategy.timeflowPointParameters *> back
    The parameter values in steps 2 to 7 above are just examples. Replace the appropriate parameter values to match your needs. In case of the V2P operation to a Physical Filesystem, both dataDirectory and archiveDirectory are required, both the delphix_os user and the Oracle software owner user (typically oracle) must have full access to the provided dataDirectory and archiveDirectory.
  8. Optionally set the following parameters:

    1. If exporting to ASM, the Target ASM diskgroup for redo log files.

    2. Number of RMAN channels. Default value for the RMAN channels is 8. 

    3. RMAN file section size. Default value is 0 (i.e. RMAN file section size is not set).

      delphix database export *> set storageStrategy.asmLayout.redoDiskgroup=+REDO
      delphix database export *> set transferStrategy.rmanChannels=10
      delphix database export *> set transferStrategy.rmanFileSectionSizeInGb=64
      The above values are just examples. Replace the redo diskgroup, number of RMAN channels and RMAN file section size to match your needs. For more details on RMAN channels and RMAN file section size, refer to Performance Tuning Considerations for Oracle Databases with Bigfile Tablespaces page.
  9. Check that all the settings you require are in place using the ls command.

    delphix database export *> ls
    Properties
        type: OracleDBExportParameters (*)
         finalizationStrategy: (unset)
        storageStrategy:
            type: OracleExportASMStorageStrategy (*)
            asmLayout:
                type: OracleASMLayout (*)
                defaultDataDiskgroup: +DATA (*)
                redoDiskgroup: (unset)
        transferStrategy:
            type: OracleExportDBTimeflowPointTransferStrategy (*)
            configParams: (unset)
            mountBase: /mnt/provision (*)
            rmanChannels: 8 (*)
            rmanFileSectionSizeInGb: 0 (*)
            sourceConfig:
                type: OracleSIConfig (*)
                databaseName: asmdb (*)
                environmentUser: (unset)
                instance:
                    type: OracleInstance (*)
                    instanceName: asmdb (*)
                    instanceNumber: 1 (*)
                linkingEnabled: true (*)
                nonSysCredentials: (unset)
                nonSysUser: (unset)
                repository: ora1914-asm-tgt/'/u01/app/oracle/product/19.14.0.0/dbhome_1' (*)
                services: (unset)
                tdeKeystorePassword: (unset)
                uniqueName: asmdb_uniq (*)
            timeflowPointParameters:
                type: TimeflowPointSemantic (*)
                container: dexample (*)
                location: LATEST_POINT (*)
    delphix database export *>

    or, for Incremental V2P:

    delphix database export *> ls 
    Properties 
        type: OracleDBExportParameters (*) 
        finalizationStrategy: 
            type: OracleExportIncrementalFinalizationStrategy (*) 
            incrementalExportParameters: 
                type: OracleIncrementalExportParameters (*) 
                backupFrequencyMinutes: 60 (*) 
                rmanChannelsForIncrementalBackup: 8 (*) 
                rmanFileSectionSizeInGbForIncrementalBackup: 0 (*) 
                rmanFilesPerSetForIncrementalBackup: 5 (*) 
        storageStrategy: 
            type: OracleExportASMStorageStrategy (*) 
            asmLayout: 
                type: OracleASMLayout (*) 
                defaultDataDiskgroup: +DATA (*) 
                redoDiskgroup: (unset) 
            ignoreInsufficientSpaceCheck: false (*) 
        transferStrategy: 
            type: OracleExportDBTimeflowPointTransferStrategy (*) 
            configParams: (unset) 
            invokeDatapatch: (unset) 
            mountBase: /mnt/provision (*) 
            rmanChannelsForExport: 8 (*) 
            rmanFileSectionSizeInGbForExport: 0 (*) 
            sourceConfig: 
                type: OracleSIConfig (*) 
                databaseName: DBOMSRAS (*) 
                environmentUser: (unset) 
                instance: 
                    type: OracleInstance (*) 
                    instanceName: NEWPHYSICAL (*) 
                    instanceNumber: 1 (*) 
                linkingEnabled: true (*) 
                nonSysCredentials: (unset) 
                nonSysUser: (unset) 
                repository: target_env/'/u01/app/oracle/product/19.14.0.0/dbhome_1' (*) 
                services: (unset) 
                tdeKeystoreConfigType: (unset) 
                tdeKeystoreLocation: (unset) 
                tdeKeystorePassword: (unset) 
                tdeKmsPkcs11ConfigPath: (unset) 
                uniqueName: DBOMSRAS333U (*) 
            timeflowPointParameters: 
                type: TimeflowPointSemantic (*) 
                container: VDBO_I0B (*) 
                location: LATEST_POINT (*) 
  10. Commit the operation in the CLI.

    delphix database export *> commit
        Dispatched job JOB-65
        DB_EXPORT job started for "dexample".
        Provisioning temporary virtual database "asmdb_uniq" from the chosen snapshot or point-in-time for performing V2P operation.
        Provisioning of temporary virtual database "asmdb_uniq" completed successfully.
        Starting V2P of database "asmdb" at "Untitled/dexample time: Wed Sep 20 14:00:13 PDT 2023" to location "+DATA" on target environment "ora1914-asm-tgt".
        Generating V2P scripts.
        Setting up environment map.
        Setting up database for V2P operation.
        Performing backup-as-copy for V2P operation.
        Performing switch-to-copy for V2P operation.
        Finalizing the V2P operation.
        Disabling virtual database "asmdb_uniq".
        Unexporting storage containers.
        Virtual database "asmdb_uniq" disabled.
        The V2P job for virtual source 'ORACLE_VIRTUAL_SOURCE-9' with name 'asmdb_uniq' got COMPLETED. Started cleanup for the same. Monitor job '<JOB-69>' and take suggested action if the cleanup fails.
    	DB_EXPORT job for "dexample" completed successfully.

    Or, for Incremental V2P:

    delphix database export *> commit  
        Dispatched job JOB-2140 
        DB_INCREMENTAL_EXPORT job started for "VDBO_I0B". 
        Provisioning temporary virtual database "NEWPHYSICAL" from the chosen snapshot or point-in-time for performing V2P operation. 
        Provisioning of temporary virtual database "NEWPHYSICAL" completed successfully. 
        Setting up source database "VDBO_I0B" for Incremental V2P. 
        Starting background workers for Incremental V2P of source database "VDBO_I0B". 
        Starting V2P of database "DBOMSRAS" at "Untitled/VDBO_I0B time: Tue Dec 16 00:53:31 PST 2025" to location "+DATA" on target environment "z1t". 
        Generating V2P scripts. 
        Setting up environment map. 
        Setting up database for V2P operation. 
        Performing backup-as-copy for V2P operation. 
        Performing switch-to-copy for V2P operation. 
        Finalizing the V2P operation. 
        The initial V2P job for virtual source "NEWPHYSICAL" finished with status "COMPLETED". 
        Incremental V2P operation is active for virtual source "VDBO_I0B" and required background workers are already running. Monitor the Incremental V2P status by querying the latest copy of the virtual source object "ORACLE_VIRTUAL_SOURCE-174". Also check any faults on the source database "VDBO_I0B" and take appropriate action before finalizing the V2P operation. 
        DB_INCREMENTAL_EXPORT job for "VDBO_I0B" completed successfully. 
Last updated
Oct 9, 2026