Upgrade R12.2.0 to R12.2.2   Leave a comment

Upgrade Steps for R12.2.0 to R12.2.2

Configuration Information for R12.2.0 Instance . Its a TWO node Instance with Database and Application running on two separate nodes

NOTE:

If it is a single node install make sure you have atleast 220GB mount point allocated for install and upgrade

Database Server Configuration:

CPU’s:2

RAM:16GB

SGA:12GB

Applications Server Configuration:

CPU’s:2

RAM:16GB

Download R12.2.2 Update Pack Patches from edelivery.oracle.com

when you extract these files you will get a folder 16207672, and 16207673 is online help patch for R12.2.2

patch

Before Upgrade:

Bala_1

Step1:

Reset FND_SQLNET_ACCESS to ALLOW_RESTRICTED

Rapid Install sets the FND_SQLNET_ACCESS profile option to ALLOW_ALL during an installation or upgrade. Peform the following steps to verify the setting of this profile option and reset as needed:

Log in to the application tier and source the environment.

Connect to the database as APPS schema owner.

Execute the following query to determine the current profile setting:

SQL>SELECT profile_option_value FROM fnd_profile_option_values WHERE (application_id,profile_option_id) IN (SELECT application_id,profile_option_id FROM fnd_profile_options WHERE profile_option_name='FND_SQLNET_ACCESS');

If the profile_option_value is already set to ALLOW_RESTRICTED, no further action is necessary:

If the profile_option_value is not set to ALLOW_RESTRICTED, execute the following SQL statement:

UPDATE fnd_profile_option_values SET profile_option_value='ALLOW_RESTRICTED' WHERE (application_id,profile_option_id) IN (SELECT application_id,profile_option_id FROM fnd_profile_options WHERE profile_option_name='FND_SQLNET_ACCESS');

Run AutoConfig on the database tier.

Step2:-

Apply mandatory fs_clone fix – Patch 17064510:R12.TXK.C

$ adop phase=apply patches=17064510 hotpatch=yes
$ adop phase=fs_clone

New Installations (Vision and PROD) Customers:

Apply mandatory Patch 17064510 (17064510:R12.TXK.C) in hotpatch mode on the Run File System.
$ adop phase=apply patches=17064510 hotpatch=yes

Step3:
Create Snapshot

After your installation or upgrade is complete, run the AD Administration Maintain Snapshot option.

Run AD Administration (adadmin).

From the Main Menu, choose Maintain Applications Files > Maintain Snapshot Information.

Select Option 2, Update Current View Snapshot. Then, from the Snapshot submenu, select Option 1, Update Complete APPL_TOP.

Step4:

Required Database and Application Tier Patches

Note: The online process is the preferred method to apply patches to the technology stack components. Refer to My Oracle Support Knowledge Document 1355068.1, Oracle E-Business Suite 12.2 Patching Technology Components Guide.
2.1 Database Patch Checker

If you are upgrading to Release 12.2 using an existing Oracle Database 11.2.0.3 ORACLE_HOME, you must check that you have all the required one-off patches by running the addbptchk.sh script before you run Rapid Install to create the upgrade file system.

The addbptchk.sh script helps you to determine if all the needed one-offs exist in the specified ORACLE_HOME.

To use the script:

Download and unzip the startCD.

Navigate to the startCD/Disk1/rapidwiz/bin directory.

Run the script addbptchk.sh.

Supply the values the script prompts for.

The script provides a list of one-offs that are either missing, or need to be rolled back.

Take the appropriate actions based on the results provided by the script.

An example of script execution is shown below.

$ pwd
/Stage/startCD/Disk1/rapidwiz/bin
$ ./addbptchk.sh Enter the full path of rapidwiz location: /Stage (the directory where startCD dir exists)
Enter $ORACLE_HOME value : /u01/oracle/PROD/11.2.0
Setting ORACLE_HOME to : /u01/oracle/PROD/11.2.0
Please confirm this is the correct value [y/n] :y
Enter database SID : PROD
Setting database SID to: PROD
Please confirm this is the correct SID [y/n] :y
Setting database context to: PROD_dbserv
Please confirm this is the correct context [y/n] :y
Looking for database context file /u01/oracle/PROD/11.2.0/appsutil/PROD_dbserv.xml
Please confirm this is the correct file [y/n] :y
Found /u01/oracle/PROD/11.2.0/appsutil/PROD_dbserv.xml...
The DB version is assumed to be 11.2.0.3.
Pre-req Patch Testing Start Phase : Thu Oct 12 11:28:59 PDT 2013
runProcess_1
Rapidwiz location from DB context file is /Stage/startCD46/Disk1/rapidwiz
Rapidwiz location in db context file differs from the value provided.
Using the rapidwiz location /Stage/startCD/Disk1/rapidwiz.
Copying templates to temp area
Executing Perl command:
perl -pi -e 's/txkTopology_R1220_DB11gR2_11202_Patches.xml/txkTopology_R1220_DB11gR2_11203.xml/g' /u01/oracle/PROD/11.2.0/temp/PROD_dbserv/xmldocs/instDB.xml
Copying one-off patches to temp area
Copying /u01/oracle/PROD/11.2.0/temp/PROD_dbserv/DBInstallHome/fnd/html/txkTopology_R1220_DB11gR2.xml to /u01/oracle/PROD/11.2.0/temp/PROD_dbserv/cfgHome
Executing command: /Stage/startCD/Disk1/rapidwiz/jre/Linux_x64/1.6.0/bin/java -cp /u01/oracle/PROD/11.2.0/temp/PROD_dbserv/DBInstallHome/fnd/../j11067593_fnd.zip:/u01/oracle/PROD/11.2.0/temp/PROD_dbserv/DBInstallHome/fnd/java/3rdparty/stdalone/xmlparserv2.zip -Doracle.apps.fnd.txk.env_home=/u01/oracle/PROD/11.2.0/temp/PROD_dbserv -Doracle.apps.fnd.txk.runtime.config=/u01/oracle/PROD/11.2.0/temp/PROD_dbserv/tmp/patch_runtime.xml -Doracle.apps.fnd.txk.AutobuildXML.generate=true -Doracle.apps.fnd.txk.AutobuildXML.file=/u01/oracle/PROD/11.2.0/temp/PROD_dbserv/tmp/patch_build.xml oracle.apps.fnd.txk.config.InstallService
Log Dir = /u01/oracle/PROD/11.2.0/temp/PROD_dbserv/logs [ Format=oracle.apps.fnd.txk.install%g.log ]
Using TXK patch template file :/u01/oracle/PROD/11.2.0/temp/PROD_dbserv/DBInstallHome/fnd/html/txkTopology_R1220_DB11gR2_11203_Patches.xml
Opatch is at the required version
All the required one-offs are not present in Oracle Database Home
Apply the one-offs from the list below that are valid for your platform :
--You will get a list of pre-patches patches that are to be applied----
Resolve the patch conflicts and run the script again to confirm.
FINISHED Pre-req Patch Testing : Thu Oct 14 10:29:24 PDT 2013
Apply the following patches:
17468141 - PL/SQL COMPILATION THROWS ERROR ORA-4063
16924879 - CLEAN UP OBSOLETE ORACLE/QSMA SYNONYMS FROM DB 11.2
17047617 - MERGE REQUEST ON TOP OF 11.2.0.3.0 FOR BUGS 15967134 12657924
17184721 - CLEAN UP OBSOLETE ORACLE/QSMA SYNONYMS POST INSTALL SCRIPT

Step5:
a. Apply Consolidated Seed Table Upgrade Patch 16605855:12.2.0 (required for both VISION and PROD)

Note: This patch is mandatory for both Vision and PROD New Installation Customers. The instructions to apply Patch 16605855 (16605855:12.2.0) on the Run File System are as follows:

b. Stop all Application tier services on the Run File System.

$ sh $ADMIN_SCRIPTS_HOME/adstpall.sh
c. Start up only the Weblogic AdminServer service on the Run File System.
UNIX
$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start
d. Apply seed table upgrade Patch 16605855:12.2.0 on Run File system using adop hotpatch mode.
$ adop phase=apply patches=16605855 hotpatch=yes
d. Start up all Application tier services.
$ sh $ADMIN_SCRIPTS_HOME/adstrtal.sh

Step6:

a. Apply the 12.2.2 AD and TXK Release Update Packs

If you are upgrading from Release 11i, 12.0.x, or 12.1.x to Release 12.2.2 and have already applied the latest AD and TXK Release Update Packs (the same or higher release version than mentioned in this readme), you can skip this section. The minimum required release versions for AD and TXK upgrading to Release 12.2.2 are R12.AD.C.Delta.2 and R12.TXK.C.Delta.2. To apply the Release 12.2.2 AD and TXK Release Update Packs, see Document 1560906.1, Applying the Release 12.2.2 AD and TXK Release Update Packs.

b. Apply the 12.2.2 Suite-Wide Release Update Pack

i) Download and unzip Oracle Applications DBA 12.2.2 Product Release Update Pack (R12.AD.C.Delta.2) , Patch 15955263.

Usage:

a. Create $ORACLE_HOME/appsutil/admin on the database server.

b. Copy the higher version of adgrants.sql (UNIX) to $ORACLE_HOME/appsutil/admin.

c. Set the environment to point to ORACLE_HOME on the database server.

d. Use SQL*Plus to run the script:

UNIX:
$ sqlplus /nolog
SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql APPLSYS

cd 15955263

$ adop phase=prepare

$ adop phase=apply

ii) Download and apply phase for R12.TXK.C.DELTA.2 Patch 15946788.

cd 15946788

$ adop phase=apply

Note: R12.AD.C.DELTA.2 and R12.TXK.C.DELTA.2 must be applied in the same online patching cycle, without merging.

iii) Complete the online patching cycle by running the following commands in the order shown.

$ adop phase=finalize

— Downtime Required Here

$ adop phase=cutover
$ adop phase=cleanup

Having applied the Release 12.2.2 AD and TXK Release Update Packs, you can now proceed to apply the 12.2.2 Suite-Wide Release Update Pack.

1. Start an online patching cycle.
$ adop phase=prepare2.

Apply Oracle E-Business Suite Release 12.2.2 Patch 16207672 and Oracle E-Business Suite Release 12.2.2 Online Help Patch 16207673.
$ adop phase=apply patches=16207672,16207673

or cd 16207672
 adop phase=apply

and 
cd 16207673
adop phase=apply

3. Instantiate the Oracle HTTP Server configuration files ssl.conf and mod_wl_ohs.conf.
a. Source the patch edition environment file:
$ . $PATCH_BASE/EBSapps/appl/APPS$CONTEXT_NAME.env
$ $ADJVAPRG oracle.apps.ad.autoconfig.InstantiateFile \
-e $CONTEXT_FILE \
-d $FND_TOP/admin/driver/ohstmpl.drv \
-tmpl $FND_TOP/admin/template/ssl_conf_FMW.tmp
$ $ADJVAPRG oracle.apps.ad.autoconfig.InstantiateFile \
-e $CONTEXT_FILE \
-d $FND_TOP/admin/driver/ohstmpl.drv \
-tmpl $FND_TOP/admin/template/mod_wl_ohs_conf_FMW.tmp
4. Complete the online patching cycle by running the following commands in the order shown.
a. Source the run edition environment file:
. $RUN_BASE/EBSapps/appl/APPS$CONTEXT_NAME.env
b.$ adop phase=finalize
c.$ adop phase=cutover
d.$ adop phase=cleanup
5. Post-Update Steps

After Upgrade

Bala_2
-------BEFORE YOU EXECUTE BELOW STEP MAKE SURE YOU HAVE atleast 75gb ADDITIONAL FREE SPACE-------------------
 In my case I was already having 100Gb mount point space, After Installation of R12.2.0 the mount is 54GB occupied, 
But after Upgrade this mount got increased to 60GB and when I was executing the below step it error ed out saying 
there is lack of space. and Suggesting me to add another 35GB to the existing mount point. So have atleast 150GB 
mount point space for installation and upgrade of R12.2.2 application.
---------------------------------------------------------------------------------------------------------------

Synchronize file systems:

Synchronize the file systems using the command shown below. This action will copy the new run edition code and configuration to the —-other file system, to help the next online patching cycle complete faster.

$ adop phase=fs_clone

This finishes the Upgrade of R12.2.0 to R12.2.2

Ref:

Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)

Oracle E-Business Suite Applications DBA (AD) Release Notes for Release 12.2 (Doc ID 1376487.1)

 

Advertisements

Posted October 15, 2013 by balaoracledba.com in OracleAppsR12, R12.2

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: