Launch the wizard in one of the following ways:

  • From your new source config entry, click + dSource.

  • Open Data Management > dSources and click + dSource.

Steps

  1. Select the data source. On the Select Data Source page, select the available Oracle EBS source configuration from the list (for example, SRC-DBTIER-TX with platform ebs122-vsdk-db).

  2. Enter the EBS-specific parameters for your DBTechstack.

  3. These parameter values will be used when adpreclone.pl utility runs. Ensure that the DB Tier Context Name uses the short hostname.

  4. Select an Environment user.

  5. Privileged OS Account (Optional) field should contain a high privileged user when the low privileged user is being used for linking. To use Privileged OS Account, sudoers entry must be defined on source side.

  6. Enter the source Oracle home directory name’s relative path to oracle base installation directory in the Oracle Home field.

  7. In the DB Tier Context Name field, enter the source context name. To get the DB Tier context name on source side:

    • For Oracle 12.1.0.2 version:
      cd $ORACLE_HOME

    • source SID_hostname.env file
      echo $CONTEXT_NAME

    • For example. Consider VISDB as the database SID and tavsrc-db as the short hostname.
      [oravis@tavsrc-db VIS]$ source /u01/oracle/VIS/12.1.0.2/VISDB_tavsrc-db.env
      [oravis@tavsrc-db VIS]$ echo $CONTEXT_NAME
      VISDB_tavsrc-db

    • For multi-tenant database, CONTEXT_NAME is (<PDB_NAME>_<short hostname>)
      For RAC, CONTEXT_NAME will be <INSTANCE_SID>_<HOSTNAME>
      For example: VIS2_exaukdb02

When preparing the source Oracle RAC system for cloning, make sure that the linking is performed against the primary database node.

  1. Provide apps schema password in the Apps Password Credentials section by selecting the Username and Password from the dropdown, leaving the username field empty.

  2. Exclude the EBS database's data files if they are stored underneath the Oracle base install directory.

  3. These data files will be linked with the database instead of with the DBTechstack. Add the "relative path" to the data files to the Paths to Exclude list. If the audit files (located under $ORACLE_HOME/rdbms/audit) are large in size, the path of these files could also be excluded so as to avoid DBTechstack timeout issues during provisioning.

Ensure that you add the relative paths and NOT the absolute paths. For example, if you want to exclude the /u01/oracle/VIS/data path, then add "data" only under the Paths to Exclude list. Here, /u01/oracle/VIS/data is the absolute path and "data" is the relative path to be added.

  1. Enter a dSource Name.

  2. Select a Database Group for the dSource.

  3. Click Next. Adding a dSource to a database group enables you to set Delphix Domain user permissions for that dSource's objects, such as snapshots.

  4. Select a SnapSync policy.

  5. Click Next.

  6. Enter any custom pre or post sync logic as Pre-Sync or Post-Sync hook operations. Remember that adpreclone.pl dbTechStack is already run prior to every Snapshot of the DBTechstack. The Pre-Sync hook operations will be run prior to running the adpreclone.pl tool.

  7. Click Next.

  8. Review the dSource Configuration and Data Management information, and then click Submit. The DCT will initiate a job to create the dSource. You can monitor these jobs by clicking Admin > Operations.
Last updated
Oct 9, 2026