Oracle E Business Suite 12.2 ADOP Patching Cycle

Before adop fs1 is run file system fs2 is patch file system You are going to apply a patch As we know there are 5 cycles in ADOP Patching Cycle 1. Prpare 2. Apply 3. Finalize 4. Cutover 5. Cleanup 1. So as the first step when you run adop with phase=prepare adop phase=prepare Enter the APPS password: apps (default password) Enter the SYSTEM password: MANAGER ( defualt password ) Enter the WLSADMIN password:welcome123 (default password) A copy of fs1 will be made in fs2 that will be called as patch file system 2. In the 2nd phase you will apply the patch with the patch number 3. In the 3rd pahse you will run the Finalize ,you go and compile the invalid objects and generate all the dervived objects 4. In the cutover phase you brings down the production system ,and you will swap the patch file system to the run file system ...(the first 3 phase should be complete before runnig the cutover phase ) The patch edition will become your new runedition file system and the patch edition of db to be your new run edition db file system and then you start the application on the patch copy which is obviously the new run ediditon file system 5. In cleanup phase ,it will remove all the obselet objects from the run file edition and send the data to reocver phase . At the end of the adop lifecycle, you will have a copy of old the run file system which will become the nex patch file system as far as application tier is concerned where as the old run system in database wil be descarded Summary of Fundamental Patching Operations Patching is performed in several phases, which are specified on the adop command line as follows: adop phase= Prepare phase - Used to start a new online patching cycle: $ adop phase=prepare Apply phase - Used to apply a patch to the patch edition of a system: $ adop phase=apply patches=123456 workers=8 Finalize phase - Used to perform the final patching operations that can be executed while the application is still online: $ adop phase=finalize Cutover phase - Used to perform the transition to the patched environment: $ adop phase=cutover Cleanup phase - Used to remove old objects that are no longer needed: $ adop phase=cleanup Abort phase - Used only if the online patching cycle needs to be terminated before completion: $ adop phase=abort Important: The abort phase can only be run after the prepare phase and before completion of the cutover phase. After the cutover phase completes, it is no longer possible to abort the online patching cycle. The adop phases are described in more detail in The Online Patching Cycle section of the Patching Procedures chapter. Patch Log Files It is advisable to review the relevant log files after any patching operation. The adop log files are located on the non-editioned file system (fs_ne), under: $NE_BASE/EBSapps/log/adop//__//log For example, if s_ne_base was /u01/R122_EBS/fs_ne, the session ID was 15, and the was patch01_testsys, the path to the adop log files from 9th July 2014 would resemble this: /u01/R122_EBS/fs_ne/EBSapps/log/adop/15/apply_20140709_112226/patch01_testsys/log The adop Interface adop is run from the command line. It prompts for required passwords, but expects all other input parameters to be specified on the command line or in an input file. Running adop The following is a summary of the steps you use to run adop. For a complete procedural description of all the steps, see Creating Customized Instructions for Patching Using PAA. Step 1: Set the environment You must set the environment to apply the configuration parameters that define your system. This task is common to many AD utilities. Your Oracle E-Business Suite installation includes a shell script in the root installation directory that helps you easily set the run edition or patch edition environment. For example: $ . /EBSapps.env run Step 2: Unzip the patch Download and unzip the patch into the patch top directory, which is identified by the $PATCH_TOP environment variable. Step 3: Review the information in the readme file In the directory where you unzipped the patch, you will find a README.txt file and a README.html file. Review either readme file for information about the patch and for instructions on using Oracle Patch Application Assistant (PAA) to generate customized instructions for your system. Step 4: Run Oracle Patch Application Assistant Run PAA (admsi.pl) to generate customized instructions for your system. Follow the steps in the customized instructions to start the patching process. Step 5: Run adop The customized instructions generated by PAA describe how to run adop using the adop command. Note: You can add arguments on the command line to refine the way adop runs. See adop Modes and Command Line Arguments. A simple example of the commands to execute a complete online patching cycle for patch 123456 is as follows: $ . /EBSapps.env run $ adop phase=prepare $ adop phase=apply patches=123456 $ adop phase=finalize $ adop phase=cutover $ . /EBSapps.env run $ adop phase=cleanup Monitoring Status You can obtain a brief report for the current patching session by running the command: $ adop -status This will display information that includes phases completed and the time taken. In the example below, the current patching session ID is 5: Current Patching Session ID: 5 Node Name Node Type Phase Status Started Finished Elapsed --------------- --------------- ----------- --------------- ------------------------------ ------------------------------ ------------ patchtest1 master PREPARE COMPLETED 06-MAY-13 11:31:38 -07:00 07-MAY-13 12:27:51 -07:00 0:56:13 APPLY COMPLETED 07-MAY-13 04:19:17 -07:00 07-MAY-13 04:43:12 -07:00 0:23:55 CUTOVER COMPLETED 07-MAY-13 05:54:03 -07:00 07-MAY-13 05:57:57 -07:00 0:03:54 CLEANUP COMPLETED 07-MAY-13 09:14:33 -07:00 07-MAY-13 09:22:46 -07:00 0:08:13 The output is also recorded in a log file, called /u01/R122_EBS/fs_ne/EBSapps/log/status__/adzdshowstatus.out. For example, /u01/R122_EBS/fs_ne/EBSapps/log/status_20130507_111647/adzdshowstatus.out. Two additional options with this command are as follows. If you want information about a particular session, specify the relevant session ID: $ adop -status If you want additional details of operations performed: $ adop -status -detail This option will give a summary of last ten adop session IDs, and full details of the file system and database changes introduced by a patch. It also shows the log file location of the current patching cycle. Aborting an Online Patching Cycle. If a patching cycle is failing and the issue cannot be resolved quickly, it is possible to abort the patching cycle and return to normal runtime operation. The patch edition will be dropped. You can abandon a patching cycle (without applying any patches) by running the command: $ adop phase=abort Important: The abort command is only available until successful completion of the cutover phase. After cutover completes, the system is running on the new edition and abort is no longer available for that patching cycle. Warning: Aborting a patching cycle will drop the patch edition, but you must then run the cleanup and fs_clone phases before starting a new patching cycle. The cleanup must be a full cleanup ($ adop phase=cleanup cleanup_mode=full). For example: $ adop phase=prepare $ adop phase=apply patches=123456 [Patch application encounters problems and you want to abort] $ adop phase=abort $ adop phase=cleanup cleanup_mode=full $ adop phase=fs_clone