Upgrade 11.1.0.7 to 11.2.0.3 on R12

SELF NOTES: Upgrade 11.1.0.7 to 11.2.0.3 on R12

1. Install Oracle 11.2.0.3 software only, and follow installing the examples CD.

2. Copy the 11.1.0.7 old necessary binary file to the new 11.2.0.3 files, they are:

                - init file from dbs (edit and replance env to new home)

                - copy the appsutil directory (edit and replance env to new home)

                - copy the network/admin/<Context_name> (edit and replance env to new home)

                - copy the env file (edit and replance env to new home)

3. Apply the AD patches.

8919489 

9062910 

9738085 

9852070 

9868229

10163753 

11071569 

12686610 

4. From AD_TOP/bin directory create the appsutil directory for DB and then FTP/Copy and unzip –o to the database 11.2.0.3

5. On 11.2.0.3 home, apply additional 11.2.0.3 RDBMS patches :

Apply the following patches (OPATCH) for all UNIX/Linux platforms:

NOTE: Do not run any of the post install instructions as those will be done after the upgrade.

a) 4247037

cd $ORACLE_HOME/md/admin

connect to the database using sqlplus / as sysdba

sqlplus> @catmgdidcode

b) 9858539

Run following files as sysdba

cd $ORACLE_HOME/rdbms/admin

@catnomtt.sql

@catnomta.sql

@dbmsmeta.sql

@dbmsmeti.sql

@dbmsmetu.sql

@dbmsmetb.sql

@dbmsmetd.sql

@dbmsmet2.sql

@catmeta.sql

@prvtmeta.plb

@prvtmeti.plb

@prvtmetu.plb

@prvtmetb.plb

@prvtmetd.plb

@prvtmet2.plb

@catmet2.sql

-- recompile dbms_metadata_int to enable the diffing code

alter package dbms_metadata_int compile plsql_ccflags = 'ku$xml_enabled:true';

-- recompile dbms_metadata_util to enable the xmlschema load code

alter package dbms_metadata_util compile plsql_ccflags = 'ku$xml_enabled:true';

c) 12942119

d) 12960302

e) 12985184

f) 13001379

connect / as sysdba

execute sys.dbms_metadata_util.load_stylesheets;

g) 14275605 (will be rollback: 9858539)

cd $ORACLE_HOME/rdbms/admin

sqlplus /nolog

SQL> CONNECT / AS SYSDBA

SQL> STARTUP

SQL> @catbundle.sql psu apply

SQL> QUIT

3343438  13696216  13923374  14275605

h) 13004894

i) 13258936

cd $ORACLE_HOME/ctx/admin/ctxpatch/

sqlplus / as sysdba

@ctxpatch11203.sql

j) 13366268

 ALTER SESSION SET CURRENT_SCHEMA=CTXSYS

@/ctx/admin/drisgp.plb

@/ctx/admin/drvddl.plb

@/ctx/admin/drvxtab.plb

6.Run utlu112isql.

- Source the 11.1.0.7 db envplsql_native_library_dir

- Shutdown the listener

- Copy the file /11.2.0/rdbms/admin/utlu112i.sql to a different location ‘/usr/tmp/’

- Run the script as sysdba, ensuring the output is spooled to a file.

                        - Increase sysaux tablespace 600mb

                        - comment out parameters: plsql_native_library_dir, plsql_native_library_subdir_count

                        - purge dba_recyclebin;

                        - Follow all recommendations.

7. Shutdown Application Server and DB listener.

8. Ensure in /etc/oratab file the OLD Oracle home and sid is set.

9. Ensure no ENV file is set and Invoke DBUA from 11.2.0.3 home/bin:

 ./dbua -initParam "_disable_fast_validate=TRUE"

10. Source the 11.1.0.7 DB env file, and then:

Go to 11.2.0.3 ORACLE_HOME/nls/data/old

Run “perl cr9idata.pl”

11. Correct sqlplus issue on DB tier (ORA_TZFILE)

Connecting sqlplus will give you error:

SP2-1503: Unable to initialize Oracle call interface

SP2-0152: ORACLE may not be functioning properly

                        Edit the 11.2.03.Oracle_home/appsutil/script/$CONTEXT_NAME/adautocfg.sh

                        Replace 11.1.0 with 11.2.0

11. Run all the post installation steps as per instruction no. 5

12. Run the utlrp.sql and verify the invalid objects.

  

13. Source DB environment file and run scripts:

sqlplus / as sysdba @$APPL_TOP/admin/adgrants.sql apps

sqlplus apps/apps @$AD_TOP/patch/115/sql/adctxprv.sql manager CTXSYS

exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');

sqlplus apps/apps @$FND_TOP/patch/115/sql/wfaqupfix.sql apps apps

14. Run DB autoconfig.

15. Gather SYS statistics

sqlplus "/ as sysdba"

alter system enable restricted session;

sqlplus / as sysdba @$APPL_TOP/admin/adstats.sql

alter system disable restricted session;

16. Recreate grants and synonyms.

17. Check the DB alert log file

18. Restart the EBS instance

ERROR : Timed out( 100000 ): Interrupted Exception.Error Starting adoacorectl.sh

Executing service control script: /u01/finsys/inst/apps/PROD_ebstest/admin/scripts/adoacorectl.sh start script returned: **************************************************** ERROR : Timed out( 100000 ): Interrupted Exception You are running adoacorectl.sh version 120.13 Starting OPMN managed OACORE OC4J instance... ****************************************************

Solution 1:
delete all .lock files from the below directory subtrees:
$INST_TOP/ora/10.1.3/j2ee/forms/persistence/forms_default_group_1/
$INST_TOP/ora/10.1.3/j2ee/oacore/persistence/oacore_default_group_1/
$INST_TOP/ora/10.1.3/j2ee/oafm/persistence/oafm_default_group_1/


Solution 2:
If not resolved, follow the below timeout workaround from Oracle:
The timeout value is defined in the $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml file   There are three entries to be concerned about, one for each of the managed OC4J containers (oacore, forms and oafm).  The entry is shown below the appropriate "process-type id=" section and looks like shown below by default:-
<start timeout="600" retry="2"/>
Modifying the timeout value from "600" to "1800" may resolve the timeout error . You can only set it for entry “process-type id="oacore"”
or all entries giving timeout errors

MOD_OC4J: FAILED TO FIND A FAILOVER OC4J PROCESS FOR SESSION REQUEST FOR DESTINATION: APPLICATION://FORMS (NO ISLAND OR JGROUP)

In File $LOG_HOME/ora/10.1.3/Apache/error_log.1363046400, You find the following error

1)

Edit vi $ORA_CONFIG_HOME/10.1.3/opmn/conf/opmn.xml

Find

-Xmx256M -Xms64M -XX:MaxPermSize=128M

Replace

-Xmx512M –Xms256M -XX:MaxPermSize=128M

2)

Restart the opmn service (ADMIN_SCRIPT_HOME/adopmnctl)

Note: restarting opmn will down the user.

Find when was the last schema statistics gathered

For Apps schema :

select count(1)

from apps.fnd_concurrent_programs_vl p , apps.fnd_concurrent_requests r

where r.concurrent_program_id = p.concurrent_program_id

and r.program_application_id = p.application_id

and p.user_concurrent_program_name in (

'OnDemand Gather Schema Statistics',

'Gather Schema Statistics',

'Gather Schema Statistics (IT_ANALYZE)'

)

and (r.phase_code = 'C' and r.status_code= 'C' and r.actual_start_date >= sysdate-7)

/

For Non-Apps schemas :

set pages 0 echo off head off termout off verify off feed off lines 1000

select count(1)

from apps.fnd_concurrent_programs_vl p , apps.fnd_concurrent_requests r

where r.concurrent_program_id = p.concurrent_program_id

and r.program_application_id = p.application_id

and p.user_concurrent_program_name in (

'Gather Statistics for Non-Apps Schema'

)

and (r.phase_code = 'C' and r.status_code= 'C' and r.actual_start_date >= sysdate-7)

Confiiguring E-Business Suite to work on Spfile

1.   By default Oracle E-Business Suite is configured to run on Pfile. In this respective work around to configure    E-Business suite to work on spfile is an indirect way of using spfile through pfile and please note that this is not an officially oracle guided way. Even though this work around was before update in metalink, they have later on removed this. I will not be explaining the advantages the SPFILE has over the PFILE, please do a google on this subject.

       1.) Ensure the database is up and running

          2.) Create spfile from pfile 

   SQL> CREATE SPFILE='/oradata/spfileORCL.ora' from PFILE='/oradata/initORCL.ora'

 3.) Shutdown the database and then modify the pfile:

           SQL> Shutdown immediate

a.       Remove all the entries in the pfile (init<sid>.ora)

b.       Only have the following entry in PFILE, i.e. Location to the SPFILE

                       spfile=/oradata/spfileORCL.ora 




4.   4.) Start the database using the adstrtl.sh in order to start the E-Business Suite (Listener, DB & Apps).

Th    That's it!!! And you are ready to run you Database with the SPFILE... Taking favour of the respective  parameter files advantages.

Checking a file version for Oracle E-Business Suite binaries.

When using Oracle products, there are certain bugs that we might come across time to time and as a result there may raise situation where we are required to raise Oracle Support requests (SR).


When dealing with SRs, support representatives might require us to provide file versions of certain oracle binaries relating to the issue that we require them to help us with. You may issue the following commands in order get the file version:


strings -a <location to the file> | grep -i '$Header'

eg: strings -a $AR_TOP/patch/115/sql/ARXPRECB.pls |grep -i '$Header'

OR

adident Header  <location to the file>
eg: adident Header $AR_TOP/patch/115/sql/ARXPRECB.pls