An experience with Oracle EBS Patching :Upgrade from 12.0.2 -> 12.0.4

Hierarchy : One off Patch -> Mini pack -> Family pack & Finally Maintenance Pack

Maintenance pack : Upgrade from one version to another . 12.0.2 -> 12.0.4

Family pack – Fixing the functional modules.FIN.B – Latest family pack for release 12 . FIN is financial B where B denotes the version -. For 11i HRPF.K – K is level of Module.

One off – One off issue

Mini Pack : Small functionality

Enhance functionality like VAT change. – One off else MINI pack. Apps patch is done by adpatch utility. Also look into readme file. “adpatch” is like opatch so can be copied from CD.

select RELEASE_NAME from FND_PRODUCT_GROUPS

[applmgr@ebs admin]$ pwd
/oracle/u01/VIS/inst/apps/VIS_ebs/appl/admin
[applmgr@ebs admin]$ whoami
applmgr

[applmgr@ebs admin]$ vi VIS_ebs.xml

You will see the version <config_option type=”adx” oa_var=”s_apps_version”>12.0.4</config_option>

Download and move patch on server . Look if patch is not in hot patch config, default is HOT so check readme.txt files. All HR global Patches should be applied after system is down. Rolling patch updates are not possible.

All HRMS patches contain unified driver file to be applied here u7202897.drv (is the unified driver)

Under 11i there were C (Copy), D ( Database), G( Forms/Reports Generate) drivers but now they were merged into one U driver – Universal driver

[applmgr@ebs ~]$ pwd
/home/applmgr
[applmgr@ebs ~]$ . APPSORA.env
[applmgr@ebs ~]$ pwd
/home/applmgr
[applmgr@ebs ~]$ cd /oracle/u01/VIS/inst/apps/VIS_ebs/admin/scripts/
[applmgr@ebs scripts]$ ls -l | grpe stop
-bash: grpe: command not found
[applmgr@ebs scripts]$ cd $INST_TOP
[applmgr@ebs VIS_ebs]$ pwd
/oracle/u01/VIS/inst/apps/VIS_ebs
[applmgr@ebs VIS_ebs]$ ls
admin appltmp conf_VIS.txt ora pids rgf
appl certs logs out portal temp
[applmgr@ebs VIS_ebs]$ cd ora
[applmgr@ebs ora]$ ls -l
total 8
drwxr-xr-x 6 applmgr applmgr 4096 Mar 3 22:05 10.1.2
drwxr-xr-x 10 applmgr applmgr 4096 Mar 3 22:04 10.1.3
[applmgr@ebs ora]$ pwd
/oracle/u01/VIS/inst/apps/VIS_ebs/ora

The patch suggets need for 6267502 & 7374316. Chekc if these pataches are already on system

the system does have 6267502 in place but not the other one. For any login issue smake sure you check the TWO_TASK variable.

[applmgr@ebs log]$ echo $TWO_TASK
VIS

$INST_TOP holds all configuration files

[applmgr@ebs admin]$ pwd
/oracle/u01/VIS/inst/apps/VIS_ebs/ora/10.1.2/network/admin
[applmgr@ebs admin]$ cd /oracle/u01/VIS/inst/apps/VIS_ebs/admin//scripts/
[applmgr@ebs scripts]$ pwd
/oracle/u01/VIS/inst/apps/VIS_ebs/admin/scripts
[applmgr@ebs scripts]$ adalnctl.sh status

adalnctl.sh version 120.3

Checking status for listener process APPS_VIS.

LSNRCTL for Linux: Version 10.1.0.5.0 – Production on 27-JUN-2009 15:14:47

Copyright (c) 1991, 2004, Oracle. All rights reserved.

Connecting to (ADDRESS=(PROTOCOL=TCP)(Host=ebs)(Port=1626))
STATUS of the LISTENER
————————
Alias APPS_VIS
Version TNSLSNR for Linux: Version 10.1.0.5.0 – Production
Start Date 27-JUN-2009 10:19:14
Uptime 0 days 4 hr. 55 min. 32 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File /oracle/u01/VIS/inst/apps/VIS_ebs/ora/10.1.2/network/admin/listener.ora
Listener Log File /oracle/u01/VIS/inst/apps/VIS_ebs/logs/ora/10.1.2/network/apps_vis.log
Listening Endpoints Summary…
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ebs.oracledbasupport.co.uk)(PORT=1626)))
Services Summary…
Service “FNDFS” has 1 instance(s).
Instance “FNDFS”, status UNKNOWN, has 1 handler(s) for this service…
Service “FNDSM” has 1 instance(s).
Instance “FNDSM”, status UNKNOWN, has 1 handler(s) for this service…
The command completed successfully

adalnctl.sh: exiting with status 0
adalnctl.sh: check the logfile /oracle/u01/VIS/inst/apps/VIS_ebs/logs/appl/admin/log/adalnctl.txt for more information …

FNDFS ( Forms Listener) & FNDSM ( Std Manager) is needed for log viewer output viewer FNDWRR(Utility communicates with log files)

To locate the staus for all Apps components pls navigate to [applmgr@ebs scripts]$ pwd
/oracle/u01/VIS/inst/apps/VIS_ebs/admin/scripts
You can select any script and add status for example “adapcctl.sh status”

Let’s get the apps environment into Maintenance mode using adadmin

[applmgr@ebs log]$ adadmin

Copyright (c) 2002 Oracle Corporation
Redwood Shores, California, USA

Oracle Applications AD Administration

Version 12.0.0

NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.

Your default directory is ‘/oracle/u01/VIS/apps/apps_st/appl’.
Is this the correct APPL_TOP [Yes] ?

Is this the correct database [Yes] ?

AD Administration needs the password for your ‘SYSTEM’ ORACLE schema
in order to determine your installation configuration.

Enter the password for your ‘SYSTEM’ ORACLE schema:

The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS

Enter the ORACLE password of Application Object Library [APPS] :

AD Administration is verifying your username/password.
The status of various features in this run of AD Administration is:

<-Feature version in->
Feature Active? APPLTOP Data model Flags
—————————— ——- ——– ———– ———–
CHECKFILE Yes 1 1 Y N N Y N Y
PREREQ Yes 6 6 Y N N Y N Y
CONCURRENT_SESSIONS No 2 2 Y Y N Y Y N
PATCH_TIMING Yes 2 2 Y N N Y N Y
PATCH_HIST_IN_DB Yes 6 6 Y N N Y N Y
SCHEMA_SWAP Yes 1 1 Y N N Y Y Y
JAVA_WORKER Yes 1 1 Y N N Y N Y
CODELEVEL Yes 1 1 Y N N Y N Y

Identifier for the current session is 407896

Reading product information from file…

Reading language and territory information from file…

Reading language information from applUS.txt …

AD Administration warning:
Product Data File
/oracle/u01/VIS/apps/apps_st/appl/admin/zfaprod.txt
does not exist for product “zfa”.
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.

AD Administration warning:
Product Data File
/oracle/u01/VIS/apps/apps_st/appl/admin/zsaprod.txt
does not exist for product “zsa”.
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.

AD Administration warning:
Product Data File
/oracle/u01/VIS/apps/apps_st/appl/admin/jtsprod.txt
does not exist for product “jts”.
This product is registered in the database but the
above file does not exist in APPL_TOP. The product
will be ignored without error.

Reading database to see what industry is currently installed.

Reading FND_LANGUAGES to see what is currently installed.
Currently, the following language is installed:

Code Language Status
—- ————————————— ———
US American English Base

Your base language will be AMERICAN.

Setting up module information.
Reading database for information about the modules.
Saving module information.
Reading database for information about the products.

Puts entire system into maintenanace mode.

We are in a Maintenanace mode now

See if the patch is already applied on the system

[applmgr@ebs scripts]$ sqlplus /nolog

SQL*Plus: Release 10.1.0.5.0 – Production on Sat Jun 27 15:48:29 2009

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

SQL> conn apps/apps
Connected.
SQL> desc ad_bugs
Name Null? Type
—————————————– ——– —————————-
BUG_ID NOT NULL NUMBER
APPLICATION_SHORT_NAME VARCHAR2(50)
BUG_NUMBER NOT NULL VARCHAR2(30)
CREATION_DATE NOT NULL DATE
ARU_RELEASE_NAME NOT NULL VARCHAR2(30)
BUG_STATUS VARCHAR2(30)
SUCCESS_FLAG VARCHAR2(1)
CREATED_BY NOT NULL NUMBER
LAST_UPDATE_DATE NOT NULL DATE
LAST_UPDATED_BY NOT NULL NUMBER
TRACKABLE_ENTITY_ABBR VARCHAR2(8)
BASELINE_NAME VARCHAR2(150)
GENERIC_PATCH VARCHAR2(1)

SQL> select count(*) from ad_bugs where BUG_NUMBER=7202897;

COUNT(*)
———-
0

If any records returned means the patch is already on the system.

Workers= 2 X No of CPUS. It’s possible to track the worker process adcontroller.

FND_INSTALL_PROCESSES & AD_DEFERRED _JOBS – Will be created by installer while running adpacth. The status of the adworkers is maintained at these tables. Let’s start worker processes else the patch application process would fail.

Please check the success at Database level

SQL> conn apps/apps
Connected.
SQL> select count(*) from ad_bugs where BUG_NUMBER=7202897;

COUNT(*)
———-
1