Patching: FS_CLONE phase

 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:

1. After Aborting an Online Patching Cycle
   If a previous online patching cycle is aborted, the file system must be synchronized.

2. 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.

3. 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 the fs_clone phase, initiating the process of synchronizing the patch edition file system with the run edition.

Monitor Progress: During execution, monitor the log files to ensure the process completes without errors. Log files provide detailed information on each step, including validation, synchronization, and finalization.

Restart the failed fs_clone:

adop phase=fs_clone force=yes

Step-by-Step Execution

1. Validating System Setup
   The process begins by validating the system setup to ensure everything is configured correctly.

2. Checking for Existing adop Sessions
   The system checks for any existing adop sessions to avoid conflicts.

3. Checking for Pending Hotpatch and Cleanup Sessions
   Pending hotpatch and cleanup sessions are checked to ensure there are no incomplete processes.

4. No Pending Session Exists
   Confirmation that no pending sessions exist, allowing the new session to start.

5. Starting New adop Session
   A new adop session is initiated to begin the fs_clone process.

6. Phase: fs_clone
   The phase is officially started.

7. Creating a Log File
   A log file is created to record all actions and changes during the fs_clone phase.

8. Validating Configuration on Node
   Configuration validation on the node ensures all settings are correct before proceeding.

9. Checking for Pending Cleanup Actions
   The system checks for any pending cleanup actions that need to be addressed.

10. Blocking Managed Server Ports
    Managed server ports are blocked to prevent any disruptions during the cloning process.

11. Performing CLONE Steps
    The actual cloning steps are performed to synchronize the file systems.

12. Alter Logon Trigger: DISABLE
    The logon trigger is temporarily disabled to prevent access during critical changes.

13. Alter Logon Trigger: ENABLE
    The logon trigger is re-enabled once the critical changes are made.

14. Releasing Managed Server Ports
    Managed server ports are released, allowing normal operations to resume.

15. Synchronizing Snapshots
    Snapshots are synchronized to ensure both file systems are identical.

16. Stopping Services on Patch File System
    Services on the patch file system are stopped to finalize the cloning process.

17. Stopping Admin Server
    The admin server is stopped as part of the process.

18. Stopping Node Manager
    The node manager is also stopped.

19. Generating Log Report
    A log report is generated to document the entire fs_clone process.

20. The fs_clone Phase Completed Successfully
    The fs_clone phase completes successfully, indicating that the file systems are now synchronized and the system is ready for further actions.