Skip to main content
Skip table of contents

Provisioning the Oracle 12C database

Procedure

Perform the following steps to provision Oracle 12c database VDB.

  1. Refresh the Target DB environment from Manage > Environments so that the Listener brought up during DBTechstack provision gets discovered and the Installation Home to be listed in dropdown during Database provision. If the Target DB environment is not refreshed, you will see `This environment has no compatible Oracle Installation Homes` in the Installation Home dropdown in the Database provision.

  2. Provision the EBS database to the target dbTier environment by following the steps outlined in Provisioning an Oracle VDB. Note: When Snapshot is running against the DBTechstack, database, or AppsTier, the Delphix Continuous Data Engine also executes pre-clone logic to ensure the latest configuration is staged in the captured snapshots. Unfortunately, if multiple Snapshots are running against the same EBS instance concurrently, this pre-clone logic may fail and produce bad snapshots.
    To avoid SnapSync conflicts, spread out your SnapSync policies for an EBS instance by one hour or more.

  3. Select the correct Installation Home.
    This should be the virtual DBTechstack you just added to the Delphix Continuous Data Engine.

  4. Select an Environment User.

  5. This user should be the oracle user-outlined in Preparing Target EBS R12.2 Environments for Provisioning.

  6. Select a Target Group for the VDB.

  7. In the VDB Configuration section, provide Target DB/CDB SID name provided during DBTechstack provisioning in the Oracle Database Name and Oracle SID field. Provide any unique user-defined name in VDB Name and Oracle Database Unique Name and click Next.

  8. Click Advanced.

  9. Select the correct Oracle Node Listeners value.
    This should be the listener corresponding to the virtual DBTechstack you just added to the Delphix Continuous Data Engine.

  10. Add the EBS R12.2 dbTier environment file as a Custom Environment Variables entry. 

  11. This file can be specified as an Environment File with Path Parameters of $ORACLE_HOME/<CONTEXT_NAME> .
    Replace <CONTEXT_NAME> with the virtual EBS instance's context name. The Delphix Continuous Data Engine will expand the $ORACLE_HOME variable at runtime.

    CODE
    . "${ORACLE_HOME}/${ORACLE_SID}_${HOSTNAME}.env";
    sqlplus -s "/ as sysdba" <<EOF
    alter system set SEC_CASE_SENSITIVE_LOGON=FALSE scope=both;
    EOF

    For more information, see Customizing Oracle VDB Environment Variables.

Note: To complete the DB Provisioning operation, you must provide content to configure clones and pre-snapshot hooks. You must either follow step 12 to use the hooks utility feature OR proceed with the conventional way by following steps 13-20.

  1. To complete the DB Provisioning operation, you must provide content to configure clones and pre-snapshot hooks. The following are the content for both the hooks:

    1. Configure Clone hook will be <DBTechstack Mount point>/hooksUtil/hooksRunner --operation configure . You can set a hooks environment variable DLPX_SOURCE_APPS_PASSWORD for providing the source apps schema password.

    2. Pre-Snapshot hook : <DBTechstack Mount point>/hooksUtil/hooksRunner --operation pre-snapshot . You can set a hooks environment variable DLPX_SOURCE_APPS_PASSWORD for providing the source apps schema password. In case of apps password change in target VDB, you can set hook environment variables DLPX_TARGET_APPS_PASSWORD for providing the target apps schema password.

Note: It is mandatory to set a hooks environment variable DLPX_SOURCE_APPS_PASSWORD for providing the source apps schema password.  In case the apps password change is required in target VDB, you can set hook environment variables DLPX_TARGET_APPS_PASSWORD for providing the target apps schema password in respective hooks. The variables will be declared in the Credential Environment Variables hook section.

The hooks environment variable will be declared as, DLPX_SOURCE_APPS_PASSWORD and then its password value will be the same variable used in hooks, along with the PASSWORD keyword appended at the end so that it will be like DLPX_SOURCE_APPS_PASSWORD_PASSWORD
We assign the value of $DLPX_SOURCE_APPS_PASSWRD to APPS_PASSWD.
In hooks, it is written as:

CODE
APPS_PASSWD=$DLPX_SOURCE_APPS_PASSWORD_PASSWORD

For more information, refer to the Oracle EBS Database Hooks in OCI ExaCC or ExaCS page.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.