Overview of FS_CLONE phase
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_CLONE phase
Collected Below information from log file
Validating
system setup.
Checking for existing adop sessions
Checking for pending hotpatch session.
Checking for pending cleanup session.
No pending session exists.
Starting new adop session
Phase: fs_clone
Creating a log file
Validating configuration on node
Checking for pending cleanup actions.
Blocking managed server ports.
Performing CLONE steps.
Alter logon trigger: DISABLE
Alter logon trigger: enable
Releasing managed server ports.
Synchronizing snapshots.
Stopping services on patch file system.
Stopping admin server.
Stopping node manager.
Generating log report.
The fs_clone phase completed successfully.
Strange "water hack" burns 2lbs overnight
ReplyDeleteMore than 160 thousand women and men are trying a easy and SECRET "water hack" to burn 2 lbs every night in their sleep.
It is easy and it works with everybody.
Here's how you can do it yourself:
1) Grab a glass and fill it with water half glass
2) And now learn this crazy HACK
and be 2 lbs skinnier the very next day!