Senthil Rajendran's Blog

Saturday, December 7, 2013

FS_CLONE Phase - R12.2 Online Patching Cycle

FS_CLONE Phase

It is a stand-alone command used for file system cloning.
Standard cloning (using adcfgclone.pl) cannot be used to synchronize the run and patch file systems.
This special phase must be run from the run file system, and cannot be specified with any other phase.
It should be before the next prepare phase is run.
It is an alternate to PREPARE phase

FS_CLONE Phase - alternate to PREPARE phase ?

Create a new patch file system by cloning the run file system.
This method is useful if the APPL_TOPs have become very unsynchronized (meaning that there would be a large number of delta patches to apply).
It is a heavyweight process, taking a backup of the entire current patch APPL_TOP and then cloning the run APPL_TOP to create a new patch APPL_TOP.
A total of least 75 GB of free disk space is required. Also, you will need at least 25 GB of free space in your temporary directory (typically /tmp).
As well as being resource-intensive, this method is very time-consuming and requires several manual actions by the user.
It should therefore be used only when necessary.

FS_CLONE Phase – Possible Scenarios

Instance is 12.2.1 and want to upgrade to 12.2.2
adop phase=prepare
adop phase=apply patches=16207672
Start time : Nov 14 2013 08:41:29 End time : Nov 14 2013 16:47:08
Total Time : approximately 8 hours
adop phase=finalize
Got downtime approval from customer
adop phase=cutover ( 1 hour downtime )
Released the instance to customer
adop phase=cleanup

How do you sync now ?

Method 1 : adop phase=prepare

This step will apply 12.2.2 16207672 patch to the PATCH file system
It takes 8 hours to apply this patch when the instance is online

Method 2 : adop phase=fs_clone + adop phase=prepare

fs_clone phase will take 2 hours 36 Minutes

Start Time : Nov 16 2013 22:06:44 End Time : Nov 17 2013 00:43:29 Total Time : 2 hours 36 Minutes

prepare phase will take 16 Minutes

Start Time : Nov 17 2013 00:44:31 End Time : Nov 17 2013 01:01:01 Total Time : 16 Minutes

It takes approximately 3 hours

Conclusion :
Method 1 takes 8 hours but consumes less resource and less complexity.
Method 2 takes 3 hours and consumes more resource and more complexity.

FS_CLONE Scenario

Abort Phase - R12.2 Online Patching Cycle

Abort Phase

If for some reason either the prepare or apply phase failed or gave problems, you can abort the patching cycle.
After running abort, you must always run a full cleanup
adop phase=cleanup cleanup_mode=full
This will remove any columns that were added by the patch but are no longer needed because of the abort. If they are not removed, they may cause problems in a later patching cycle.

Scenario

You have encountered an error while preparing instance in the prepare phase or an error occurred while applying a patch during the patching cycle or customer has asked to exclude a patch and reapply the rest of the patches.

$ adop phase=abort

Enter the APPS password:

Enter the SYSTEM password:

Enter the WLSADMIN password:

Please wait. Validating credentials...

RUN file system context file: /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml

PATCH file system context file: /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml

************* Start of session *************

version: 12.2.0

started at: Sun Nov 17 2013 03:38:58

APPL_TOP is set to /inst122i/applmgr/fs1/EBSapps/appl

Cleanup is not done in earlier session

[START 2013/11/17 03:39:45] adzdoptl.pl run

ADOP Session ID: 9

Phase: cleanup

Log file: /inst122i/applmgr/fs_ne/EBSapps/log/adop/9/adop_20131117_033835.log

[START 2013/11/17 03:40:11] abort phase

[EVENT] [START 2013/11/15 22:25:34] Performing abort phase steps

[PROCEDURE] [START 2013/11/15 22:25:40] Calling AD_ZD_ADOP.ABORT

[PROCEDURE] [END 2013/11/15 22:28:58] AD_ZD_ADOP.ABORT

[EVENT] [START 2013/11/15 22:28:59] Running ABORT ddls in ddl handler table

Calling: adpatch options=hotpatch,nocompiledb interactive=no console=no workers=4 restart=no abandon=yes defaultsfile=/inst122i/applmgr/fs2/EBSapps/appl/admin/INST122I/adalldefaults.txt patchtop=/inst122i/applmgr/fs2/EBSapps/appl/ad/12.0.0/patch/115/driver logfile=abort.log driver=uabort.drv

ADPATCH Log directory: /inst122i/applmgr/fs_ne/EBSapps/log/adop/7/abort_20131115_221940/INST122I_testserver01/log

[PROCEDURE] Running: adpatch options=hotpatch,nocompiledb interactive=no console=no workers=4 restart=no abandon=yes defaultsfile=/inst122i/applmgr/fs2/EBSapps/appl/admin/INST122I/adalldefaults.txt patchtop=/inst122i/applmgr/fs2/EBSapps/appl/ad/12.0.0/patch/115/driver logfile=abort.log driver=uabort.drv stdin=yes

[EVENT] [END 2013/11/15 22:29:35] Running ABORT ddls in ddl handler table

[PROCEDURE] [START 2013/11/15 22:29:36] Cancelling ADZDPATCH concurrent program

[STATEMENT] Concurrent Request Number: 476524

[PROCEDURE] [END 2013/11/15 22:29:41] Cancelling ADZDPATCH concurrent program

[EVENT] [END 2013/11/15 22:29:47] Performing abort phase steps

[START 2013/11/15 22:29:54] Generating AD_ZD_LOGS Report

[PROCEDURE] [START 2013/11/15 22:29:55] Generating Report to spool all logs from ad_zd_logs

[EVENT] Report: /inst122i/applmgr/fs2/EBSapps/appl/ad/12.0.0/sql/ADZDSHOWLOG.sql

[EVENT] Output: /inst122i/applmgr/fs_ne/EBSapps/log/adop/7/abort_20131115_221940/INST122I_testserver01/adzdshowlog.out

[PROCEDURE] [END 2013/11/15 22:29:58] Generating Report to spool all logs from ad_zd_logs

[END 2013/11/15 22:29:59] Generating AD_ZD_LOGS Report

[END 2013/11/17 04:06:05] adzdoptl.pl run