Skip to main content

Error during rapid clone on, exit code 255

I needed to run a clone and was running into a really head scratcher. As is Oracle\'s way they sometimes enjoy giving us DBA's a bit of detective work to do. As usual I kept knocking my head into various brick walls instead of tracking back through the logs. Eventually I came up with the problem

Start to configure the run filesystem. You can do a dualfs from AD-TXK Delta 7 but for now I just needed to get this up and running:
perl appsTier
START: Creating FMW Home.
Running /u03/APPLUAT/UAT/fs1/EBSapps/comn/clone/FMW/ -javaHome /u03/APPLUAT/UAT/fs1/EBSapps/comn/util/jdk64 -al /u03/APPLUAT/UAT/fs1/EBSapps/comn/clone/FMW/FMW_Home.jar -tl /u03/APPLUAT/UAT/fs1/FMW_Home -invPtrLoc /etc/oraInst.loc -ldl /u03/APPLUAT/UAT/fs1/inst/apps/UAT_erpapp05/admin/log/clone/fmwT2PApply -silent true -debug true -executeSysPrereqs false
Script Executed in 21933 milliseconds, returning status 255
ERROR: Script failed, exit code 255

Oracle has left me a cryptic error and I come up with this note on MOS: Timeout Error Encountered for While Running "adop phase=fs_clone" (Doc ID 1599424.1). Quite excited I run is again but again it fails. Again not reading the logs I think it has something to do with a possible firewall on the system. Also not the case and after some searching the logs reveal this is the error:
cd /u03/APPLUAT/UAT/fs1/inst/apps/UAT_erpapp05/admin/log/clone/fmwT2PApply
cat CLONE2016-01-03_08-28-11AM.error
SEVERE : Jan 3, 2016 8:28:19 AM - ERROR - CLONE-20218   Cloning is not successful.
SEVERE : Jan 3, 2016 8:28:19 AM - CAUSE - CLONE-20218   An internal operation failed.
SEVERE : Jan 3, 2016 8:28:19 AM - ACTION - CLONE-20218   Provide the clone log and error file for investigation. /u03/APPLUAT/UAT/fs1/FMW_Home/CLONE20160103082659250/oraclehomes/ORACLEHOME_APPSEBS_CLONE20160102115537662-oraclehome2@Oracle_EBS-app1/applications/oacore/html/WEB-INF/classes/_pages/__iecresgrptype.class (Stale file handle)
        at Method)
SEVERE : /u03/APPLUAT/UAT/fs1/FMW_Home/CLONE20160103082659250/oraclehomes/ORACLEHOME_APPSEBS_CLONE20160102115537662-oraclehome2@Oracle_EBS-app1/applications/oacore/html/WEB-INF/classes/_pages/__iecresgrptype.class (Stale file handle)


Because this is a clone of the same instance the mount points have become stale. Most of the times you'll get an error straight out the bat when working on something like this. So I remounted the instance and the clone happily continued.
umount /u03
mount /u03


Popular posts from this blog

Cancel or abort adop session

ADOP is in my opinion still pretty half baked. This is a critical tool that just isn't as intuitive as the old adpatch was. However we move with the times and get the hang of the new way of doing things. Along the way you might want to abort or cancel a patching cycling. With the two file systems and db editioning this can be a bit more to manage. I have learnt the hard way so you need to use the full cleanup after aborting a session.
adop phase=abort
adop phase=cleanup cleanup_mode=full

Creating new WLS domain ends with exit code 255

Cloning the instance I ran into this weird error. Was not sure what to do but after learning my lesson I dug through the error logs after seeing this in the adcfgclone log file.
START: Creating new WLS domain.
Running /u03/APPLYES/YES/fs2/FMW_Home/oracle_common/bin/ -javaHome /u03/APPLYES/YES/fs2/EBSapps/comn/util/jdk64 -al /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/EBSdomain.jar -tdl /u03/APPLYES/YES/fs2/FMW_Home/user_projects/domains/EBS_domain_YES -tmw /u03/APPLYES/YES/fs2/FMW_Home -mpl /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/WLS/plan/moveplan.xml -ldl /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply -silent true -debug true -domainAdminPassword /u03/APPLYES/YES/fs2/EBSapps/comn/clone/FMW/tempinfo.txt
Script Executed in 1903 milliseconds, returning status 255
ERROR: Script failed, exit code 255

Dig a bit deeper into the log files
cd /u03/APPLYES/YES/fs2/inst/apps/YES_erpapyes/admin/log/clone/wlsT2PApply
cat CLONE2016-01-10_04-37-11PM.log

Failed to initialize the application 'EBSDataSource' due to error weblogic.application.ModuleException after FNDCPASS apps change

Started testing password changes in our clone environments. Weblogic seems to love throwing you curve balls and when I changes the apps password with the below:
I was not able to start the weblogic managed servers. A look in the log an I found this:

        at weblogic.jdbc.module.JDBCModule.prepare(
        at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(
        at weblogic.application.internal.flow.DeploymentCallbackFlow$
        at weblogic.application.utils.StateMachineDriver.nextState(
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(
        at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(
        at weblogic.application.internal.BaseDep…