DBA Arena

The latest RUPs while writing this post are R12.AD.C.Delta.10 (Patch 25820806) and R12.TXK.C.Delta.10 (Patch 25828573).

Apply Required Database Patches

 
AD-TXK Delta 10 requires a number of database bug fixes to install and operate correctly.
 
NOTE: Take Central Inventory backups on the database and application tiers.
 
Before you apply the AD and TXK Delta 10 release update packs (RUPs), you must run the latest version (available via Patch 17537119) of the EBS Technology Codelevel Checker (ETCC). Use the command checkDBpatch.sh (on UNIX) or checkDBpatch.cmd (on Windows).

Check the OPatch utility version.

/u01/oracle/product/dbhome1/OPatch/opatch version
OPatch Version: 11.2.0.3.16

OPatch succeeded.

Upgrade to the latest OPatch Utility.

[oracle@ebsdb01 OPatch]$ ./opatch version
OPatch Version: 11.2.0.3.18

OPatch succeeded.


Running the latest version of ETCC is required in order to:
1. Check that all the required database patches have been applied.
2. Ensure all the required ETCC database objects will be found by the Delta 10 RUP installation process. This means that you must still run the latest version of ETCC on your database, even if you already have all the required database patches installed.
 
In my environment, the following patches were missing on the Database Tier,

 
After applying the ETCC patches, follow Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes (Doc ID 1594274.1)
Section 3.1: Database 11.2.0.4 Patches and Bug Numbers
Make sure all the patches mentioned in the document for the appropriate database version has been applied.
 
You can apply the latest AD-TXK delta RUPs directly on top of any earlier Release 12.2 AD-TXK delta codelevel.
 

Source the run edition environment file.
$ . /EBSapps.env run
 
Start a new online patching cycle.
$ adop phase=prepare
 
Apply the latest embedded application tier technology patches on the patch file system.
From a separate session, source the patch edition environment file.
$ . /EBSapps/appl/APPS.env
 
Run ETCC MT checker.
You must execute the latest version of ETCC on your application tier or the patch application procedure will fail.
• Run the ETCC MT checker utility checkMTpatch.sh (checkMTpatch.cmd on Microsoft Windows) on the E-Business Suite application tier nodes, to identify and apply any missing patches. Make a note of any missing application tier technology patches. Missing application tier technology patches will be applied on the patch file system.
Application Tier:
 
After all application tier technology patches are applied to the patch file system, re-run the ETCC MT checker utility checkMTpatch.sh to check for any missing patches.
 

Below are the list of DELTA 10 patches along with the Critical patches for AD and TXK.
 
Download and unzip the following patches:

Critical AD Patches

Critical TXK Patches

Execute adgrants by following the instructions in the readme of Patch 25820806 (R12.AD.C.Delta.10).
 

Compare the version of adgrants.sql(UNIX) in $APPL_TOP/admin to that in patch directory.
 
Check the version of adgrants.sql from $APPL_TOP/admin directory.

[applmgr@ebsapp01 admin]$ adident Header /oradata/oracle/fs2/EBSapps/appl/admin/adgrants.sql
/oradata/oracle/fs2/EBSapps/appl/admin/adgrants.sql:
$Header adgrants.sql 120.67.12020000.46 2016/10/26 05:48:58 rputchak ship $


Check the version of adgrants.sql from Patch/admin directory.

[applmgr@ebsapp01 admin]$ adident Header adgrants.sql
adgrants.sql:
$Header adgrants.sql 120.67.12020000.51 2017/02/22 21:26:05 jwsmith ship $

 
Copy the higher version of adgrants.sql (UNIX) to the database tier.

[oracle@ebsdb01 AD_TXK_10]$ sqlplus / as sysdba @adgrants.sql APPS
SQL> @adgrants.sql APPS

Copy and unzip the patches to the $PATCH_TOP directory.
 
Apply Patch 25820806 (R12.AD.C.Delta.10) and Patch 26720905:R12.AD.C (plus any additional critical patches).

$ adop phase=apply patches=25820806,26720905 merge=yes

Note: You should also add any applicable AD patches as a comma-separated list of patches to this command. Ensure you add "merge=yes" to the end of your command, as shown here:

$ adop phase=apply patches=25820806,26720905,Your first critical AD patch,Your second critical AD patch merge=yes
 
adop phase=apply patches=25820806,26720905,24591000,26482811 merge=yes


Apply Patch 25828573 (R12.TXK.C.Delta.10) (plus any additional critical patches).

adop phase=apply patches=25828573
 
$ adop phase=apply patches=25828573,Your first critical TXK patch,Your second critical TXK patch merge=yes
 
adop phase=apply patches=25828573,26400116,26720231 merge=yes


Apply Patch 19259764:R12.FND.C.
Note: Do not apply this patch if you are on either of:
i. Oracle E-Business Suite Release 12.2.4 or above
ii. R12.ATG_PF.C.Delta.4 Release Update Pack (Patch 17909318) or above

 
Login to sqlplus as apps user from the PATCH FS and check the applied patches.

SQL> select bug_number from ad_bugs where bug_number in ('25820806','24591000','26482811','25828573','26400116','26720231','26720905');

9 rows selected.

 
Run Middle Tier EBS Technology Codelevel Checker (MT-ETCC)
 
Execute the Middle Tier EBS Technology Codelevel Checker (MT-ETCC) utility checkMTpatch.sh (checkMTpatch.cmd on Microsoft Windows) on the Oracle E-Business Suite application tier node's patch file system.
 
Complete the online patching cycle by running the following commands in the order shown.
$ . /EBSapps.env run
$ adop phase=finalize
$ adop phase=cutover
$ . /EBSapps.env run
$ adop phase=cleanup


[applmgr@ebsapp01 ~]$ adop -status

adop exiting with status = 0 (Success)


Source the RUN FILE SYSTEM
 
[applmgr@ebsapp01 ~]$ adop phase=finalize
 
[applmgr@ebsapp01 ~]$ adop phase=cutover
 
Source the RUN FILE SYSTEM
 
[applmgr@ebsapp01 ~]$ adop phase=cleanup
 

[applmgr@ebsapp01 ~]$ adop -status
Enter the APPS password:
Connected.
==============================================================
ADOP (C.Delta.10)
Session Id: 23
Command: status
Output: /oradata/oracle/fs_ne/EBSapps/log/adop/23/20180204_122700/adzdshowstatus.out
===============================================================
Node Name Node Type Phase Status Started Finished Elapsed
--------------- ---------- --------------- --------------- -------------------- -------------------- ------------
ebsapp01 master PREPARE COMPLETED 2018/02/01 12:06:45 2018/02/01 13:00:38 0:53:53
APPLY COMPLETED 2018/02/01 17:47:26 2018/02/01 19:22:07 1:34:41
FINALIZE COMPLETED 2018/02/04 11:28:46 2018/02/04 11:48:40 0:19:54
CUTOVER COMPLETED 2018/02/04 11:51:15 2018/02/04 12:06:07 0:14:52
CLEANUP COMPLETED 2018/02/04 12:07:09 2018/02/04 12:24:32 0:17:23

adop exiting with status = 0 (Success)

 
Update database tier with the latest patches
 
On the application tier (as the APPLMGR user):
a. Source the run edition environment file.
b. Execute the admkappsutil.pl utility to create the appsutil.zip file in /admin/out.


[applmgr@ebsapp01 ~]$ cd $AD_TOP/bin
[applmgr@ebsapp01 bin]$ perl admkappsutil.pl
Starting the generation of appsutil.zip
Log file located at /oradata/oracle/fs2/inst/apps/ERPPROD_ebsapp01/admin/log/MakeAppsUtil_02041237.log
output located at /oradata/oracle/fs2/inst/apps/ERPPROD_ebsapp01/admin/out/appsutil.zip
MakeAppsUtil completed successfully.

On the database tier (as the ORACLE user):
 
a. Source the environment for RDBMS ORACLE_HOME.
 
b. Copy or FTP the appsutil.zip file to .
 
c. Take backup of the current appsutil folder.

[oracle@ebsdb01 dbhome1]$ mv appsutil appsutil_BKP
 
Copy jre folder from old appsutil to current appsutil folder.

[oracle@ebsdb01 dbhome1]$ cp -rp appsutil_DELTA10_BKP/jre appsutil
 
d. Uncompress appsutil.zip, under RDBMS ORACLE_HOME.
$ cd $ORACLE_HOME
$ unzip -o appsutil.zip


e. Build the $CONTEXT_FILE.

[oracle@ebsdb01 bin]$ perl adbldxml.pl

The context file has been created at:
/u01/oracle/product/dbhome1/appsutil/ERPPROD_ebsdb01.xml

f. Run AutoConfig on the Database Tier.


[oracle@ebsdb01 bin]$ ./adconfig.sh contextfile=/u01/oracle/product/dbhome1/appsutil/ERPPROD_ebsdb01.xml
Enter the APPS user password:
The log file for this session is located at: /u01/oracle/product/dbhome1/appsutil/log/ERPPROD_ebsdb01/02041253/adconfig.log

AutoConfig completed successfully.

Note: For RAC systems, the above steps need to be executed on each RAC node.

 
Run AutoConfig on the RUN FS of all application tier nodes (as the APPLMGR user).
 
$ sh $ADMIN_SCRIPTS_HOME/adautocfg.sh

 
Synchronize file systems
 
adop phase=fs_clone