VDB provisioning wizard

Users can provision VDBs from the DCT UI using the Provision VDB button located under the action button on a VDB details page.

Supported database platforms

• Oracle Multi Instance (Single Tenant)

• Oracle Multi Instance (Multi Tenant) with linked vCDB

  • TDE is supported for Oracle versions greater than or equal to 12.2.

  • Only vCDBs with database versions greater than or equal to 12.1.0.2 can be linked.

  • Auto VDB restart is supported for Oracle versions greater than or equal to 12.1.0.2.

• Oracle Single Instance (Multi Tenant) with linked vCDB

  • TDE is supported for Oracle versions greater than or equal to 12.2.

  • Only vCDBs with database versions greater than or equal to 12.1.0.2 can be linked.

  • Auto VDB restart is supported for Oracle versions greater than or equal to 12.1.0.2.

• MSSQL Multi Instance

  • Drive letters are not supported and are set to default values.

• SAP ASE

• AppData

  • AppData is used for connecting with other databases like Postgres, SAP HANA, etc. by uploading the plugin. Refer to the Provisioning a PostgreSQL VDB page for more details.

• vFiles

  • Refer to the Unstructured files and app data page for more details.

Extending the developer experience capabilities in DCT, users can now provision MSSQL single instance databases or Oracle single instance multi-tenant databases with linked CDB data platforms from the user interface, using an intuitive wizard workflow. Located on the VDB page is a Provision VDB button that opens the provisioning wizard. (Note: non admin users will only be able to see provisionable sources (dSources and/or VDBs), environments, and engines to which they are authorized to see and act upon).

Step examples

The provisioning wizard will walk through the following steps:

• Source: search and select either a dSource or VDB to provision from.
  

  

• Provision Point: three options for a provision point, similar to a refresh point.

  • A selected snapshot

  • A specific timestamp (closest snapshot to the timestamp)

  • A location ID/number (closest snapshot to the location number)

• Target Environment: shows compatible environments with compatible repositories, and can optionally provide privileged credentials.

• Target Configuration: should be prefilled with default configurations. One thing to note here are the tags which are additive when “Include Tags from Parent” is checked, and you wouldn’t immediately see the tags from the parent in the editor. Tags are added when the Include Tags from Parent box is checked, you would not immediately see them from the parent in the editor.

  • Users can also select the engine group and register listeners by expanding the advanced section below. In DCT, it is recommended to use tags instead of engine groups.

  • The Target Configuration screen will present different options depending on the chosen Source.

• vCDB Configure Parameters: Applicable to Oracle Single Instance (Multi Tenant) with linked vCDB.

• Policies: choose a snapshot policy.

• Masking:

• Hooks: Delphix users now have the ability to add custom hooks to a VDB at the time of provision (as part of the provision wizard UI) and update them under a VDB detail page, so that they will execute during refresh operations. A Hooks section in the Summary page shows a list of all the hooks configured (if any). Hooks can be modified in the details page after creation.

• Summary: review the selections that have been made. In 10.0 and above, a hooks header has been added to the Summary page that shows a list of all the hooks configured for Hook Operations while provisioning a VDB (if this was configured).

Limitations

TDE and Auto VDB restart are only supported for Oracle version 12.2 or higher.