Modern Oracle DBA

The patch edition file system is normally synchronized with the run edition file system during the prepare phase. There are some cases where it is helpful or required to manually re-clone the patch  edition file system from the run edition. 1) After aborting an online patching cycle. 2) After manually changing the run edition file system. 3) After patching middle-tier technology components. 4) After applying an EBS RUP. By re-cloning the patch edition file system, you can be certain that it is correctly synchronized, and also minimize any synchronization delay that would normally occur on the next prepare command . adop phase=fs_clone If there is any error you must examine log files and correct the problem, then restart the fs_clone by running the command again. If fs_clone does not restart correctly you can force the process to restart from the beginning. Example - Restart failed fs_clone from the beginning: adop phase=fs_clone force=yes What happening in FS_CLON

Finalize Parameters: finalize_mode=(full|quick) [default: quick] Quick mode will provide the shortest execution time, by skipping non-essential actions. Full mode performs additional actions such as gathering statistics that may improve performance after cutover. Example - Perform additional optimizations during Finalize: adop phase=finalize finalize_mode=full Using full mode after applying a major patch can help maintain optimal system performance. What happening finalize phase Collected below information in log files Adop phase=finalize Checking for pending hotpatch session. Checking for pending cleanup session. Continuing with existing session [Session ID: 22]. Verifying data dictionary. Running finalize phase database actions. Log: @ADZDSHOWLOG.sql Finalize System Executing FINALIZE actions Compiling invalid objects. Generating log report: adzdshowlog.out The finalize phase completed successfully.

adop phase=prepare Prepare Parameters:   skipsyncerror=(yes|no) [default: no] Specifies whether to ignore errors that may occur during incremental file system synchronization. This might happen if you applied a patch in the previous patching cycle that had errors but decided to continue with the cutover. When the patch is synchronized on the next patching cycle, the apply errors may occur again, but can be ignored.   sync_mode=(delta|patch) [default: patch] Specifies the method used to synchronize the patch file system with the run file system. ‘delta' mode uses the file system synchronization command specified in $AD_TOP/patch/115/etc/delta_sync_drv.txt. 'patch' mode reapplies the patches that were applied on the run file system. Example: adop phase=prepare skipsyncerror=yes sync_mode=delta Below details Collected from the log file   Validating the apps,system and weblogic password Creating the session id Ex: session id: 22 Generate the log fi