I.  INSTALLATION OF EBS WITH RAPID INSTALL

With Rapid Install, you can perform the following tasks:

• Install a new, fully configured Oracle E-Business Suite system, including the latest certified Oracle E-Business Suite technology stack and all patches, product family release update packs, release update packs, and other updates available at the time of this Oracle E-Business Suite release.
• Lay down the file system and configure server processes for an upgraded system.
• Install a new database node or Applications node technology stack.

Rapid Install employs a wizard that guides you through the screens used to carry out the selected task. On the wizard screens, you enter configuration values for your system; these will typically be saved in the Oracle E-Business Suite database for later use.

New Installation (Standard)

In a new Standard installation, we need to choose where to install the required nodes (database node and primary Applications node).

New Installation (Express)

In an Express installation, you set up a fully configured, single-user/single-machine system using a few basic configuration parameters, such as database type and name, top-level installation directory, and port pool choice. The remaining directory specifications and mount points are supplied by Rapid Install using default values. An Express installation includes a set of core products and uses the US7ASCII character set.

II.    REQUIREMENTS

1.      Operating System Supported Version for R12.1.1

For Linux Installation Steps we will see in separate document.

Operating System Name	Supported Version	Minimum Kernel
Oracle Enterprise Linux	4 – Update 4 or higher (32-bit)	2.6.9-42.0.0.0.1.EL
Oracle Enterprise Linux	5 – Update 1 or higher (32-bit)	2.6.18-8.el5PAE
Red Hat Enterprise Linux	4 – Update 4 or higher (32-bit)	2.6.9-42.EL
Red Hat Enterprise Linux	5 – Update 1 or hgiher (32-bit)	2.6.18-8.el5PAE
SUSE Linux Enterprise Server	10 – GA, SP1 or higher (32-bit)	2.6.16.21-0.8

2.      System Software

Platform-Specific Software Requirements

Operating System	Required Maintenance Tools
Linux x86	ar, gcc, g++, ld, ksh, make, X Display Server
Microsoft Windows	Microsoft C++, MKS Toolkit*, GNU make

3.      Minimal Hardware

• Memory: At least 2GB of 3GB would be better and 4GB is best choice.
• File System Space Requirements for Standard Installation:
  • At least 300GB. 350GB will be better

File System Space Requirements for Standard Installation

Node	Space Required
Applications node file system (includes OracleAS 10.1.2 Oracle Home, OracleAS 10.1.3 Oracle Home, OMMON_TOP, APPL_TOP, and INST_TOP)	35 GB (50 GB on HP-UX Itanium)
Database node file system (Fresh install)	55 GB
Database node file system (Vision Demo database)	208 GB (210 GB on HP-UX Itanium)

• Temporary directories and files
  • For install time temporary disk space, Rapid Install uses the directory defined by the TMPDIR variable (on UNIX) or TEMP and TMP variables (on Windows).
  • We should ensure there is at least  1GB of free temporary space before starting an installation.

• Stage Area
  • For a production database install, running Rapid Install from a stage area requires atleast 47 GB to accommodate the file system and database files in the stage area.

III. PREPARATION OF THE R12 INSTALLATION IN REDHAT LINUX

1. What is RPM?

The Red Hat Package Manager (RPM) is a toolset used to build and manage software packages on UNIX systems. Distributed with the Red Hat Linux distribution and its derivatives (CentOS is 100% compatible rebuild of the Rehat Enterprise Linux). The rpm files represent application or package that you can install on Linux system.

The naming scheme of RPM files is itself a standardized convention. RPMs have the format

(name)-(version)-(build).(platform).rpm.

The location of the documentation for installed packages is:   /usr/share/doc

Note:   We can find them via rpmfind.net and rpm.phone.net

HOW TO SEE IF A PACKAGE IS ALREADY INSTALLED?

An interesting command for checking if a package is installed or to find out all packages that match a string is:

rpm -qa | grep -i

where: q = query;

a = all;

grep=filters content based on certain strings;

HOW TO DEINSTALL A PACKAGE?

From the command above, take the package name (without the architecture and rpm extension) and perform the following command

rpm -e package where: e = erase

2.      From the RHEL 5 distribution media

The following i386 packages(RPM) are not part of the OS distribution media and must be downloaded separately from http://oss.oracle.com/projects/compat-oracle/files/EnterpriseLinux for RHEL 5 and installed manually:

• openmotif21-2.1.30-11.EL5.i386
• xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386

The following i386 packages must be installed from the RHEL 5 distribution media. Some rpm are distributed as part of the ‘default’ installation of RedHat Enterprise Linux.

compat-glibc-2.3.4-2.26

compat-glibc-headers-2.3.4-2.26

compat-libstdc++-33-3.2.3-61

compat-libstdc++-296-2.96-138

compat-oracle-rhel4-1.0-5 – Not need to install, still works

gcc-4.1.2-33 – Not need to install, still works

gcc-4.1.2-46.el5

gcc-c++-4.1.2-46.el5

gdbm-1.8.0-26.2.1

glibc-2.5-42

glibc-common-2.5-42

glibc-devel-2.5-42

glibc-headers-2.5-42

libaio-0.3.106-3.2

libgcc-4.1.2-46.el5

libgomp-4.4.0-6.el5

libstdc++-4.1.2-46.el5

libstdc++-devel-4.1.2-46.el5

libXau-devel-1.0.1-3.1

libXp-1.0.0-8.1.el5

make-3.81-3.el5

openmotif21-2.1.30-11.EL5 –After installing libaio-devel-0.3.106

sysstat-7.0.2-3.el5

xorg-x11-libs-compat-6.8.2-1.EL.33.0.1

Additionally, the following RPMs are required for an 11gR1 Database (which is bundled with the 12.1.1 release) on the database tier:

• elfutils-libelf-devel-0.125 – Installed from OS
• elfutils-libelf-devel-static-0.125 – Installed from OS
• libaio-devel-0.3.106
• unixODBC-2.2.11 -2nd
• unixODBC-devel-2.2.11 -1st
• kernel-headers-2.6 – Installed from OS

Below code is to check whether the required rpm’s are installed in Linux System.

rpm -q compat-glibc-2.3.4-2.26 compat-glibc-headers-2.3.4-2.26 compat-libstdc++-33-3.2.3-61 compat-libstdc++-296-2.96-138 compat-oracle-rhel4-1.0-5 gcc-4.1.2-33 gcc-4.1.2-46.el5 gcc-c++-4.1.2-46.el5 gdbm-1.8.0-26.2.1 glibc-2.5-42 glibc-common-2.5-42 glibc-devel-2.5-42 glibc-headers-2.5-42 libaio-0.3.106-3.2 libgcc-4.1.2-46.el5 libgomp-4.4.0-6.el5 libstdc++-4.1.2-46.el5 libstdc++-devel-4.1.2-46.el5 libXau-devel-1.0.1-3.1 libXp-1.0.0-8.1.el5 make-3.81-3.el5 openmotif21-2.1.30-11.EL5 sysstat-7.0.2-3.el5 xorg-x11-libs-compat-6.8.2-1.EL.33.0.1

After installing these patches (Sets the RPM)

Run

ldconfig –v

3.      Networking – Hosts Name settings

We can do following actions by Terminal itself or by GUI Navigation also.

a.      /etc/hosts

The /etc/hosts file must contain a fully qualified name for the server:

   

We must configure the host to resolve hostnames to the loopback IP address by modifying the /etc/hosts file to contain the following entries:

127.0.0.1 hostname.domainname hostname

127.0.0.1 localhost.localdomain localhost

Example with hostname = vision and domainname = r12apps.com

Then the hosts will be like this.

[root@vision etc]# cat hosts

#Do not remove the following line, or various programs

# that require network functionality will fail.

127.0.0.1       vision.r12apps.com    vision

127.0.0.1       localhost.localdomain localhost

::1             localhost6.localdomain6 localhost6

Note: The configuration line must be in first place! 

After doing so, check that the hostname resolves to the loopback IP address by entering the following command for verifying that our hostname works or not:

/bin/ping vision.r12apps.com

b.      /etc/sysconfig/network

Verify that the /etc/sysconfig/network file is formatted as follows: HOSTNAME=.

Example with the node_name = vision and domain_name = r12apps.com

[root@vision ~]# cat /etc/sysconfig/network

NETWORKING=yes

NETWORKING_IPV6=no

HOSTNAME= vision.r12apps.com

c.       default/network

If the /etc/sysconfig/networking/profiles/default/network file exists, remove it.

[root@vision ~]# rm /etc/sysconfig/networking/profiles/default/network

rm: remove regular file ‘/etc/sysconfig/networking/profiles/default/network’? y

[root@vision ~]# cat /etc/sysconfig/networking/profiles/default/network

cat: /etc/sysconfig/networking/profiles/default/network: No such file or directory

4.      Restart of the system

[root@ vision ~]# rebootBroadcast message from root (pts/2) (Sun May 18 09:42:14 2011):The system is going down for reboot NOW!

5.      Kernel Setting

Add or amend the following lines in the “/etc/sysctl.conf”

Specifying the parameters in the sysctl.conf file causes the parameters to be set upon reboot.

# Append this one in sysctl.conf

kernel.sem = 256 32000 100 142

fs.file-max = 131072

net.ipv4.ip_local_port_range = 10000 65000

net.core.rmem_default = 262144

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 262144

kernel.shmmni = 4096

kernel.msgmni = 2878

kernel.shmmax must have the half size of the physical memory (in bytes), and at least 2147483648

Run the following command to change the current kernel parameters:

/sbin/sysctl -p

6.      The resolver – DNS parameters

The file /etc/resolv.conf is used by the resolver a library that determines the IP address from an host name. It defines the DNS.These low values may cause attempted network connections to an Oracle database to fail. If this happens, add or update the following entries to these minimum settings in the /etc/resolv.conf file on each server node:

[root@vision ~]# cat /etc/resolv.conf

; generated by /sbin/dhclient-script

search r12apps.com

nameserver 192.168.1.1

options attempts:5

options timeout:15

7.      Limiting user processes

To limit the user processes, open the /etc/security/limits.conf file and change the existing values for “hard” and “soft” parameters as follows. Restart the system after making changes.

*               hard    nofile          65535

*               soft    nofile          4096

*               hard    nproc           16384

*               soft    nproc           2047

8.      Create Operating System Accounts

Before running Rapid Install, you must create the operating system accounts that will be used:

• in the installation of the database node: the oracle account

The operating system user that owns the database node file system and starts the database node services is called the oracle user.

• and Applications node file systems: the applmgr account

The operating system user that owns the Applications node file system and starts the Applications node services is called the applmgr user. The applmgr user is the account that owns the Applications node technology stack (APPL_TOP, COMMON_TOP, OracleAS 10.1.2 Oracle Home, and OracleAS 10.1.3 1-14 Oracle E-Business Suite Installation Guide: Using Rapid Install Oracle Home).

The names of these accounts must be the same on all nodes in an Oracle E-Business Suite system.

We can perform (Reference – Page 27 –in R12.1.1 documentation):

• a single-user installation: one user for the two account
• An Multi-user installations: one user by account.

The default name for the oracle user is ora. For example, for a production (PROD) environment, the default Oracle OS username might be oraprod.

For the applmgr user, the default name is appl. For example, for a Vision Demo (VIS) environment, the default Apps OS username might be applvis.

Note:   Two common groups that are defined in installations are:

• the oinstall group (which owns the Oracle Inventory information)
• And the dba group whose members have SYSDBA privileges of the database.

[root@vision ~]#       groupadd dba

[root@vision ~]#         useradd -m -g dba oracle

[root@vision ~]#       passwd oravis

[root@vision ~]#       useradd -m -g dba applmgr

[root@vision ~]#       passwd applvis 

Where:

• the –m flag indicates that a new home directory should be created,
• -g specified the primary group

o   Once the user is created, the password is immediately reset using the passwd command.

9.      Maintenance tools

To verify that they are installed, just run the version command and see if you have an answer.

Required Maintenance Tools	Description	Version command
ar	create, modify, and extract from archives	ar V
gcc	GNU project C and C++ compiler	gcc –version
g++	gcc – GNU project C and C++ compiler	g++ –version
ld	The GNU linker	ld –version
ksh	KornShell, a standard/restricted command and pro-gramming language	ksh –version
make	GNU make utility to maintain groups of programs	make –version
X Display Server	Linux – X Windows System (commonly X or X11)	X -version

10.  Directories

a.      Inventory Directory – oraInst.loc

As per note 405293.1, on all platforms except Windows, oraInst.loc must exist and point to a valid inventory directory. Specifically:

• oraInst.loc must be located in /etc (for Linux)
• oraInst.loc must point to a valid central inventory location
• the central inventory location must be writable by the owner of the oracle files and the application files

If oraInst.loc does not exist, create it in the proper directory. The contents should look like this:       inventory_loc=/d01/oracle/oraInventory

Where: /d01/oracle/oraInventory points to the directory where the central inventory is to be located and must be writable by the owner of the oracle files and the application files. Installation directories

Allow the users to actually create files in the directory, so we need to give permission for oravis in /d01

[root@vision ~]#   mkdir -p /d01/oracle/VIS

[root@vision ~]# mkdir -p /d01/oracle/VIS/inst

[root@vision ~]# chown -R oracle:dba /d01

[root@vision ~]# chmod -R 775 /d01

11.  Setting Up the Stage Area

As preparation for running Rapid Install, you must run a Perl script that creates the install directory and copies the contents of the Release 12.1.1 software bundle to the appropriate location in the file system, known as the stage area (or staging area).

You must have perl 5.0053 or higher installed, and it must be in PATH. Verify software version (perl).

Perl –v

Give permission for Staging Folder (StageR12) as 777 using chmod.

Unset the ENV environment variable prior to installing installation, as it can alter variables that are set by the Oracle installation scripts. The command unset ENV can be used to unset the variable if necessary.

[root@vision ~]# unset ENV

1. Patches

Oracle HTTP Server Patch (RHEL 5)

Download and apply the patch 6078836 from OracleMetaLink to fix an issue with the Oracle HTTP Server bundled with the E-Business Suite technology stack. Perform the following command as root:

[root@vision ~]# cd /d01/StageR12

[root@vision StageR12]# unzip p6078836_101330_LINUX.zip

Archive:  p6078836_101330_LINUX.zip

creating: 6078836/

inflating: 6078836/libdb.so.2

inflating: 6078836/README.txt

[root@vision StageR12]# cd 6078836

[root@vision 6078836]# cp libdb.so.2 /usr/lib

13.  Link to Motif library for Oracle Application Server 10.1.2 (on RHEL 5)

Perform the following command (as root on your system) to update a required link to a Motif library prior to re linking or patching the 10.1.2 Application Server Oracle Home:

[root@vision ~]#  unlink /usr/lib/libXtst.so.6

[root@vision ~]# ln -s /usr/X11R6/lib/libXtst.so.6.1 /usr/lib/libXtst.so.6

IV.  Starting the installation

For Unix:[root@vision ~]# cd /d01/StageR12/startCD/Disk1/rapidwiz/

[root@vision  ~]# ./rapidwiz

Rapid Install Wizard is validating your file system……

4 dvd labels found

Rapid Install Wizard will now launch the Java Interface…..

It will open the Install Oracle Applications – Welcome screen. Click Next