Prepare Phase Scenario 4 - R12.2 Online Patching Cycle

Scenario

You have been asked to apply a patch after a fresh installation of R12.2.X. So you are running PREPARE phase for the first time on the instance.

$ adop phase=prepare

Passwords are validated

RUN and PATCH file system is verified

Validates Configuration

Performs Sanity Check on the file system.

Runs configuration detector

[STATEMENT] [START 2013/11/10 02:26:14] Detecting config changes in FS

  [STATEMENT] [START 2013/11/10 02:26:16] Executing adConfigChangeDetector on testserver01

  [STATEMENT] Calling: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/adConfigChangeDetector.pl

  [STATEMENT] [END   2013/11/10 02:26:26] Executing adConfigChangeDetector on testserver01

 [STATEMENT] Config changes detected in testserver01

  [STATEMENT] [START 2013/11/10 02:26:27] Insert Config Clone tracking row for NODE: testserver01

  [STATEMENT] [END   2013/11/10 02:26:34] Insert Config Clone tracking row for NODE: testserver01

[STATEMENT] [END   2013/11/10 02:26:36] Detecting config changes in FS

Content of adConfigChanges.log

Validated the passed arguments for the option –detectConfigChanges

/inst122i/applmgr/fs1/inst/apps/INST122I_testserver01/appl/admin/cutover directory not found, so configuration changes cannot be detected. The directory may have been deleted intentionally or accidentally. Or, if this is the first adop cycle, the directory will only be created after cutover.

Without this directory, the configuration changes will be propagated to the patch file system forcefully.

Program exiting with status 2

Checks if Cleanup activity has to be performed

[STATEMENT] [START 2013/11/10 02:26:37] Performing check to see if pending cleanup actions exist

 [STATEMENT] Checking if pending cleanup actions

 [STATEMENT] No pending cleanup actions, proceeding with other steps

[STATEMENT] [END   2013/11/10 02:26:45] Performing check to see if pending cleanup actions exist

Performs Sanity Check on the database.

[STATEMENT] [START 2013/11/10 02:26:51] Performing DB Sanity checks

  [STATEMENT] [START 2013/11/10 02:26:52] Checking if edition enabled users exist

  [STATEMENT] [END   2013/11/10 02:26:55] Checking if edition enabled users exist

  [STATEMENT] [START 2013/11/10 02:26:57] Performing Check for patch service existence

  [STATEMENT] [END   2013/11/10 02:27:00] Performing Check for patch service existence

  [STATEMENT] [START 2013/11/10 02:27:01] Performing Check for Logon Trigger existence and enablement

  [STATEMENT] [END   2013/11/10 02:27:07] Performing Check for Logon Trigger existence and enablement

[STATEMENT] [END   2013/11/10 02:27:08] Performing DB Sanity checks

Validates the ADZDPATCH concurrent program

[STATEMENT] [END   2013/11/10 02:27:33] Checking status of the ADZDPATCH concurrent program

[STATEMENT] Concurrent Request Number: 457214

Validates the Patch Edition

[STATEMENT] [START 2013/11/10 02:28:07] Check and create Patch Edition (if required)

[STATEMENT] [START 2013/11/10 02:28:09] Checking if Patch Edition already exists

[STATEMENT] Patch Edition does not exist

[STATEMENT] [START 2013/11/10 02:28:13] Creating Patch Edition

[STATEMENT] [END   2013/11/10 02:29:07] Creating Patch Edition

[STATEMENT] [END   2013/11/10 02:29:08] Checking if Patch Edition already exists

[STATEMENT] [END   2013/11/10 02:29:10] Check and create Patch Edition (if required)

Performing Steps to Synchronize the File System

1.  Perform steps to CLONE FS of RUN and PATCH appltops

2.  Perform steps to syncup FS of RUN and PATCH appltops

3.  Performing steps to CONFIG_CLONE FS of RUN and PATCH appltops

a.  Checking if LOGON trigger is enabled since fs CONFIG_CLONE is done else create it

b.  Sources the Patch Edition environment and the Run Edition environment

c.  Running AutoConfig

Step 1 and 2 - since this is a fresh installation the appltops between RUN and PATCH edition will be same so there is no activity performed here.

Step 3 Autoconfig runs using the PATCH edition context file.

Validates the Configuration

[STATEMENT] [START 2013/11/10 02:43:42] Performing steps to validate configuration

[STATEMENT] [START 2013/11/10 02:43:44] Validating Configuration

[STATEMENT] Calling: /inst122i/applmgr/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/txkADOPPreparePhaseSanityCheck.pl

[STATEMENT] Output directory: /inst122i/applmgr/fs_ne/EBSapps/log/adop/2/prepare_20131110_022443/INST122I_testserver01

[STATEMENT] [END   2013/11/10 02:43:50] Validating Configuration

[STATEMENT] [END   2013/11/10 02:43:51] Performing steps to validate configuration

Stops Patch FS Admin Server

    [STATEMENT] [START 2013/11/10 02:44:15] Check and Stop Patch FS Admin Server

    [STATEMENT] [END   2013/11/10 02:44:30] Check and Stop Patch FS Admin Server

Prepare Phase Completed Successfully

[STATEMENT] [END   2013/11/10 02:44:37] adzdoptl.pl run

[STATEMENT] adop phase=prepare - Completed Successfully 

Prepare Phase  - Scenario

You have been asked to apply a patch and you start with the first phase “PREPARE”. Customer has recently applied two patches during the last downtime window.

You have been asked to apply a patch and you start with the first phase “PREPARE”. Another engineer has already run the prepare phase and for some reasons the engineer did not proceed further.

You have been asked to apply a patch and you start with the first phase “PREPARE”. Your terminal got disconnected when prepare phase was running or there was an outage and server got rebooted.

You have been asked to apply a patch after a fresh installation of R12.2.X. So you are running PREPARE phase for the first time on the instance.