EBS Oracle Database 11.1.0.7 upgrade to 11.2.0.4 steps .

Oracle Database 11.1.0.7 upgrade to 11.2.0.4

 

 

 

Section 1: Upgrading an R12 Database to Oracle Database 11g Release 2 (11.2.0)

Verify software versions:-

 

The following software component versions must exist in your environment.

Software	Minimum Version	Tier	Details
Oracle Database Enterprise Edition	N/A	Database	Read the "Determine the Upgrade Path" subsection in Chapter 2 of theOracle Database Upgrade Guide 11g Release 2 (11.2). Make sure that direct upgrade is supported from your current release.
Oracle E-Business Suite	12.0.4 or 12.1.1	Application	If you are on E-Business Suite Release 12.0, apply Patch 6435000 - Oracle E-Business Suite 12.0.4 Patch 8623536 - 11g Release 2 interoperability patch for Release 12.0.4 Patch 9868229 If you are on E-Business Suite Release 12.1, apply 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 18843706 - apply only if you have applied a Recommended Patch Collection (RPC) patch

 

 

AutoConfig

Latest version with 9852070, 9738085, 11692965, and 12686610

Application

Implement AutoConfig or upgrade to the latest version. See Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12 on My Oracle Support for instructions. If you are on Oracle E-Business Suite Release 12.1, apply patches Patch 9738085 and Patch 9852070. If you are on the IBM Linux on System Z platform and on Oracle E-Business Suite Release 12.1, apply Patch 11692965. Apply Patch 12686610 (for Oracle E-Business Suite Release 12.0 and 12.1).

 

 

Apply patch 6400501 (conditional)

If you are on a UNIX/Linux platform, apply the 10.1.0.5 version of Patch 6400501 to the iAS 10.1.2 Applications tier Oracle home.

Note: For Linux x86-64 environments, download the Linux 32-bit version of the patch as the Applications tier Oracle home is 32-bit.

 

 

1. Update application tier context file with new database listener port number (conditional)

The new 11.2.0 Oracle home uses its own database listener for the database instance, replacing the current database listener. Use the Context Editor to update the following variables in the Applications context file on each application tier server node to reflect the 11.2.0 configuration:

Variable Name	Value
s_dbhost	New database hostname
s_dbdomain	New database domain name
s_db_serv_sid	New database SID
s_dbport	New database listener port
s_apps_jdbc_connect_descriptor	NULL

See Using AutoConfig to Manage System Configurations with Oracle E-Business Suite Release 12 on My Oracle Support for instructions on how to update and run the Context Editor.

Attention: Do not run AutoConfig on the application tier once the context file has been updated. Doing so will cut off the entire application tier from the database instance until after the upgrade is complete. You will be instructed to run AutoConfig on the application tier to configure the system for the new port number once the upgrade is finished and the new database listener is in use.

Database Installation:

4. Prepare to create the 11.2.0 Oracle home

The 11.2.0 Oracle home must be installed on the database server node in a different directory than the current Oracle home.

Read Chapters 1 and 2 of the Oracle Database Installation Guide 11g Release 2 (11.2) for your platform. Also read Chapter 1 and the "System Considerations and Requirements" section of Chapter 3 of the Oracle Database Upgrade Guide 11g Release 2 (11.2). Make sure you thoroughly understand the installation and upgrade processes. Perform any step that is relevant for your environment.

Attention: For HP Itanium and HP PA RISC platforms using the NFS file system, choose a disk to install the 11g Oracle home separate from the database files. The mount options of the disk containing the database files must include forcedirectio. The 11g Oracle home (or any other binaries) must not include the forcedirectio mount option.

Cd   /clndb/dbfin/db/tech_st

Mkdir 11.2.0.4

Chmod –R 775  11.2.0.4

$export ORACLE_BASE=/clndb/dbfin/db/tech_st/

$export ORACLE_SID=CLNR12

$export ORACLE_HOME=/clndb/dbfin/db/tech_st/11.2.0.4

$export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/perl/bin:$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  OPTACH_HOME=$ORACLE_HOME/OPatch

5. Install the 11.2.0.4 software

Log in to the database server node as the owner of the Oracle RDBMS file system and database instance. Ensure that environment settings, such as ORACLE_HOME, are set for the new Oracle home you are about to create, and not for any existing Oracle homes on the database server node. Perform all the steps in Chapter 4, "Installing Oracle Database" of the Oracle Database Installation Guide 11g Release 2 (11.2) for your platform.

In the Installation Types window, use the Product Languages button to select any languages other than American English that are used by your Applications database instance. Choose the Enterprise Edition installation type. In the subsequent windows, select the options not to upgrade an existing database and to install the database software only.

Note: 1.      When installing 11.2.0.4 on Oracle Linux 7 or Red Hat Linux 7, ignore the warning regarding missing package 'pdksh-5.2.14' during pre-requisite checks. 2.      When installing 11.2.0.4 on Oracle Linux 7 or Red Hat Linux 7 and encountering the installer error in invoking target 'agent nmhs' of makefile with the log file showing an undefined reference to symbol 'B_DestroyKeyObject', users should review and implement the workaround noted in the documentInstallation of Oracle 11.2.0.4 Database Software on OL7 fails with "undefined reference to symbol 'B_DestroyKeyObject'" error".

 

 

 

 

 

 

6. Install Oracle Database 11g Products from the 11g Examples CD (mandatory)

On the database server node, as the owner of the Oracle RDBMS file system and database instance, perform the tasks in the "Install Oracle Database Examples" section in the Oracle Database Examples Installation Guide.

In the Installation Types window, use the Product Languages button to select any languages other than American English that are used by your Applications database instance.

After the installation, make sure that:

a.    The ORACLE_BASE environment variable must be set accordingly.

b.    The ORACLE_HOME environment variable points to the new 11.2.0 Oracle home.

c.    The PATH environment variable includes $ORACLE_HOME/bin and the directory where the new perl executable is located (usually $ORACLE_HOME/perl/bin).

d.    The LD_LIBRARY_PATH environment variable includes $ORACLE_HOME/lib.

e.    The PERL5LIB environment variable points to the directories where the new perl libraries are located ($ORACLE_HOME/perl/lib/[perl version] and $ORACLE_HOME/perl/lib/site_perl/[perl version] for UNIX/Linux, $ORACLE_HOME/perl/lib and $ORACLE_HOME/perl/site/lib for Windows)

 

·         Execute following command on new database 11.2.0.4

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

 

If we get any issue for cr9idata.pl script. Please set following environment variable again.

 

ORACLE_SID=CLNR12; export ORACLE_SID

ORACLE_BASE=/clndb/dbfin/db/tech_st/; export ORACLE_BASE

ORACLE_HOME=/clndb/dbfin/db/tech_st/11.2.0.4; export ORACLE_HOME

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

LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/ctx/lib:/usr/dt/lib:/usr/openwin/lib; export LD_LIBRARY_PATH

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

TNS_ADMIN=$ORACLE_HOME/network/admin; export TNS_ADMIN

 

 

 

 

 

·         After creating the directory, make sure that the ORA_NLS10 environment variable is set to the full path of the 9idata directory whenever you enable the 11g Oracle home. $export ORA_NLS10=$ORACLE_HOME/nls/data/9idata

Apply Additional 11.2.0.4 RDMS Patches:

·         Opatch - Apply additional 11.2.0.4 RDBMS patches – Database tier

$cd $HOME/Patches – Make sure opatch is in path

·         Patch 4247037

 

 

o    Patch 17402822

o    Patch 17468141

o    Patch 17501296

§  Postinstallation

§  $cd 17501296

§  $sqlplus /nolog

§  SQL> CONNECT / AS SYSDBA

§  SQL> @postinstall.sql

§  Check the output for any errors

o    Patch 17892268

o    Patch 19393542

   Patch 22731026

 

 

 

 

·         Set new optatch path:

$cd $ORACLE_HOME/OPatch

$export PATH=$PATH:$ORACLE_HOME/OPatch

 

·         Apply 4247037 Opatch:

$cd /mnt/software/RDBMS_patches/4247037

$opatch apply

 

·         Apply 17402822 Opatch:

$cd /mnt/software/RDBMS_patches/17402822

$opatch apply

·         Apply 17468141 Opatch:

$cd /mnt/software/RDBMS_patches/17468141

$opatch apply

 

·         Apply 17501296 Opatch:

$cd /mnt/software/RDBMS_patches/17501296

$opatch apply

 

·         Apply 17892268 Opatch:

$cd /mnt/software/RDBMS_patches/17892268

$opatch apply

 

·         Verify patch application status

Back up old TNS:

Need to check:

$cp -r /u01/oraR12/VIS/db/tech_st/11.1.0/network/admin/VIS_ebsdb /u01/oraR12/VIS/db/tech_st/11.2.0/network/admin/

 

Start Old Database:

·         Login with oravis account

$ ./appsora.env

$sqlplus / as sysdba

SQL> startup

Note: Do not start the listeners and make sure all application services are down.

 

Pre Upgrade Process:

·         Copy utlu112i.sql (From new database):

$Login with oravis and set new database 11.2.0.4 env values

$cp $ORACLE_HOME/rdbms/admin/utlu112i.sql $HOME/

$cd $HOME

$ ./appsora.env (from bash_profile)

$ sqlplus '/ as sysdba'

SQL> spool upgrade_info.log

SQL> @utlu112i.sql

SQL> spool off

Review the Issues

 

 

Listeners Stop:

·         Stop Listeners – Source Database

$lsnrctl stop

 

·         Remove Local Listeners from Source Database

$sqlplus / as sysdba

SQL>create pfile from spfile;

$cd $ORACLE_HOME/dbs

$ls -lrt

$vi initVIS.ora

And remove line from pfile

*.local_listener='VIS'

Save and exit

 

·         oratab file edit  it should be old oracle home path and additionally end must be Y

$vi /etc/oratab

VIS: /u01/oraR12/VIS/db/tech_st/11.1.0:Y

 

·         Save and exit

Database Upgrade -11.2.0.4:

·         Set following values:

$export ORACLE_BASE=/u01/oraR12/VIS

$export ORACLE_SID=VIS

$export ORACLE_HOME=/u01/oraR12/VIS/db/tech_st/11.2.0

$export LD_LIBRARY_PATH=$ORACLE_HOME/lib;

$export TNS_ADMIN=/u01/oraR12/VIS/db/tech_st/11.2.0/network/admin/VIS_ebsdb

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

$PERL5LIB=/u01/oraR12/VIS/db/tech_st/11.2.0/perl/lib/5.10.0:/u01/oraR12/VIS/db/tech_st/11.2.0/perl/lib/site_perl/5.10.0:$ORACLE_HOME/appsutil/perl

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

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

 

·         Invoke the dbua

$cd $ORACLE_HOME/bin

./dbua

 

Follow the screens.

Validate all log files

Screens:

 

 

 

 

 

 

 

 

 

 

 

 

After Upgrade:

·         After complete update restarts the database:

$sqlplus / as sysdba

SQL> shutdown immediate

SQL> startup

SQL> exit

 

·         Listeners Validation:

$lsnrctl stop VIS

$lsnrctl start VIS

 

·         Run adgrants.sql:

If it is not updated one copy $APPL_TOP/admin/adgrants.sql from apps tier to DB tier

$cp $HOME < adgrants copied oravis user home location >

$sqlplus / as sysdba

·         SQL>@adgrants.sql apps

Database Validation:

 

 

CTXSYS Changes:

·         Copy the adctxprv.sql file to db tier from apps tier

Login Apps tier copy file from $AD_TOP/patch/115/sql/ location

Copy to oravis home location on db tier (through winscp or others)

Login to db tier with

$cd $HOME

Execute: sqlplus apps/[APPS password] @adctxprv.sql \ [SYSTEM password] CTXSYS

$sqlplus apps/apps @adctxprv.sql \ manager CTXSYS

 

·         Set CTXSYS parameter:

$sqlplus / as sysdba

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

Validate Workflow Rule:

·         Copy the wfaqupfix.sql file to db tier from apps tier

Login Apps tier copy file from $FND_TOP/patch/115/sql/ location

Copy to oravis home location on db tier (through winscp or others)

Login to db tier with

$cd $HOME

Execute: sqlplus [APPS user]/[APPS password] @wfaqupfix.sql\ [APPLSYS user] [APPS user]

$sqlplus apps/apps @ wfaqupfix.sql \ applsys apps

Copy Autoconfig:

·         Copy appsutil.zip from apps tier, if not exist create new one

Login to apps tier with applmgr account

$perl $AD_TOP/bin/admkappsutil.pl

appsutil.zip will be created

Copy appsutil.zip to oravis home location on db tier (through winscp or others)

Login to db tier with oravis

$cd $ORACLE_HOME or /u01/oraR12/VIS/db/tech_st/11.2.0

$cp $HOME/appsutil.

DB JRE Copy:

·         Copy JRE folder from source database to new database

Login to db tier with oravis

$cp -r /u01/oraR12/VIS/db/tech_st/11.1.0/appsutil/jre /u01/oraR12/VIS/db/tech_st/11.2.0/appsutil/

New Context File:

·         Generate the Database Context File

$perl $ORACLE_HOME/appsutil/bin/adbldxml.pl

Required apps password

 

Note: Error - Perl lib version (5.10.0) doesn't match executable version (v5.10.1) at Workaround - $export ORACLE_HOME=/u01/oraR12/VIS/db/tech_st/11.2.0 export $PERL5LIB=$ORACLE_HOME/perl/lib/5.10.0:$ORACLE_HOME/perl/site_perl/5.10.0:$ORACLE_HOME/appsutil/perl export PATH=$ORACLE_HOME/perl:$ORACLE_HOME/perl/lib:$ORACLE_HOME/perl/bin:$PATH

DB Auto Config:

·         Auto Config on new database

Login to apps tier with applmgr account

$cd $ADMIN_SCRIPTS_HOME

 $adstpall.sh apps/apps

Login to db tier with oravis

$cd $ORACLE_HOME/appsutil/scripts

$adautocfg.sh

OR

·         Run adconfig  on the Database tier from xml file (it will create environment file for db tire )

$ORACLE_HOME/appsutil/bin/adconfig.sh contextfile=/u01/oraR12/VIS/db/tech_st/11.2.0/appsutil/VIS_ebsdb.xml

 

·         Stop All services on DB tier

$sqlplus / as sysdba

SQL> shutdown immediate

SQL> exit

$lsnrctl stop

 

·         Start all services on DB tier

$sqlplus / as sysdba

SQL> startup

SQL> exit

$lsnrctl start

Note: Database is started with all new configuration

 

Gather statistics for SYS schema:

·         Copy the adstats.sql file to db tier from apps tier

Login Apps tier copy file from $APPL_TOP/admin/ location

Copy to oravis home location on db tier (through winscp or others)

Login to db tier with oravis account

$cd $HOME

$ sqlplus "/ as sysdba"

SQL> alter system enable restricted session;

SQL> @adstats.sql

 

$ sqlplus "/ as sysdba"

SQL> alter system disable restricted session;

SQL> exit;

 

Apps Autoconfig:

·         Auto config on Apps tier

$login to apps tier with applmgr account

$cd $ADMIN_SCRIPTS_HOME

$adstpall.sh apps/apps

$adautocfg.sh

$adstrtal.sh apps/apps

Note: Apps tier and DB Tier started with all new configuration