12C UPGRADE

Determine the Upgrade Path for Oracle Database
The path that you must take to upgrade to the latest release of
Oracle Database 12c depends on the release number of your current database.
You may perform a direct upgrade to the new release if your current Oracle Database is release 10.2.0.5, 11.1.0.7, or release 11.2.0.2 or later.
Obtaining the Software 12.1.0.2.0 from the patchset  21419221
Before the database installation
Determine the Upgrade Path for Oracle Database
The path that you must take to upgrade to the latest release of Oracle Database 12c depends on the release number of your current database.
You may perform a direct upgrade to the new release if your current Oracle Database is release 10.2.0.5, 11.1.0.7, or release 11.2.0.2 or later.
Apply necessary Oracle E-business suite 11.5.10 CU2 patches
Patch 3460000 - 11.5.10 E-Business Suite Consolidated Update 2
Patch 10350522 - Prerequisite patch for 16289505
Patch 12539637 - Prerequisite patch for 16289505
Patch 20621314 - Prerequisite patch for 16289505
Patch 9535311 - TXK AUTOCONFIG AND TEMPLATES ROLLUP PATCH U
Patch 16289505 - 12c Release 1 interoperability patch for 11.5.10
Patches already applied in the environment:
Patch 3460000 - 11.5.10 E-Business Suite Consolidated Update 2
Patch 9535311 - TXK AUTOCONFIG AND TEMPLATES ROLLUP PATCH U
Patches to be applied:
Patch 10350522 - Prerequisite patch for 16289505
Patch 12539637 - Prerequisite patch for 16289505
Patch 20621314 - Prerequisite patch for 16289505
Patch 16289505 - 12c Release 1 interoperability patch for 11.5.10
ATG Rollup Patch  7 (Application Tier)
Apply Patch 6241631
Install 12cR1 RDBMS Software
Install 12cR1 RDBMS Oracle Home in a separate directory from the existing Oracle Home.
The current Oracle Home location is "/u01/ora_test/11.2.0" and 12cR1 Oracle Home will be Installed in "/u01/ora_test/12.1.0"
- Set the Proper Display Variable and execute "runInstaller"






Install R12cR1 Examples CD
Installation of Examples CD is mandatory and one should not skip its Installation before starting the upgrade process.
Examples CD will be Installed in existing newly Installed 12cR1 Oracle home.
- set the proper display variable and execute runInstaller



Create nls/data/9idata directory
apdba@apdba-blog~]$ perl $ORACLE_HOME/nls/data/old/cr9idata.pl
Creating directory /ora/bovdev/home/product/12102/nls/data/old/9idata ...
Copying files to /ora/bovdev/home/product/12102/nls/data/9idata...
Copy finished.
Please reset environment variable ORA_NLS10 to /ora/bovdev/home/product/12102/nls/data/9idata!
[apdba@apdba-blog~]$
Check the Opatch lsinventory command and make sure the command succeeds
[apdba@apdba-blog ~]$ export ORACLE_HOME=/ora/bovdev/home/product/12102
[apdba@apdba-blog ~]$ export PATH=$ORACLE_HOME/bin:$PATH
[apdba@apdba-blog ~]$ export PATH=$ORACLE_HOME/bin:$ORACLE_HOME/OPatch:$PATH
[apdba@apdba-blog ~]$ vi 12c.env
[apdba@apdba-blog~]$ which opatch
/ora/bovdev/home/product/12102/OPatch/opatch
[apdba@apdba-blog~]$ opatch lsinventory
Apply additional 12.1.0.2 RDBMS patches
• Patch 19393542
• Patch 19627012
• Patch 20204035
• Patch 20903906
Attention: Do not apply any of the patch special instructions. The scripts will be run after the upgrade.
Database Upgrade:
Shut down Applications server processes and database listener
On each application tier server node, shut down all server processes or services. On the database tier server node,
shut down the Oracle Net or Net8 database listener in the old Oracle home.
Drop SYS.ENABLED$INDEXES (conditional)
apdba@apdba-blog 11.2.0]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.2.0 Production
Copyright (c) 1982, 2011, Oracle. All rights reserved.
 Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
 SQL> drop table sys.enabled$indexes;
Run pre upgrade tool
Pre Upgrade tool will lists all changes need to be performed before starting the upgrade process.
Copy pre upgrade scripts from 12cR1Oracle home to any other directory. I used "db_scripts" directory to keep all upgrade related scripts in one location.
[apdba@apdba-blog]$cp /ora/bovdev/home/product/12102/rdbms/admin/preupgrd.sql .
[apdba@apdba-blog]$cp /ora/bovdev/home/product/12102/rdbms/admin/utluppkg.sql .
Make sure that preupgrd.sql and utluppkg.sql files are copied in the same directory.
- Connect from 11.2.0.2 Home as sysdba and run pre-upgrade tool
SQL> @preupgrd.sql
Loading Pre-Upgrade Package...
Executing Pre-Upgrade Checks...
Pre-Upgrade Checks Complete.
************************************************************
Results of the checks are located at:
/ora/bovdev/home/product/11.2.0/cfgtoollogs/BOVDEV/preupgrade/preupgrade.log
Pre-Upgrade Fixup Script (run in source database environment):
/ora/bovdev/home/product/11.2.0/cfgtoollogs/BOVDEV/preupgrade/preupgrade_fixups.sql
Post-Upgrade Fixup Script (run shortly after upgrade):
/ora/bovdev/home/product/11.2.0/cfgtoollogs/BOVDEV/preupgrade/postupgrade_fixups.sql
************************************************************
Fixup scripts must be reviewed prior to being executed.
************************************************************
************************************************************
====>> USER ACTION REQUIRED <<====
************************************************************
The following are *** ERROR LEVEL CONDITIONS *** that must be addressed
prior to attempting your upgrade.
Failure to do so will result in a failed upgrade.
1) Check Tag: INVALID_SYS_TABLEDATA
Check Summary: Check for invalid (not converted) table data
Fixup Summary:
"UPGRADE Oracle supplied table data prior to the database upgrade."
+++ Source Database Manual Action Required +++
You MUST resolve the above error prior to upgrade
SQL>
Perform full database backup.
Use DBUA for upgrading database




Install patch post Installation steps for all RDBMS patches (opatches)
Run the post installation “datapatch” for the patch #20204035
Start Listener from 12cR1 Home:
Copy TNS_ADMIN directory from 11gR2 Home to 12cR1 home and modify all required files with 12c Oracle Home location.
 [apdba@apdba-blog admin]$ cp -pr BOVDEV_usfitodbtst1 /ora/bovdev/home/product/12102/network/admin
[apdba@apdba-blog admin]$ pwd
/ora/bovdev/home/product/11.2.0/network/admin
[apdba@apdba-blog admin]$
[apdba@apdba-blog]$ pwd
/ora/bovdev/home/product/12102/network/admin/BOVDEV_apdba-blog
[apdba@apdba-blog]$ export TNS_ADMIN=/ora/bovdev/home/product/12102/network/admin/BOVDEV_apdba-blog
[apdba@apdba-blog]$ lsnrctl start BOVDEV
Ensure that your sqlnet_ifile.ora has the line:
SQLNET.ALLOWED_LOGON_VERSION_SERVER = 8
Run adgrants.sql
Copy $APPL_TOP/admin/adgrants.sql from the administration server node to the database server node.
Use SQL*Plus to connect to the database as SYSDBA and run the script using the following command:
$ sqlplus "/ as sysdba" @adgrants.sql apps
Grant create procedure privilege on CTXSYS
Copy $AD_TOP/patch/115/sql/adctxprv.sql from the administration server node to the database server node.
Use SQL*Plus to connect to the database as APPS and run the script using the following command:
@adctxprv.sql manager CTXSYS
Compile Invalid Objects
SQL>@$ORACLE_HOME/rdbms/admin/utlrp.sql
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');
Gather statistics for SYS schema 
Copy $APPL_TOP/admin/adstats.sql from the administration server node to the database server node.
Note that adstats.sql has to be run in restricted mode.
Use SQL*Plus to connect to the database as SYSDBA and use the following commands to restart the database in restricted mode, run adstats.sql, and restart the database in normal mode:
$ sqlplus "/ as sysdba"
SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus "/ as sysdba"
SQL> alter system disable restricted session;
SQL> exit;
Implement and run AutoConfig
Run script "$AD_TOP/bin/admkapsutil.pl" to generate new appsutil.zip file, It will generate file in $INST_TOP/out directory. Copy this file to 12c Oracle Home and unzip it.
[apdba@apdba-blog2 bin]$ ls -l admkappsutil.pl
-rwxr-xr-x 1 apdba dba 5683 Apr 21  2007 admkappsutil.pl
[apdba@apdba-blog2 bin]$ perl admkappsutil.pl
Starting the generation of appsutil.zip
Log file located at /ora/bovdev/appl/BOVDEVappl/admin/log/MakeAppsUtil_01171629.log
output located at /ora/bovdev/appl/BOVDEVappl/admin/out/appsutil.zip
MakeAppsUtil completed successfully.
Copy the appsutil.zip into 12c Oracle home and unzip it.
[obdev@usfit-odbtst1 12102]$ unzip -o appsutil.zip
Archive: appsutil.zip
inflating: appsutil/template/adclobtmp.sql
inflating: appsutil/template/afinit_db112.ora
inflating: appsutil/template/adstrtdb.sql
inflating: appsutil/template/adregtools.drv..............
[obdev@usfit-odbtst1 bin]$ pwd
/ora/bovdev/home/product/12102/appsutil/bin
[obdev@usfit-odbtst1 bin]$ perl adbldxml.pl
Starting context file generation for db tier..
Using JVM from /ora/bovdev/home/product/12102/appsutil/jre/bin/java to execute java programs..
APPS Password:
The log file for this adbldxml session is located at:
/u01/ora_test/12.1.0/appsutil/log/adbldxml_11200955.log
Could not Connect to the Database with the above parameters, Please answer the Questions below
Enter Hostname of Database server: usfit-odbtst1.global.internal
Enter Port of Database server: 1542
Enter SID of Database server: BOVDEV
Enter Database Service Name: BOVDEV
Enter the value for Display Variable: 0.0
The context file has been created at:
/ora/bovdev/home/product/12102/appsutil/BOVDEV_usfit-odbtst1.xml
Shut down all processes, including the database and the listener, and restart them to load the new environment settings.
After running adbldxml.pl on the database tier server node, the new Context file will contain the entry:
<DB_LISTENER oa_var="s_db_listener"/>
Modify this to:
<DB_LISTENER oa_var="s_db_listener">BOVDEV</DB_LISTENER>
Execute autoconfig on database Tier:
[[obdev@usfit-odbtst1 bin]$ pwd
/ora/bovdev/home/product/12102/appsutil/bin
[obdev@usfit-odbtst1 bin]$ sh adconfig.sh
AutoConfig completed successfully.
Execute autoconfig on Application Tier.
Re-create OPATCH_INST_DIR directory
Use SQL*Plus to connect to the database as SYSDBA and run the following command to re-create the OPATCH_INST_DIR directory:
SQL> create or replace directory OPATCH_INST_DIR as '[ORACLE_HOME]/OPatch';