RCU-6130:Action failed – RCU-6135 Error while trying to execute java action

RCU-6130:Action failed – RCU-6135 Error while trying to execute java action

This error is caused because some of the expected components installed with the fusion applications database are not installed

Step1

while installing the database we need to check the mandatory options as below in the screen

[1]Oracle Partitioning [2] OLAP [3]Lable Security[4]Data Mining[5]Real Time Applications Testing 

Step2

Install the required patches in the database from the installers

find the patch list in the location /path_of_staged_rup3/rup3/installers/database/11202patch

This patches may change according to the oracle's advice please refer the latest release note's for the fusion applications before installing the patches

Oracle Fusion Applications Release Notes, 11g Release 1, Update 3 (11.1.4) [ID 1455116.1]

[oracle@fahdb 11202patch]$ ls

10077191  10220058  10238786  10269193  10419629  11742094  11883804  12544032  12686274  13004894  13365700  13476197  8223165  9700115  9885553 10142788  10232083  10259620  10325230  11689869  11786272  12329775  12579349  12737666  13356617  13420723  13576540  9401552  9729764

Step 3

Check the components

SQL> select * from v$option where parameter in (
2 'Data Mining','Java','OLAP','Oracle Label Security','Spatial');PARAMETER VALUE
-------------------------------------------------- ------------------------------
Spatial                                          TRUE
Java                                              TRUE
Oracle Label Security                     TRUE
OLAP                                            TRUE
Data Mining                                   TRUE 

SQL> SELECT comp_name, status, substr(version,1,10) as version FROM dba_registry WHERE comp_id = 'CONTEXT';

COMP_NAME                      STATUS                         VERSION
------------------------------ ------------------------------ ------------------------------
Oracle Text                    VALID                          11.2.0.3.0

SQL> select * from ctxsys.ctx_version;

VER_DICT                                 VER_CODE

---------------------------------------- ----------------------------------------

11.2.0.3.0                               11.2.0.3.0

Now rerun The RCU...

If you had missed up nay post patching steps of the CTX Package then you may get this error also to rectify this error we need to follow all the steps the post install patch for all the patches which has it

when you have completed all the patching and the post patching steps then proceed to install the rcu .. RCU has the automatic cleaning of the Previous session so when this kind of error occurs cancel the RCU and rectify the cause and then rerun the RCU

Check the post regarding the steps to create the RCU

http://orafapp.blogspot.com/2012/10/creating-fusion-applications-database.html

Creating Fusion applications database RCU

Creating the repository in fusion applications database [RCU]

The repository creation utility is used to create the  Fusion schema's in the bare Mattel database before Installing the fusion applications we need to install the separate database which holds the data's of the fusion applications and two other database's for IDM

The fusion applications database which holds the schema for all the modules of the fusion applications ...there are some special init Parameter's for the Fusion applications database we need to specify refer to the release notes or EDG for init parameters which suites your environment 

For starting the RCU screens we need go to the location where the binaries are unzipped  /fashared/rup3/installers/apps_rcu/linux
you will find a  zip file called  rcuHome_fusionapps_linux.zip
unzip the rcuHome_fusionapps_linux.zip in the /tmp directory
copy the bi component  from rcu/integration/biapps/schema and place it in the unzipped directory /tmp/rcu

Step1

Run the  RCU

Step 2
Select the create to create the RCU in the database

Step 3

We need to Specify the database connection  

Host name    :fully qualified host name
Port              :database port
service name :database service name
Username      :sys
Role               :sysdba

Step4

Rcu will check the prerequisites  to create the repository

Step5

We need to select the Fusion applications ,secure Enterprise search  to create the fusion applications repository

Step6

Click Ok when all the prerequisites are fulfilled

Step 7

Provide the necessary password for all the schema

Step8

Provide the values in the boxes

Directory on the database machine  :        /tmp/rcu  we have unzipped the rcu from the installers  in the /tmp/rcu
APPLCP_FILE_LOG                              =$ORACLE_HOME/log
APPLLOG_DIR                                      =$ORACLE_HOME/log
OBIEE backup dir                                     /tmp/rcu
KEYFLEXCOMPFIELTER                     /tmp/rcu
Advanced compression option                   N    [if you have advanced compression options in you db environment then you can give Y]
partitioning                                                 Y     [ oracle partitioning ]
Master repository                                      501
Work repository                                         D == provide the value D not provide the value R ...
Work repository ID                                   501
Work repository_Name                             Fusionapps_WREP
Oracle transactional   BI                             /tmp/rcu
Activity Graph and analysis                      Y

Step9

Create the necessary table spaces

Step10

click Ok to proceed to the next page

Step11

Check the summary of creation done by the Rcu

Step12

check the Rcu had completed successfully

Upgrading grid +ASM with oracle restart from 11.2.0.2 to 11.2.0.3

Upgrading grid +ASM with oracle restart from 11.2.0.2 to 11.2.0.3

It is an "out of place upgrade"and we need to install the new grid home for the upgrade and we need to apply the PSU patch on the grid home and the oracle home [Things to Consider Before Upgrading to 11.2.0.3 Grid Infrastructure/ASM [ID 1363369.1]

Refer the post how to apply the PSU patches before upgrading the grid
http://orafapp.blogspot.com/2012/08/applying-psu-patch-on-grid-asm-and-db.html

we need to unset all the environmental variables before we start the upgrade

[grid@fahdb grid]$ echo $ORACLE_HOME
/u01/app/oracle/grid/11.2.0/grid
[grid@fahdb grid]$ echo $ORACLE_SID

+ASM

[grid@fahdb grid]$ unset ORACLE_HOME

[grid@fahdb grid]$ echo $ORACLE_HOME

[grid@fahdb grid]$ unset ORACLE_BASE

[grid@fahdb grid]$ unset ORACLE_SID

[grid@fahdb grid]$ echo $ORACLE_BASE

[grid@fahdb grid]$ echo $ORACLE_SID

Create the directory where the new grid home is going to be installed and it is to be owned by the root with the oinstall as the group

[root@fahdb 11.2.0]# mkdir  /u01/app/oracle/grid/11.2.0.3/grid_3 -p 

[root@fahdb 11.2.0]# chown root:oinstall  /u01/app/oracle/grid/11.2.0.3/grid_3

unzip the grid software downloaded from the updates.oracle.com

[root@fahdb 11.2.0]   unzip  p10404530_112030_Linux-x86-64_3of7.zip
[root@fahdb 11.2.0]# ls

grid  grid_3

The grid_3 will the empty directory where the grid software is going to be installed the ad the grid is the directory create when we unzip the grid software downloaded from the updates.oracle.com

/u01/app/oracle/grid/11.2.0.3/grid_3 -- empty directory  for the new grid home
/u01/app/oracle/grid/11.2.0.3/grid     -- the directory which contains the unzipped grid software

Step 1

Run the Grid installer from the grid user where you have unzipped the the software

Skip the software update' science  we are upgrading to the latest software

Step 2

In the installation set select the option upgraded the oracle grid infrastructure and ASM

Step3

It will Run a while to gather  the system details

Step4

Select the Product Language according to your requirement

Step4

Select the O/s groups for the ASM instances

Step 5

The installation location of the grid  the grid home which we created for this grid and the software location we need to specify
here we have unzipped the software in the /u01/app/oracle/grid/11.2.0.3/grid
and the location of the new grid home is    /u01/app/oracle/grid/11.2.0.3/grid_3

Step 6

After the prerequisites Checks check the summary file which contains the grid home /u01/app/oracle/grid/11.2.0.3./grid_3
and the software location /u01/app/oracle/grid/11.2.0.3/grid/install and the ASM also will be upgraded Automatically with the upgraded process

Step 7
Save the summary file

Step8

you can check the details of the grid installation process by the details

Step9

Run rootupgrade.sh script from the root to upgrade the css

Step10

Step11

Grid infrastructure had been installed successfully on the machine

Applying PSU Patch on the grid ASM and db with oracle restart before Upgrade to 11.2.0. 3

Applying the PSU Patchs on the grid ASM and db  with oracle restart environment before starting the Upgrade

Here we upgrade the 11.2.0.2 grid infrastructure  ASM with oracle restart and database to 11.2 .0.3

Before starting the upgrade we need to apply the PSU[patch set update] patches on the grid home and the oracle home for applying the  PSU patches we need the latest OPatch .. we can download the latest OPatch from the MOS

we can download the  p6880880_112000_Linux-x86-64.zip for the OPatch from the MOS

Upgrading the OPatch with the latest  version of OPatch available from MOS

Step1

Backup the $ORACLE_HOME/OPatch  in to the new directory OPatch_bkp

cp -r OPatch/ OPatch_bkp

[oracle@fahdb dbhome_1]$ ll OP*

OPatch:

total 140

drwxr-xr-x 3 oracle oinstall  4096 Aug 20 00:55 crs

drwxr-xr-x 2 oracle oinstall  4096 Aug 20 00:55 docs

-rw-rw-r-- 1 oracle oinstall 23695 Mar 21 23:24 emdpatch.pl

drwxr-xr-x 2 oracle oinstall  4096 Feb 20 21:58 fmw

drwxr-xr-x 2 oracle oinstall  4096 Aug 20 00:55 jlib

drwxr-xr-x 5 oracle oinstall  4096 Aug 20 00:55 ocm

-rwx--x--- 1 oracle oinstall 31471 Mar 21 23:24 opatch

-rwxrwxr-x 1 oracle oinstall 18425 Mar 21 23:24 opatch.bat

-rwxrwxr-x 1 oracle oinstall 10056 Mar 21 23:24 opatchdiag

-rwxrwxr-x 1 oracle oinstall  9352 Mar 21 23:24 opatchdiag.bat

-rw-rw-r-- 1 oracle oinstall    49 Mar 21 23:24 opatch.ini

-rw-rw-r-- 1 oracle oinstall  2576 Mar 21 23:24 opatch.pl

drwxr-xr-x 4 oracle oinstall  4096 Aug 20 00:55 opatchprereqs

drwxrwxr-x 3 oracle oinstall  4096 Mar 21 23:25 oplan

-rw-rw-r-- 1 oracle oinstall  2913 Mar 21 23:24 README.txt

OPatch_bkp:

total 80

drwxr-xr-x 3 oracle oinstall  4096 Aug 20 00:54 crs

drwxr-xr-x 2 oracle oinstall  4096 Aug 20 00:54 docs

-rw-r--r-- 1 oracle oinstall 23695 Aug 20 00:54 emdpatch.pl

drwxr-xr-x 2 oracle oinstall  4096 Aug 20 00:54 fmw

drwxr-xr-x 2 oracle oinstall  4096 Aug 20 00:54 jlib

drwxr-xr-x 2 oracle oinstall  4096 Aug 20 00:54 ocm

-rwxr-xr-x 1 oracle oinstall 22150 Aug 20 00:54 opatch

-rw-r--r-- 1 oracle oinstall    49 Aug 20 00:54 opatch.ini

-rw-r--r-- 1 oracle oinstall  2590 Aug 20 00:54 opatch.pl

drwxr-xr-x 4 oracle oinstall  4096 Aug 20 00:54 opatchprereqs

Step2

And remove the contents from the OPatch  directory and 

cd $ORACLE_HOME/OPatch

rm -rf *

Step3

unzip the p6880880_112000_Linux-x86-64.zip in the oracle home and the grid home where we need the latest version of the OPatch

make sure you are in the ORACLE_HOME and the unzip the OPatch

unzip /home/oracle/p6880880_112000_Linux-x86-64.zip

Step4

Check the verion of the OPatch

[oracle@fahdb ~]$ /u01/app/oracle/oracle/product/11.2.0/dbhome_1/OPatch/opatch version

OPatch Version: 11.2.0.3.0

OPatch succeeded.

NOTE:

The above mentioned steps are normal process of upgrading the Opatch please read the latest patch README according to nay specific change for that patch  

Creating the OCM Response file [ocm.rsp]

Step 1
we need to create the response file for the oracle configuration manager if you have installed on your system

Go to the Opatch directory and then find the ocm/bin

[oracle@fahdb bin]$ pwd
/u01/app/oracle/oracle/product/11.2.0/dbhome_1/OPatch/ocm/bin

[oracle@fahdb bin]$ ls
emocmrsp

Step2

Run the emocmrsp to generate a new response file 

[oracle@fahdb bin]$ ./emocmrsp                                                

  OCM Installation Response Generator 10.3.4.0.0 - Production                   

  Copyright (c) 2005, 2010, Oracle and/or its affiliates.  All rights reserved.                                                                              

  Provide your email address to be informed of security issues, install and  initiate Oracle Configuration Manager. Easier for you if you    use your My Oracle Support Email address/User Name. Visit http://www.oracle.com/support/policies.html for details.                    Email address/User Name:  bpalaneandavar@a-bits.biz

Password (optional):                            

 The OCM configuration responsefile (ocm.rsp) was successfully created

Step3
Check the File has been created on the same location
[oracle@fahdb bin]$ ll                                                      
 total 16                                                                    
 -rwxrw---- 1 oracle oinstall 9063 Nov 27  2009 emocmrsp                    
 -rw-r--r-- 1 oracle oinstall 2969 Aug 20 11:45 ocm.rsp                      

NOTE:
we can use the same response file for different patchs if you MOS details are changed then you can proceed with creating the new ocm.rsp file

Applying the PSU patches according the  version  we have the source as 11.2.0. 2 and to be upgraded to 11.2.0.3 

we are applying the patch on 11.2.0.2 home [both the grid and the oracle home] we are applying the patch 12539000 as the pre reqiust

For grid apply the patch as the root 

Check the oracle HAS  is running in the system if not the patch will fail HAS should be up and running for applying the patch
any database which is using the ASM should be shutdown The LISTENER,ASM,CRS shoud be up for applying the patch


[root@fahdb 12539000]# /u01/app/oracle/grid/11.2.0/grid/OPatch/opatch auto /home/grid/12539000/ -oh /u01/app/oracle/grid/11.2.0/grid/
Executing /usr/bin/perl /u01/app/oracle/grid/11.2.0/grid/OPatch/crs/patch112.pl -patchdir /home/grid -patchn 12539000 -oh /u01/app/oracle/grid/11.2.0/grid/ -paramfile /u01/app/oracle/grid/11.2.0/grid/crs/install/crsconfig_params
opatch auto log file location is /u01/app/oracle/grid/11.2.0/grid/OPatch/crs/../../cfgtoollogs/opatchauto2012-08-20_00-27-44.log
Detected Oracle Restart install
Using configuration parameter file: /u01/app/oracle/grid/11.2.0/grid/crs/install/crsconfig_params
OPatch  is bundled with OCM, Enter the absolute OCM response file path:
/u01/app/oracle/grid/11.2.0/grid/OPatch/ocm/bin/ocm.rsp
Enter 'yes' if you have unzipped this patch to an empty directory to proceed  (yes/no):yes
Clusterware is either  not running or not configured. You have the following 2 options
1. Configure and Start the Clusterware on this node and re-run the tool
2. or Run the tool with the -och <CRS_HOME_PATH> option and then invoke  tool with -oh <comma seperated ORACLE_HOME_LIST> to patch the RDBMS home

[grid@fahdb ~]$ crsctl start has

CRS-4123: Oracle High Availability Services has been started.

[grid@fahdb ~]$ crsctl status resource -t

--------------------------------------------------------------------------------

NAME           TARGET  STATE        SERVER                   STATE_DETAILS

--------------------------------------------------------------------------------

Local Resources

--------------------------------------------------------------------------------

ora.DATA.dg

               ONLINE  ONLINE       fahdb

ora.FLASH.dg

               ONLINE  ONLINE       fahdb

ora.LISTENER.lsnr

               ONLINE  ONLINE       fahdb

ora.asm

               ONLINE  ONLINE       fahdb                    Started

ora.ons

               OFFLINE OFFLINE      fahdb

--------------------------------------------------------------------------------

Cluster Resources

--------------------------------------------------------------------------------

ora.cssd

      1        ONLINE  ONLINE       fahdb

ora.diskmon

      1        ONLINE  ONLINE       fahdb

ora.evmd

      1        ONLINE  ONLINE       fahdb

ora.fahdb.db

      1        OFFLINE OFFLINE

[root@fahdb 12539000]# /u01/app/oracle/grid/11.2.0/grid/OPatch/opatch auto /home/grid/12539000/ -oh /u01/app/oracle/grid/11.2.0/grid/

Executing /usr/bin/perl /u01/app/oracle/grid/11.2.0/grid/OPatch/crs/patch112.pl -patchdir /home/grid -patchn 12539000 -oh /u01/app/oracle/grid/11.2.0/grid/ -paramfile /u01/app/oracle/grid/11.2.0/grid/crs/install/crsconfig_params

opatch auto log file location is /u01/app/oracle/grid/11.2.0/grid/OPatch/crs/../../cfgtoollogs/opatchauto2012-08-20_00-56-16.log

Detected Oracle Restart install

Using configuration parameter file: /u01/app/oracle/grid/11.2.0/grid/crs/install/crsconfig_params

OPatch  is bundled with OCM, Enter the absolute OCM response file path:

/u01/app/oracle/grid/11.2.0/grid/OPatch/ocm/bin/ocm.rsp

Enter 'yes' if you have unzipped this patch to an empty directory to proceed  (yes/no):yes

The opatch minimum version  check for patch /home/grid/12539000/etc failed  for /u01/app/oracle/grid/11.2.0/grid

The opatch minimum version  check for patch /home/grid/12539000/files failed  for /u01/app/oracle/grid/11.2.0/grid

Opatch version check failed for oracle home  /u01/app/oracle/grid/11.2.0/grid

Opatch version  check failed

update the opatch version for the failed homes and retry

Check the version of the opatch 

[root@fahdb 12539000]# /u01/app/oracle/grid/11.2.0/grid/OPatch/o

ocm/            opatch          opatch.bat      opatchdiag      opatchdiag.bat  opatchprereqs/  oplan/

[root@fahdb 12539000]# /u01/app/oracle/grid/11.2.0/grid/OPatch/opatch version

OPatch Version: 11.2.0.3.0

OPatch succeeded.

As the patch need the version higher that the 11.2.0.1 we are with the with the latest version the the patch fails then we need  apply the patch manually

Steps for applying the Patch 12539000 manually 

Unlock the grid from the root

[root@fahdb grid]# cd crs/install/

[root@fahdb install]# ls

cmdllroot.sh             crsconfig_params      crspatch.pm    install.excl        onsconfig      preupdate.sh  rootofs.sh                 s_crsconfig_lib.pm

crsconfig_addparams.sbs  crsconfig_params.sbs  hasdconfig.pl  install.incl        oracss.pm      rootcrs.pl    s_crsconfig_defs

crsconfig_lib.pm         crsdelete.pm          inittab        installRemove.excl  paramfile.crs  roothas.pl    s_crsconfig_fahdb_env.txt

[root@fahdb install]# ./roothas.pl -unlock

Using configuration parameter file: ./crsconfig_params

CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'fahdb'

CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'fahdb'

CRS-2673: Attempting to stop 'ora.DATA.dg' on 'fahdb'

CRS-2673: Attempting to stop 'ora.FLASH.dg' on 'fahdb'

CRS-2673: Attempting to stop 'ora.evmd' on 'fahdb'

CRS-2677: Stop of 'ora.FLASH.dg' on 'fahdb' succeeded

CRS-2677: Stop of 'ora.DATA.dg' on 'fahdb' succeeded

CRS-2673: Attempting to stop 'ora.asm' on 'fahdb'

CRS-2677: Stop of 'ora.asm' on 'fahdb' succeeded

CRS-2673: Attempting to stop 'ora.cssd' on 'fahdb'

CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'fahdb' succeeded

CRS-2677: Stop of 'ora.cssd' on 'fahdb' succeeded

CRS-2673: Attempting to stop 'ora.diskmon' on 'fahdb'

CRS-2677: Stop of 'ora.evmd' on 'fahdb' succeeded

CRS-2677: Stop of 'ora.diskmon' on 'fahdb' succeeded

CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'fahdb' has completed

CRS-4133: Oracle High Availability Services has been stopped.

Successfully unlock /u01/app/oracle/grid/11.2.0/grid

When you unlock it it will bring down Oracle has[crs]

login with the grid owner and the apply the patch manually

$ORACLE_HOME/OPatch/opatch apply -oh <the oracle home to be patched> -local <patch dir>

                          

 [grid@fahdb 12539000]$ /u01/app/oracle/grid/11.2.0/grid/OPatch/opatch napply -oh /u01/app/oracle/grid/11.2.0/grid -local /home/oracle/12539000                

Oracle Interim Patch Installer version 11.2.0.3.0                            

Copyright (c) 2012, Oracle Corporation.  All rights reserved.                                                                                                                                                                                   Oracle Home       : /u01/app/oracle/grid/11.2.0/grid                            

Central Inventory : /u01/app/oracle/oraInventory                                  

 from           : /u01/app/oracle/grid/11.2.0/grid/oraInst.loc                

OPatch version    : 11.2.0.3.0              

OUI version       : 11.2.0.2.0                                                 

Log file location : /u01/app/oracle/grid/11.2.0/grid/cfgtoollogs/opatch/opatch2012-08-20_02-03-58AM_1.log                                                                                                                                       Verifying environment and performing prerequisite checks...                    

OPatch continues with these patches:   12539000                                                                                                               

Do you want to proceed? [y|n]                                               

 Y                                                                              

User Responded with: Y

All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/app/oracle/grid/11.2.0/grid')

Is the local system ready for patching? [y|n]

y

User Responded with: Y

Backing up files...

Applying interim patch '12539000' to OH '/u01/app/oracle/grid/11.2.0/grid'

Patching component oracle.rdbms, 11.2.0.2.0...

Verifying the update...

Patch 12539000 successfully applied.

Log file location: /u01/app/oracle/grid/11.2.0/grid/cfgtoollogs/opatch/opatch2012-08-20_02-03-58AM_1.log

OPatch succeeded.

[grid@fahdb 12539000]$

Login as the oracle database owner and apply the patch mannulay

[oracle@fahdb ~]$  /u01/app/oracle/oracle/product/11.2.0/dbhome_1/OPatch/opatch napply -oh /u01/app/oracle/oracle/product/11.2.0/dbhome_1 -local /home/oracle/12539000  

Oracle Interim Patch Installer version 11.2.0.3.0

Copyright (c) 2012, Oracle Corporation.  All rights reserved.

Oracle Home       : /u01/app/oracle/oracle/product/11.2.0/dbhome_1

Central Inventory : /u01/app/oracle/oraInventory

 from           : /u01/app/oracle/oracle/product/11.2.0/dbhome_1/oraInst.loc

 OPatch version    : 11.2.0.3.0

 OUI version       : 11.2.0.2.0

  Log file location : /u01/app/oracle/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2012-08-20_02-09-37AM_1.log

Verifying environment and performing prerequisite checks...

OPatch continues with these patches:   12539000

Do you want to proceed? [y|n]

y

User Responded with: Y

All checks passed.

Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.

(Oracle Home = '/u01/app/oracle/oracle/product/11.2.0/dbhome_1')

Is the local system ready for patching? [y|n]

y

User Responded with: Y

Backing up files...

Applying interim patch '12539000' to OH '/u01/app/oracle/oracle/product/11.2.0/dbhome_1'

Patching component oracle.rdbms, 11.2.0.2.0...

Verifying the update...

Patch 12539000 successfully applied.

Log file location: /u01/app/oracle/oracle/product/11.2.0/dbhome_1/cfgtoollogs/opatch/opatch2012-08-20_02-09-37AM_1.log

OPatch succeeded.

[oracle@fahdb ~]$

Now we had applied the patch in oracle home and the grid home successfully again we have to lock the roor user by running the scripts

For database

As the root user we need to lock the rdbms first by running the rootadd_rdbms.sh

move to the directory rdbms install and you can find the script 

cd /u01/app/oracle/grid/11.2.0/grid/rdbms/nstall

[root@fahdb install]# ls

config_filemap.sbs  filemap.ora  install.excl  rdbms  rootadd_filemap.sh  rootadd_rdbms.sh  sbs

 [root@fahdb install]# ./rootadd_rdbms.sh

For Grid

[root@fahdb install]# pwd

/u01/app/oracle/grid/11.2.0/grid/crs/install

[root@fahdb install]# ls

cmdllroot.sh             crsconfig_params      crspatch.pm    install.excl        onsconfig      preupdate.sh  rootofs.sh              s_crsconfig_lib.pm crsconfig_addparams.sbs  crsconfig_params.sbs  hasdconfig.pl  install.incl        oracss.pm      rootcrs.pl    s_crsconfig_defs  crsconfig_lib.pm         crsdelete.pm          inittab        installRemove.excl  paramfile.crs  roothas.pl    s_crsconfig_fahdb_env.txt

[root@fahdb install]# ./roothas.pl -patch

Using configuration parameter file: ./crsconfig_params

Undefined subroutine &main::read_file called at crspatch.pm line 86

Error Undefined subroutine &main::read_file

roothas.pl -patch or rootcrs.pl -patch Fails with 'Undefined subroutine' [ID 1268390.1

Step 1

we need to run scrip with the below syntax the perl version which is used by the script is the wrong one so we need to run the script with the blow syntax

$<GRID_HOME>/perl/bin/perl -I$<GRID_HOME>/perl/lib -I$<GRID_HOME>/crs/install $<GRID_HOME>/crs/install/roothas.pl -patch

[root@fahdb install]# which perl

/usr/bin/perl

[root@fahdb install]# /u01/app/oracle/grid/11.2.0/grid/perl/bin/perl -l /u01/app/oracle/grid/11.2.0/grid/perl/lib -l /u01/app/oracle/grid/11.2.0/grid/crs/install/ /u01/app/oracle/grid/11.2.0/grid/crs/install/roothas.pl -patch

Step 2

[root@fahdb install]$ cp crsconfig_lib.pm crsconfig_lib_bkp.pm

[root@fahdb install]$ ls

cmdllroot.sh             crsconfig_lib.pm      crsdelete.pm   inittab       installRemove.excl  paramfile.crs  roothas.pl        s_crsconfig_fahdb_env.txt

crsconfig_addparams.sbs  crsconfig_params      crspatch.pm    install.excl  onsconfig           preupdate.sh   rootofs.sh        s_crsconfig_lib.pm

crsconfig_lib_bkp.pm     crsconfig_params.sbs  hasdconfig.pl  install.incl  oracss.pm           rootcrs.pl     s_crsconfig_defs

[grid@fahdb install]$ vi crsconfig_lib.pm

change the line From  @exp_func = qw(check_CRSConfig validate_olrconfig validateOCR       

                          To    @exp_func = qw(check_CRSConfig validate_olrconfig validateOCR read_file

Step3

Re run the script now

[root@fahdb install]# ./roothas.pl -patch

Using configuration parameter file: ./crsconfig_params

ACFS-9200: Supported

CRS-4123: Oracle High Availability Services has been started.

Now the environment is ready for the upgrading the grid Home

 show parameter memory_max_target which can be upto 1536M  for the safer side 

Kernel Parameters for the Oracle 11g R2 Fusion Applications Database

Configuring the Kernel Parameters according to the requirements of the fusion applications 

To know the kernel parameter which is present in the system user sysctl  command

we have the bellow kernel parameters setting as the default

net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
fs.file-max = 6815744
kernel.msgmni = 2878
kernel.msgmax = 8192
kernel.msgmnb = 65536
kernel.sem = 250 32000 100 142
kernel.shmmni = 4096
kernel.shmall = 1073741824
kernel.shmmax = 4398046511104
kernel.sysrq = 1
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
fs.aio-max-nr = 3145728
net.ipv4.ip_local_port_range = 9000 65500
vm.min_free_kbytes = 51200

To edit the kernel parameters vi /etc/sysctl.conf

The recommended Kernel parameters for the Oracle Fusion Applications Database

Refer to the Link  http://docs.oracle.com/cd/E15586_01/fusionapps.1111/e16684/set_up_db_tier.htm#BABGGIGA

fs.file-max = 6815744

kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
net.core.rmem_default = 4194304
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
tcp.ipv4.tcp_wmem = 262144 262144 262144
tcp.ipv4.tcp_rmem = 4194304 4194304 4194304
fs.aio-max-nr = 1048576
net.ipv4.ip_local_port_range = 9000 65000

Change the parameters according to your environment 

Changing the kernel parameters according to the requirement set the kernel.Shmmax

as to the half of the Physical ram present in your system 

[root@fahtestdb ~]# sysctl -p
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
fs.file-max = 6815744
kernel.msgmni = 2878
kernel.msgmax = 8192
kernel.msgmnb = 65536
kernel.sem = 250 32000 100 142
kernel.shmmni = 4096
kernel.shmall = 4294967296
kernel.shmmax = 88046829568
kernel.sysrq = 1
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
fs.aio-max-nr = 3145728
net.ipv4.ip_local_port_range = 9000 65500
vm.min_free_kbytes = 51200
net.ipv4.tcp_wmem = 262144 262144 262144
net.ipv4.tcp_rmem = 4194304 4194304 4194304

Requirements for Installing Oracle 11g R2 Fusion Applications Database

The fusion applications has Four  database [including one optional data ware house database]
In the fusion applications oracle had come up with two database for the OAM[single sign on] and the OID [oracle internet directory]
now the user details are stored in the separate database not in the transnational database which holds the real data
The User's transitional data or stores in the fusion applications database
There is a fourth optional database known as the datawarehoue database for the fusion applications when you are using the fusion applications BI
[1]Fusion applications transaction database

Holds the schema's of the different domains in which all the translation data's are stored

[2]Oracle Identity management 

In the identity management category oracle has two database

[1] OID database which holds the data of the oracle internet directory
[3]OAM database which holds the data of the oracle access mangement

[4]Fusion data warehouse database --- Optional database when you are using Bi with fusion then we need to install this Db

If you are using the BI with the fusion applications then we need to install the fusion data warehouse  database or you can use OTBI which comes along with the fusion applications

It is recommended to go with the three server architecture with out datawarehouse database

Server 1 

Which holds the fusion application database 

Server 2

Which hold's the oracle Identity management database's [OID and OAM] with the IDM web logic middle ware

Server 3

Which holds the fusion applications 

It can be done with the two server arrchicture as we can install the IDM database and the Fusion application database and the IDM web logic in the single server  and fusion applications in the another server

Check the prerequisits for creating the fusion app database and the idm database

1] Create the fully qualified Host name

login to the root and check the /etc/hosts file for the fully qualified hostname with the IP

[root@fah]# vi /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1            localhost.localdomain localhost
::1                      localhost6.localdomain6 localhost6
<ip number>     fahtestdb.<domain_name>.com fahtestdb

and save the hosts file 

2]Before installing The database conform the O/S archicture 

To know the archicture type uname -a

[root@fah ~]# uname -a
Linux fahtestdb.oasiserp.com 2.6.18-194.el5 #1 SMP Mon Mar 29 22:10:29 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux

here we are using the x86_64 bit archicture system for installing and database 

To know the releease of the linux type  $ lsb_release -id

[root@fah ~]# lsb_release -id
Distributor ID: EnterpriseEnterpriseServer
Description:    Enterprise Linux Enterprise Linux Server release 5.5 (Carthage)

To know the kernal which is installed

[root@fah ~]# uname -r
2.6.18-194.el5

3] Rpm's required for the oracle database in the linux x86-64

These are the rpm's which is mandatory to install the oracle database in the Linux environment  the Rpm version numbers may slightly change according to the Linux version you are using

1] binutils-2.17.50*
2] compat-libstdc++-33-3.2.3-61*
3] elfutils-libelf-*
4]  glibc-2.5-81.el5_8.2.
5] glibc-common-2.5-81.el5_8.2.
6] ksh-20100621-5.el5_8.1
7] libaio-0.3.106-5.x86_64
8] libgcc-4.1.2-52.el5_8.1
9] libstdc++-4.1.2-52.el5_8.1
10]libstdc++44-devel.x86_64

11]glibc-headers-2.5-81.el5_8.2.x86_64

12] sysstat-7.0.2-11.el5.x86_64

13] unixODBC-devel-2.2.11-10.el5

14]unixODBC-2.2.11-10.el5

15]unixODBC-libs-2.2.11-10.el5

16]gcc-c++-4.1.2-52.el5_8.1.x86_64

17]kernel-headers.x86_64

18] glibc-devel-2.5-81.el5_8.2.

19] libgomp-4.4.6-3.el5.1

20] make-3.81-3.el5.x86_64 

21]openmotif22-2.2.3-20
22]openmotif-2.3.1-6.1.el5_8
23]xorg-x11-utils

Query to conform all the rpms are installed 

rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" | grep <rpm name>

1]   rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep binuti

binutils-2.17.50.0.6-20.el5_8.3 (x86_64)
binutils-devel-2.17.50.0.6-20.el5_8.3 (i386)
binutils-devel-2.17.50.0.6-20.el5_8.3 (x86_64)
binutils220-2.20.51.0.2-5.29.el5 (x86_64)

2]   rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep compat-libstdc++
compat-libstdc++-33-3.2.3-61 (x86_64)
compat-libstdc++-33-3.2.3-61 (i386)
compat-libstdc++-296-2.96-138 (i386)

3]   rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep elfutils-libelf-
elfutils-libelf-devel-0.137-3.el5 (x86_64)
elfutils-libelf-0.137-3.el5 (x86_64)
elfutils-libelf-devel-static-0.137-3.el5 (i386)
elfutils-libelf-0.137-3.el5 (i386)
elfutils-libelf-devel-0.137-3.el5 (i386)
elfutils-libelf-devel-static-0.137-3.el5 (x86_64)

4]   rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep glibc-2.5-81.el5_8.2
glibc-2.5-81.el5_8.2 (x86_64)
glibc-2.5-81.el5_8.2 (i686)

5]   rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep glibc-common

glibc-common-2.5-81.el5_8.2 (x86_64)

6]  rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep ksh

ksh-20100621-5.el5_8.1 (x86_64)

7] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep libaio-
libaio-0.3.106-5 (x86_64)
libaio-devel-0.3.106-5 (i386)
libaio-devel-0.3.106-5 (x86_64)
libaio-0.3.106-5 (i386)

8] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep libgcc

libgcc-4.1.2-52.el5_8.1 (x86_64)

libgcc-4.1.2-52.el5_8.1 (i386)

compat-libgcc-296-2.96-138 (i386)

9] and [10] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep libstdc++

libstdc++-4.1.2-52.el5_8.1 (i386)

libstdc++-devel-4.1.2-52.el5_8.1 (i386)

compat-libstdc++-33-3.2.3-61 (x86_64)

compat-libstdc++-33-3.2.3-61 (i386)

compat-libstdc++-296-2.96-138 (i386)

libstdc++-devel-4.1.2-52.el5_8.1 (x86_64)

libstdc++44-devel-4.4.6-3.el5.1 (x86_64)

libstdc++-4.1.2-52.el5_8.1 (x86_64)

libstdc++44-devel-4.4.6-3.el5.1 (i386)

11] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep glibc-headers

glibc-headers-2.5-81.el5_8.2 (x86_64)

12] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep sysstat-

sysstat-7.0.2-11.el5 (x86_64)

13] [14] [15]rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep unixODBC

unixODBC-devel-2.2.11-10.el5 (x86_64)

unixODBC-2.2.11-10.el5 (x86_64)

unixODBC-libs-2.2.11-10.el5 (x86_64)

unixODBC-2.2.11-10.el5 (i386)

unixODBC-libs-2.2.11-10.el5 (i386)

unixODBC-devel-2.2.11-10.el5 (i386)

16] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep gcc-c++

gcc-c++-4.1.2-52.el5_8.1 (x86_64)

17] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep kernel-headers

kernel-headers-2.6.18-308.8.2.0.1.el5 (x86_64)

18]rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep glibc-devel

glibc-devel-2.5-81.el5_8.2 (i386)

glibc-devel-2.5-81.el5_8.2 (x86_64)

19] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep libgomp

libgomp-4.4.6-3.el5.1 (i386)

libgomp-4.4.6-3.el5.1 (x86_64)

20] rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep make

make-3.81-3.el5 (x86_64)

21] [22]  rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep openmotif
openmotif22-2.2.3-20 (x86_64)
openmotif-devel-2.3.1-6.1.el5_8 (x86_64)
openmotif22-2.2.3-20 (i386)
openmotif-devel-2.3.1-6.1.el5_8 (i386)
openmotif-2.3.1-6.1.el5_8 (i386)
openmotif-2.3.1-6.1.el5_8 (x86_64)

23]  rpm -qa --queryformat "%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n" |grep xorg-x11-utils
xorg-x11-utils-7.1-2.fc6 (x86_64)

If any of the rpm's are not installed then use the yum install to install the particular rpm and check again 

for an  example here we have installed the libstdc++* .. like wise you need to install all the rpm's which are not installed  in your environment  for installing the Public yum please check the previous post   http://orafapp.blogspot.com/2012/06/creating-public-yum-repositiry-for.html

For more information Regarding the different versions of operating system requirements refer to the below link
http://docs.oracle.com/html/E18558_01/fusion_requirements.htm#CHDGICGE
Requirements for Installing Oracle 11gR2 RDBMS on RHEL (and OEL) 5 on AMD64/EM64T [ID 880989.1]

4] creating the O/S user and groups for the necessary installation

Here we explained the structure for the two node and the three node arrchicture for the fusion applications

for three node arch                                                                   For two node arch

server1    [node1]                                                                                Server1 [node1]

fusion database                                                          Fusion database,IDM database's IDMDomain

server2    [node2]                                                                                Server2 [node2]

IDM database's and IDM domain                             Fusion Applications

server3    [node3]

Fusion applications

Creating o/s username and group's for the fusion applications database

1] oracle fusion applications database
2]Oracle OID database
3]Oracle Access manager database
  
Creating the Group names
groupadd  oinstall
groupadd  dba  
we have create two groups know as the oinstall and the dba the oinstall will be the primary group and the dba will be the secondary group for the database's

If you are suing the ASM  create the asm groups

groupadd   asmadmin
groupadd   asmoper
groupadd   asmoper
if you are using the file system ignore this groups

To Create Users for the database

useradd grid         -g   oinstall -G  dba, asmoper, asmadmin ,asmdba  -- [if you are using the asm]
useradd oraidm    -g   oinstall -G  dba       --[IDM database o/s user]
useradd oraoam   -g    oinstall -G  dba       --[OAM database o/s user]
useradd oracle      -g   oinstall -G  dba       --[fusiondb database o/s user]
useradd  fmwidm  -g oinstall -G dba     --[oraweblogic IDM Domain o/s user]
useradd orafapp        -g oinstall -G dba    --[fusion applications username]

The small g is used to specify the primary group of the user and the G is used to specify the Other groups which the user is assigned to 


[root@fa ~]# id oraidm
uid=54322(oraidm) gid=54321(oinstall) groups=54321(oinstall),54322(dba)
[root@fa ~]# id oraoam
uid=54323(oraoam) gid=54321(oinstall) groups=54321(oinstall),54322(dba)

[root@fa ~]# id oracle

uid=54321(oracle) gid=54321(oinstall) groups=54321(oinstall),54322(dba)

[root@fa~]# id grid
uid=54324(grid) gid=54321(oinstall)groups=54321(oinstall),54322(dba),54333(asmadmin),54334(asmdba),54335(asmoper)

If You have the wrong group combinations then use the  usermod command to modify the  user group to match all the remaining users

 usermod -g oinstall -G dba oraoam

5]Creating the Directory and mount to the label and change the owner to the oracle Users 

For creating the directory and mount to the appropriated label please refer to the previous post 

http://orafapp.blogspot.com/2012/06/mounting-partitions-in-oracle-linux.html
http://orafapp.blogspot.com/2012/06/installing-oracle-11gr2-database-in.html


mkdir  /u01/app/oracle -p

mkdir  /u02/app/oracle -p

mkdir  /u03/app/oracle -p

mkdir  /u04/app/oracle -p

There are three directories which is to be owned by the oracle database users here we are going to install three database in the same machine..
and the fourth directory is used to install the IDM Domain

if you are installing with the three servers then you can create only  one directory
/u01/app/oracle in the fusiondb linux box and remaining  three in the IDMbox


chown command is used to change the owner of the particular directory or file

Server 1
[root@fah ~]# chown oracle:oinstall   /u01/app/oracle       --[Installing Location of the Fusionapp db]
[root@fah ~]# chown oraidm:oinstall /u02/app/oracle       --[Installing Location of OID   db]
[root@fah ~]# chown oraoam:oinstall /u03/app/oracle      --[Installing Location of OAM db]

[root@fah ~]# chown orafmw:oinstall /u04/app/oracle      --[Installing Location Of IDM Domain]
Server 2 [for fusion applications installation]
[root@fah ~]#chown orafapp:oinstall  /u05/app/oracle      -- [Installation location of the fusion applications ]

chmod command is used to change the file permissions to the file system 

we have to assign  the write permission to the group for all the user's 

[root@fah]# cd /u01/app

[root@fah]# chmod 765 oracle

[root@fah]# cd /u02/app

[root@fah]# chmod 765 oracle

[root@fah]# cd /u03/app

[root@fah]# chmod 765 oracle

[root@fah]# ll /u0*/app

 

now the owner has the full access read write and execute to the file system and the group had the read and write and other's has read and execute 

6] Open file Limits for the users

To set the open file limits go the /etc/security/limites.conf

Set the open below parameters in the limites .conf we can use the wild card to match multiple users when we are installing the fusion applications

*     soft     nproc         131072
*     hard     nproc         131072
*     soft     nofile        327679
*     hard     nofile        327679
*     soft     stack         131072

7] Init Parameters for the fusion applications database

[1]  audit_trail                                  string      NONE

Desc :audit trail is set to be none for disable the database auditing

[2]  plsql_code_type                       string      NATIVE

Desc: we need to set the value to the NATIVE PL/SQL library units (with the possible exception of top-level anonymous PL/SQL blocks) will be compiled to native (machine) code. Such modules will be executed natively without incurring any interpreter overhead.

[3]  nls_sort                                    string          BINARY

Desc :Setting NLS_SORT to anything other than BINARY causes a sort to use a full table scan, regardless of the path chosen by the optimizer. BINARY is the exception because indexes are built according to a binary order of keys. Thus the optimizer can use an index to satisfy the ORDER BY clause when NLS_SORT is set to BINARY. If NLS_SORT is set to any linguistic sort, the optimizer must include a full table scan and a full sort in the execution plan Nls_sort is set to Binary for the improved performance of the ORDER BY quires

[4]open_cursors                              integer     1000

Desc: OPEN_CURSORS specifies the maximum number of open cursors (handles to private SQL areas) a session can have at once. You can use this parameter to prevent a session from opening an excessive number of cursors ..no of Cursors open is set to be 500 to 1000 according to you environment

[5]session_cached_cursors               integer     1000


DESC :  Recommended value for the parameter is 500 to 1000 according to the env 
Specifies the number of session cursors to cache. Repeated parse calls of the same SQL statement cause the session cursor for that statement to be moved into the session cursor cache. Subsequent parse calls find the cursor in the cache and do not reopen the cursor. Oracle uses a least recently used algorithm to remove entries in the session cursor cache to make room for new entries when needed.This parameter also constrains the size of the PL/SQL cursor cache that PL/SQL uses to avoid having to re-parse as statements are re-executed by a user

[6] processes                            integer     5000

Desc : The recommended vale for the process is 5000 for fusion database and 2500 for idm database's
Sets the maximum number of operating system processes that can be connected to Oracle concurrently. The value of this parameter must account for Oracle background processes. SESSIONS parameter is deduced from this value
[7]star_transformation_enabled          string      FALSE

Desc recommended value is False Determines whether a cost-based query transformation will be applied to star queries

[8] query_rewrite_integrity              string      enforced


Desc QUERY_REWRITE_INTEGRITY determines the degree to which Oracle must enforce query rewriting. At the safest level, Oracle does not use query rewrite transformations that rely on unenforced relationships.
Determines whether a cost-based query transformation will be applied to star queries
we need to set the value as Enforced  as it  guarantees consistency and integrity


[9]parallel_max_servers                 integer     640

Desc :PARALLEL_MAX_SERVERS specifies the maximum number of parallel execution processes and parallel recovery processes for an instance. As demand increases, Oracle increases the number of processes from the number created at instance start up up to this value. we need to specify the value as 640 in the fusion applications  

[10] job_queue_processes                  integer     100

Desc Specifies the maximum number of job slaves per instance that can be created for the execution of DBMS_JOB jobs and Oracle Scheduler (DBMS_SCHEDULER) jobs the recommended value is 10 to 100

[11]_b_tree_bitmap_plans                 boolean     FALSE

Desc we need to set the value as false we are setting to false for the improved performance with the sql quries

[12]_fix_control                         string      5483301:OFF, 6708183:ON

Desc we need to specify the two values one is OFF and another is ON

[13] sga_target                           big integer 18

Desc The suggested value for an Oracle Fusion Applications Starter database is 9 GB

[14]pga_aggregate_target                 big integer 8G

Desc The suggested value for an Oracle Fusion Applications Starter database is 4 GB