CLI cookbook: export a non-multitenant virtual Oracle database to ASM

This topic describes how to perform an export or an in-place conversion of a non-multitenant virtual database to a physical database using the Delphix Engine command-line interface. This procedure will work irrespective of the VDB being a single instance configuration or RAC.

Prerequisites

You must have the following configuration before you start the export:

Target ASM data diskgroup, or the diskgroup that will contain all the database files
The VDB that needs to be exported to ASM.
Optionally, the target ASM disk group for redo log files, database unique name for the resulting physical database and the number of RMAN channels.

Ensure that a database instance with the same unique name as the VDB is not running on the target host before starting the below procedure, otherwise the export operation will fail.

Procedure

Execute the database export command.
CODE
```
delphix> database export
```

Set the database export parameters type, transfer strategy type, storage strategy type, default target data diskgroup, and virtual source.

BASH

delphix database export *> set type=OracleDBExportParameters
delphix database export *> set storageStrategy.type=OracleExportASMStorageStrategy
delphix database export *> set storageStrategy.asmLayout.defaultDataDiskgroup=+DATA
delphix database export *> set transferStrategy.type=OracleExportDBInPlaceTransferStrategy
delphix database export *> set transferStrategy.virtualSource=v2p_db

Info: The above values are just examples. Replace the default data diskgroup and virtual source name to match your needs.

Optionally set the following parameters:
1. Target ASM disk group for redo log files.
2. Database unique name for the resulting physical database.
  1. If no database unique name is specified, the default is the unique name of the VDB.
  2. If a database unique name is specified, as noted in step 2 of this procedure, you need to ensure that a database instance with the same database unique name as the VDB is not running on the target host.
3. Number of RMAN channels. Default value for the RMAN channels is 8.
4. RMAN file section size. Default value is 0 (i.e. RMAN file section size is not set).
  CODE
```
delphix database export *> set storageStrategy.asmLayout.redoDiskgroup=+REDO
delphix database export *> set transferStrategy.dbUniqueName=v2asm_db
delphix database export *> set transferStrategy.rmanChannels=10
delphix database export *> set transferStrategy.rmanFileSectionSizeInGb=64
```

Info: The above values are just examples. Replace the redo diskgroup, database unique name, 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 the section titled "Performance tuning considerations for Oracle databases with bigfile tablespaces" on the Export an Oracle VDB or a vPDB to a Physical ASM or Exadata Database page.

Commit the configuration to execute the job.

CODE

delphix database export *> commit

The export operation takes a snapshot of the VDB before proceeding with the export. After a successful export operation, the original VDB will be left in a DISABLED state. If the VDB needs to be re-enabled, the VDB needs to be migrated to a different host. Ensure there is no instance running with the same name as the VDB on the target host. Subsequently, you must rewind the VDB to the latest snapshot, after which the VDB will be back up and running. Since the export operation takes a snapshot before the actual export, the rewind can be performed to the point just before the export started.

Refer to the Export an Oracle VDB or a vPDB to a Physical ASM or Exadata Database page for additional considerations after a successful export.