Scenario
You
have been asked to apply two patches and you completed the prepare phase and
now you start with the phase “APPLY”.
Background
The
two patches are from different module so they are not candidate for merge
option.
Before you
start patching you will always have to do pre check with the ADOP STATUS
option.
$ adop -status
Enter
the APPS username: apps
Enter
the APPS password:
Current Patching
Session ID: 9
Node
Name Node Type Phase Status Started Finished Elapsed
---------------
--------------- ----------- --------------- ------------------------------
------------------------------ ------------
testserver01 master APPLY
ACTIVE 17-NOV-13 01:35:15 -06:00
17-NOV-13 01:40:59 -06:00 0:05:44
PREPARE COMPLETED 17-NOV-13 12:46:19 -06:00 17-NOV-13
01:00:28 -06:00 0:14:09
CUTOVER NOT STARTED
CLEANUP NOT STARTED
$
So this
instance is already in the APPLY phase and it is ACTIVE. To see what are those
patches you can run the below query on the ad_adop_session_patches table.
Always pass the current session ID which you can get from the adop –status
output and the PATCH file system.
SQL>
select ADOP_SESSION_ID,NODE_NAME, APPLTOP_ID,
BUG_NUMBER,PATCH_TOP,DRIVER_FILE_NAME from ad_adop_session_patches where
ADOP_SESSION_ID=9 and APPLIED_FILE_SYSTEM_BASE like '%fs1%';
ADOP_SESSION_ID
NODE_NAME APPLTOP_ID BUG_NUMBER PATCH_TOP DRIVER_FILE_NAME
---------------
------------ ---------- ---------------
------------------------------------------------------- ------------------
9 testserver01 195 17539845 /inst122i/applmgr/fs_ne/EBSapps/patch u_3312281727.drv
9 testserver01 195 17637775 /inst122i/applmgr/fs_ne/EBSapps/patch u_3312281727.drv
SQL>
Staging
the patches to the PATCH_TOP
$
pwd
/inst122i/product/patchtop
$
$
unzip p17337532_R12.PO.D_R12_GENERIC.zip
Archive: p17337532_R12.PO.D_R12_GENERIC.zip
inflating: 17337532/README.html
inflating: 17337532/u17337532.drv
inflating: 17337532/f17337532.ldt
inflating: 17337532/po/patch/115/import/US/poclmreg.ldt
inflating: 17337532/marker1.txt
inflating: 17337532/b17337532.ldt
inflating: 17337532/README.txt
inflating: 17337532/patch_metadata.xml
inflating:
17337532/ad/patch/115/manualsteps/ad_apply_patch.xml
$
$
unzip p14769523_R12.INV.C_R12_GENERIC.zip
Archive: p14769523_R12.INV.C_R12_GENERIC.zip
inflating: 14769523/README.html
inflating: 14769523/u14769523.drv
inflating: 14769523/f14769523.ldt
extracting: 14769523/j14769523_inv.zip
inflating: 14769523/marker1.txt
inflating: 14769523/b14769523.ldt
inflating: 14769523/README.txt
inflating: 14769523/patch_metadata.xml
inflating:
14769523/ad/patch/115/manualsteps/ad_apply_patch.xml
$
$
mv 17337532 /inst122i/applmgr/fs_ne/EBSapps/patch
$
mv 14769523 /inst122i/applmgr/fs_ne/EBSapps/patch
$
Here
the patches are for PO and INV module
$ adop phase=apply
patches=17337532,14769523 merge=no
merge=no is the
default option
RUN file system context file: /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
PATCH file system context file: /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
************* Start of session *************
version: 12.2.0
started at: Sun Nov 17 2013 01:55:47
APPL_TOP is set to /inst122i/applmgr/fs2/EBSapps/appl
Using ADOP Session ID from currently incomplete patching cycle
[START 2013/11/17 01:56:21] adzdoptl.pl
run
ADOP Session ID: 9
Phase: apply
Log file: /inst122i/applmgr/fs_ne/EBSapps/log/adop/9/adop_20131117_015521.log
[START 2013/11/17 01:56:38] apply phase
Calling: adpatch workers=4 flags=autoskip console=no interactive=no defaultsfile=/inst122i/applmgr/fs1/EBSapps/appl/admin/INST122I_patch/adalldefaults.txt
patchtop=/inst122i/applmgr/fs_ne/EBSapps/patch/17337532 driver=u17337532.drv
logfile=u17337532.log
ADPATCH Log directory: /inst122i/applmgr/fs_ne/EBSapps/log/adop/9/apply_20131117_015521/INST122I_testserver01/17337532/log
Calling: adpatch workers=4 flags=autoskip console=no interactive=no defaultsfile=/inst122i/applmgr/fs1/EBSapps/appl/admin/INST122I_patch/adalldefaults.txt
patchtop=/inst122i/applmgr/fs_ne/EBSapps/patch/14769523 driver=u14769523.drv
logfile=u14769523.log
ADPATCH Log directory: /inst122i/applmgr/fs_ne/EBSapps/log/adop/9/apply_20131117_015521/INST122I_testserver01/14769523/log
[END 2013/11/17 02:23:11] apply
phase
[END 2013/11/17 02:23:29] adzdoptl.pl run
adop phase=apply -
Completed Successfully
Log file: /inst122i/applmgr/fs_ne/EBSapps/log/adop/9/adop_20131117_015521.log
adop exiting with status = 0 (Success)
$
$ adop -status
Enter
the APPS username: apps
Enter
the APPS password:
Current
Patching Session ID: 9
Node
Name Node Type Phase Status Started Finished Elapsed
---------------
--------------- ----------- --------------- ------------------------------
------------------------------ ------------
testserver01 master APPLY
ACTIVE 17-NOV-13 01:56:43 -06:00
17-NOV-13 02:23:13 -06:00 0:26:30
PREPARE COMPLETED 17-NOV-13 12:46:19 -06:00
17-NOV-13 01:00:28 -06:00 0:14:09
CUTOVER NOT STARTED
CLEANUP NOT
STARTED
$
SQL>
select ADOP_SESSION_ID,NODE_NAME, APPLTOP_ID,
BUG_NUMBER,PATCH_TOP,DRIVER_FILE_NAME from ad_adop_session_patches where
ADOP_SESSION_ID=9 and APPLIED_FILE_SYSTEM_BASE like '%fs1%';
ADOP_SESSION_ID
NODE_NAME APPLTOP_ID BUG_NUMBER PATCH_TOP DRIVER_FILE_NAME
---------------
------------ ---------- ---------------
------------------------------------------------------- ------------------
9 testserver01 195 17539845 /inst122i/applmgr/fs_ne/EBSapps/patch u_3312281727.drv
9 testserver01 195 17637775 /inst122i/applmgr/fs_ne/EBSapps/patch u_3312281727.drv
9 testserver01 195 17337532 /inst122i/applmgr/fs_ne/EBSapps/patch/17337532 u17337532.drv
9 testserver01 195 14769523 /inst122i/applmgr/fs_ne/EBSapps/patch/14769523 u14769523.drv
SQL>
The above SQL gives the confirmation
that two patches are applied on the PATCH edition.
Apply Phase - Scenario
