EBS DB 11.1.0.7 upgrade to 12c 12.1.0.

DBUA upgrade GUI has changed a bit from 12c release. The changes are as follows:

The utlu121s.sql script has been replaced with the preupgrd.sql script. The new Pre-Upgrade
Information Tool provides fix-up scripts(preupgrade_fixups.sql) and postupgrade_fixups.sql with the
ability to fix and address any issues identified by the pre-upgrade check script. The preupgrd.sql has to
be copied to any temp directory and has to be ran from the db to be upgraded.

The previous upgrade script catupgrd.sql has been replaced with the new catctl.pl Parallel Upgrade
Utility script which provides the ability to run upgrade scripts in parallel taking advantage of spare CPU
capacity which can potentially reduce upgrade times

If Flashback database is enabled, DBUA creates a guaranteed restore point which can be used in case we
have a failure in the upgrade process. We can also restart DBUA to recover from any failures during the
upgrade.

We can now use an existing RMAN backup which DBUA is aware of in case we need to restore the
database to the pre-12c upgrade state

Oracle XML DB is now a mandatory component of the Oracle 12c database and is automatically installed
as part of the upgrade process if not found.

Now lets move to the upgrade process.

Existing EBS-12.1.1

Existing DB-11.1.0.7

Target DB-12.1.0.2

Supported Upgrade Paths

Direct upgrades to 12c are possible from existing databases with versions 10.2.0.5+, 11.1.0.7+, or
release 11.2.0.2+. Upgrades from other versions are supported only via intermediate upgrades to a
supported upgrade version.

Step 1: Applied the application patches

Patch 8796558

Patch 12923944

Patch 13473483

Patch 16289505 - 12c Release 1 interoperability patch for Release 12.1

Patch 19558309

Step 2: Applied the patch 6400501 to iAS 10.1.2 applications tier home

Step 3: Prepare to create the 12c Oracle home

Click next to complete the installation.
Step 4: Install Oracle Database 12c Products from the 12c Examples CD (mandatory)

Step 5:Create an env file and export Oracle SID, Oracle Home, Path which should be pointing to new
Oracle home

Step 6: Create nls/data/9idata directory

Step 7: Apply additional 12.1.0.2 RDBMS patches

Patch 6880880- the latest OPatch version for 12.1.0.

Patch 19382851

Patch 19393542

Patch 19627012

Patch 19649152

Patch 20204035

Patch 22731026

Step 8: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.

In the existing Database 11.1.0.7 init file, comment the LOCAL_LISTENER parameter.

Step 9: Drop SYS.ENABLED$INDEXES (conditional)

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 10: Remove the MGDSYS schema

If you are upgrading from an RDBMS version prior to 12c, on the old database server
node, use SQL*Plus to connect to the database as SYSDBA and run the
$ORACLE_HOME/md/admin/catnomgdidcode.sql script. This drops the MGDSYS
schema.
$ sqlplus "/ as sysdba" @?/md/admin/catnomgdidcode.sql

Prepare to Upgrade

Step 11. Run the pre upgrade tool. To run it, copy the preupgrade scripts from 12c to some temp
directory. Then from the old 11.1.0.7 this script has to be run.

On 12c Database, go to $ORACLE_HOME/rdbms/admin and copy the scripts.

[oracle@rac1 admin]$ cppreupgrd.sql /u02/r12/database/db/11.1.0

[oracle@rac1 admin]$ cputluppkg.sql /u02/r12/database/db/11.1.0

Run the pre upgrade utility.

[oracle@rac1 11.1.0]$ echo $ORACLE_HOME

/u02/r12/database/db/11.1.0

[oracle@rac1 11.1.0]$ sqlplus / as sysdba

SQL*Plus: Release 11.1.0.7.0 - Production on Sun Sep 11 10:27:03 2016

Copyright (c) 1982, 2008, Oracle. All rights reserved.

Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> @preupgrd.sql;

Loading Pre-Upgrade Package

Executing Pre-Upgrade Checks in PROD...

 ====>> ERRORS FOUND for PROD <<====

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 +++

2) Check Tag: PURGE_RECYCLEBIN

Check Summary: Check that recycle bin is empty prior to upgrade

Fixup Summary:

"The recycle bin will be purged."

You MUST resolve the above errors prior to upgrade

************************************************************

************************************************************

====>> PRE-UPGRADE RESULTS for PROD <<====

ACTIONS REQUIRED

Then run, @preupgrade_fixups.sql and follow the instructions accordingly.

Step 12

The source db should be up and entry should be there in /etc/oratab file.

DBUA execution.

Step 13.
SQL> SELECT comp_name || ' : '||version|| ' : '|| status FROM dba_registry;

COMP_NAME||':'||VERSION||':'||STATUS

Oracle XML Database : 12.1.0.2.0 : VALID

Oracle Text : 12.1.0.2.0 : VALID

Spatial : 12.1.0.2.0 : UPGRADED

Oracle Multimedia : 12.1.0.2.0 : VALID

Oracle Database Catalog Views : 12.1.0.2.0 : UPGRADED

Oracle Database Packages and Types : 12.1.0.2.0 : UPGRADED

JServer JAVA Virtual Machine : 12.1.0.2.0 : VALID

Oracle Database Java Packages : 12.1.0.2.0 : VALID

Oracle XDK : 12.1.0.2.0 : VALID

Oracle Real Application Clusters : 12.1.0.2.0 : OPTION OFF

OLAP Analytic Workspace : 12.1.0.2.0 : VALID

SQL> select open_mode from v$database;

OPEN_MODE

--------------------

READ WRITE

Step 14: Create a listener file or copy it from old oracle home and edit it.

Modified the initialization parameter as per note:396009.1, Database Initialization Parameter Settings

for Oracle Applications Release 12

Step 15. Run adgrants.sql

Copy $APPL_TOP/admin/adgrants.sql (adgrants_nt.sql for Windows) 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 (or adgrants_nt.sql) [APPS schema name]

[oracle@rac1 database]$ sqlplus / as sysdba

SQL*Plus: Release 12.1.0.2.0 Production on Tue Jan 3 21:02:08 2017

Copyright (c) 1982, 2014, Oracle. All rights reserved.

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

SQL> @adgrants.sql APPS;

Connected.

---------------------------------------------------

--- adgrants.sql started at 2017-01-03 21:02:30 ---

Creating PL/SQL profiler objects.

PL/SQL procedure successfully completed.

Commit complete.

Step 16: 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:
$ sqlplus apps/[APPS password] @adctxprv.sql \
[SYSTEM password] CTXSYS

Step 17: 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 18: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 19: 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 run adstats.sql in restricted mode:
$ sqlplus "/ as sysdba"
SQL> alter system enable restricted session;
SQL> @adstats.sql
$ sqlplus "/ as sysdba"
SQL> alter system disable restricted session;
SQL> exit;

Note: Make sure that you have at least 1.5 GB of free default temporary tablespace

Step 20. Deregister the current database server (conditional)

If you plan to change the database port, host, SID, or database name parameter on the
database server, you must also update AutoConfig on the database tier and deregister
the current database server node.

Use SQL*Plus to connect to the database as APPS and run the following command:
$ sqlplus apps/[APPS password]
SQL> exec fnd_conc_clone.setup_clean;

Implement autoconfig

In the application tier, go to $AD_TOP/bin

applmgr@ebs1 bin]$perl admkappsutil.pl

Starting the generation of appsutil.zip

Log file located at /u02/r12/application/inst/apps/PROD_ebs1/admin/log/MakeAppsUtil_12190144.log

output located at /u02/r12/application/inst/apps/PROD_ebs1/admin/out/appsutil.zip

MakeAppsUtil completed successfully.

[applmgr@ebs1 bin]$
Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>
cd<RDBMS ORACLE_HOME>
unzip -o appsutil.zip

This will create an appsutil directory under Oracle Home.

copy the old jre from old oracle home to new oracle home/appsutil directory.

Now go to $Oracle_HOME/appsutil/bin and run the command.

[oracle@rac1 bin]$ perl adbldxml.pl

Starting context file generation for db tier..

Using JVM from /u03/r12/database/db/12.1.0.2/db_home/jdk/jre/bin/java to execute java programs..

APPS Password: **

The log file for this adbldxml session is located at:

/u03/r12/database/db/12.1.0.2/db_home/appsutil/log/adbldxml_01032155.log

Could not Connect to the Database with the above parameters, Please answer the Questions below

Enter Hostname of Database server: rac1

Enter Port of Database server: 1522

Enter SID of Database server: PROD

Enter the value for Display Variable: rac1:0.0

The context file has been created at:

/u03/r12/database/db/12.1.0.2/db_home/appsutil/PROD_rac1.xml

[oracle@rac1 bin]$
Run autoconfig now

[oracle@rac1 bin]$ sh adconfig.sh

Enter the full path to the Context file:

/u03/r12/database/db/12.1.0.2/db_home/appsutil/PROD_rac1.xml

Enter the APPS user password:

The log file for this session is located at:

/u03/r12/database/db/12.1.0.2/db_home/appsutil/log/PROD_rac1/01032159/adconfig.log

AutoConfig is configuring the Database environment...

AutoConfig will consider the custom templates if present.

Using ORACLE_HOME location : /u03/r12/database/db/12.1.0.2/db_home

Classpath :
:/u03/r12/database/db/12.1.0.2/db_home/jdbc/lib/ojdbc6.jar:/u03/r12/database/db/12.1.0.2/db_hom
e/appsutil/java/xmlparserv2.jar:/u03/r12/database/db/12.1.0.2/db_home/appsutil/java:/u03/r12/data
base/db/12.1.0.2/db_home/jlib/netcfg.jar

Using Context file : /u03/r12/database/db/12.1.0.2/db_home/appsutil/PROD_rac1.xml

Context Value Management will now update the Context file

Updating Context file...COMPLETED

Attempting upload of Context file and templates to database...COMPLETED

Updating rdbms version in Context file to db121

Updating rdbms type in Context file to 64 bits

Configuring templates from ORACLE_HOME ...

AutoConfig completed successfully.

[oracle@rac1 bin]$

And then run the autoconfig in apps tier.

Step 21: Create the new MGDSYS schema (conditional)

If you upgraded from an RDBMS version prior to 12c, use SQL*Plus to connect to the
database as SYSDBA and run the $ORACLE_HOME/rdbms/admin/catmgd.sql script. This
creates the new MGDSYS schema.
$ sqlplus "/ as sysdba" @?/rdbms/admin/catmgd.sql

Step 22: Start the services.