This topic outlines the prerequisites for provisioning a virtual EBS R12.1 instance to target environments.

Ensure your target EBS R12.1 instance is supported

See Virtual EBS R12.1 Instance Requirements to ensure that you can provision your EBS R12.1 instance.

Ensure your EBS 12.1 environments comply with Oracle's documentation

Your environments must comply with Oracle's requirements for installing EBS. These requirements are outlined on Oracle E-Business Suite Release 12 Installation Guidelines (Doc ID 405565.1) found at http://docs.oracle.com.

E-Business Suite Pre-Install RPM

Oracle has released an E-Business Suite Pre-Install RPM (available on ULN and public yum) that includes all required rpms for both the application and database tiers of an R12 installation - Details can be found in  (Doc ID 405565.1 for 12.0 and 761566.1 for 12.1) found at http://docs.oracle.com. 

Prepare the dbTier for provisioning

Delphix Engine's Unix Environment Requirements

The dbTier must meet the target requirements outlined in Requirements for Unix Environments. These requirements are generic to all target Unix environments added to the Delphix Engine.

oracle User

The Delphix Engine must have access to an oracle user on the dbTier.

  • This user should be a member of both the EBS dba and oinstall groups.
  • This user will be given proper permissions to manage the dbTechStack and database.

oraInst.loc

An oraInst.loc file must exist on the dbTier prior to provisioning. This file will specify where the oraInventory directories live or where they should be created if they do not already exist.

The oraInst.loc file is typically located at /etc/oraInst.loc on Linux or /var/opt/oracle/oraInst.loc on Solaris. Ensure that the oraInventory to which this file points to is writeable by the oracle user.

Consult Oracle EBS documentation for more information about where to place this file on your dbTier and what this file should contain.

Delphix Engine's Oracle Database Requirements

The dbTier must meet the target requirements outlined in Oracle Support and Requirements. These requirements are generic to all target Unix environments expected to host a virtual Oracle database.

Prepare the appsTier for Provisioning

There are two ways to access the Oracle EBS appsTier for linking a Delphix dSource:

  1. The simple approach of logging in directly to the OS account which owns the Oracle EBS appsTier (a.k.a. "applmgr")
  2. The secure approach of logging in using a non-privileged OS account and running "applmgr" privileged commands using elevation

Using the simple approach

This method involves linking to the EBS appsTier host using the existing OS account typically named "applmgr" which owns the Oracle EBS appsTier.  No additional modification is necessary for this account, other than choosing to use SSH password authentication or SSH public-key authentication from the Delphix virtualization engine.

Using the secure approach

This method involves linking to the EBS appsTier host using a new non-privileged OS account, typically named "delphix_os".  This account by itself does not have any special privileges, but it expects to use a privilege elevation mechanisms (default is "sudo") to run privileged commands as the OS account which owns the Oracle EBS appsTier, typically named "applmgr".

 Delphix Engine's Unix Environment Requirements

The appsTier must meet the source requirements outlined in Requirements for Unix Environments. These requirements are generic to all source Unix environments added to the Delphix Engine.

delphix_os OS user account

In order to separate authentication and perform privileged operations with a non-privileged OS account, first, create an OS user account (i.e. "delphix_os") on the EBS appsTier node to be used as a source.
This user is easily created by the createDelphixOSUser.sh script.

  • The primary OS group of the Delphix Engine software owner account's (i.e. delphix_os) should be the same as the EBS AppsTier software owner account (i.e. applmgr).
  • Primary group = OSDBA Group (typically dba), secondary group = Oracle Install Group (typically oinstall). There are lots of cases where the OS group named dba fills this role, so be sure to check the group membership of the EBS AppsTier software owner account.
  • Please note, the non-privileged OS account must have the same group as assigned to EBS AppsTier privileged account (like applmgr).

Host Requirements:

To accomplish necessary tasks on the EBS appsTier source hosts, the Delphix OS user account (henceforth referred to as "delphix_os") requires privilege elevation specifications.

Here is an example specification for the "sudo" privilege elevation utility, using the "visudo" to edit the "sudoers" configuration file.  This specification makes the following assumptions...

  • OS = Linux
  • OS account owning Oracle EBS appsTier is named "applmgr"
  • root EBS appsTier dataset path provisioned by Delphix is "/u01/oracle/VIS"
Defaults:delphix_os !requiretty
delphix_os ALL =  NOPASSWD: /bin/su - applvis -c ps *, /bin/su - applvis -c /bin/mount, /bin/su - applvis -c /bin/umount, /bin/su - applvis -c mkdir /u01/oracle/VIS/*, /bin/su - applvis -c rmdir /u01/oracle/VIS/*, /bin/su - applvis -c export *, /bin/su - applvis -c trap *, /bin/su - applvis -c cd *, /bin/su - applvis -c echo *, /bin/su - applvis -c rm */dlpx_force_autoflush.*, /bin/su - applvis -c rm */change_apps_password*, /bin/su - applvis -c */adstrtal.sh*, /bin/su - applvis -c */adstpall.sh*, /bin/su - applvis -c perl */adcfgclone.pl *, /bin/su - applvis -c perl */adclonectx.pl *, /bin/su - applvis -c perl */adconfig.pl *, /bin/su - applvis -c perl */adpreclone.pl *, /bin/su - applvis -c */bin/runInstaller -silent -detachHome *, /bin/su - applvis -c */*.env; sqlplus apps/* <<< exit;, /bin/su - applvis -c */*.env; sqlplus -s apps/* <<-EOF*SELECT fpv.profile_option_value FROM fnd_profile_option_values fpv*, /bin/su - applvis -c */*.env; sqlplus -s apps/* <<-EOF*UPDATE fnd_profile_option_values fpv SET fpv.profile_option_value*, /bin/su - applvis -c */*.env; cd *; *FNDCPASS*, /bin/su - applvis -c */rsync*, /bin/su - applvis -c */EBS_kill/kill_script.sh*, /bin/su - applvis -c test*sudo chown root*oinstall */kill_script.sh* sudo mv */kill_script.sh */EBS_kill/* sudo chmod 750 */EBS_kill/kill_script.sh * sudo chown -R root*oinstall */EBS_kill/*, /bin/su - applvis -c test*, /bin/su - applvis -c rm */CREATE_KILL_SCRIPT_FILE*, /bin/su - applvis -c whoami*, /bin/su - applvis -c *lsof*, /bin/mount, /bin/umount, /bin/ps

oraInst.loc

An oraInst.loc file must exist on every appsTier node prior to provisioning. This file will specify where the oraInventory directories live or where they should be created if they do not already exist.

The oraInst.loc file is typically located at /etc/oraInst.loc on Linux or /var/opt/oracle/oraInst.loc on Solaris. Ensure the oraInventory to which this file points to is writeable by the applmgr user.

Delphix recommends that this file specify an oraInventory location under the virtual appsTier mount path.

  • If you are provisioning a single-node appsTier, this recommendation is OPTIONAL; putting the oraInventory directories on Delphix-provided storage merely eases administration of the virtual EBS instance.
  • If you are provisioning a multi-node appsTier, this recommendation is REQUIRED; the Delphix Engine's automation requires that all nodes in the appsTier have access to the oraInventory directories via Delphix-provided storage.

Consult Oracle EBS documentation for more information about where to place this file on your appsTier and what this file should contain.

Related Topics