g:\prints\ebs_upgrade\12.0.4 to 12.1.1.

txt
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Upgrade Oracle Application E Business Suite 12.0.X to 12.1.1
=============================================================:

Includes Upgrade of Database, Complete Middle Tier and Java Upgrade with
Application TOP

This includes Challenges and issues and fixes during the process of upgrade.
This document refers to Redhat Enterprise Linux 4 update 5., Database 10.2.0.2,
Forms server version 10.1.2.0.1 and 10g AS Web server 10.1.3

High Level Steps:

Step 1: Process of Database Upgrade from (10.2.0.2 to 10.2.0.4)

Step 2: (Upgrade 10gAS 10.1.3 to 10.1.3.4)
Step 3: Upgrading the Java JDK
Step 4: Forms server Upgrade from 10.1.2.0.1 to 10.1.2.3 is to be done.
Step 5: upgrading to 12.1.1

Take a backup of the production before doing (Strong Recommendation)

Metalink Document to refer: 752619.1 (But many challenges ahead if you follow the
document)
The as-is server is being 12.0.5 and database is of 10.2.0.2, we upgraded the
Database to 10.2.0.4 using Patchset 6810189

Step 1: Process of Database Upgrade:

1. Unzip the p6810189_10204_Linux-x86.zip to a temporary directory which is

obtained from metalink.
2. Shut down all the application services, DB, listener, isqlplus and emctl
dbconsole.
Please do remember, Take a backup of the database and inventory.
3. Go to unzipped directory and run ./runInstaller
$./runInstaller
Once completed, startup the database using
$sqlplus / as sysdba
SQL> startup upgrade;
SQL> spool 'upgrade10204.log'
SQL> @$ORACLE_HOME/rdbms/admin/catupgrd.sql
At the end the script will return the results of upgrade validity. Verify the
validity of the database after upgrade.
SQL> shut immediate;
SQL> Startup;
SQL> @$ORACLE_HOME/rdbms/admin/utlrp.sql
This will compile all the invalid objects that are added and not compiled during
upgrade.
After co-mpilation:
Shutdown the instance and apply the additional RDBMS Patches using Opatch for E
Business Suite upgrade.
Please be sure to have OPatch in the PATH
To Include OPatch in the path use
$export PATH=$PATH:$ORACLE_HOME/OPatch
Using Opatch Apply the following Patches
4247037
6600051
6870937
6991626
Step 2: (Upgrade 10gAS 10.1.3 to 10.1.3.4)

Important:
1.Take a backup of inventory before proceeding.
2. Source the environment file from $INST_TOP/ora/10.1.3/
$. PROD_appsmachine.env
3. Verify echo $ORACLE_HOME as $ORACLE_APPS_BASE/apps/tech_st/10.1.3
$ export ORACLE_HOME=/u01/oracle/PROD/apps/tech_st/10.1.3
4. Ensure that all the OC4J services are up and running.
1. Unzip and Apply Patch 7272722 obtained from metalink using ./runInstaller
If you are using local inventory please use
./runInstaller -invPtrLoc $ORACLE_HOME/oraInst.loc
During the process, the OPMN services will be down and started up by the OUI.
When prompted please give the OC4J admin password as either 'secret' or 'opmn' (As
I upgraded two instance, one (12.0.6) was successful with 'secret' and another
(12.0.5) by 'opmn' or ' oafm' )
This will complete the 10gAS (10.1.3.0.1) to be upgraded with 10.1.3.4
Time taken for this procedure ~ 1 hour.
Shutdown the services, Run Autoconfig on the apps Tier.
-----------------------------------------------------------------------------------
------------------------
As per the metalink document, dont upgrade Opatch version to 1.0.0.0.62, it failed
two times for me during the other patches. I advise you to keep the current Opatch
as opatch tool.
Be sure, the path of the Opatch is present in the PATH variable.
Apply the following patches:
(if you are using local inventory, then use
Patch_Directory$opatch apply -invPtrLoc $ORACLE_HOME/oraInst.loc)
1. 6702510 (The issue is that.. being a general platform Patch, Opatch will fail at
the verification of platform)
use $export OPATCH_PLATFORM_ID=46,
then rerun the opatch apply.
2. Apply 6771776 (If you are getting error during opatch as Platform as 196 then
use OPATCH_PLATFORM_ID = 46)
3. 7411481
4. 7139320
5. 7139339
Post Upgrade steps
Source Application environment file
Regenerate appsborg.zip and appsborg2.zip using adadmin
Navigation: adadmin -> Choose Option 1-> Regenerate Product JAR files -> Force
Option: No
Run autoconfig in application tier system.
Verify the Upgrade using:
either:
use ./runInstaller and then select installed products, it will show you the
components from WEB_OH that are all upgraded to 10.1.3.4
or:
use opatch lsinventory -detail
Look for Oracle Application Server Patchset as 10.1.3.4 as follows:
Installed Patch List:
===================== 1) Patch 7139339 applied on Fri Jul 17 20:03:46 IST 2009
[ Base Bug(s): 7139339 ]
2) Patch 7139320 applied on Fri Jul 17 20:02:23 IST 2009 [ Base Bug(s): 7139320 ]
3) Patch 7411481 applied on Fri Jul 17 20:00:42 IST 2009 [ Base Bug(s): 7411481 ]
4) Patch 6771776 applied on Fri Jul 17 19:58:55 IST 2009 [ Base Bug(s): 6771776 ]
5) Patch 6702510 applied on Fri Jul 17 19:51:41 IST 2009 [ Base Bug(s): 6702510 ]
6) Patch 5586892 applied on Sat Dec 30 08:18:37 IST 2006
[ Base Bug(s): 5586892 5126270 4689959 5238255 ]
Verification from Opatch lsinventory �detail
oracle@xyz.com 7139339]$ opatch lsinventory -detail
Oracle Interim Patch Installer version 1.0.0.0.56
Copyright (c) 2006 Oracle Corporation. All Rights Reserved..
We recommend you refer to the OPatch documentation underOPatch/docs for usage
reference.We also recommend usingthe latest OPatch version. For the latest OPatch
versionand other support related issues, please refer to document293369.1 which is
viewable from metalink.oracle.com
Oracle Home:/oracle/ACE/apps/tech_st/10.1.3Oracle Home
Inventory:/oracle/ACE/apps/tech_st/10.1.3/inventoryCentral
Inventory:/oracle/ACE/inst/apps/ACE_samarth/admin/oraInventory
from:/oracle/ACE/apps/tech_st/10.1.3/oraInst.locOUI
location:/oracle/ACE/apps/tech_st/10.1.3/ouiOUI shared
library:/oracle/ACE/apps/tech_st/10.1.3/oui/lib/linux/liboraInstaller.soJava
location:/oracle/ACE/apps/tech_st/10.1.3/jre/1.4.2/bin/javaLog file
location:/oracle/ACE/apps/tech_st/10.1.3/.patch_storage//*.log
Creating log file "/oracle/ACE/apps/tech_st/10.1.3/.patch_storage/LsInventory__07-
17-2009_20-17-29.log"
Result:
PRODUCT NAME VERSION
============ =======
Agent Required Support Files Patch 10.1.0.5.0
Agent Required Support Files 10.1.0.2.0
Apache Module for Oracle Distributed Authoring and Versioning 10.1.2.1.0
Assistant Common Files Patch 10.1.0.5.0
Assistant Common Files 10.1.0.2.0
Bali Share 1.1.18.0.0
DataDirect Connect JDBC Drivers 10.1.2.0.1
DBJAVA Required Support Files Patch 10.1.0.5.0
DBJAVA Required Support Files 10.1.0.2.0
Documentation Required Support Files 10.1.0.3.0
Enterprise Manager Minimal Integration Patch 10.1.0.5.0
Enterprise Manager Minimal Integration 10.1.0.2.0
Enterprise Manager plugin Common Files 10.1.0.2.0
Enterprise Manager plugin Common Files 10.1.0.5.0
Extended Windowing Toolkit 3.3.18.0.0
HTTP Server Files 1.3.31.0.0
Oracle Application Server PatchSet 10.1.3.4.0
Oracle ASkernel Common 10.1.3.0.0
Oracle Business Rules 10.1.3.0.0
.
.
.
OPatch succeeded.
Now upgrade the Opatch using 6880880 (Unzip the patch directly into the 10.1.3
Oracle Home)
Do not Start the application services and try to login to the applications using
the port. As it throws login page cannot be displayed as the variable in context
are pointing to portal/AppsLogin.jsp.
This will be resolved once you complete applying the patch 7303030.

Step 3: Upgrading the Java JDK

Download the latest JDK from http://java.sun.com/javase/downloads/index.jsp

download jdk-6u14-linux-i586.bin
1. Be sure to shutdown all the middle tier services.
a) Perform JDK Upgrade in IAS_ORACLE_HOME:
Navigate to $IAS_ORACLE_HOME/appsutil/
$mv jdk/ jdk_old/
$mkdir jdk/
copy the jdk-6u14-linux-i586.bin to $IAS_ORACLE_HOME/appsutil/jdk
Install the bin file using
$./jdk-6u14-linux-i586.bin
This will install latest jdk in appsutil/jdk
Copy the *.ttf files from $FND_TOP/resource to
$IAS_ORACLE_HOME/appsutil/jdk/jre/lib/fonts.
Important: You need to do the steps as a post upgrade step if you complete with
7303030
b) Upgrade jre in $RDBMS_ORACLE_HOME
copy the jdk-6u14-linux-i586.bin to $RDBMS_ORACLE_HOME/appsutil
Source the database environment file
1. Navigate to $ORACLE_HOME/appsutil/
2. mv jre/ jre_old/
3. mkdir jre/
Install the jdk_version_linus-i586.bin to appsutil/jre
Verification of JDK installation
$ADJVAPRG -version
[oracle@prod appl]$ $ADJVAPRG -version
"1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)
echo $CLASSPATH
[oracle@prod appl]$ echo $CLASSPATH
/oracle/PRODN/apps/tech_st/10.1.3/appsutil/jdk/lib/dt.jar:
/oracle/PRODN/apps/tech_st/10.1.3/appsutil/jdk/lib/tools.jar:
/oracle/PRODN/apps/tech_st/10.1.3/appsutil/jdk/jre/lib/rt.jar:
/oracle/PRODN/apps/apps_st/comn/java/lib/appsborg.zip:
/oracle/PRODN/apps/tech_st/10.1.2/forms/java:
/
oracle/PRODN/apps/tech_st/10.1.2/forms/java/frmall.jar:/oracle/PRODN/apps/tech_st/1
0.1.2/jlib/ewt3.jar:/
oracle/PRODN/apps/tech_st/10.1.2/j2ee/OC4J_BI_Forms/applications/formsapp/formsweb/
WEB-INF/lib/frmsrv.jar:/oracle/PRODN/apps/apps_st/comn/java/classes
$AFJVAPRG -version
[oracle@prod appl]$ $AFJVAPRG -version
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)
echo $AF_CLASSPATH
Each should reflect the paths belonging to latest JDK like this
[IAS_ORACLE_HOME]/appsutil/jdk/lib/dt.jar,
[IAS_ORACLE_HOME]/appsutil/jdk/lib/tools.jar,
[IAS_ORACLE_HOME]/appsutil/jdk/jre/lib/rt.jar, and
[IAS_ORACLE_HOME]/appsutil/jdk/jre/lib/charsets.jar
Method:1
Create an jsp file under $OA_HTML like jdktest.jsp
The JDK version is: <%= System.getProperty("java.version") %>
compile the jdktest.jsp using ojspcompile, syntax is:
perl -x $FND_TOP/patch/115/bin/ojspCompile.pl --compile -s jdktest.jsp'
Dont check it now, as your middle tier services are down.
Check with Database Tier:
$cd $ORACLE_HOME/appsutil/jre/bin
./java -version
[oracle@prod jre]$ cd bin
[oracle@prod bin]$
./java -version
java version "1.6.0_14"
Java(TM) SE Runtime Environment (build 1.6.0_14-b08)
Java HotSpot(TM) Client VM (build 14.0-b16, mixed mode, sharing)

Run Autoconfig on both tiers

Step 4: Forms server Upgrade

In this Step upgradation of Forms server from 10.1.2.0.1 to 10.1.2.3 is to be done.

Backup the inventory file.
Source the application environment file
1. Unzip 5983622 and run ./runInstall
2. Supply oc4jadmin as 'secret' when prompted.
(Note here configuration assistant will fail at oc4j configuration Assistant,
Simply skip and click next. This is normal behavior for E Business Upgrade)
Once completed:
Apply the Following Patches using OPatch tool from TOOLS_ORACLE_HOME

Error was: OPatch failed with error code 73

OPatch version : 10.2.0.5.1

OUI version : 10.1.0.6.0
=====================
p3559326_10105_LINUX.zip
p6880880_102000_LINUX.zip ---
p4407272_10123_LINUX.zip
p7016961_101210_LINUX.zip
p4526825_10123_LINUX.zip
p7016961_10123_LINUX.zip
p5394728_10105_LINUX.zip
p5917053_10123_LINUX.zip
p7121788_10123_LINUX.zip
p5983622_10123_LINUX.zip
p7140392_10123_GENERIC.zip
p6371228_10123_LINUX.zip
p7329300_10123_LINUX.zip
p6857221_10123_LINUX.zip
p8300196_10123_GENERIC.zip
p8374931_10123_GENERIC.zip
Note: if you face the error below during any of the Opatch or ./runInstaller:
rwconverter error: like this
/ACE/apps/tech_st/10.1.2/lib//librw.a -lnsl/oracle/ACE/apps/tech_st/10.1.2//lib/
/librw.so: undefined reference to `rolgxinoci_cid'
collect2: ld returned 1 exit status
make: *** [rwbuilder] Error 1
DO the following:
Restore the file
librw.so, and librw.a
from old backup to $TOOLS_ORACLE_HOME/lib and run
$TOOLS_ORACLE_HOME/reports/lib/make -f ins_reports.mk install
The result will be
/oracle/ACE/apps/tech_st/10.1.2/lib,-
rpath,/oracle/ACE/apps/tech_st/10.1.2/jdk/jre/lib/i386:/lib:/usr/lib -lm `cat
/oracle/ACE/apps/tech_st/10.1.2/lib/sysliblist` -ldl -lpthread -lm
-L/oracle/ACE/apps/tech_st/10.1.2/lib -L/oracle/ACE/apps/tech_st/10.1.2/lib/stubs/
-lsnls10 -lpthread -ljvm -lhpi -Wl,-rpath,/usr/X11R6/lib -L/usr/X11R6/lib -lXm -lXt
-lX11 -lm -lXp -lXext /oracle/ACE/apps/tech_st/10.1.2/lib//librw.a -lnslmv
rwbuilder /oracle/ACE/apps/tech_st/10.1.2/bin/rwbuilderchmod 700
/oracle/ACE/apps/tech_st/10.1.2/bin/rwbuilder
then proceed with the patch, it should complete normally.
Create formsapp.ear
$FND_TOP/bin/txkrun.pl -script=CfgOC4JApp
Enter Application name for re-deployment ? forms
Enter Oc4j Instance password for re-deployment ? welcome (or current password)
error message 1
? No ">Run Autoconfig ? No
If you are prompted with oc4jadmin password is incorrect Do the following:
$INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml
$cp system-jazn-data.xml system-jazn-data-ori.xml
$vi system-jazn-data.xml
locate oc4j-admin section
[user]
[name]oc4jadmin[/name]
[display-name]OC4J Administrator[/display-name]
[guid]88836370D11611DC9F30F9C1CD6F1A73[/guid]
[description]OC4J Administrator[/description]
[credentials]{903}F+iG1A46edXG9RdfY0pD2O4Ge/qyEjsg[/credentials]
[/user]
replace
{903}F+iG1A46edXG9RdfY0pD2O4Ge/qyEjsg
with !Welcome [Please note '!' is important]
then issue oc4jadmin password as 'Welcome'. it will pass the step.
Run Autoconfig on Apps Tier
Apply Interoperability Patch 7120543
Apply OPatch 6880880 as in the previous section to upgrade Opatch tool to
1.0.0.0.62
Rebuild Forms and Reports executables
cd $ORACLE_HOME/forms/lib32
Note: if this directory does not exist: cd $ORACLE_HOME/forms/lib
$ make -f ins_forms.mk install
cd $ORACLE_HOME/reports/lib32
Note: if this directory does not exist: cd $ORACLE_HOME/reports/lib
$ make -f ins_reports.mk install
Regenerate appsborg.zip and appsborg2.zip using adadmin

Step 5: upgrading to 12.1.1

Apply AD.B.1 Patch (7461070)

Copy adgrants.sql from patch/admin directory to $RDBMS_ORACLE_HOME/appsutil/admin
directory
If it is not present create a directory /admin inside $RDBMS_ORACLE_HOME/appsutil
run adgrants.sql as sys user with syntax
sqlplus "/as sysdba" @adgrants.sql APPS
once finished,
Apply the patch AD.B.1
run d below patch as applmgr:-
cd /software/qadar_patches/7461070
adpatch
Recreate grants and synonyms using adadmin
Run adadmin -> Maintain Applications Database Entities menu ->
Re-create grants and synonyms for APPS schema.

Apply the Main patch 7303030 (Contains 8 parts)

During the patch run, please expect
XDOLoader.class will fail on user xdo
Follow the procedure from http://balajiabhi.blogspot.com/2009/07/rebuilding-xdo-
objects-failed-worker-on.html
(Completed within 15 hours)
Apply online Help patch 7303031 using adpatch. (It takes 28 minutes)
Apply the product specific patches as per the metalink document stated above.
Start the application services using adstrtal.sh from $ADMIN_SCRIPT_HOME
Verify the forms version using 'About Applications' from Forms session.
It should show the version as follows

To get other versions, enable about this page link in LOGINPAGE of the server
To do this please do the following:
set the profile option FND: Diagnostics = Yes
Then bounce the middle tier services, you will see a link 'About This Page' at the
bottom of the web page

The output of the About this page will give all the particulars about the version
upgrade.

g:\prints\ebs_upgrade\12.1.1 to 12.1.3.txt
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Oracle Applications Upgrade from 12.1.1 to 12.1.3 ( With Database 11.1.0.7 )
=============================================================================:

The below steps outline the step by step actions to upgrade Oracle applications
from 12.1.1 to 12.1.3
Bring down all the services and Take cold backup of the instance (Recommended)

Step.1
Modify Initialization Parameters:

_disable_fast_validate=TRUE
recyclebin=off
_pga_max_size

Use the following command to change the mentioned parameters:

SQL> alter system set recyclebin=off scope=spfile;

System altered.
SQL> alter system set "_disable_fast_validate"=TRUE SCOPE=spfile;
System altered.
SQL> alter system set "_pga_max_size"=104857600 scope=spfile;

If you don't change the _pga_max_size to greater than 104857600. You may get the
following error during upgrade.
ORA-04030: out of process memory when trying to allocate 822904 bytes
(pga heap,kco buffer)
ORA-07445: exception encountered: core dump [dbgtfdFileWrite()+48]
SIGSEGV] [ADDR:0xFFFFFFFF7FFC1C88] [PC:0x1063BD2D0] [Address not mapped
to object]

Step.2
Apply Database Patches
Please check and apply the below database patches.
For all UNIX/Linux platforms
7111245
7211965
7330434
7486407
7627743
7639602
7684818
8199107
8639653
8940108
9026927
9066130
9554727
9743057

For Linux x86-64, patch 7319922 contained within 7684818 was packaged incorrectly.

The new version of patch 7319922 has to be applied. Perform the following
instructions:
Go to the 11.1.0.7 $ORACLE_HOME/inventory/oneoffs/7319922 directory.
Run "opatch rollback -id 7319922" to rollback patch 7319922.
Download the new version of patch 7319922 on My Oracle Support.
Go to the patch 7319922 directory.
Run "opatch apply"

Step.3
Techstack Upgrade:
A)Verify the 10.1.3.X Oracle Home version and the required version is 10.1.3.4 or
higher <Use Document 454811.1> (for 10.1.3.5 ) or <Document 728531.1> (for 10.1.3.4
) to upgrade it

TO check the versions perform the below

----------------------------------------
cd $INST_TOP/ora/10.1.3
. ./$CONTEXT_NAME.env
$ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc
| egrep 'Oracle Application Server 10g|
Patch of Oracle Application Server 10g'
Note: Oracle Application Server 10g signifies the Base Install and
Patch of Oracle Application Server 10g signifies the Patchset on top of it
Example:
$ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc
| egrep 'Oracle Application Server 10g|
Patch of Oracle Application Server 10g'
Oracle Application Server 10g 10.1.3.0.0
Patch of Oracle Application Server 10g 10.1.3.4.0

B)Verify the 10.1.2.X Oracle Home version and the required version is 10.1.2.3
<Use Document 437878.1 to upgrade it.>

TO check the versions perform the below

----------------------------------------
Log-out and Re-Login, before performing the following steps.

$ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc

| egrep 'Oracle Application Server 10g|
Patch of Oracle Application Server 10g'
Note: Oracle Application Server 10g signifies the Base Install
Patch of Oracle Application Server 10g signifies the Patchset on top of it
Example:
$ORACLE_HOME/OPatch/opatch lsinventory -detail -invPtrLoc $ORACLE_HOME/oraInst.loc
| egrep 'Oracle Application Server 10g|

Patch of Oracle Application Server 10g'

Oracle Application Server 10g 10.1.2.0.2
Patch of Oracle Application Server 10g 10.1.2.3.0
Step.4
Applications upgrade

a)Apply R12.AD.B.DELTA.3 <Patch 9239089>

Usage:
------
1.Create $ORACLE_HOME/appsutil/admin on the database server.
2.Copy adgrants.sql (UNIX) from this patch directory to
$ORACLE_HOME/appsutil/admin.
3.Set the environment to point to ORACLE_HOME on the database server.
4.Use SQL*Plus to run the script:
$ sqlplus /nolog
SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql APPLSYS

Apply the below patches using adpatch options:

-Enable maintenance mode

adpatch defaultsfile=$APPL_TOP/admin/$TWO_TASK/adalldefaults.txt
logfile=u9239089.log patchtop=/software/patches/9239089 driver=u9239089.drv
workers=10

Apply u9239089.drv of the patch using adpatch

Apply u9239090.drv of the patch using adpatch
Apply the latest consolidated online help
Apply u9239095.drv of the patch using adpatch

Post-Update Steps:

Apply post-install Oracle E-Business Suite Applications Technology patches.

(Required)

Apply mandatory Patch 9817770 (9817770:R12.ATG_PF.B [POST-R12.ATG_PF.B.DELTA.3

CONSOLIDATED PATCH].)
Apply u9817770.drv of the patch using adpatch
Apply mandatory Patch 9966055 (9966055:R12.FND.B [TRANSLATED VERSION OF FNDSCSGN
NOT LAUNCHED].)
Apply u9966055.drv of the patch using adpatch

Step.5
Run autoconfig on both tiers:

Application tier:
-----------------
$cd $ADMIN_SCRIPTS_HOME
$adautocfg.sh
Run the admkappsutil.pl utility to create the file appsutil.zip in the
<INST_TOP>/admin/out directory.
$perl $AD_TOP/bin/admkappsutil.pl

Database tier:
--------------
Copy or FTP the appsutil.zip file to the <RDBMS ORACLE_HOME>.
$cd $ORACLE_HOME
$unzip -o appsutil.zip
Run AutoConfig on the Database Node:
$cd $ORACLE_HOME/appsutil/scripts
$adautocfg.sh
Step.6
Database Tier and Application Tier
Re-run adpreclone.pl on the database tier and the application tier. Since updates
included in Oracle E-Business Suite Release 12.1.3 were applied to the system,
adpreclone must be run again to apply the updates to the clone directory structures
that were used during cloning.

perl adpreclone.pl dbTier

perl adpreclone.pl appsTier

Step.7
Modify Initialization Parameters and bounce database

-remove entry _disable_fast_validate=TRUE

-set recyclebin=ON
-Disable maintenance mode

Step.8
Start Applications and Perform a health check of the instance.

cd $ADMIN_SCRIPTS_HOME
sh adstrtal.sh apps/apps

SQL> select release_name from fnd_product_groups;

RELEASE_NAME
-------------
12.1.3

Reference Metalink Document:

Oracle E-Business Suite Release 12.1.3 Readme [ID 1080973.1]
Database Preparation Guidelines for an E-Business Suite Release 12.1.1 Upgrade [ID
761570.1]
Database Initialization Parameters for Oracle Applications Release 12 [ID 396009.1]
Oracle� E-Business Suite Upgrade Guide

Changes In 12.1.3 While Doing Clone

====================================:

1.while running adcfgclone on appsTier it will ask hostname(FQDN).

2.after providing all the inputs to adcfgclone.pl it will ask to start the services
or not.
3.when you are running cmclean.sql it will give notification to stop all the
concurrent managers.

No Need to Disable Fast Validation

===================================:

With database versions prior to Oracle 11gR2 (11.2.0.2), you needed to disable Fast
Validation in the database when performing Applications upgrades or maintenance
operations.

To disable Fast Validation, you needed to add the following parameter to the
database initialization parameter file:

_disable_fast_validate=TRUE
Failing to set this in Oracle Database 11gR1 (11.1.0.7) or 11gR2 (11.2.0.1) could
lead to invalid objects and forms or reports compilation failures, potentially
causing problems with product functional flows.

Starting with 11gR2 (11.2.0.2), this parameter no longer needs to be set for
upgrade or maintenance operations (and then unset again for normal operations).
This is one less thing for you to have to remember.

g:\prints\ebs_upgrade\before upgrade.txt
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Production downtime:

Downtime can be split into two phases:

-Technical (DBA) downtime � when only DBAs are accessing the system and running
upgrade scripts exclusively.

-Functional downtime � when DBAs and functional and development teams work in
parallel, but the system is not yet released for end-users.

Have bigger redo logs

� Database in no archive log mode
� Disabling Auditing
� Disable flashback
� Disable TDE
� Enable Degree of Parallelism (DOP)
� Tune init.ora parameters
� SGA_MAX_SIZE
� PGA_AGGREGATE_SIZE
� db_file_multiblock_read_count
� Copyright 2014. Apps Associates LLC. 14
Reduce Upgrade Downtime
DB Considerations
� Disable custom triggers and business events
� Tablespace sizing
� Allocate parallel channels for RMAN backups
� Recycle bin = off
� Copyright 2014. Apps Associates LLC. 15
Reduce Upgrade Downtime
Application Considerations
� Batch size
� AD workers
� Increase ADJREOPTS, ADJRIOPTS parameters (Ref: 557926.1)
� Avoid errors �occurred during initialization of VM, could not reserve enough
space
for object heap errors�
� Distributed AD
� Copyright 2014. Apps Associates LLC. 16
Reduce Upgrade Downtime
Application Considerations
� Merge NLS patches
� Apply Help and NLS patches online
� Apply HR Global driver online
� Merge and apply product specific patches (post upgrade)
� 62 patches merged as 10 patches
� 20 hours patching time reduced to 8 hours
� Automate the upgrade process as much as possible
� Use Shell scripts, adalldefaults.txt, identify the steps we can do ahead of
cutover
time
� Time every activity and deal with bottlenecks
� A baseline for upgrade execution time, analyse adtimrpt.sql output
� Maintain Issues & Resolution document for quick reference
� Maintain cookbook
� Cookbook includes end to end activities along with various phases which are
sequentially listed down
� Copyright 2014. Apps Associates LLC. 18
Reduce Upgrade Downtime
Process Considerations
� Maintain Checklist
� Crosscheck the checklist before start any major tasks (like 12.1.1 or 12.1.3
upgrade
etc.) This checklist should have SGA, PGA, job_queue_processes,
parallel_max_servers, heap size etc.