R12

[lawrence]

Hi,

Good Evening.

I need your favour in knowing some piece of information for which I am not getting exact answer that satisfies me

1)After Abort is ran,it is recommended to run fsclone or prepare will run it.wanted to know the reason behind this

Thanks,
Lawrence

[ErmanArslansOracleBlog]

It is recommended that you run the prepare phase after the abort phase, so if there is a need to abort
the patching cycle, it is advisable to use the adop phase=abort,cleanup cleanup_mode=full command to abort the patching cycle.

[ErmanArslansOracleBlog]

Here is an info from my book, it may give you an idea.

Practical Oracle E-Business Suite - the book.

if abort is called after executing the adop phase=apply command to apply patches into the patch
edition and patch file system, then there is a need to run an fs_clone too. In this case, the adop phase=abort
command should be followed by a full cleanup (adop phase=cleanup cleanup_mode=full) and an fs_clone
(adop phase=fs_clone) to make the database be in a clear state and to make the patch file system re-created
from the run/active file system. Using fs_clone, the patch file system is re-created to be in a clear state
(without patches applied) and also in a synchronized state with the run file system.

[satish]

Then what I think was wrong.Abort will rollback the changes introduced by patch in patch file system.if it is correct then fsclone is not required right?

Glad to get an update for my query

[ErmanArslansOracleBlog]

Let me tell you this with Oracle 's own sentences:

" Attention to the ""if"" statement below!!""

Reference: Oracle E-Business Suite Maintenance Guide
Release 12.2
Part Number E22954-21

After running abort, a full cleanup must be performed. The cleanup command is:adop phase=cleanup cleanup_mode=full). This will remove any columns that were added by the patch but are no longer needed because of the abort. If they are not removed, they may cause problems in a later patching cycle.

Alternatively, you can run a combined command to abort the patching cycle and perform a full cleanup:

$ adop phase=abort,cleanup cleanup_mode=full
If any attempt was made to apply patches to the patch edition, after abort you must run the fs_clone phase (adop phase=fs_clone) to recreate the patch file system.

[satish]

Thank you.abort will drop the patch edition in database.what I wanted to know is what happens at file system level?

Thanks for your time
Regards,
Lawrence

[ErmanArslansOracleBlog]

Did you ever take a look at the log file of adop abort phase?

Here, it runs adpatch and it uses uabort.drv.
This drv should give adpatch the instructions.
So abort phase again runs like a patching activity.
check the uabort.drv and see the actions.

For ex:

adpatch options=hotpatch,nocompiledb interactive=no blablablabla ... patchtop=/erman/applmgr/fs2/EBSapps/appl/ad/12.0.0/patch/115/driver logfile=abort.log driver=uabort.drv

[ErmanArslansOracleBlog]

The driver files are located in AD_TOP.

/u01/install/APPS/fs2/EBSapps/appl/ad/12.0.0/patch/115/driver
[applmgr@ermansrv1 driver]$ ls -al
total 44
drwxr-xr-x 2 applmgr oinstall 4096 Aug 25 14:31 .
drwxr-xr-x 9 applmgr oinstall 4096 Jan 13  2014 ..
-rwxr-xr-x 1 applmgr oinstall  145 Jan 13  2014 adrmoad.drvx
-rwxr-xr-x 1 applmgr oinstall  275 Jan 13  2014 adzdgrants.drvx
-rwxr-xr-x 1 applmgr oinstall 7770 Jan 13  2014 ADZDPREP.drvx
-rwxr-xr-x 1 applmgr oinstall  526 Jan 13  2014 explode.drv
-rwxr-xr-x 1 applmgr oinstall  994 Jan 13  2014 uabort.drv
-rwxr-xr-x 1 applmgr oinstall 1391 Jan 13  2014 uactualize.drv
-rwxr-xr-x 1 applmgr oinstall  943 Jan 13  2014 ucleanup.drv
-rwxr-xr-x 1 applmgr oinstall  943 Jan 13  2014 ucutover.drv

I checked it now, and it seems it doesn't do anyting in the filesystem level.


So, that's why , we say, run fs_clone after abort, "if" you patched the filesystem.. (if you applied any patches).. This is logical, since abort does not do anything in the filesystem level. (no reverting back in the filesystem level)

[satish]

Got it. Thanks for your time. Appreciate your good work in this blog.