Step by Step instruction on EBS R12.1.3 upgrade to R12.2.0
In this post, I am going to share step-by-step instructions on upgrading EBS R12.1.3 to R12.2.
My Source Application version: R12.1.3
Database version: 12.1.0.2
Make sure the Database is up and running and Application services are down for 12.1.3.
1) Download the R12.2.0 software zip and keep on the server.(How to Download EBS 12.2.0)
2) Add Service ebs_patch in EBS Database
[oracle@ebsupgrade 12.1.0]$ sqlplus '/as sysdba' SQL*Plus: Release 12.1.0.2.0 Production on Thu Dec 10 21:13:21 2020 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> show parameter service NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ service_names string GOLD121 SQL> show parameter spfile; NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ spfile string /tarmachin/EBS1213/GOLD/DB/tec h_st/12.1.0/dbs/spfileGOLD121. ora SQL> alter system set service_names='GOLD121,ebs_patch' scope=both; System altered. SQL> show parameter service NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ service_names string GOLD121,ebs_patch
3) Download Patch 17537119 on the server and run as below. No need to apply the patches as recommended for now.
[oracle@ebsupgrade EBS1213_1220_upgrade_patches]$ pwd /media/sf_Downloads/EBS1213_1220_upgrade_patches [oracle@ebsupgrade EBS1213_1220_upgrade_patches]$ ls checkDBpatch.cmd checkDBpatch.sh checkMTpatch.cmd checkMTpatch.sh db mw p17537119_R12_GENERIC.zip README.txt [oracle@ebsupgrade EBS1213_1220_upgrade_patches]$ ./checkDBpatch.sh contextfile=$CONTEXT_FILE +===============================================================+ | Copyright (c) 2005, 2020 Oracle and/or its affiliates. | | All rights reserved. | | Oracle E-Business Suite Release 12.2 | | Database EBS Technology Codelevel Checker | +===============================================================+ Validating context file: /tarmachin/EBS1213/GOLD/DB/tech_st/12.1.0/appsutil/GOLD121_ebsupgrade.xml Using context file from command line argument: /tarmachin/EBS1213/GOLD/DB/tech_st/12.1.0/appsutil/GOLD121_ebsupgrade.xml Starting Database EBS Technology Codelevel Checker, Version 120.82 Thu Dec 10 22:36:35 IST 2020 Log file for this session : /media/sf_Downloads/EBS1213_1220_upgrade_patches/log/checkDBpatch_7817.log Identifying database release. Database release set to 12.1.0.2. Connecting to database. Database connection successful. Database GOLD121 is in READ WRITE mode. Identifying APPS and APPLSYS schema names. - APPS schema : APPS - APPLSYS schema : APPLSYS Checking for DB-ETCC results table. Creating DB-ETCC results table. Created the table to store DB-ETCC results.
4) Setup new layout for R12.2 file system. Login as root and go to the directory where the EBS12.2.0 zip files are kept and run rapidwiz.
[root@ebsupgrade APPS12.2]# pwd /tarmachin/EBS12210/software/APPS12.2 [root@ebsupgrade APPS12.2]# ls V100052-01_1of3.zip V100060-01_1of3.zip V29856-01.zip V35804-01_1of2.zip V100052-01_2of3.zip V100060-01_2of3.zip V35802-01.zip V35804-01_2of2.zip V100052-01_3of3.zip V100060-01_3of3.zip V35803-01_1of3.zip V46095-01_1of2.zip V100059-01_1of2.zip V100061-01.zip V35803-01_2of3.zip V46095-01_2of2.zip V100059-01_2of2.zip V100102-01.zip V35803-01_3of3.zip V75792-01.zip
Patching the Stage Area
After running the buildStage script, you should patch the stage area with the latest consolidated fixes since the release of the current StartCD. For StartCD 12.2.0.51, the consolidated fixes are delivered in Patch 25525148.
Download Patch 25525148.
Unzip this patch using the following command:
unzip p25525148_R12_GENERIC.zip.Change to the 25525148 directory.
Patch the stage area using the following commands:
UNIX:
sh patchRIStage.sh
When prompted for the location of the Rapid Install stage, enter the path to the stage area you created for StartCD 12.2.0.51.
Tip: Run the script as the same user(root) that you used to run the buildStage script when creating the stage area.
[root@ebsupgrade 25525148]# ./patchRIStage.sh Patch directory is /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148 Enter the location of the Rapid Install Stage area:/tarmachin/EBS12210/software/APPS12.2 Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148/Disk1/rapidwiz/template/adrun12c.sh to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adrun12c.sh. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148/Disk1/rapidwiz/template/adrundb.sh to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adrundb.sh. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148/Disk1/rapidwiz/template/adrunat.sh to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adrunat.sh. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148/Disk1/rapidwiz/etc/appsutil.zip to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/appsutil.zip. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148/Disk1/rapidwiz/etc/adlsnr10RAC.ora to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/adlsnr10RAC.ora. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148/Disk1/rapidwiz/jlib/java/oracle/apps/ad/tools/configuration/RACAutoConfig.class to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/jlib/java/oracle/apps/ad/tools/configuration/RACAutoConfig.class. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148/Disk1/rapidwiz/jlib/java/oracle/apps/ad/tools/configuration/RACAutoConfig$ClusterCmdHolder.class to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/jlib/java/oracle/apps/ad/tools/configuration/RACAutoConfig$ClusterCmdHolder.class. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148/Disk1/rapidwiz/etc/admerge.pl to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/admerge.pl. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148/Disk1/rapidwiz/template/afinit_db121.ora to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/afinit_db121.ora. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/25525148/Disk1/rapidwiz/template/afinit_db121RAC.ora to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/afinit_db121RAC.ora. Completed patching of the Rapid Install Stage area /tarmachin/EBS12210/software/APPS12.2
Finally, apply the additional Rapid Install patch, Patch 31033613.
Patch 25525148 should be applied Patch 31033613.
Download Patch 31033613 from My Oracle Support.
Unzip this patch using the following command:
unzip p31033613_R12_GENERIC.zip
Change to the 31033613 directory.
Patch the Rapid Install stage area using the following commands:
UNIX:
sh patchRIStage.sh
When prompted for the location of the Rapid Install stage, enter the path to the stage area you created for StartCD 12.2.0.51.
[root@ebsupgrade 31033613]# ./patchRIStage.sh Patch directory is /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613 Enter the location of the Rapid Install Stage area:/tarmachin/EBS12210/software/APPS12.2 Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/template/adcfgdeploy.sh to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adcfgdeploy.sh. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/template/adcfgdeploy.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adcfgdeploy.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/template/adrundeploy.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adrundeploy.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/template/adrundb.sh to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adrundb.sh. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/template/adrundb.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adrundb.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/template/adrunat.sh to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adrunat.sh. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/template/adrunat.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adrunat.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/template/adrunfmw.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adrunfmw.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/template/adsetpass.sh to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adsetpass.sh. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/template/adsetpass.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/template/adsetpass.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/afcpctx.sh to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/afcpctx.sh. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/afcpctx.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/afcpctx.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/bin/riwTDBup.sh to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/bin/riwTDBup.sh. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/bin/riwTDBup.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/bin/riwTDBup.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/adstartallmanaged.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/adstartallmanaged.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/oamksvc.obj to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/oamksvc.obj. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/OAMKSVC.exe to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/OAMKSVC.exe. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/adwindowsservicesuser.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/adwindowsservicesuser.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/adsvNodeManager.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/adsvNodeManager.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/igccmprf.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/igccmprf.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/jlib/java/oracle/apps/ad/rapidwiz/data/AppsInstall.class to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/jlib/java/oracle/apps/ad/rapidwiz/data/AppsInstall.class. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/jlib/java/oracle/apps/ad/clone/util/OracleHomeCloner.class to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/jlib/java/oracle/apps/ad/clone/util/OracleHomeCloner.class. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/jlib/java/oracle/apps/ad/clone/util/OracleHomeCloner$AbsorbPrintStream.class to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/jlib/java/oracle/apps/ad/clone/util/OracleHomeCloner$AbsorbPrintStream.class. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/jlib/java/oracle/apps/ad/rapidwiz/util/CheckerClass.class to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/jlib/java/oracle/apps/ad/rapidwiz/util/CheckerClass.class. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/jlib/java/oracle/apps/ad/util/TimedProcess.class to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/jlib/java/oracle/apps/ad/util/TimedProcess.class. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/jlib/java/oracle/apps/ad/util/TimedProcess$TimedProcessProcess.class to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/jlib/java/oracle/apps/ad/util/TimedProcess$TimedProcessProcess.class. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/jlib/java/oracle/apps/ad/util/TimedProcess$AsyncStreamReader.class to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/jlib/java/oracle/apps/ad/util/TimedProcess$AsyncStreamReader.class. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/jlib/java/oracle/apps/ad/util/TimedProcess$TimedProcessTimer.class to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/jlib/java/oracle/apps/ad/util/TimedProcess$TimedProcessTimer.class. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/txkManageDBConnectionPool.pl to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/txkManageDBConnectionPool.pl. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/TechInstallers/ASInstallHome/fnd/patch/115/etc/txkUpdateBSU.sh to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/TechInstallers/ASInstallHome/fnd/patch/115/etc/txkUpdateBSU.sh. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/TechInstallers/ASInstallHome/fnd/patch/115/etc/txkUpdateBSU.cmd to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/TechInstallers/ASInstallHome/fnd/patch/115/etc/txkUpdateBSU.cmd. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/Java.pm to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/Java.pm. Copied /media/sf_Downloads/EBS1213_1220_upgrade_patches/31033613/Disk1/rapidwiz/etc/TechstackDB.pm to /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz/etc/TechstackDB.pm. Completed patching of the Rapid Install Stage area /tarmachin/EBS12210/software/APPS12.2
Give 777 permission to stage location.
[root@ebsupgrade rapidwiz]# cd /tarmachin/EBS12210
[root@ebsupgrade EBS12210]# ls -ltr
total 8
drwxr-xr-x. 3 root root 4096 Dec 10 21:01 software
[root@ebsupgrade EBS12210]# chmod -R 777 software
[root@ebsupgrade EBS12210]# ls -ltrr
total 8
drwxrwxrwx. 3 root root 4096 Dec 10 21:01 software
Now kick-off Rapidwiz from root user.
[root@ebsupgrade rapidwiz]# pwd /tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz [root@ebsupgrade rapidwiz]# ls bin etc jlib rapidwiz RapidWizVersion template ClientWiz.cmd File jre RapidWiz.cmd RapidWizVersion.cmd unzip driver images oui RapidWiz.ini TechInstallers Xpatches [root@ebsupgrade rapidwiz]# ./rapidwiz
b) Default Territory: AMERICA
c) Database Character Set: AL32UTF8
d) APPL_TOP Character Set: AL32UTF8
e) IANA Character Set: UTF-8
As soon as you click next it will do a pre-check to validate.
Please ignore the Technology CodeCheck, These patches we will apply later and proceed as per the below screenshots.
Verify the new EBS12.2 file system layout has been created.
[applmgr@ebsupgrade APPS]$ pwd /tarmachin/EBS12210/GOLD/APPS [applmgr@ebsupgrade APPS]$ ls -ltr total 12 drwxr-xr-x. 5 applmgr oinstall 4096 Dec 11 00:34 fs1 drwxr-xr-x. 5 applmgr oinstall 4096 Dec 11 00:34 fs2 drwxr-xr-x. 4 applmgr oinstall 4096 Dec 11 03:14 fs_ne
5) Enable the maintenance mode by setting the environment file from the new EBS12.2 file system. Please use fs1 only as it will be the run file system.
/tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl [applmgr@ebsupgrade appl]$ ls -ltr APPSGOLD121_ebsupgrade.env -rw-r--r--. 1 applmgr oinstall 1112 Dec 11 05:46 APPSGOLD121_ebsupgrade.env
[applmgr@ebsupgrade appl]$ . APPSGOLD121_ebsupgrade.env [applmgr@ebsupgrade appl]$ adadmin
AD Administration Main Menu -------------------------------------------------- 1. Generate Applications Files menu 2. Maintain Applications Files menu 3. Compile/Reload Applications Database Entities menu 4. Maintain Applications Database Entities menu 5. Change Maintenance Mode 6. Exit AD Administration
Select option 5 and then select option 1. Once maintenance mode is set, please exit.
Enter your choice [6] : 5
Change Maintenance Mode
----------------------------------------
Maintenance Mode is currently: [Disabled].
Maintenance mode should normally be enabled when patching
Oracle E-Business Suite and disabled when users are logged on
to the system. See the Oracle E-Business Suite Maintenance
Utilities manual for more information about maintenance mode.
Please select an option:
1. Enable Maintenance Mode
2. Disable Maintenance Mode
3. Return to Main Menu
Enter your choice [3] : 1 sqlplus -s &un_apps/***** @/tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/adsetmmd.sql ENABLE Successfully enabled Maintenance Mode.
6) Apply AD 12.2 Upgrade Driver
Download below patches and need to be applied
10117518
22742061
Connect as database user, source the environment file and Create
$ORACLE_HOME/appsutil/admin if not present.
[oracle@ebsupgrade ~]$ . GOLD121_ebsupgrade.env [oracle@ebsupgrade ~]$ cd $ORACLE_HOME/appsutil [oracle@ebsupgrade appsutil]$ ls -ld admin drwxr-xr-x. 2 oracle oinstall 4096 Dec 9 18:16 admin
Compare the version of adgrants.sql(UNIX) in $APPL_TOP/admin to that in patch directory.
Copy the higher version of adgrants.sql (UNIX) to $ORACLE_HOME/appsutil/admin.
Set the environment to point to ORACLE_HOME on the database server.
sqlplus /nolog
SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql <APPS schema name>
[applmgr@ebsupgrade admin]$ pwd
/media/sf_Downloads/EBS1213_1220_upgrade_patches/10117518/admin
[applmgr@ebsupgrade admin]$ adident Header adgrants.sql
adgrants.sql:
$Header adgrants.sql 120.67.12020000.8 2012/10/05 15:19:21 sstomar ship $
$Header adgrants.sql 120.67.12020000.8 2012/10/05 15:19:21 sstomar ship $
$Header adgrants.sql 120.67.12020000.8 2012/10/05 15:19:21 sstomar ship $
$Header adgrants.sql 120.67.12020000.8 2012/10/05 15:19:21 sstomar ship $
$Header adgrants.sql 120.67.12020000.8 2012/10/05 15:19:21 sstomar ship $
[applmgr@ebsupgrade admin]$ ls -ltr /tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/admin/adgrants.sql
-rwxr-xr-x. 1 applmgr oinstall 96710 Nov 24 2012 /tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/admin/adgrants.sql
[applmgr@ebsupgrade admin]$ adident Header /tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/admin/adgrants.sql
/tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/admin/adgrants.sql:
$Header adgrants.sql 120.67.12020000.8 2012/10/05 15:19:21 sstomar ship $
$Header adgrants.sql 120.67.12020000.8 2012/10/05 15:19:21 sstomar ship $
$Header adgrants.sql 120.67.12020000.8 2012/10/05 15:19:21 sstomar ship $
$Header adgrants.sql 120.67.12020000.8 2012/10/05 15:19:21 sstomar ship $
$Header adgrants.sql 120.67.12020000.8 2012/10/05 15:19:21 sstomar ship $
[applmgr@ebsupgrade admin]$ cd ../../22742061/admin/ [applmgr@ebsupgrade admin]$ ls -ltr total 300 -rwxrwx---. 1 root vboxsf 9580 Jan 1 2002 Preinstall_Codelevel_MP.txt -rwxrwx---. 1 root vboxsf 3717 Jan 1 2002 adsysapp2.sql -rwxrwx---. 1 root vboxsf 97806 Jan 1 2002 adgrants.sql -rwxrwx---. 1 root vboxsf 97741 Jan 1 2002 adgrants_nt.sql -rwxrwx---. 1 root vboxsf 92139 Jan 1 2002 adddlb.pls [applmgr@ebsupgrade admin]$ adident Header adgrants.sql adgrants.sql: $Header adgrants.sql 120.67.12020000.36 2015/07/16 09:22:15 absandhw ship $ $Header adgrants.sql 120.67.12020000.36 2015/07/16 09:22:15 absandhw ship $ $Header adgrants.sql 120.67.12020000.36 2015/07/16 09:22:15 absandhw ship $ $Header adgrants.sql 120.67.12020000.36 2015/07/16 09:22:15 absandhw ship $ $Header adgrants.sql 120.67.12020000.36 2015/07/16 09:22:15 absandhw ship $
Copy adgrants from 22742061 to DB oracle home.
[oracle@ebsupgrade 10117518]$ cd /media/sf_Downloads/EBS1213_1220_upgrade_patches/22742061/admin [oracle@ebsupgrade admin]$ ls -ltr total 300 -rwxrwx---. 1 root vboxsf 9580 Jan 1 2002 Preinstall_Codelevel_MP.txt -rwxrwx---. 1 root vboxsf 3717 Jan 1 2002 adsysapp2.sql -rwxrwx---. 1 root vboxsf 97806 Jan 1 2002 adgrants.sql -rwxrwx---. 1 root vboxsf 97741 Jan 1 2002 adgrants_nt.sql -rwxrwx---. 1 root vboxsf 92139 Jan 1 2002 adddlb.pls [oracle@ebsupgrade admin]$ cp adgrants.sql /tarmachin/EBS1213/GOLD/DB/tech_st/12.1.0/appsutil/admin/
[oracle@ebsupgrade admin]$ sqlplus /nolog SQL*Plus: Release 12.1.0.2.0 Production on Fri Dec 11 18:24:42 2020 Copyright (c) 1982, 2014, Oracle. All rights reserved. SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql apps
We will need to merge both patches and apply. Remember the source environment is set from fs1.
Create AD_source and AD_target directory and copy both patches to AD_source. Make sure the owner of directories is applmgr.
[applmgr@ebsupgrade patches]$ admrgpch -s /tarmachin/patches/AD_source -d /tarmachin/patches/AD_target -merge_name ad_cup7_patch -admode Executing the merge of the patch drivers -- Processing patch: /tarmachin/patches/AD_source/22742061 -- Processing file: /tarmachin/patches/AD_source/22742061/u22742061.drv -- Done processing file: /tarmachin/patches/AD_source/22742061/u22742061.drv -- Done processing patch: /tarmachin/patches/AD_source/22742061 -- Processing patch: /tarmachin/patches/AD_source/10117518 -- Processing file: /tarmachin/patches/AD_source/10117518/u10117518.drv -- Done processing file: /tarmachin/patches/AD_source/10117518/u10117518.drv -- Done processing patch: /tarmachin/patches/AD_source/10117518 Copying files... 5% complete. Copied 47 files of 925... 10% complete. Copied 93 files of 925... 15% complete. Copied 139 files of 925... 20% complete. Copied 185 files of 925... 25% complete. Copied 232 files of 925... 30% complete. Copied 278 files of 925... 35% complete. Copied 324 files of 925... 40% complete. Copied 370 files of 925... 45% complete. Copied 417 files of 925... 50% complete. Copied 463 files of 925... 55% complete. Copied 509 files of 925... 60% complete. Copied 555 files of 925... 65% complete. Copied 602 files of 925... 70% complete. Copied 648 files of 925... 75% complete. Copied 694 files of 925... 80% complete. Copied 740 files of 925... 85% complete. Copied 787 files of 925... 90% complete. Copied 833 files of 925... 95% complete. Copied 879 files of 925... 100% complete. Copied 925 files of 925... Character-set converting files... 2 unified drivers merged. Patch merge completed successfully Please check the log file at ./admrgpch.log.
Source fs1 file system environment file.
cd /tarmachin/patches/AD_target
Run
adpatch
when prompted for drive file, give the merge driver file name
u_ad_cup7_patch.drv
It will take around 1 hrs to complete.
7) Fix Timestamp Mismatch
Download patch 17268684 and unzip.
Copy file 17268684/admin/ADZDDTFIX.sql from patch to DB ORACLE HOME
[oracle@ebsupgrade EBS1213_1220_upgrade_patches]$ cp 17268684/admin/ADZDDTFIX.sql $ORACLE_HOME/appsutil/admin
Connect as system user only and execute the script.
[oracle@ebsupgrade admin]$ sqlplus system/manager SQL*Plus: Release 12.1.0.2.0 Production on Fri Dec 11 19:19:32 2020 Copyright (c) 1982, 2014, Oracle. All rights reserved. Last Successful login time: Fri Dec 11 2020 19:08:03 +05:30 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> @ADZDDTFIX.sql begin dbms_utility.invalidate(20857,NULL,0); dbms_utility.invalidate(20837,NULL,0); dbms_utility.invalidate(20849,NULL,0); dbms_utility.invalidate(20791,NULL,0); dbms_utility.invalidate(20829,NULL,0); dbms_utility.invalidate(233652,NULL,0); dbms_utility.invalidate(20838,NULL,0); dbms_utility.invalidate(233653,NULL,0); end; / exec sys.utl_recomp.recomp_parallel; exit;
An out file will be created.
[oracle@ebsupgrade admin]$ cat adzddtfix.out begin dbms_utility.invalidate(20857,NULL,0); dbms_utility.invalidate(20837,NULL,0); dbms_utility.invalidate(20849,NULL,0); dbms_utility.invalidate(20791,NULL,0); dbms_utility.invalidate(20829,NULL,0); dbms_utility.invalidate(233652,NULL,0); dbms_utility.invalidate(20838,NULL,0); dbms_utility.invalidate(233653,NULL,0); end; / exec sys.utl_recomp.recomp_parallel; exit;
Execute the adzddtfix.out file from the system user.
[oracle@ebsupgrade admin]$ sqlplus system/manager
SQL*Plus: Release 12.1.0.2.0 Production on Fri Dec 11 19:21:45 2020
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Last Successful login time: Fri Dec 11 2020 19:19:33 +05:30
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> @adzddtfix.out
PL/SQL procedure successfully completed.
PL/SQL procedure successfully completed.
Re-execute script ADZDDTFIX.sql to check for any pending TimeStamp Mismatch issues.It should show no output.
8) Apply Consolidated Upgrade Patch and Run the 12.2.0 Upgrade
Connect as sysdba at db node and set
sec_case_sensitive_logon to False if set to True.
alter system set sec_case_sensitive_logon=false;
I have already kept it false so nothing to do.
SQL> show parameter case NAME TYPE VALUE ------------------------------------ ----------- ------------------------------ sec_case_sensitive_logon boolean FALSE
Download 22742071
Go to the Application node and run below from the patch location. Source fs1 environment file.
[applmgr@ebsupgrade patches]$ cd 22742071
[applmgr@ebsupgrade 22742071]$ pwd
/tarmachin/patches/22742071
adpatch preinstall=y
Now merge the patch.
Note: American English Patch driver u10124646.drv comes with 12.2 filesystem layout installation as done earlier
[applmgr@ebsupgrade 22742071]$ cd $AU_TOP/patch/115/driver [applmgr@ebsupgrade driver]$ ls augenmsg.drvx ausstats.drvx u10124646.drv u10201000.drv [applmgr@ebsupgrade driver]$ admrgpch -d . -preinstall -master u10124646.drv Executing the merge of the patch drivers -- Processing file: /tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/admin/GOLD121/preinstall/u22742071.drv -- Done processing file: /tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/admin/GOLD121/preinstall/u22742071.drv -- Processing file: u10124646.drv -- Done processing file: u10124646.drv 2 unified drivers merged. Patch merge completed successfully Please check the log file at ./admrgpch.log.
The default merged driver by name u_merged.drv is then created in the destination directory.
Apply the merge patch on fs1 filesystem. Source the environment file.
[applmgr@ebsupgrade driver]$ cd /tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/au/12.0.0/patch/115/driver [applmgr@ebsupgrade driver]$ adpatch options=nocopyportion,nogenerateportion
It will take 6-7 hrs to complete.
Please keep monitoring the database alert log and patch log on other putty/terminal sessions.
-----------------------------------------------------------------------------------------------------------------------------
Known Error:
Updating FND_PRODUCT_GROUPS.release_name, if necessary... Done saving Patch History information. AutoPatch error: adptaskStoreTimInfoToHist: Error while inserting into AD_PROGRAM_RUN_TASK_JOBS. AutoPatch error: ORA-01653: unable to extend table APPLSYS.AD_PROGRAM_RUN_TASK_JOBS by 16 in tablespace APPS_TS_TX_DATA AutoPatch error: adpmrp: Error calling adptaskStoreTimInfoToHist(2).
Add space to tablespace/or autoextend the datafile.Rerun adpatch again.
Solution:
SQL> select file_name,bytes/1024/1024,autoextensible from dba_data_files where tablespace_name='APPS_TS_TX_DATA'; FILE_NAME BYTES/1024/1024 AUT ---------------------------------------------------------------------- --------------- --- /tarmachin/EBS1213/GOLD/DB/apps_st/data/a_txn_data04.dbf 1744 NO /tarmachin/EBS1213/GOLD/DB/apps_st/data/a_txn_data01.dbf 1267.5 NO /tarmachin/EBS1213/GOLD/DB/apps_st/data/a_txn_data02.dbf 1657.625 NO /tarmachin/EBS1213/GOLD/DB/apps_st/data/a_txn_data03.dbf 1323 NO SQL> alter database datafile '/tarmachin/EBS1213/GOLD/DB/apps_st/data/a_txn_data01.dbf' autoextend on; Database altered. SQL> SQL> select file_name,bytes/1024/1024,autoextensible from dba_data_files where tablespace_name='APPS_TS_TX_DATA' 2 ; FILE_NAME BYTES/1024/1024 AUT ---------------------------------------------------------------------- --------------- --- /tarmachin/EBS1213/GOLD/DB/apps_st/data/a_txn_data04.dbf 1744 NO /tarmachin/EBS1213/GOLD/DB/apps_st/data/a_txn_data01.dbf 1267.5 YES /tarmachin/EBS1213/GOLD/DB/apps_st/data/a_txn_data02.dbf 1657.625 NO /tarmachin/EBS1213/GOLD/DB/apps_st/data/a_txn_data03.dbf 1323 NO
Re-run adpatch now.
-----------------------------------------------------------------------------------------------------------------------------
Verify patch 22742071 has been applied.
SQL> select bug_number from ad_bugs where bug_number='22742071'; BUG_NUMBER ------------------------------ 22742071
9) Disable Maintenance Mode
Run adadmin after sourcing fs1 environment file.
Change Maintenance Mode ---------------------------------------- Maintenance Mode is currently: [Enabled]. Maintenance mode should normally be enabled when patching Oracle E-Business Suite and disabled when users are logged on to the system. See the Oracle E-Business Suite Maintenance Utilities manual for more information about maintenance mode. Please select an option: 1. Enable Maintenance Mode 2. Disable Maintenance Mode 3. Return to Main Menu Enter your choice [3] : 2 sqlplus -s &un_apps/***** @/tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/ad/12.0.0/patch/115/sql/adsetmmd.sql DISABLE Successfully disabled Maintenance Mode.
10)Run AutoConfig on the Apps Tier
On Application node and Source the applications run file system environment file
Verify if below autoconfig table exists
[applmgr@ebsupgrade driver]$ sqlplus apps/apps SQL*Plus: Release 10.1.0.5.0 - Production on Sat Dec 12 08:01:25 2020 Copyright (c) 1982, 2005, 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> select object_name, object_type, owner, status from dba_objects where upper(object_name)='ADX_PRE_AUTOCONFIG' and object_type='TABLE' and upper(owner)='APPS'; 2 3 OBJECT_NAME -------------------------------------------------------------------------------- OBJECT_TYPE ----------------------- OWNER -------------------------------------------------------------------------------- STATUS ------- ADX_PRE_AUTOCONFIG TABLE APPS VALID
Execute the following commands to drop table ADX_PRE_AUTOCONFIG from APPS
schema:
sqlplus apps/apps
SQL> @$AD_TOP/patch/115/sql/txkDropAdxPreAutoConfig.sql Table ADX_PRE_AUTOCONFIG dropped Synonym ADX_PRE_AUTOCONFIG does not exist PL/SQL procedure successfully completed. Commit complete.
Execute auto-config now
Make sure it completes successfully.
[applmgr@ebsupgrade driver]$ $ADMIN_SCRIPTS_HOME/adautocfg.sh
11) Configuring the Oracle E-Business Suite Release 12.2 Application Tier by rapid install
Go to the stage area which was also used in step 4 earlier.
connect with root user and launch rapidwiz
[root@ebsupgrade rapidwiz]# pwd
/tarmachin/EBS12210/software/APPS12.2/startCD/Disk1/rapidwiz
./rapidwiz
Click next on the Welcome Screen
Select Upgrade Option
Don't provide any email address and continue.
On Select Upgarde Action screen, select Configure Upgarde Release 12.2.0 Instance
and Browse the path ($INST_TOP>/appl/admin/<CONTEXT_NAME>.xml) and click Next.
Enter the WebLogic password which was given earlier in Step 4. and click Next. It will do pre-checks.
Click next on the Validate system configuration screen. But before that ensure that all the checks should be passed
Verify the Database and Middle tier Information
Confirm rapidwiz to start configuring the EBS 12.2.0
It took 2 hrs for me to complete.
Click Next and Finish.
12) Enable the Online patching
Run the Online Patching Enablement - Readiness Reports
Source run file system and create below directory.
mkdir $LOG_HOME/appl/op
cd $LOG_HOME/appl/op
Run the following Readiness reports:
a) ADZDPSUM.sql - Provides a summary of the schemas that will be editioned and also schemas with objects that depend on E-Business Suite code that is recommended to be editioned. You can register these schemas with the application by running the commands that will be listed in the last section of this report. Oracle recommends that you run this report again after the custom schemas are registered with the application. You should run ADZDPSUM.sql repeatedly to handle dependent schemas until no further EBR violations are reported.
sqlplus system/manager
@$AD_TOP/sql/ADZDPSUM.sql
Once completed rename the outfile which is created.
mv adzdpsum.txt adzdpsum_pre_dbprep.txt
b) ADZDPMAN.sql - Lists objects with different categories of violations to EBR rules that must be fixed prior to running the enablement process to avoid errors during this process. Oracle recommends that you run this report after all custom schemas are registered with the application according to instructions in the above report ADZDPSUM.sql.
sqlplus system/manager
@$AD_TOP/sql/ADZDPMAN.sql
Once completed rename the outfile which is created.
mv adzdpman.txt adzdpman_pre_dbprep.txt
c) ADZDPAUT.sql - This report lists all the objects with violations of the EBR rules that will be fixed automatically from the enablement process. This report is provided for information purposes and no action should be taken from this report.
Note: Please make sure you have sufficient space in TEMP tablespace as it can fail with "unable to extend temp tablespace error".
sqlplus system/manager
SQL> @$AD_TOP/sql/ADZDPAUT.sql
Once completed rename the outfile which is created.
mv adzdpaut.txt adzdpaut_pre_dbprep.txt
----------------------------------------------------------------------------------------------------
Important
The Online Patching Readiness Report contains sections with different violation types.
Review all sections listed from the ADZDPMAN.sql report. Follow instructions in each section to fix violations.
Note: Many violations in the Readiness report can be automatically fixed by registering your custom schemas. Review the last section of the Summary Readiness Report (ADZDPSUM.sql) for sample commands on how to register your custom schemas as well as any schema installed as part of an Oracle technology such as APEX, XDB, and OWBSYS. You must register any custom or third-party schema that does not support Oracle E-Business Suite Online Patching.
The following schemas should NOT be registered:
SYS
SYSTEM
CTXSYS
Any dependency between these schemas and Editioned Objects is a coding standards violation and must be fixed manually.
Oracle recommends that you perform the chosen fix by customizing template file $AD_TOP/sql/ADZDPCUST.sql. The reports provide more details on this step.
Repeat the Run the Online Patching Enablement - Readiness Report step above until all violations have been addressed.
-------------------------------------------------------------------------------------------------------------------------
Verify database tablespace free space
On application node and Source the application run environment file.
perl $AD_TOP/bin/adzdreport.pl apps
a) Enter apps password (apps) when prompt to enter.
b) Select option 3 - 'Other Generic Reports'
Select the next option 3 - 'Free Space in Important Tablespaces
========================================================================= = Important Tablespace Status ========================================================================= TABLESPACE_NAME TOTAL_SPACE(GB) USED_SPACE(GB) FREE_SPACE(GB) PCT_USED ------------------------------ --------------- -------------- -------------- -------- APPS_TS_SEED 2.97 2.81 .16 94.74 APPS_TS_TX_DATA 6.16 5.86 .30 95.13 APPS_TS_TX_IDX 8.26 7.57 .69 91.63 SYSTEM 12.38 11.79 .60 95.18 Above report is captured in file : /tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/admin/GOLD121/out/adzdshowts.out. ===============================================================================
Ensure the following:
SYSTEM Tablespace: has a minimum of 25 GB of free space
APPS_TS_SEED Tablespace: has a minimum of 5 GB of free space
APPS_TS_SEED is used to host all tables that have been registered as seed tables and that require seed data storage infrastructure.
Add the required space in the tablespaces and rerun the report to validate.
========================================================================= = Important Tablespace Status ========================================================================= TABLESPACE_NAME TOTAL_SPACE(GB) USED_SPACE(GB) FREE_SPACE(GB) PCT_USED ------------------------------ --------------- -------------- -------------- -------- APPS_TS_SEED 8.82 2.81 6.01 31.86 APPS_TS_TX_DATA 10.46 5.86 4.60 56.06 APPS_TS_TX_IDX 13.18 7.57 5.60 57.47 SYSTEM 38.43 11.79 26.64 30.67 Above report is captured in file : /tarmachin/EBS12210/GOLD/APPS/fs1/EBSapps/appl/admin/GOLD121/out/adzdshowts.out. ===============================================================================
Note: Verify that all middle-tier E-Business Suite services are shut down prior to applying the Online Patching Enablement patch.
Check compatible is 12.1.0 for database
Your database should be set to compatible 12.1.0 and if is pointing to 11.1.0 then change else if database is pointing to 12.1.0 then skip this.
sqlplus “/as sysdba”
SQL> show parameter compatible
If value is 11.1.0 then change and restart database
SQL> alter system set compatible=’12.1.0’ scope=spfile;
SQL> shutdown immediate
SQL> startup
Run the Online Patching Enablement - Status Report
This report provides an overall status of the enabling online patching process. You can run it before, during, and after the enablement, the patch is applied. At this stage, you will receive report results before you enable online patching.
Set the current directory to $LOG_HOME/appl/op:
$ cd $LOG_HOME/appl/op
Run the report using the following command. Ensure that you verify any invalid objects at this stage. Take special note to ensure that all online patching objects (objects that match the pattern 'AD_ZD%') are valid:
$ sqlplus <apps username> @$AD_TOP/sql/ADZDEXRPT.sql
Note: Enter the apps password when prompted.
Save the output as pre_dbprep for future references, such as:
$ mv adzdexrpt.txt adzdexrpt_pre_dbprep.txt
Apply the Online Patching Enablement patch
Download patch 13543062
On the application node and source the environment file.
Copy the 13543062 patch to the default patch directory.
cd /tarmachin/EBS12210/GOLD/APPS/fs_ne/EBSapps/patch
cp /media/sf_Downloads/EBS1213_1220_upgrade_patches/p13543062_R12.AD.C_R12_GENERIC.zip .
.
unzip p13543062_R12.AD.C_R12_GENERIC.zip
Run Autopatch in hotpatch mode to apply the patch
Note: We are not placing in maintenance mode as we are applying it in hotpatch mode,after this patch is applied, maintenance mode will be removed from good, so should not enable maintenance mode.
This patch is reapplied here for online Patching enablement, that is why it is applied in forceapply mode.
cd /tarmachin/EBS12210/GOLD/APPS/fs_ne/EBSapps/patch/13543062
adpatch options=hotpatch,forceapply
Important: While applying the Online Enablement patch, you may receive the following error: 'Attention: Adpatch should no longer be used to apply patches. Please use ADOP tool for applying patches.' If you receive this error, then you must use adop in hotpatch mode to apply the enablement patch.
Known Error:
There are now 46 jobs remaining (current phase=A3):
0 running, 1 ready to run and 45 waiting.
Assigned: file ADZDPREP.sql on worker 1 for product ad username APPLSYS.
FAILED: file ADZDPREP.sql on worker 1 for product ad username APPLSYS.
Deferred: file ADZDPREP.sql on worker 1 for product ad username APPLSYS. (Deferment number 1 for this job)
Assigned: file ADZDPREP.sql on worker 1 for product ad username APPLSYS.
FAILED: file ADZDPREP.sql on worker 1 for product ad username APPLSYS.
Deferred: file ADZDPREP.sql on worker 1 for product ad username APPLSYS. (Deferment number 2 for this job)
Assigned: file ADZDPREP.sql on worker 1 for product ad username APPLSYS.
FAILED: file ADZDPREP.sql on worker 1 for product ad username APPLSYS.
ATTENTION: All workers either have failed or are waiting:
FAILED: file ADZDPREP.sql on worker 1.
Solution:
Check the status of all the AD_ZD objects:
SQL> col OWNER for a12;
col OBJECT_NAME for a25;
col STATUS for a15;
set pages 500;
select owner,object_name,status from dba_objects where object_name like 'AD_ZD%';Below object is seen as invalidAPPS AD_ZD_PREP INVALID
When trying to compile:
SQL> alter package apps.AD_ZD_PREP compile body;
Warning: Package Body altered with compilation errors.
SQL> show errors
Errors for PACKAGE BODY APPS.AD_ZD_PREP:
LINE/COL ERROR
-------- -----------------------------------------------------------------
424/3 PL/SQL: SQL Statement ignored
424/19 PL/SQL: ORA-00942: table or view does not exist
428/5 PL/SQL: SQL Statement ignored
428/21 PL/SQL: ORA-00942: table or view does not exist
448/5 PL/SQL: Statement ignored
448/5 PLS-00201: identifier 'SYS.XDB_MIGRATESCHEMA' must be declared
462/5 PL/SQL: SQL Statement ignored
462/21 PL/SQL: ORA-00942: table or view does not exist
1. Confirm if the package 'xdb_migrateschema' exists using the following select statement:
select owner, object_name from dba_objects where object_name like upper ('xdb_migrateschema');
If it does NOT exist, then use the following scripts to create it and confirm results again using the above query:
conn / as sysdba
@?/rdbms/admin/dbmsxdbschmig.sql
@?/rdbms/admin/prvtxdbschmig.plb
2. Run adgrants.sql.
3. Recompile the package AD_ZD_PREP and ensure it compiles successfully.
SQL> alter package apps.AD_ZD_PREP compile body;
Package body altered.
4. Continue with the upgrade and confirm online patching is successfully enabled.
Use adctrl to restart the failed worker.
Monitor the Online Patching Enablement patch application.
The enablement patch application may take several hours to finish. You can monitor its progress at any time by running the DDL Status Report (ADZDSHOWDDLS.sql) as follows:
$ sqlplus <apps Username> @$AD_TOP/sql/ADZDSHOWDDLS.sql
This report lists a count of the DDL statements that are required to EBR enable your environment. The report is organized by outcome of execution: 'Successfully Executed', 'Not Executed', and 'Failed Execution'. At the end of the patch application the report should have a zero count in the sections: 'Not Executed' and 'Failed Execution'. If the report contains 'Not Executed' and 'Failed Execution' items, then report these failures to Oracle Support. You will be asked to provide the output from the report, the patch log and all worker logs, and the online patching enablement status report output. If there is any worker failure during the Online Enablement patch, you should not ignore or skip the failed error. The issue should be addressed before restarting the worker. Ignoring or skipping the error can cause database corruption.
Example:
[applmgr@ebsupgrade ~]$ sqlplus apps @$AD_TOP/sql/ADZDSHOWDDLS.sql SQL*Plus: Release 10.1.0.5.0 - Production on Sat Dec 12 14:26:43 2020 Copyright (c) 1982, 2005, Oracle. All rights reserved. Enter password: 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 DOC> DOC> Count of Current DDL Jobs per Phase and Status DOC> DOC> Phases: DOC> 1. DROP_UNUSED_OBJECT : Remove obsolete objects from XLA schema. DOC> 2. COPY_TYPE : Create EBS Types in APPS_NE schema, stop Advanced Queues. DOC> 3. COMPILE_TYPE : Recompile APPS_NE schema. DOC> 4. COPY_EVOLVED_TYPE : Create evolved types in APPS_NE schema. DOC> 5. FIX_COLUMN : Fix TYPE reference to APPS_NE.<type> at table and AQ level. DOC> 6. FIX_TYPE : Additional check, Fix TYPE reference and then drop TYPE DOC> from source schema. DOC> 7. FIX_PUBLIC_SYNONYM : Fix public synonyms. DOC> 8. RECREATE_AQ_OBJECT : Re-create internal AQ objects after TYPE Ref fix. DOC> 9. DROP_OBJECT : Drop objects like CTXSYS.<package>, CTXSYS.<synonym> and others if any. DOC> 10. ENABLE_EDITIONING : Enable registered schemas for Online Patching. DOC> 11. UPGRADE_TABLE : Create Editioning View cover layer over EBS data model. DOC> 12. UPGRADE_SEED : Upgrade seed data tables to support edition based storage. DOC> 13. COLLECT_STATS : Gather Statistics on Seed Data Tables after upgrade. DOC> 14. UPGRADE_MVIEW : Convert Materialized Views with expand query. DOC> 15. CUTOVER : Perform maintenance operations on columns and indexes after adop APPLY phase DOC> and before actually changing Patch-Edition as Default-Edition. DOC> 16. ACTUALIZE_ALL : Actualize all editioned objects into the current edition. DOC> 17. CLEANUP : Cleanup task after adop CUTOVER. DOC> DOC> DOC> Results spooled to: ADZDSHOWDDLS.out DOC># Phase Count Status -------------------- ------- ------------------------------ COPY_TYPE 41 S - Successfully Executed COMPILE_TYPE 1 S - Successfully Executed COPY_EVOLVED_TYPE 1 S - Successfully Executed FIX_COLUMN 2 S - Successfully Executed FIX_TYPE 22 S - Successfully Executed FIX_PUBLIC_SYNONYM 4486 S - Successfully Executed RECREATE_AQ_OBJECT 11 S - Successfully Executed DROP_OBJECT 10 S - Successfully Executed ENABLE_EDITIONING 163 S - Successfully Executed UPGRADE_TABLE 11508 N - Not Executed 4 R - Running 6331 S - Successfully Executed UPGRADE_SEED 2605 N - Not Executed COLLECT_STATS 2605 N - Not Executed UPGRADE_MVIEW 120 N - Not Executed 15 rows selected. DOC> DOC> Currently running phase is: DOC> DOC># Running Phase -------------------- UPGRADE_TABLE 1 row selected.
Total time taken is 7 hrs .
13) Compile Invalid Objects (if any)
Connect to sqlplus as 'apps' and run the following:
$ exec sys.utl_recomp.recomp_parallel
14) Re-run the Online Patching Enablement Status Report after the Online Patching Enablement patch has been applied
Set the current directory to $LOG_HOME/appl/op:
$ cd $LOG_HOME/appl/op
Run the Status Report immediately after the enablement patch completes:
$ sqlplus <Apps Username> @$AD_TOP/sql/ADZDEXRPT.sql
Note: You must provide the APPS schema password when prompted.
The purpose of running this report at this stage is to identify and fix any errors that occurred during the enablement process.
Important: You must fix errors listed by this report. Failure to comply may result in unexpected failures during future patching cycles.
15) Re-run the Online Patching Enablement Readiness Report after the Online Patching Enablement patch has been applied
Set the current directory to $LOG_HOME/appl/op:
$ cd $LOG_HOME/appl/op
Run the Readiness Report after the enablement patch completes:
$ sqlplus system @$AD_TOP/sql/ADZDPSUM.sql
Note: You must provide the SYSTEM schema password when prompted.
$ mv adzdpsum.txt adzdpsum_post_dbprep.txt
$ sqlplus system @$AD_TOP/sql/ADZDPMAN.sql
$ mv adzdpman.txt adzdpman_post_dbprep.txt
$ sqlplus system @$AD_TOP/sql/ADZDPAUT.sql
$ mv adzdpaut.txt adzdpaut_post_dbprep.txt
The purpose of running this report at this stage is to ensure that all EBR violations that could have appeared before enabling the online patching feature are fixed.
16) Run the Online Patching Database Compliance Checker report to check for coding standards violations
There are two levels of compliance that can be targeted:
Minimal Compliance (Minimal) - These checks represent the minimum requirement for correct operation of Oracle E-Business Suite Release 12.2.
Warning: Do not attempt to operate the system if there are P1 minimal compliance violations. Custom code should pass the minimal compliance checks before being used in a Release 12.2 system.
Full Compliance (Full) - These checks indicate whether an object can be patched using Online Patching. Objects which do not meet full compliance may have limitations in how they can be patched, or may need to be patched using downtime patching. Full compliance also requires that all minimal compliance checks are passed. Custom code that will only be patched using downtime patching does not need to meet the full compliance level.
Set the current directory to $LOG_HOME/appl/op:
$ cd $LOG_HOME/appl/op
Run the Online Patching Database Compliance Checker report to check for online patching database objects standards violations:
sqlplus <Apps Username> @$AD_TOP/sql/ADZDDBCC.sql
This utility reports all violations to the Online Patching Development Standards. All Oracle E-Business Suite violations are fixed by the 12.2 upgrade. You must fix any object listed in this report that is part of your custom code. If you do not fix the violation, then you cannot leverage the online patching infrastructure to patch the objects listed in this report.
Note:
The 'recyclebin' parameter must be turned off to allow the cleanup phase of the online patching cycle to be performed without having to connect as SYS. This feature may still be used at other times.
For example:
$ recyclebin=off
If the _SYSTEM_TRIG_ENABLED parameter is set to false, then system triggers are not processed. The post Online Patching Enablement parameter must be set to true.
_SYSTEM_TRIG_ENABLED=true
$ _SYSTEM_TRIG_ENABLED=true
This completes our upgrade of EBS to R12.2.0. How to upgrade to the latest code level will be shared in another post.
Reference Note:
- R12.2: How To Create the Stage In Preparation For Installation (Doc ID 1596433.1)
- Oracle E-Business Suite Release Notes, Release 12.2 (Doc ID 1320300.1)
- Oracle E-Business Suite Release 12.2: Suite-Wide Rollup and AD/TXK Delta Information (Doc ID 1583092.1)
- Applying the Latest AD and TXK Release Update Packs to Oracle E-Business Suite Release 12.2 (Doc ID 1617461.1)
- Using the Online Patching Readiness Report in Oracle E-Business Suite Release 12.2 (Doc ID 1531121.1)
- https://docs.oracle.com/cd/E26401_01/doc.122/e73540/T660854T660862.htm#8360043
- 12.2 E-Business Suite DBA Upgrade Script ADZDEXRPT.sql Fails On Invalid Object 'AD_ZD_PREP' Or Patch 13543062 Fails With Error: ORA-06508: PL/SQL: could not find APPS.AD_ZD_PREPAD_ZD_PREP Due To Missing Package 'xdb_migrateschema' (Doc ID 2066607.1)
19 Comments
i am upgrading from 12.1.3 -------> 12.2.0 , DB=12.1.0.2 , OEL=6.4
ReplyDeletei did multiple try multiple times , even through try with startcd 51 patch as well , but my installation get stuck at 38 % with below error :
cannot install webtier utilities :
at oracle.apps.fnd.txk.config.PatchActionNode.processState(PatchActionNode.java:187)
at oracle.apps.fnd.txk.config.PatchNode.processState(PatchNode.java:338)
at oracle.apps.fnd.txk.config.PatchesNode.processState(PatchesNode.java:79)
at oracle.apps.fnd.txk.config.InstallNode.processState(InstallNode.java:68)
at oracle.apps.fnd.txk.config.TXKTopology.traverse(TXKTopology.java:594)
at oracle.apps.fnd.txk.config.InstallService.doInvoke(InstallService.java:224)
at oracle.apps.fnd.txk.config.InstallService.invoke(InstallService.java:237)
at oracle.apps.fnd.txk.config.InstallService.main(InstallService.java:291)
Cannot install Web Tier Utilities
RW-50010: Error: - script has returned an error: 1
RW-50004: Error code received when running external process. Check log file for details.
Running APPL_TOP Install Driver for PROD instance
NO solution for this error yet for me worked
Deletei was getting error bcz in oraInst.loc file
inventory_loc=/u01/app/oracle/oraInventory ( these was space at the end after oraInventory word)
so due to this in /u01/app/oracle two oraInventory folder created and rapidwiz was getting stuck at 38%.
so we removed this space at the end in oraInst.loc and removed oraInventory in /u01/app/oracle ( bcz it is ccreated again automatically when u run rapidwiz )
im greatful to sir himanshu he diagnosed and resolved this error.
thanks
only issue will be either files corrupted or something you have missed somewhere.
ReplyDeletesolution given in oracle (Doc ID 2083134.1)
Deletecp /u02/R12_upgrade/R12.2.0/startCD/Disk1/rapidwiz/etc/filegroup3.jar.modified
( location given in oracle doccument but could not find in my installation )
/TechInstallMedia/ohs11117/Disk3/stage/Components/oracle.calypso/11.1.1.7.0/1/DataFiles
-----------------------------------------------
( location i copied file )
/u02/R12_upgrade/R12.2.0/TechInstallMedia/ohs11119/Disk4/stage/Components/oracle.calypso/11.1.1.9.0/1/DataFiles
but getting error even after that
The note you are referring is for startCD 50, if you are using startCD 51 no issues should be there.
ReplyDeletebefore executing
ReplyDelete8) Apply Consolidated Upgrade Patch and Run the 12.2.0 Upgrade
enable auto extend on for all datafiles .
generate a script with below command and execute :
select
'alter database datafile '||
file_name||
' '||
' autoextend on maxsize unlimited;'
from
dba_data_files;
while applying patch patch 13543062
ReplyDeleteadgrants.sql -------- this i could not find how and where to run, so resolved it by below method :
grant select,update,delete,insert on sys.xdb$moveSchemaTab to apps;
alter package apps.AD_ZD_PREP compile body;
Hello Himanshu,
ReplyDeleteGreat work !!.
One doubt , why the Rapidwiz using the root user for installation application, instead of applmgr.
Pradeep.
Hi Pradeep.
DeleteThis is requirement for the EBS as lot of action are required to be done from root.
Hi
ReplyDeleteHi# tail -f /oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/logs/02071329.log
ReplyDeleteInstalling Web Tier Utilities.
Using /oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/temp/xmldocs/instWeb.xml
Executing command: /BACKUP/OH_HOME/StageR122/startCD/Disk1/rapidwiz/jre/IBM_AIX/1.6.0/bin/java -cp /oracle/ebiz/MVFNP1/EBS12PPS/fs1/inst/apps/MVFNP1_mvc01a/temp/ASInstallHome/fnd/../j11067592_fnd.zip:/oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/1_mvc01a/temp/ASInstallHome/fnd/java/3rdparty/stdalone/xmlparserv2.zip -Doracle.apps.fnd.txk.env_home=/oracle/ebiz/MVFNP1/EB0/APPS/fs1/EBSapps/appl/admin/MVFNP1_mvc01a/ -Doracle.apps.fnd.txk.runtime.config=/oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/MVFNP1_mvc01a/temp/xmldocs/instWeb.xml oracle.apps.fnd.txk.config.InstallService
Web Tier Utilities installed successfully
Registering EBSUsing /oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/temp/xmldocs/instEBS.xml
Executing command: /BACKUP/OH_HOME/StageR122/startCD/Disk1/rapidwiz/jre/IBM_AIX/1.6.0/bin/java -cp /oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/temp/ASInstallHome/fnd/../j11067592_fnd.zip:/oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/temp/ASInstallHome/fnd/java/3rdparty/stdalone/xmlparserv2.zip -Doracle.apps.fnd.txk.env_home=/oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/EBSapps/appl/admin/MVFNP1_mvc01a/ -Doracle.apps.fnd.txk.runtime.config=/oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/temp/xmldocs/instEBS.xml oracle.apps.fnd.txk.config.InstallService
EBS Registered successfully
Renaming /home/appprd1/bea/beahomelist to /home/appprd1/bea/beahomelist.50594862 to avoid issues during WLS
patching
/home/appprd1/bea/beahomelist renamed successfully.
Applying one-off patches
Using /oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/temp/xmldocs/instASpatches.xml
Executing command: /BACKUP/OH_HOME/StageR122/startCD/Disk1/rapidwiz/jre/IBM_AIX/1.6.0/bin/java -cp /oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/temp/ASInstallHome/fnd/../j11067592_fnd.zip:/oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/temp/ASInstallHome/fnd/java/3rdparty/stdalone/xmlparserv2.zip -Doracle.apps.fnd.txk.env_home=/oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/EBSapps/appl/admin/MVFNP1_mvc01a/ -Doracle.apps.fnd.txk.runtime.config=/oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/temp/xmldocs/instASpatches.xml oracle.apps.fnd.txk.config.InstallService
Fatal Error: TXK Install Service
oracle.apps.fnd.txk.config.ProcessStateException: Patch directory does not exist or not writable - /oracle/ebiz/MVFNP1/EBS12210/APPS/fs1/inst/apps/MVFNP1_mvc01a/temp/patches/31136426 ## Node=NodeId=1553 Type=18 TypeName=patch Name=31136426 RefId=845 State=init ConfigDoc=APPS_JAVA_HOME ParentDoc=null Topology=R12 Id= Unzip=true Validate=true Version=1036 PatchFileName=null
at oracle.apps.fnd.txk.config.PatchNode.validatePatch(PatchNode.java:376)
at oracle.apps.fnd.txk.config.PatchNode.processState(PatchNode.java:284)
at oracle.apps.fnd.txk.config.PatchesNode.processState(PatchesNode.java:79)
at oracle.apps.fnd.txk.config.InstallNode.processState(InstallNode.java:68)
at oracle.apps.fnd.txk.config.TXKTopology.traverse(TXKTopology.java:594)
at oracle.apps.fnd.txk.config.InstallService.doInvoke(InstallService.java:224)
at oracle.apps.fnd.txk.config.InstallService.invoke(InstallService.java:237)
at oracle.apps.fnd.txk.config.InstallService.main(InstallService.java:291)
Cannot install one-off patches
RW-50010: Error: - script has returned an error: 1
Cell: 718-517-0996
Any ideas?
I got same problem i need solution for fix this error too.
DeleteCheck log, it will tell you the symtoms.
DeleteI found solution for fix this problem last night I follow check from Doc ID 2442369.1 this error about oraInst.loc check this file and move location orainventory Thx for reply
DeleteThis is because you missed to follow all steps after applying patch 32947483. Go to startCD/Disk1/rapidwiz/bin and execute: ./buildStage.sh, choose option "2. Copy patches to existing stage area".
DeleteI hope this help, it worked for me
Thanks. Can you please advise regarding:
ReplyDelete1.Customized Reports (There is no customized schema) after upgrading to 12.2
2.Forms personalization.
Thanks and regards,
Shareef
Thanks. Can you pleas advise regarding:
ReplyDelete1. How to use customized reports in 12.1.3 with 12.2. There is no customized schema. Only reports.
2. What about forms personalizations.
Thanks and regards,
Shareef
Hello, do you have an instructions for the EBS upgrade to 12.2.13 from 12.2.10? Please share if you have already performed the upgrade.
ReplyDeleteThanks in advance!
Syed
Please check the which version you are asking. may be you want from 12.1.3 to 12.2.10. For that also we need to first do till 12.2.0 then 12.2.0 to 12.2.10(Steps: https://www.funoracleapps.com/2020/11/ebs-upgrade1220to12210.html)
DeletePost a Comment