Building a 5 nodes Oracle EBS using RAC and shared appl top 4.

Install Oracle Database Software

In the previuos step we have successfully installed the Oracle Cluster infrastructure. Now it's time to install the RAC enabled Database software.

The installation will takes these steps

• Install the base 11g R2 version 11.2.0.3 software
• Implement EBS - 11gR2 interoperability note's step

Install 11g R2 version 11.2.0.3

First take a safety backup of the current oraInventory on the database nodes. (with root user)
# mkdir -p /u02/backup
# cd /u02/backup
# tar cvzf orainventory_app_db01_predbinst.tar.gz /u01/app/oraInventory

# cd /u02/backup
# tar cvzf orainventory_app_db02_predbinst.tar.gz /u01/app/oraInventory

Check the oracle user group member

# id oracle

uid=1101(oracle) gid=1000(oinstall) groups=1000(oinstall),1031(dba),1020(asmadmin),1021(asmdba)

Check the new ORACLE_HOME base directory owner ship
# ll /u01/app/oracle
drwxr-xr-x 2 oracle oinstall   4096 Feb  5 14:18 oracle

Login through vnc client into db01 server.
Vnc erdb01:1

In a new xterm window
# su – oracle
$ export DISPLAY=db01:1.0
$ cd /u02/stage/unzipped/db/database
$ ./runInstaller

Use this example guide
Configure security Updates
   turn off OCM
Skip software updates
Select Installation Option
Install Database software only
Grid Installation Option
Oracle RAC database installation
db01
db02
SSH connectivity
OS username: oracle
password: <oracle user password>
uncheck: User home is shared …
  uncheck: Reuse private and public keys
Setup gomb
Test gomb
Languages
English
<any language that you need>
Database Edition
Enterprise Edition
Specify Installation Location
Oracle Base: /u01/apps/PROD/db/tech_st/rac/admin
Software Location: /u01/apps/PROD/db/tech_st/rac/11.2.0.3
(ignore warning on INS-32018 message )
Operating System Groups
OSDBA group: dba
OSOPER group: dba
Perform Prerequisite Checks
Summary
Install

At the end run root.sh on both node as root. I will take a long time, be patient it is working. If you wish you could check the progression in the log files.

If you carefully read the above guide you easily find out that I will use PROD name for Oracle SID.

Interoperability note's step

So let's continue with the 1058763.1 interoperability note. Allway for the freshest version of this note on Oracle Support. In this post I will only talk from those steps what should have to done.

Install the example CD

The 6. point of the note require to install the 11gR2 example CD. Let's do it.

On db01 server with VNC, in a new xterm window.

# su – oracle

$ cd /u02/stage/unzipped/db/examples

$ ./runInstaller

Use this example guide

Skip software updates

Specify Installation Location

Oracle Base: /u01/apps/PROD/db/tech_st/rac/admin

Software Location: /u01/apps/PROD/db/tech_st/rac/11.2.0.3

(ignore warning INS-32018)

Grid Installation Option

Oracle RAC database installation

db01

db02

Perform Prerequisite Checks

Summary

Install

Generate 9i nls data directory

The 7. point require to generate 9i nls data directory. Without this Oracle EBS will not work well!

ssh root@erdb01

su – oracle

export DISPLAY=erdb01:1.0

export ORACLE_BASE=/u01/apps/ERUZEM/db/tech_st/rac/admin

export ORACLE_HOME=/u01/apps/ERUZEM/db/tech_st/rac/11.2.0.3

export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$ORACLE_HOME/OPatch:$PATH

export LD_LIBRARY_PATH=$ORACLE_HOME/lib

export PERL5LIB=$ORACLE_HOME/perl/lib/5.10.0:$ORACLE_HOME/perl/lib/site_perl/5.10.0

perl $ORACLE_HOME/nls/data/old/cr9idata.pl

export ORA_NLS10=$ORACLE_HOME/nls/data/9idata

ssh root@erdb02

su – oracle

export DISPLAY=erdb02:1.0

export ORACLE_BASE=/u01/apps/ERUZEM/db/tech_st/rac/admin

export ORACLE_HOME=/u01/apps/ERUZEM/db/tech_st/rac/11.2.0.3

export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$ORACLE_HOME/OPatch:$PATH

export LD_LIBRARY_PATH=$ORACLE_HOME/lib

export PERL5LIB=$ORACLE_HOME/perl/lib/5.10.0:$ORACLE_HOME/perl/lib/site_perl/5.10.0

perl $ORACLE_HOME/nls/data/old/cr9idata.pl

export ORA_NLS10=$ORACLE_HOME/nls/data/9idata

Now do not close the first node's ssh session. You will need this session during patch installation. Alternatively create a temporary patch.env file which could be used during the next patch installation step. I recommend to put the patch.env file in oracle's $HOME/bin directory.
The patch.env content should be:

export DISPLAY=erdb02:1.0

export ORACLE_BASE=/u01/apps/ERUZEM/db/tech_st/rac/admin

export ORACLE_HOME=/u01/apps/ERUZEM/db/tech_st/rac/11.2.0.3

export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$ORACLE_HOME/OPatch:$PATH

export LD_LIBRARY_PATH=$ORACLE_HOME/lib

export PERL5LIB=$ORACLE_HOME/perl/lib/5.10.0:$ORACLE_HOME/perl/lib/site_perl/5.10.0

export ORA_NLS10=$ORACLE_HOME/nls/data/9idata

Collect applied database patches from the source system's database tier

Before continue collect all applied database patches from the source system. (use opatch lsinventory command). This is a very important step on the next steps you should install a database software what should be on the same patch level as the source system.

Install patches required by interoperability note

On the source system's database check whether all required interoperability patches applied or not. If not apply them now! Don't forget to refresh the opatch patch on the source system too.

Copy all patch zip file into the stage area. I recommend to create a subdirectory for them. For example /u02/stage/zipped/patches/db. Then unzip all patch zip file into this subdirectory: /u02/stage/unzipped/patches/db. Don't unzip the opatch patch into this subdirectory.

Apply the latest opatch patch on the 2 new database software home - one per each node! (use 11.2.0.0.0 version of 6880880 patch)

Apply all required interoperability database patch. Use the left open ssh session or use the patch.env during installation process. If you have choosed the alternative patch.env you could apply the patches like this example:
# su – oracle
# . ./bin/patch.env
# cd /u02/stage/unzipped/patches/db/<patch number>
# opatch apply

Install remaining database patches

If you have other applied database patches on the source system then apply them on the new database software home too! (any PSU, CPU too!)

Don't forget! You should have be on a same patch level as the source system's database!