Provision the Oracle 19c database in DCT

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

1. As prerequisites, first and then refresh the Target DB environment from Home > Infrastructure Connection. Select the DBTechStack environment. This ensures the DBTechStack’s Listener is discovered for the Oracle database provisioning. 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 wizard.

2. During the Provision vPDB wizard,select the correct Installation Home.
   This should be the virtual DBTechstack you just added to the Delphix Continuous Data Engine.

3. Select an Environment User. This user should be an Oracle environment user.

4. For the Container Database option, select the checkbox next to Create a New Container Database, and click Next.

5. Select a Target Group for the VDB.

6. In the vPDB Configuration section, enter the Target PDB name given during DBTechstack provision in the Oracle Pluggable Database Name field and provide any unique user-defined name in vPDB Name to be displayed in the Delphix Continuous Data Engine.

7. In vCDB CONFIGURATION section, enter the Target DB/CDB SID name given during DBTechstack provision in the Database Name field and SID and provide identical name in the vCDB Name and Database Unique Name field, and click Next.

   As a best practice, provide the same value in the Database Name field, vCDB Name, Database Unique Name field, and SID unless any environment specific custom requirement.

8. Click Next.

9. Click Advanced. Select the respective vCDB Listeners value.

10. This should be the listener corresponding to the virtual DBTechstack you just added to the Delphix Continuous Data Engine. Oracle EBS Data connector starts a listener with CDB name.

11. (Optional) Add the EBS R12.2 dbTier environment file as a Custom Environment Variables entry.
    This file can be specified as an Environment File with Path Parameters of $ORACLE_HOME/<CONTEXT_NAME>.env.

12. Replace <CONTEXT_NAME> with the virtual EBS instance's context name. The Delphix Continuous Data Engine will expand the $ORACLE_HOME variable at runtime.

13. To complete the DB Provisioning operation, it is mandatory to provide content to configure clone and pre-snapshot hooks.

14. 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:

    • Use the Configure hook ${ORACLE_BASE}/hooksUtil/hooksRunner --operation configure.

    • You must set a hooks environment variable DLPX_SOURCE_APPS_PASSWORD for providing the source apps schema password, DLPX_SYS_PASSWORD for the source SYSTEM schema password, and SOURCE_PDB_NAME for the source PDB name.

    • If source database is AD-TXK Delta 13 or later then supply source EBS_SYSTEM schema’s password to variable DLPX_SYS_PASSWORD. EBS_SYSTEM or SYSTEM password is needed for supplemental utl_file_dir(Doc ID 2525754.1).

    • If the SOURCE_PDB_NAME variable is not declared then source services will be carried over to the target vPDB tenant else source services like ebs_<SOURCE_PDB_NAME> & <SOURCE_PDB_NAME>_ebs_patch will be deleted in target vPDB.

    • Use the Pre-Snapshot hook: ${ORACLE_BASE}/hooksUtil/hooksRunner --operation pre-snapshot.

    • You must set a hooks environment variable DLPX_SOURCE_APPS_PASSWORD for providing the source apps schema password.

    • In case an apps password change is required in the target VDB, you can set hook environment variables DLPX_TARGET_APPS_PASSWORD for providing the target apps schema.

    • For versions 19.3 or later, follow the below guidelines if you see any of the following errors:

      • ORA-01017: Invalid username/password logon denied.

      • ORA-28040 During cloning: No Matching Authentication Protocol..

    • For troubleshooting hooksUtil failure, check the hooks.log file to verify the configure clone and pre snapshot hook logs, which is available here:

      • <Toolkit_directory>/Delphix_COMMON*host/data connector/ebs122-vsdk-db_9f7f5a63-1da7-495c-80df-e0fa61941342/logs/hook_logs.

    • Occasionally, it is necessary to restart the database to resolve connectivity to the database. This is atypical but may be necessary in certain cases.

    • On the target container database, run the following command:

      • alter system set SEC_CASE_SENSITIVE_LOGON=FALSE scope=both;

    • The above ALTER command should run as a first configure clone hook.

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

15. To take advantage of the password protections introduced in Oracle Database 19c, users must change their passwords.

16. Add a Run Bash Shell Command operation to the Configure Clone hook to ensure that adcfgclone utility is run against the newly provisioned database for a high privileged user, as shown in the script below.

17. You can pass the credentials securely to Hook Operations by setting up the base variables.

18. 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 the target VDB, you can set hook environment variables DLPX_TARGET_APPS_PASSWORD and DLPX_SYS_PASSWORD for providing the target apps schema and system schema passwords in respective hooks. The variables will be declared in the Credential Environment Variables hook section. You can pass the credentials securely to Hook Operations by setting up the base variables. For more information, see Oracle EBS Database Hooks in OCI ExaCC or ExaCS.