AIM

Application R12.1.3 to R12.2.5 Upgrade

Reference Manual

Contents

Upgrade Target Information3

OS Check3

Clone And Preparation3

Apply Application Interoperability Patches3

Install 11.2.0.4 ORACLE_HOME3

Apply PreUpgrade Database patches3

Preparing Target datatabase 12c4

Upgrade database from 11.2.0.3 to 11.2.0.4.6

Perform DB post upgrade task6

Perform code level check (ETCC) for DB and apply all DB Patches10

Install R12.2.0 file system in upgrade mode12

Apply preinstall Patches14

Apply Consolidated Upgrade Patch19

Take full backup of DB and Application24

Install R12.2.0 to configure the 12.2.025

Oracle E-Business Suite Online Patching26

Perform 12.2.0 Post upgrade task 37

Perform code level check (ETCC) for Application and apply all MT Patches37

Apply the Latest AD and TXK for Release 12.239

Upgrade Application From 12.2.0 to 12.2.5.42

Register Custom Application using ADSPLICE43

Apply NLS translation Patch52

Apply 12.2.5 post upgrade task 52

Issues and Solutions52

Upgrade Target Information

This document provides the basic information about Oracle Application R12.2.5 upgradation at MBC

Environment Details:

Business Suite Version 12.2.5

Type -- Multi-node Installation

Instance Name ERPUPG

Operating Systems LINUX 6.6

Target OS Preparation

Database Preparation Guidelines for an E-Business Suite Release 12.2 Upgrade (Doc ID 1349240.1)

Oracle E-Business Suite Installation and Upgrade Notes Release 12 (12.2) for Linux x86-64 (Doc ID 1330701.1)

Cloning Oracle DB and APPS

Cloning Oracle Application Release 12 with Rapid Clone (Doc ID 406982.1)

Before the RDBMS software Installation:

Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2 (Doc ID 1058763.1)

STEP 1 : On E-Business Suite Release 12.1.3 apply below patches (Doc ID 1058763.1)

Patch 7303030

(Oracle E-Business Suite 12.1.1)

Patch 9062910

(11g Release 2 interoperability patch for Release 12.1)

Patch 8919489

(12.1 TXK Delta 3 patch)

Patch 9868229

Patch 10163753

Patch 11071569

Patch 9738085

(Auto Config)

Patch 9852070

Patch 12686610

$ adstpall.sh apps/apps

$ enable maintenance mode

[aperpup@ERPUPGAPP-01 APERPUP]$ adpatch

$ disable maintenance mode

STEP 2 : Install the 11.2.0.4 Database software

STEP 3 : Apply additional 11.2.0.4 Database patches

Patch 4247037

(This patch has post steps. Need to be completed after upgrade)

Patch 17402822

Patch 17468141

Patch 17501296

(This patch has post steps. Need to be completed after upgrade)

Patch 17892268

Patch 19393542

Opatch lsinventory:

Count Invalid Objects:

SQL> select count (*) from dba_objects where status='INVALID';

COUNT (*)

----------

23

STEP 4: How to Download and Run Oracle's Database Pre-Upgrade Utility (Doc ID 884522.1)

SQL>@/u01/oracle/product/11.2.0/dbhome_1/rdbms/admin/utlu112i.sql

SQL> PURGE DBA_RECYCLEBIN;

SQL> EXECUTE dbms_stats.gather_dictionary_stats;

SQL> alter system set JOB_QUEUE_PROCESS=50;

Remove Hidden Parameters:

STEP 5: The DMSYS schema exists in the database. Prior to performing an upgrade Oracle recommends that the DMSYS schema, and its associated objects be removed from the database. Doc id 1497250.1

STEP 6: Database Links with Passwords:

Doc ID 1536345.1

WARNING: ->Database contains schemas with objects dependent on DBMS_LDAP package: Ignore

Database Check:

STEP 7: Check for the integrity of the source database.Note 556610.1 Script to Collect DB Upgrade/Migrate Diagnostic Information (dbupgdiag.sql)

STEP 8: National Characterset

Check that the National Characterset (NLS_NCHAR_CHARACTERSET) is UTF8 or AL16UTF16.

Sql>select value from NLS_DATABASE_PARAMETERS where parameter =

'NLS_NCHAR_CHARACTERSET';

AL16UTF16

STEP 9: Run Analyze.sql

Check for logical corruption in underlying objects and their dependencies.This creates a script called analyze.sql

STEP 10 : MV Refressh DOC ID 1442457.1

Before upgrading Oracle Database, you must wait until all materialized views have completed refreshing and check that replication is stopped.

STEP 11: Media Recovery Status

Ensure that no files need media recovery and that no files are in backup mode.

STEP 12 : System Tablespace

Ensure the users SYS and SYSTEM have 'SYSTEM' as their default tablespace. You must have sufficient space in the tablespace or be set to extents unlimited.

Aud$ table:

Ensure that if the aud$ table exists that it is in the SYS schema and in the SYSTEM tablespace

STEP 13: Drop SYS.ENABLED$INDEXES

If the SYS.ENABLED$INDEXES table exists, use SQL*Plus to connect to the database as SYSDBA and running the following command to drop it: sql>drop table sys.enabled$indexes;

STEP 14: Stop Listener & Database

$ lsnrctl stop ERPUPG

Sql>shut immediate

STEP 15: Create 9idata directory

Create nls/data/9idata directory. $ perl $ORACLE_HOME/nls/data/old/cr9idata.pl

STEP 16: Set environment New Oracle Home

STEP 17 : Copy PFILE to new 11.2.0.4 ORACLE_HOME

Copy the initialization file from source Oracle Home to /dbs& change diag location

STEP 18: Start Database in Upgrade mode

At the operating system prompt, change to the $ORACLE_HOME/rdbms/admin directory of 11.2.0.4 Oracle Home.$ cd $ORACLE_HOME/rdbms/admin

$ sqlplus "/ as sysdba"

SQL> startup upgrade

STEP 19: Catupgrade

Set the system to spool results to a log file for later verification after the upgrade is completed and start the upgrade script.

SQL> set echo on

SQL> SPOOL upgrade.log

SQL> @catupgrd.sql

SQL> spool off

STEP 20: Post-Upgrade Status Tool

Run the Post-Upgrade Status Tool $ORACLE_HOME/rdbms/admin/utlu112s.sql

STEP 21: Catuppst.sql

Run catuppst.sql, located in the $ORACLE_HOME/rdbms/admin directory, to perform upgrade actions that do not require the database to be in UPGRADE mode.

SQL> @catuppst.sql

STEP 22: Compile Invalid objects

Sql>EXEC UTL_RECOMP.recomp_parallel (3);

STEP 23: Copy TNS and Listener to new home

From 11.2.0.3 to 11.2.0.4 home and copy to new home location

Set environment for TNS_ADMIN

export TNS_ADMIN=/u01/oracle/product/11.2.0/dbhome_1/network/admin/ERPUPG_erpupgdb-01

Start Listener

$ lsnrctl start ERPUPG

STEP 24: DST Upgrade Doc id 1579838.1

Check for TIMESTAMP WITH TIMEZONE Datatype. Uppgrade DST using Note 1579838.1: Actions for DST Updates When Upgrading to or applying the 11.2.0.4 Patchset

STEP 25: Create SPFILE

createspfilefrompfile;

STEP 26: Run adgrants.sql

Copy $APPL_TOP/admin/adgrants.sql

$ sqlplus "/ as sysdba" @adgrants.sql APPS

STEP 27: Grant create procedure privilege on CTXSYS

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

Set CTXSYS parameter

Use SQL*Plus to connect to the database as SYSDBA and run the following command:$sqlplus "/ as sysdba" SQL> exec ctxsys.ctx_adm.set_parameter('file_access_role', 'public');

STEP 28: Validate Workflow ruleset

On the administration server node, use SQL*Plus to connect to the database as APPS and run the $FND_TOP/patch/115/sql/wfaqupfix.sql script using the following command $sqlplus [APPS user]/[APPS password] @wfaqupfix.sql [APPLSYS user] [APPS user]

STEP 29: Re-generate appsutil

Post Patch steps: Regenerate appsutilperl $AD_TOP/bin/admkappsutil.pl

This will create appsutil.zip in $APPL_TOP/admin/out

Copy appsutil:

Copy appsutil to RDBMS ORACLE HOME

Unzip appsutil:

Unzip the files

unzip -o appsutil.zip

Create CONTEXT_FILE:

adbld.xml

[oraerpup@ERPUPGDB-01 bin]$ pwd

/u01/oracle/product/11.2.0/dbhome_1/appsutil/bin

[oraerpup@ERPUPGDB-01 bin]$ adbldxml.pl

Implement autoconfig:

./adconfig.sh contextfile=/u01/oracle/product/11.2.0/dbhome_1/appsutil/ERPUPG_erpupgdb-01.xml

STEP 30: Gathers stats

Copy $APPL_TOP/admin/adstats.sqlsysdba"

SQL> alter system enable restricted session;

SQL> @adstats.sql

$ sqlplus "/ as sysdba"

SQL> alter system disable restricted session;

SQL> exit;

STEP 31: Re-create custom database links

$ sqlplus apps/[apps password]

SQL> select db_link from dba_db_links;

If you have custom self-referential database links in the database instance, use the following commands to drop and re-create them:

$ sqlplus apps/[apps password]

SQL> drop database link [custom database link];

SQL> create database link [custom database link] connect to [user] identified by [password] using '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=[hostname]) (PORT=[port number]))(CONNECT_DATA=(SID=[ORACLE_SID])))';

where [custom database link], [user], [password], [hostname], [port number