Linking an Oracle non multi tenant staging push dSource

You can perform the following steps to link a Non Multi Tenant dSource using the staging push mechanism.

Login to the Delphix management application.
Go to Manage > Datasets.
Click the plus (+) icon and select Add dSource.
On the Preparation tab, click Next.
From the dSource type tab, select the Oracle staging push as dSource type and click Next.
On the dSource configuration step, provide the following dSource configurations:
1. dSource name - This name will be shown on the Delphix Engine interface.
2. Target group - Select a target group from the drop-down list.
3. Database type - Select the database type as Non Multi Tenant.
4. Staging environment - Select an environment from the drop-down list. The staging database will be hosted in this environment.
5. User - Select an environment user from the drop-down list.
6. Repository - Select a repository (Oracle installation) from the drop-down list.
7. Database name: Provide the Database Name for the staging dSource.
  Info : Consider the following while providing the database name:
  - This is the name of the staging database that is created on the staging host after linking.
  - The Database Name should be the same as the source database’s database name. The source database is the database whose data will be populated on this staging database.
  - Database Name is case-sensitive.
  - You can run either of the two queries on the source database to get the database name:
    - show parameter db_name;
    - select name from v$database;
8. Database unique name - Provide a database unique name for the staging database. It can be different from the database unique name of the source database.
9. SID - Provide the SID for the staging database.
10. Mount base - Provide a mount path. This is the location on the staging host at which the Delphix Engine will mount its storage for the staging database. To know about the permissions that the mount path directory must-have, see the Additional Target/Staging Host Requirements section of this article.
11. Custom environment variables - Configure the custom environment variables, similar to VDBs, if needed.
12. Optionally, you can configure Auto staging push restart, Configure staging database parameters, Physical standby, and Validate snapshot by Opening database in read only mode, as per requirement.
  1. Auto staging push restart indicates whether this staging database should be automatically restarted when the staging host reboot is detected.
  2. Configure staging database parameters to override Oracle database configuration parameters.
  3. Physical standby indicates that the staging database will be configured as a physical standby.
    Info : The staging database is not configured as a Physical Standby by Delphix Engine. The setup should be done outside Delphix Engine before initiating the Snapshot operation.
  4. Validate Snapshot by Opening Database in Read Only Mode indicates whether the staging database snapshots will be validated by opening the database in read-only mode. Info : All these options are disabled by default.
13. Click Next.
From the Staging database parameters tab, select a template and click Next.
From the Policies tab, select any policy for the new dSource. SnapSync Policy is used as a default policy for taking snapshots. For more information on SnapSync policy, see Policies for Scheduled Jobs Click Next.
From the Hooks tab, enter any script that should be run before (pre-sync) or after (post-sync) the snapshot operation.
From the Summary tab, review the staging Push dSource configuration profile and click Submit. When all the above steps are executed on the staging host, a new database is instantiated with the above provided Database Name, Database Unique Name, and SID, and the database files are expected to be placed at the location: MOUNT_BASE/<Database_Unique_Name>/datafile. Once linking is done, you can see this Staging Push dSource under the Datasets.