Modern Oracle DBA

 Adop Phase=fs_clone What is the fs_clone Phase? The fs_clone phase in Oracle EBS refers to the process of cloning the patch edition file system from the run edition.  It is used for file system cloning, and the usual cloning (adcfgclone.pl) script cannot be used to synchronize the run and patch file systems. Normally, fs_clone deletes the patch file system and restores the run system. When to Use  fs_clone Consider using the  fs_clone  phase in the following scenarios: After Aborting an Online Patching Cycle If a previous online patching cycle is aborted, the file system must be synchronized. If Technology Stack Patch is Applied in the Run Edition If any manual changes are made in the run file system, such as applying a technology stack patch, the file system must be synchronized. After Applying a RUP Patch Using  fs_clone  will synchronization between run and patch file and its help complete the prepare phase quickly. How to Execute fs_clone? adop Phase=fs_clone This command starts t

What is the ADOP Finalize Phase? After applying the patches in the patch edition, it will create lots of invalid objects. The finalize phase will compile the invalid objects, and it will prepare the environment for the cutover phase. The finalize phase is the optional phase in the patching cycle. After applying the patch, if we missed it, run Finalize and directorally run the cutover. The cutover phase will check if the if the finalize phase is completed or not. If not completed, the finalize phase cutover phase will start. Key Actions during the Finalize Phase Mode Selection : ADOP offers two modes for finalization - "quick" and "full": Quick Mode : This mode prioritizes speed by skipping non-essential tasks, making it ideal for scenarios where minimal downtime is critical. Full Mode : In contrast, full mode executes additional actions such as gathering statistics to the DML statment and enhance system performance after the patch is applied. This mode is beneficial

adop phase=prepare Understanding ADOP Prepare Parameters Before diving into the prepare phase, let's go over the key parameters: skipsyncerror : This parameter specifies whether to ignore errors that may occur during incremental file system synchronization. Options :  yes  or  no  (default:  no ) Usage : Set to  yes  if you encountered errors in a previous patching cycle but decided to continue with the cutover. This will ignore apply errors during the next synchronization. sync_mode : This parameter determines the method used to synchronize the patch file system with the run file system. Options :  delta  or  patch  (default:  patch ) Usage : delta : Uses the file system synchronization command specified in  $AD_TOP/patch/115/etc/delta_sync_drv.txt . patch : Reapplies patches applied on the run file system. Example Command adop phase=prepare skipsyncerror= yes sync_mode=delta Step-by-Step Execution 1. Validating Passwords The process begins by validating the credentials for app