1) INSTALL R12.1.1 WITH 11.1.0.7db

The below set-up is done on Oracle Enterprise Linux version :

OS version : OEL 5.6 ( Equivalent to RHEL 5.6)

Apps node : 192.168.2.131 rac1.mycorpdomain.com     rac1

DB Node : 192.168.2.132 rac2.mycorpdomain.com      rac2

1) SYSTEM REQUIREMENTS

1.1 ) Space required

The minimum required installation size of Oracle E-Business Suite R12.1.1 is:

• A) 90 GB for a fresh install with a production database:

Application tier file system – 35 GB (For HP-UX Itanium 50 Gb)

Database tier file system – 55 GB

OR

• B) 243 GB for a fresh install with a Vision Demo database.

Application tier file system – 35 GB

Database tier file system–208 GB (For HP-UX Itanium 210 Gb)

File system created:

DB Node : /u01 ( 240gb)

Apps Node : /u01 (100gb)

Shared : /shared(100gb)

/tmp has more than 1GB of space.

1.2) Users and Group required

On Apps Node

============

On DB Node

==========

1.3) Directory Structure and permissions

On Apps Node

============

On DB Node

==========

1.4) Packages and Patch required

Packages 

========

The following maintenance tools must be installed on all machines, and their locations specified both in the PATH of the account that runs Rapid Install and in the PATH of the accounts that will own the database tier and application tier file systems. 

•  ar

• gcc

• g++

• ld

• ksh

• make

• X Display Server

VERIFICATION :

[root@rac1 ~]# which ar

/usr/bin/ar

[root@rac1 ~]# which gcc

/usr/bin/gcc

[root@rac1 ~]# which g++

/usr/bin/g++

[root@rac1 ~]# which ld

/usr/bin/ld

[root@rac1 ~]# which ksh

/bin/ksh

[root@rac1 ~]# which make

/usr/bin/make

Also xclock is opening fine

The following packages (or versions of packages) are not part of the OS distribution media and must be downloaded separately (from http://oss.oracle.com/projects/compat-oracle/files/Enterprise_Linux/ for both Oracle Linux 5 and RHEL 5) and installed manually: 

• openmotif22-2.2.3-18.i386.rpm ( openmotif21-2.1.30-11.EL5.i386  or higher) 

[root@rac1 ~]# rpm -qa|grep -i openmotif

openmotif22-2.2.3-18

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

• perl 5.0053 or higher ( check by ' perl -v ' what is the version isntalled ) 

[root@rac1 ~]# perl -v

This is perl, v5.8.8 built for x86_64-linux-thread-multi

The following packages must be installed from the Oracle Linux 5 or RHEL 5 distribution media:

• gcc-4.1.2-14.el5.x86_64

• gcc-c++-4.1.2-14.el5.x86_64

• glibc-2.5-18.i686 (32-bit)

• glibc-2.5-18.x86_64

• glibc-common-2.5-18.x86_64

• glibc-devel-2.5-18.i386 (32-bit)

• glibc-devel-2.5-18.x86_64

• libgcc-4.1.2-14.el5.i386

• libgcc-4.1.2-14.el5.x86_64

• libstdc++-devel-4.1.2-14.el5.i386

• libstdc++-devel-4.1.2-14.el5.x86_64

• libstdc++-4.1.2-14.el5.i386

• libstdc++-4.1.2-14.el5.x86_64

• make-3.81-1.1.x86_64

• gdbm-1.8.0-26.2.1.i386

• gdbm-1.8.0-26.2.1.x86_64

• libXp-1.0.0-8.1.el5.i386

• libXp-1.0.0-8.1.el5.x86_64

• libaio-0.3.106-3.2.i386

• libaio-0.3.106-3.2.x86_64

• libgomp-4.1.2-14.el5.x86_64

• sysstat-7.0.0-3.el5.x86_64

• util-linux-2.13-0.45.el5.x86_64

• compat-libstdc++-296-2.96-138.i386

• compat-libstdc++-33-3.2.3-61.i386

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

• compat-libstdc++-33-3.2.3-61.x86_64

• elfutils-libelf-devel-0.125-3.el5.x86_64

• elfutils-libelf-devel-static-0.125-3.el5.x86_64

• libaio-devel-0.3.106-3.2.x86_64

• unixODBC-2.2.11-7.1.i386

• unixODBC-devel-2.2.11-7.1.i386

• unixODBC-2.2.11-7.1.x86_64

• unixODBC-devel-2.2.11-7.1.x86_64

• kernel-headers-2.6.18-8.el5.x86_64

>> To install a new package use command

Code:

rpm -ivh package.rpm

>> To check availability of the package

Code:

rpm -qa package.rpm

JDK 6 is bundled with Oracle E-Business Suite version 12.1.1 and is NOT REQUIRED to be installed separately.

Patches

========

1) patch "6078836"

It is a small patch of 4.7 kb only.

# pwd

/u01/sw_home/6078836

# ls

libdb.so.2 README.txt

# mv /usr/lib/libdb.so.2 /usr/lib/libdb.so.2.6078836 (if libdb.so.2 exist already in /usr/lib)# cp libdb.so.2 /usr/lib/

# ls -l /usr/lib/libdb.so.2

-rw-r--r-- 1 root root 5825 Nov 27 11:38 /usr/lib/libdb.so.2

1.5) Configure kernel parameters

Minimum kernel version >> 2.6.18-53.1.4.EL5

Note: If the current value for any parameter is higher than the value listed in the following table, then do not change the value of that parameter.

1.5.1) Edit /etc/sysctl.conf

1: set using the following entry in the /etc/sysctl.conf file: kernel.sem = 256 32000 100 142

2: On the server running the EBS Database, this kernel parameter must be the lesser of half the size of the physical memory (in bytes) and 4294967295

3: values recommended for the local port range may need to be adjusted according to the specific needs of the user's environment in order to avoid port conflicts.

1.5.2) Edit /etc/security/limits.conf

1.5.3) Edit /etc/resolv.conf

Two Domain Name System (DNS) resolver parameters (timeout and attempts) are set by default to low values when the operating system is installed. 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.

options attempts:5 

options timeout:15

1.5.4) Verify  /etc/hosts

Verify that the /etc/hosts file is formatted as follows:

127.0.0.1 localhost.localdomain localhost 

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

IMPORTANT : Add both server entery to /etc/hosts on both servers

1.5.5) Verify  /etc/sysconfig/network

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

HOSTNAME=[node_name].[domain_name]

1.5.6) Verify /etc/sysconfig/networking/profiles/default/network

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

1.5.7) Run sysctl -p

After editing the files, use the "sysctl -p" command or restart the system to invoke the new settings.

1.5.9) Run xhost + command to enable GUI windows

1.6) Other pre-req setups

1.6.1) Link to Motif library in Oracle Application Server 10.1.2 (on Oracle Linux 5 and RHEL 5 only)

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

# unlink /usr/lib/libXtst.so.6

# ln -s /usr/X11R6/lib/libXtst.so.6.1 /usr/lib/libXtst.so.6

Without this updated link, you may see the following errors during a relink of the 10.1.2 Oracle Home:

/usr/lib/libXtst.so.6: undefined reference to `__stack_chk_fail@GLIBC_2.4'

/usr/lib/libXtst.so.6: undefined reference to `__fprintf_chk@GLIBC_2.3.4'

/usr/lib/libXtst.so.6: undefined reference to `__sprintf_chk@GLIBC_2.3.4'

Since the ldconfig command overrides this link, the above link command (ln) will have to be re-issued after running the ldconfig command.

1.6.2) OPMN port conflict

Attention: By default, the OPMN service of the Application Server technology stack listens on port 6000 when started up during Rapid Install. This can conflict with the X11 port used for the graphics console on Linux servers and prevent Rapid Install from completing.

To address this issue, perform the following steps before installing or upgrading:

• • Check if the port 6000 is being used ("netstat -a | grep 6000")

  • If so, you should disable the graphics console login process on the Linux server. This can be accomplished by logging in as root and issuing the following commands:

    • • Find the process that uses port 6000 by the command "lsof -i TCP:6000".

      • Use "kill -9" to abort the process found in the previous step

      • Confirm that nothing is listening at port 6000 ("netstat -a | grep 6000")

      • Modify /etc/inittab by changing "id:5:initdefault:" to "id:3:initdefault:"

      • Run "/sbin/init 3" to restart dtlogin

1.6.3) Set environment for oracle and applmgr users

As oracle on <database-tier>

vi $HOME/.bash_profile

Add the following and save

if [ $USER = "oracle" ]; then

  if [ $SHELL = "/bin/ksh" ]; then

    ulimit -u 16384

    ulimit -n 65535

  else

    ulimit -u 16384 -n 65535

  fi

fi

. /u01/vis/db/tech_st/11.1.0/vis_rac2.env

alias sql='sqlplus "/ as sysdba" '

alias cdadm='cd /u01/vis/db/tech_st/11.1.0/appsutil/scripts/VIS_rac2'

As applmgr on <middle-tier>

vi $HOME/.bash_profile

Add the following and save

if [ $USER = "applmgr" ]; then

  if [ $SHELL = "/bin/ksh" ]; then

    ulimit -p 16384

   ulimit -n 65535

  else

    ulimit -u 16384 -n 65535

  fi

fi

. /u01/vis/apps/apps_st/appl/APPSvis_rac1.env

alias cdadm='cd /u01/vis/inst/apps/vis_rac1/admin/scripts'

1.6.4) Net Service Listeners in Multi-user Installations

Net Service Listeners use the /var/tmp.oracle directory to store temporary files. To give all users in a multi-user installation write privileges, update /var/tmp/.oracle with 777 permissions:

$ chmod 777 /var/tmp/.oracle

1.6.5) Unset ENV if using ksh

If using the Korn Shell (ksh), ensure that the $ENV environment variable is not set before starting the 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.

1.6.6) Set Variable DISPLAY

On UNIX, set the environment variable DISPLAY to an active and authorized display.

**IMPORTANT**

 In Release 12.1.1, the required Java Development Kit (JDK) is automatically installed by Rapid Install. You do not need to install the JDK separately.

<----------------------------------REBOOT BOTH SERVERS-------------------------------------->

2) CREATE STAGE AREA DIRECTORY

You need to put setups file for Oracle E-Business Suite R12.1.1 installation.

Use edelivery.oracle.com site to download Oracle E-Business Suite latest version software package. Oracle E-Business Suite R12.1 setup files almost have 50 GB size(with NLS patch)

There are two ways we can create stage for R12

1. Stage using script adautostage.pl from start here CD

2. Manual stage - create directories and copy media as listed below

create /u02/stage/R12 and copy all R12 software zip files in it

As root on any one of the servers  unzip the software

cd /u02/stage/R12

unzip B53824-01_1of4.zip

unzip B53824-01_2of4.zip

unzip B53824-01_3of4.zip

unzip B53824-01_4of4.zip

rm -f B53824-01_?of4.zip or mv B53824-01_?of4.zip /u02

unzip V15679-01_1of3.zip

unzip V15679-01_2of3.zip

unzip V15679-01_3of3.zip

rm -f V15679-01_?of3.zip or mv V15679-01_?of3.zip /u02

unzip V15680-01_1of3.zip

unzip V15680-01_2of3.zip

unzip V15680-01_3of3.zip

rm -f V15680-01_?of3.zip or mv V15680-01_?of3.zip /u02

unzip V15681-01_1of3.zip

unzip V15681-01_2of3.zip

unzip V15681-01_3of3.zip

rm -f V15681-01_?of3.zip or mv   V15681-01_?of3.zip  /u02

unzip V15682-01_1of3.zip

unzip V15682-01_2of3.zip

unzip V15682-01_3of3.zip

rm -f V15682-01_?of3.zip or mv  V15682-01_?of3.zip  /u02

unzip V15683-01_1of3.zip

unzip V15683-01_2of3.zip

unzip V15683-01_3of3.zip

rm -f V15683-01_?of3.zip or mv  V15683-01_?of3.zip  /u02

unzip V15684-01_1of3.zip

unzip V15684-01_2of3.zip

unzip V15684-01_3of3.zip

rm -f V15684-01_?of3.zip or mv  V15684-01_?of3.zip  /u02

unzip V15685-01_1of3.zip

unzip V15685-01_2of3.zip

unzip V15685-01_3of3.zip

rm -f V15685-01_?of3.zip or mv  V15685-01_?of3.zip  /u02

unzip V15686-01_1of3.zip

unzip V15686-01_2of3.zip

unzip V15686-01_3of3.zip

rm -f V15686-01_?of3.zip or mv  V15686-01_?of3.zip  /u02

unzip V15687-01_1of3.zip

unzip V15687-01_2of3.zip

unzip V15687-01_3of3.zip

rm -f V15687-01_?of3.zip or mv  V15687-01_?of3.zip  /u02

unzip V15688-01_1of2.zip

unzip V15688-01_2of2.zip

rm -f V15688-01_?of2.zip  or mv  V15688-01_?of2.zip /u02

unzip V15689-01.zip

rm -f V15689-01.zip or mv  V15689-01.zip  /u02

unzip V15690-01_1of3.zip

unzip V15690-01_2of3.zip

unzip V15690-01_3of3.zip

rm -f V15690-01_?of3.zip  or mv  V15690-01_?of3.zip  /u02

unzip V15691-01_1of3.zip

unzip V15691-01_2of3.zip

unzip V15691-01_3of3.zip

rm -f V15691-01_?of3.zip  or mv  V15691-01_?of3.zip  /u02

Create staging area for optional components if not already created.

cd /u002/stage/R12 

mkdir -p optional/AS1012

mkdir -p optional/IM1014

mv B2448?-01.zip optional/AS1012

cd optional/AS1012

mkdir Disk1 Disk2 Disk3 Disk4

mv B24483-01.zip Disk1

mv B24484-01.zip Disk2

mv B24485-01.zip Disk3

mv B24486-01.zip Disk4

cd Disk1

unzip B24483-01.zip

cd ../Disk2

unzip B24484-01.zip

cd ../Disk3

unzip B24485-01.zip

cd ../Disk4

unzip B24486-01.zip

cd ..

rm -f Disk1/B24483-01.zip

rm -f Disk2/B24484-01.zip

rm -f Disk3/B24485-01.zip

rm -f Disk4/B24486-01.zip

The below directories will gets created with content as mentioned

3) START INSTALLATION

3.1 Install Database Tier

Installation will be done on DB tier first. After installation on DB tier you will copy over generated config.txt to apps server.

Then after you will start installation on apps server and give config.txt for instalaltion.

What is config file?

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 Applications database for later use.

Previous releases of Oracle Applications only used a text file, config.txt, to store the supplied configuration values. In Release 12, the name of this configuration file changed, and it now includes the database SID, to give a file name of conf_<SID>.txt (for example, conf_PROD.txt). This file stores the information collected by Rapid Install for all database and Applications nodes.

Rapid Install stores copies of the conf_<SID>.txt file in three separate locations:

1) Database 11gR1 <ORACLE_HOME>/appsutil: This copy is used on database nodes, on Applications nodes in multi-node installs, and in upgrades. It is permanently stored and not deleted.

2) $INST_TOP: This copy is used on Applications nodes in multi-node installs, and in upgrades. It is permanently stored and not deleted.

3) /tmp/<time stamp>: This copy is used by Rapid Install during the installation run. It is deleted when the installation is completed.

The config file would save your time instead of entering the same configuration details on other node(s). In addition, it tells RapidWiz what tasks should be done on the current node.

IMPORTANT : Restarting the Installation!

If the installation process terminates before completion, you can use the -restart parameter to run Rapid Install again.

Example

$ rapidwiz -restart

The configuration file, conf_<SID>.txt, plays an important role in restarts. It is stored in the operating system's temporary directory, and utilized if the user wishes to restart an install in which Rapid Install did not get as far as creating the database.

Login as root user and run rapidwiz from the staging

#cd /u02/stage/R12/startCD/Disk1/rapdiwiz

#./rapidwiz

Rapid Install offers two options for a new installation: 

a) Standard installation

which involves creating a new system using system-specific configuration parameters

b) Express installation

where Rapid Install supplies default values for many parameters, requiring only a few to be supplied by the user carrying out the install.

Express install is ONLY for single node, single user installation.

Important: You need to carry out the relevant steps on every node that will be part of your Applications system; for example, a database node and two Applications nodes. Where applicable, operations should be carried out on the database node first.

We will be doing our 2-node installation by the Standard installation method.

4) Post Install Steps

REQUIRED STEPS :

4.1) Change Default Passwords

The default passwords are :

SYSTEM : manager

SYS         : change_on_install

The password for both SYS and SYSTEM in the Vision Demo is manager.

You should also change the default passwords for the Applications product accounts of the production and test databases.

4.2) Configure Database Initialization Parameters

The current init.ora settings allow for a total of 100 connections. However, after the standard setup is complete, only a few users can be connected because of the connections used by the concurrent managers, AQ workers, and job queues.

Check Note 396009.1, Database Initialization Parameters for Oracle Applications Release 12.

4.3) Apply Oracle Application Server 10g (10.1.2.3) Patches

Check Note 437878.1, Upgrading OracleAS 10g Forms and Reports in Oracle E-Business Suite Release 12

4.4) Update PL/SQL Log and Out Directory (utl_file_dir setup)

The temporary directory on your database server for log and output files from PL/SQL concurrent programs is set to /usr/tmp by default.

This value is specified in the utl_file_dir parameter of the database initialization file, and assigned to the APPLPTMP environment variable.

Enter your choice of directory as the new value for utl_file_dir in the database initialization parameter file. Then use the edit AutoConfig parameters feature of Oracle Applications Manager to update the APPLPTMP variable in the Applications context file with the new utl_file_dir directory location. Finally, run AutoConfig to recreate the environment files.

4.5) Check Client Software For Use With Forms Applet

The connection between the client and the E-Business Suite forms is provided through an applet in the client Web browser.

Note: For a list of Web browsers supported for use with Oracle E-Business Suite Release 12, see My Oracle Support Knowledge Document 389422.1, Recommended Browsers for Oracle Applications 12.

Instead of using the browser's own JVM, Oracle Applications Release 12 uses the Sun Java Runtime Engine (JRE). This component is invoked when a user accesses a function that requires it, such as running a form. If the JRE Plug-in has not already been installed, the browser prompts the user to download the required installation executable. JRE replaces Oracle JInitiator, which was used in Release 11i.

Check Note 393931.1, Upgrading JRE Plugin with Oracle Applications R12.

4.6) Apply Security Patches and Review Best Practices

Oracle strongly recommends that you apply the latest available CPU patches for each product after you install Oracle Applications Release 12.1.1

you should also review the recommended security practices described in My Oracle Support Knowledge Document 403537.1, Best Practices for Securing Oracle E-Business Suite Release 12.

CONDITIONAL STEPS :

Perform all that apply to your newly installed Oracle Applications system.

4.7) Resize the Database

You will need to increase the size of your database to meet the specific requirements of your system. The increase will in part depend on the products you have licensed and the additional features (such as multiple languages or multiple organizations) you configure in your installation.

4.8) Configure Parallel Concurrent Processing (PCP)

PCP allows you to distribute concurrent managers across multiple nodes. If you chose to enable load balancing for Concurrent Processing servers

during the Rapid Install process, you must complete additional setup steps.

See Managing Parallel Concurrent Processing in Oracle Applications System Administrator's Guide - Configuration.

4.9) Configure Forms Socket Mode

By default, Oracle Applications Release 12.1.1 supports Oracle Forms 10g in servlet mode , which facilitates use of firewalls, load balancing, proxies, and other networking options. 

The use of socket mode is also supported, however, and can be enabled by following the instructions in My Oracle Support Knowledge Document 384241.1, Using Forms Socket Mode in Oracle Applications Release 12.

4.10) Set Up National Language Support (NLS)

If you plan to use languages other than American English in your installation, read the information in the Oracle Applications NLS Release Notes, and complete the necessary steps for installing the translated software.

STEPS :

1) Complete the tasks in the Oracle Applications NLS Release Notes

2) Activate the additional languages via the License Manager utility (within Oracle Applications Manager)

3) The multilingual tables must be updated for the activated languages. Go to the AD Administration main menu, choose the 'Maintain Applications Database Entities' submenu, and run the 'Maintain Multi-lingual Tables' task.

4) Install the relevant NLS software for all the active languages, to lay down the NLS translated files into the APPL_TOP.

5) Use the Translation Synchronization Patch Utility to synchronize the languages with the American English patch level. This step is needed in case any

American English patches were applied after Rapid Install was run.

Check Note 393320.1, Internationalization Update Notes for Release 12.

Check Note 405992.1, Oracle Applications Release 12 Translation Scope and Availability.

4.11) Complete Workflow Notification Mailer Configuration

Before you can send Oracle Workflow email notifications and Oracle Alert email alerts, you must complete the Workflow Notification Mailer configuration, using the Notification Mailer configuration wizard in Oracle Applications Manager.

1. From the Applications Dashboard of Oracle Applications Manager, select Workflow Manager from the "Navigate to" pull-down menu, and click on the Go button.

2. In the Workflow System region, click the Notification Mailers status icon to navigate to the Service Components page for notification mailers. At this point, the Notification Mailers status icon should be showing the status Down.

3. In the Service Components page, select the Workflow Notification Mailer service component and click the Edit button to navigate to the Notification Mailer configuration wizard.

4. In the Outbound Email Account (SMTP) region, enter the name of the outbound SMTP mail server.

5. If you want to enable inbound email processing, select the Inbound Processing parameter in the Inbound Email Account (IMAP) region, and enter the name of the inbound IMAP mail server, the username and password of the email account that the Notification Mailer uses to receive email messages, and the reply-to address of the email account that receives incoming messages, to which notification responses should be sent.

6. Click Apply.

7. Return to the Service Components page, and verify that the status of the Workflow Notification Mailer service component is now Running

.

****After installation is complete****

• Back up the Oracle Applications product files, including the Application Server technology stack components

• Back up the Oracle Applications database components.