FS Clone Failed to Deregister Oracle Home

Share on:

Most of the time, on a newly commissioned Linux OS, Swap space might not be allotted. Suppose under such circumstances, you want to install EBS R12.2 file system for which Oracle recommended Swap memory is 16 GB or more.

It is acceptable to ignore the recommendation and proceed with laying down of R12.2 file system, provided you don’t hit swap issues. If you are lucky enough, you can even carry out subsequent tasks that rely heavily on RAM and Swap space.

But as you approach towards the end of R12.2 configuration on the server, you encounter an issue after running fs_clone. It might so happen that fs_clone lets you away without any warnings during the first run post RUP 12.2.11, but in the next run, it’s not amused.

Excerpts from various logs below helps in the RCA:

 

1. adop.log

fs clone1

 

2. adopscanlog

Scanning /u32/apps/TWO_TASK/fs_ne/EBSapps/log/adop/5/ directory …

/u32/apps/TWO_TASK/fs_ne/EBSapps/log/adop/5/20221117_192621/fs_clone/hostname/TXK_SYNC_create/fsclone_apply/FSCloneApplyAppsTier_11171936.log:
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -Lines #(996–1000):
.end err out.
ERROR: Failed to deregister Oracle Home Name=u32_apps_**_fs1_Oracle_EBS_app location=/u32/apps/TWO_TASK/fs1/FMW_Home/Oracle_EBS-app1

START: Inside exitClone….
/u32/apps/TWO_TASK/fs_ne/EBSapps/log/adop/5/20221117_192621/fs_clone/hostname/TXK_SYNC_create/txkADOPPreparePhaseSynchronize.log:

Lines #(523–525):

TIME : Thu Nov 17 19:36:08 2022

FUNCTION: main::runFSCloneApply [ Level 1 ]

ERRORMSG: /u32/apps/TWO_TASK/fs2/EBSapps/comn/adopclone_hostname/bin/adclone.pl did not go through successfully.

/u32/apps/TWO_TASK/fs_ne/EBSapps/log/adop/5/20221117_192621/adop.log:
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

 

3. FSCloneApplyAppsTier_datetimestamp.log

fs clone2

You will notice the same error recorded in Oracle Home inventory location log file.

Now that you have found out the root cause of fs_clone failure and you surely want to get past any potential hit-and-miss, you would have to allocate Swap memory and re-try fs_clone with force=yes option.

Share on:
Back to Top