Requirements for Oracle EBS target data sources

Target environment requirement

Explanation

Ensure your target EBS R12.2 instance is supported

See Virtual EBS R12.2 instance requirements to ensure you can provision your EBS R12.2 instance.

Ensure your EBS 12.2 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 Notes, Release 12.2 (Doc ID 1320300.1) found at https://support.oracle.com.

Oracle has released an E-Business Suite Pre-Install RPM (available on ULN and public yum) that includes all required RPMs for both the AppsTier and DBTier of an R12.2 installation. Details can be found in Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1) found at https://support.oracle.com.

Unix requirements

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

oracle user

The Delphix Continuous Data 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.
The user should own the stage directory for DBTechstack and database files that will be cloned.

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 is writable 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.

/etc/hosts

For compatible Oracle Linux, RHEL, AIX and Solaris environments make sure that the /etc/hosts file is formatted as follows:

127.0.0.1 localhost.localdomain localhost

[ip_address] [node_name].[domain_name] [node_name]

Hostname and its IP address of Database host and AppsTier host(s) (primary and secondary hosts for multi node) should be added in the /etc/hosts file of all the Database, host, AppsTier host(s) (primary and secondary hosts for Multi Node).

These correct entries are required to avoid adcfgclone utility timeout issue on the prompt for "Target System Domain Name".

Permission to run:

• ps on Linux, AIX, and solaris as super-user.

• nfso on AIX hosts as super-user

• rootpre.sh on AIX hosts as super-user(on target DB server)

The following permissions are usually granted via sudo authorization of the commands. See Sudo Privilege Requirements for Oracle Environments for further explanation of the commands, and  Sudo File Configuration Examples for Oracle Environments for examples of the /etc/sudoers file on different operating systems.

Kernel shmmax and shmall values

The minimum required kernel.shmmax value on target hosts should be at least  half the size of physical memory in bytes.

The minimum required kernel.shmall value on target hosts should be greater than or equal to the value of shmmax, in pages.
For more information refer to Oracle documentation:  https://docs.oracle.com/en/database/oracle/oracle-database/19/ladbi/minimum-parameter-settings-for-installation.html#GUID-CDEB89D1-4D48-41D9-9AC2-6AD9B0E944E3

Target environment requirement

Explanation

applmgr user or OS user which will own the application binary file system

The Delphix Continuous Data Engine must have access to an applmgr user on the AppsTier.

This user should be a member of the EBS oinstall group.

The user should own the stage directory for AppsTier files that will be cloned.

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 DB Tier and AppsTier node to be used as a target. This user is easily created by the createDelphixOSUser.sh (located below on this page) script.

The primary OS group of the Delphix Continuous Data Engine software owner account (i.e. delphix_os) must be the same as the EBS Database/AppsTier software owner account (i.e. oravis or applmgr).

Primary group = Oracle Install Group (typically oinstall), secondary group = OSDBA Group (typically dba). 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 Database and AppsTier software owner account.

Please note, the non-privileged OS account must have the same group as assigned to EBS Database or AppsTier privileged account (like oravis or applmgr).

utilities

Ensure that "expect", "wget" and "lsof" utilities exist on the remote host.

username and GID

The primary host and the secondary host user name and its UID, Group name and GID must be the same to avoid any permission issue during the provisioning operation.

Check the high and low privilege user id and GID in the primary and secondary node and change it accordingly using groupmod with the following commands:

·   $ id oravis

·   uid=509(oravis) gid=502(oinstall)

·   $ id delphix_os

·   uid=510(delphix_os) gid=502(oinstall)

·   Change the group id as root using,

·   ```

·   ```

·   # groupmod -g 502 oinstall

·   # usermod -g oinstall oravis

# usermod -g oinstall delphix_os

passwordless ssh

Primary and secondary AppsTier hosts need to be configured with passwordless ssh if the target WLS password is going to be different from the source WLS password or for configuring WLS password different from source.

Oracle central inventory should be on common shared location between Application servers

While configuring shared APPL_TOP application, instead of storing oraInventory on the local directory of each server, all application servers should point to the same oraInventory directory on shared Delphix mount storage, so that you need to patch only on a single server and the oralnventory gets in-sync for all application servers thus preventing the oralnventory of remaining servers becoming invalid.

Details can be found in Sharing The Application Tier File System in Oracle E-Business Suite Release 12 (Doc ID 384248.1) found at https://support.oracle.com. You can also consult Oracle EBS documentation for more information about where to place this file on your AppsTier and what this file should contain.