Scenario
You
have been asked to apply a patch and you start with the first phase “PREPARE”.
Background
Customer
has recently applied two patches during the last downtime window.
$
adop phase=prepare
Enter
the APPS password:
Enter
the SYSTEM password:
Enter
the WLSADMIN password:
Please wait. Validating credentials...
Apps/System/Weblogic
Passwords are validated.
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
Here the RUN
file system is fs1 and PATCH file system is fs2
*************
Start of session *************
version: 12.2.0
started at: Thu Nov 14 2013 08:41:29
APPL_TOP is set to /inst122i/applmgr/fs1/EBSapps/appl
[START 2013/11/14 08:42:09] adzdoptl.pl run
ADOP Session ID: 5
Phase: prepare
Log file: /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/adop_20131114_084100.log
(detailed logging)
[START 2013/11/14 08:42:21] prepare phase
[EVENT] [START 2013/11/14 08:42:38] Validating
Configuration
[EVENT] Calling: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSanityCheck.pl
Program
: started @ Thu Nov 14 08:42:40 2013
***
Log File = /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/TXK_SANITY_filesystemcheck_Thu_Nov_14_08_42_40_2013/txkADOPPreparePhaseSanityCheck_Thu_Nov_14_08_42_40_2013.log
Program
: completed @ Thu Nov 14 08:42:43 2013
[EVENT] [END
2013/11/14 08:42:43] Validating Configuration
Sanity Check
on File System
·
Checks if
Apps/System/Weblogic Passwords are correct.
·
Checks if
Context File is Valid
·
Checks if RUN
and PATCH edition file system has READ/WRITE permission.
·
Checks if
environment variable RUN and PATCH edition are correct.
·
Checks if 25GB
free space is available on the PATCH edition file system.
[EVENT] [START 2013/11/14 08:42:43] Detecting config
changes in FS
[EVENT] Calling task:
adConfigChangeDetector
on testserver01>; script: ;
args: < -detectConfigChanges contextfile=/inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
promptmsg=hide log=/inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/adConfigChanges.log
hostname=testserver01>
adConfigChangeDetector
function compares the key configuration files and identifies if there are any
differences. In this current environment there are no configuration changes
found.
Validated the
passed arguments for the option -detectConfigChanges
Comparing the
HTTP config files in /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I
and /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/httpd.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/httpd.conf
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/ssl.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/ssl.conf
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/mod_wl_ohs.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/mod_wl_ohs.conf
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/url_fw_ws.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/url_fw_ws.conf
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/url_fw.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/url_fw.conf
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/custom.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/custom.conf
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/trusted.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/trusted.conf
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/ssl_terminator.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/ssl_terminator.conf
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/admin.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/admin.conf
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/oracle_apache.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/oracle_apache.conf
Comparing /inst122i/applmgr/fs1/FMW_Home/webtier/instances/EBS_web_INST122I_OHS1/config/OHS/EBS_web_INST122I/security2_dmz.conf
with /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/OHS/EBS_web_INST122I/security2_dmz.conf
Comparing the
deployment plans /inst122i/applmgr/fs1/FMW_Home/Oracle_EBS-app1/deployment_plans/oacore/plan.xml
and /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/deployment_plans/oacore/plan.xml
Comparing the
deployment plans /inst122i/applmgr/fs1/FMW_Home/Oracle_EBS-app1/deployment_plans/oafm/plan.xml
and /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/deployment_plans/oafm/plan.xml
Comparing the
deployment plans /inst122i/applmgr/fs1/FMW_Home/Oracle_EBS-app1/deployment_plans/forms/plan.xml
and /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/deployment_plans/forms/plan.xml
Comparing the
deployment plans /inst122i/applmgr/fs1/FMW_Home/Oracle_EBS-app1/deployment_plans/forms-c4ws/plan.xml
and /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover/deployment_plans/forms-c4ws/plan.xml
There is no
configuration change.
Program exiting
with status 0
[EVENT] [START 2013/11/14 08:42:46] Executing
adConfigChangeDetector on testserver01
[EVENT] Calling: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/adConfigChangeDetector.pl
The
log file is /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/adConfigChanges.log
[EVENT] [END
2013/11/14 08:42:55] Executing adConfigChangeDetector on testserver01
[EVENT] [END
2013/11/14 08:42:56] Detecting config changes in FS
[EVENT] [START 2013/11/14 08:42:57] Performing
check to see if pending cleanup actions exist
[EVENT] Checking if pending cleanup actions
[EVENT] A full cleanup needed as abort phase was
run in previous cycle
A full cleanup
is required because the previous patching session was aborted. There are
several reasons for aborting a patch which we will discuss in the abort phase.
[EVENT] [START 2013/11/14 08:43:05] Performing steps
for cleanup
[EVENT] Calling cleanup since cleanup was not run
in previous patching session.
[EVENT] [START 2013/11/14 08:43:08] Performing
Cleanup steps
[EVENT] [START 2013/11/14 08:43:12] Running
CLEANUP ddls in ddl handler table
Calling: adpatch
options=hotpatch,nocompiledb interactive=no console=no workers=4 restart=no
abandon=yes defaultsfile=/inst122i/applmgr/fs1/EBSapps/appl/admin/INST122I/adalldefaults.txt
patchtop=/inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/patch/115/driver
logfile=cleanup.log driver=ucleanup.drv
The cleanup
driver ucleanup.drv does the database cleanup like dropping / recreating tables
FND_INSTALL_PROCESS and AD_DEFERRED_JOBS. It then inserts the patch history
information into the ADOP repository tables.
ADPATCH Log directory: /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/log
[EVENT] [END
2013/11/14 08:43:45] Running CLEANUP ddls in ddl handler table
[START 2013/11/14 08:43:48]
Generating All DDL Report
[EVENT]
Report: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/sql/ADZDALLDDLS.sql
[EVENT] Output: /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/adzdallddls_20131114_091033.out
[END 2013/11/14 08:43:53] Generating All DDL
Report
[EVENT] Calling cleanup in FULL mode
[WARNING] Cleanup may take a while. Please wait.
[EVENT] [END
2013/11/14 15:31:32] Performing Cleanup steps
[EVENT] [END
2013/11/14 15:31:41] Performing steps for cleanup
[EVENT] No pending cleanup actions, proceeding
with other steps
ADZDALLDDLS.sql
generates other cleanup activities and executes them. Some of the cleanup
activities that were done during this PREPARE phase are below;
·
begin
ad_zd_seed.cleanup('IBY_BEPINFO'); end;
·
begin
ad_zd_seed.cleanup('FND_APPLICATION'); end;
·
begin
ad_zd_seed.cleanup('FND_LANGUAGES'); end;
·
begin
ad_zd_seed.cleanup('FND_PRINTER'); end;
·
begin
ad_zd_seed.cleanup('FND_PRINTER_TL'); end;
·
begin
ad_zd_seed.cleanup('FND_PROFILE_OPTION_VALUES'); end;
·
begin
ad_zd_seed.cleanup('WF_RESOURCES'); end;
[EVENT] [END
2013/11/14 15:31:42] Performing check to see if pending cleanup actions
exist
[EVENT] [START 2013/11/14 15:31:46] Performing DB
Sanity checks
[EVENT] [END
2013/11/14 15:31:58] Performing DB Sanity checks
Sanity Check
on Database
·
Checks if
Apps/System/Weblogic Passwords are correct.
·
Checks if
Context File is valid
·
Checks if
Database connectivity is fine.
[START 2013/11/14 15:31:59] Generating
Tablespace Report
[EVENT] Report: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/sql/ADZDSHOWTS.sql
[EVENT] Output: /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/adzdshowts.out
[END
2013/11/14 15:32:05] Generating Tablespace Report
[EVENT] [START 2013/11/14 15:32:06] Run the
ADZDPATCH concurrent program
[EVENT] [START 2013/11/14 15:32:15] Checking status of
the ADZDPATCH concurrent program
[EVENT] Status of ADZDPATCH:
[EVENT] This request is waiting to be processed by
the Conflict Resolution
Manager. This request cannot yet begin execution
because other requests
may
conflict with it. The Conflict Resolution Manager will determine when
this
request may begin execution. User SYSADMIN submitted this request on
14-NOV-2013
15:58:55. No action required. This is a
normal condition.
[EVENT] [END
2013/11/14 15:32:20] Checking status of the ADZDPATCH concurrent program
[EVENT] [END
2013/11/14 15:33:01] Run the ADZDPATCH concurrent program
ADZDPATCH: The
introduction of online patching with Release 12.2 has involved the introduction
of a new concurrent program, ADZDPATCH, to ensure that concurrent programs
cannot run during an online patching cycle if they are incompatible with this
new patching model.
[START 2013/11/14 15:33:01] Generating
All DDL Report
[EVENT] Report: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/sql/ADZDALLDDLS.sql
[EVENT] Output: /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/adzdallddls_20131114_035947.out
[END
2013/11/14 15:33:06] Generating All DDL Report
[EVENT] [START 2013/11/14 15:33:07] Check and create
Patch Edition (if required)
[EVENT] [START 2013/11/14 15:33:08] Checking if
Patch Edition already exists
[EVENT] Patch Edition does not exist
[START 2013/11/14 15:33:11] Creating
Patch Edition
[END
2013/11/14 15:33:49] Creating Patch Edition
[EVENT] [END
2013/11/14 15:33:50] Checking if Patch Edition already exists
[EVENT] [END
2013/11/14 15:33:51] Check and create Patch Edition (if required)
What happens
in the database:
1. A patch
edition is created in the database.
2. All code
objects in the patch edition begin as pointers to code objects in the run
edition. Code objects in the patch edition begin as lightweight "stub
objects" that point to the actual object definitions, which are inherited
from earlier editions. Stub objects consume minimal space, so the database
patch edition is initially very small in size.
3. As patches
are applied to the patch edition, code objects are actualized (have a new
definition created) in that edition.
Note: Storage
objects (such as transaction tables) are not copied.
[EVENT] [START 2013/11/14 15:33:52] Performing steps to
synchronise the FS
[EVENT] [START 2013/11/14 15:34:01] Sync FS of RUN
and PATCH
The txkADOPPreparePhaseSynchronize.pl
script checks the table ad_adop_session_patches to see if there are patches
applied to the RUN file system. If there are any patches then the script
sources the environment of the PATCH edition and applies the patch to the PATCH
file system.
The below
query gets the patch number that are applied to the RUN filesystem.
SELECT
bug_number||':'||driver_file_name||',' FROM ad_adop_session_patches WHERE
node_name = 'testserver01' AND applied_file_system_base = '/inst122i/applmgr/fs1'
and patch_file_system_base IS NULL ORDER BY
TO_CHAR(end_date,'YYYY.MM.DD:HH24:MI:SS')
Output :
16207672:u16207672.drv,16207673:u16207673.drv ( 2 patches )
Sourcing the
PATCH file system environment: /inst122i/applmgr/fs2/EBSapps/appl/APPSINST122I_testserver01.env
Executing
SYSTEM command: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/bin/adpatchnew
defaultsfile=/inst122i/applmgr/fs2/EBSapps/appl/admin/INST122I_patch/adalldefaults.txt
patchtop=/inst122i/applmgr/fs_ne/EBSapps/patch/16207672 driver=/inst122i/applmgr/fs_ne/EBSapps/patch/16207672/u16207672.drv
logfile=u_16207672.log workers=4
options="hotpatch,nodatabaseportion,nocompiledb,syncfs" restart=no
abandon=yes interactive=no console=no stdin=yes flags=autoskip
*************
Start of AutoPatch session *************
AutoPatch
version: 12.2.0
AutoPatch
started at: Thu Nov 14 2013 15:34:54
APPL_TOP is
set to /inst122i/applmgr/fs2/EBSapps/appl
Defaults
Feature Enabled = YES.
Non-Interactive
Mode = YES.
Num Workers =
4.
Flags =
"autoskip".
Options =
"hotpatch,nodatabaseportion,nocompiledb,syncfs".
Patch Top =
"/inst122i/applmgr/fs_ne/EBSapps/patch/16207672".
Patch Driver
File = "/inst122i/applmgr/fs_ne/EBSapps/patch/16207672/u16207672.drv".
Sourcing the
PATCH file system environment: /inst122i/applmgr/fs2/EBSapps/appl/APPSINST122I_testserver01.env
Executing
SYSTEM command: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/bin/adpatchnew
defaultsfile=/inst122i/applmgr/fs2/EBSapps/appl/admin/INST122I_patch/adalldefaults.txt
patchtop=/inst122i/applmgr/fs_ne/EBSapps/patch/16207673 driver=/inst122i/applmgr/fs_ne/EBSapps/patch/16207673/u16207673.drv
logfile=u_16207673.log workers=4
options="hotpatch,nodatabaseportion,nocompiledb,syncfs" restart=no
abandon=yes interactive=no console=no stdin=yes flags=noautoskip
*************
Start of AutoPatch session *************
AutoPatch
version: 12.2.0
AutoPatch
started at: Thu Nov 14 2013 16:35:20
APPL_TOP is
set to /inst122i/applmgr/fs2/EBSapps/appl
Defaults
Feature Enabled = YES.
Non-Interactive
Mode = YES.
Num Workers =
4.
Flags =
"noautoskip".
Options =
"hotpatch,nodatabaseportion,nocompiledb,syncfs".
Patch Top =
"/inst122i/applmgr/fs_ne/EBSapps/patch/16207673".
Patch Driver
File = "/inst122i/applmgr/fs_ne/EBSapps/patch/16207673/u16207673.drv".
[EVENT] Calling: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSynchronize.pl
Program
: started @ Thu Nov 14 15:34:03 2013
***
Log File = /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/TXK_SYNC_update_Thu_Nov_14_15_34_03_2013/txkADOPPreparePhaseSynchronize_Thu_Nov_14_15_34_03_2013.log
Oracle E-Business
Suite Online Patching
PATCH
edition environment variables have been set.
Oracle
E-Business Suite Online Patching
RUN
edition environment variables have been set.
========================================
SUMMARY
OF PATCHES BEING SYNCHRONIZED...
========================================
[1] SINGLE PATCH
(DRV=u16207672.drv): 16207672
[2] SINGLE PATCH (DRV=u16207673.drv): 16207673
SYNCHRONIZATION
is in progress. This may take a little longer depending on the number and size
of patches that are being synchronized.
Check
log file /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/TXK_SYNC_update_Thu_Nov_14_15_34_03_2013/txkADOPPreparePhaseSynchronize_Thu_Nov_14_15_34_03_2013.log
for details.
Oracle
E-Business Suite Online Patching
PATCH edition
environment variables have been set.
LOGPATH is set to /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/TXK_SYNC_update_Thu_Nov_14_15_34_03_2013/log
Oracle
E-Business Suite Online Patching
RUN
edition environment variables have been set.
Oracle
E-Business Suite Online Patching
PATCH
edition environment variables have been set.
LOGPATH is set to /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/TXK_SYNC_update_Thu_Nov_14_15_34_03_2013/log
Oracle
E-Business Suite Online Patching
RUN
edition environment variables have been set.
cmd
= /inst122i/applmgr/fs1/FMW_Home/jrockit32/jre/bin/java -classpath /inst122i/applmgr/fs1/FMW_Home/Oracle_EBS-app1/shared-libs/ebs-appsborg/WEB-INF/lib/ebsAppsborgManifest.jar:/inst122i/applmgr/fs1/EBSapps/comn/java/classes
-mx256m oracle.apps.ad.tools.configuration.ADOPCustomSyncUp
-contextFile /inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/INST122I_testserver01.xml
-custSyncDrv /inst122i/applmgr/fs_ne/EBSapps/appl/ad/custom/adop_sync.drv
-logFile /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/TXK_SYNC_update_Thu_Nov_14_15_34_03_2013/txkADOPCustomSyncUp.log
-promptmsg 'hide'
Removing
PS artifacts from PATCH fs
Copying
PS artifacts from RUN to PATCH fs for exectier
Removing
SNO artifacts from PATCH fs
Copying
SNO artifacts from RUN to PATCH fs for exectier
ADOP
Custom Synchorization successfully run
Program
: completed @ Thu Nov 14 16:45:00 2013
[EVENT] [END
2013/11/14 16:45:00] Sync FS of RUN and PATCH
[EVENT] [END
2013/11/14 16:45:09] Performing steps to synchronise the FS
[EVENT] [START 2013/11/14 16:45:10] Performing
steps to validate configuration
[EVENT]
[START 2013/11/14 16:45:11] Validating Configuration
[EVENT] Calling: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSanityCheck.pl
Program
: started @ Thu Nov 14 16:45:14 2013
***
Log File = /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/TXK_SANITY_dbcheck_Thu_Nov_14_16_45_14_2013/txkADOPPreparePhaseSanityCheck_Thu_Nov_14_16_45_14_2013.log
Program
: completed @ Thu Nov 14 16:45:16 2013
[EVENT] [END
2013/11/14 16:45:16] Validating Configuration
[EVENT] [END
2013/11/14 16:45:16] Performing steps to validate configuration
[EVENT] [START 2013/11/14 16:45:17] Synchronizing
Snapshots
[EVENT] [END
2013/11/14 16:46:22] Synchronizing Snapshots
[END
2013/11/14 16:46:27] prepare phase
[START 2013/11/14 16:46:36] Generating
AD_ZD_LOGS Report
[EVENT] Report: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/sql/ADZDSHOWLOG.sql
[EVENT] Output: /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/prepare_20131114_084100/INST122I_testserver01/adzdshowlog.out
[END
2013/11/14 16:46:42] Generating AD_ZD_LOGS Report
[EVENT] [START 2013/11/14 16:46:50] Check and Stop
Patch FS Admin Server
You
are running adadminsrvctl.sh version 120.10.12020000.4
The AdminServer is already shutdown
adadminsrvctl.sh:
exiting with status 2
adadminsrvctl.sh:
check the logfile /inst122i/applmgr/fs2/inst/apps/INST122I_testserver01/logs/appl/admin/log/adadminsrvctl.txt
for more information ...
[EVENT] [END
2013/11/14 16:47:00] Check and Stop Patch FS Admin Server
[END
2013/11/14 16:47:08] adzdoptl.pl run
adop phase=prepare - Completed Successfully
Log file: /inst122i/applmgr/fs_ne/EBSapps/log/adop/5/adop_20131114_084100.log
adop
exiting with status = 0 (Success)
$
exit
Observation
Prepare
Phase execution time frame is more than 8 hours in this scenario.
Started
at Thu Nov 14 2013 08:41:29 and Ended at Thu Nov 14 2013 16:47:08
This
did not affect the users online but cause some overhead to the server for 8
hours and the patch was running with 4 workers.
Reason:
Patch
16207672 is
a 12.2.2 upgrade patch. During the previous upgrade window customer has
requested to upgrade from 12.2.0 to 12.2.2.
Recommendation:
During
such huge or mass patching cycle it is better to end the patching cycle with
one additional phase which is called fs_clone. This step basically copies the
run file system to the patch file system. So after fs_clone phase if we run the
prepare phase it will not take too much time as there are no differences
between the file systems.
Prepare Phase - Scenario
