Skip to main content unexpected error for adop

After aborting a adop session I ran into a bit of a problem with fs_clone. Log files weren't helping so I ran:

adop phase=fs_clone loglevel=statement

This is what I saw

*******FATAL ERROR*******
PROGRAM : (/oa01/oradata/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/
TIME    : Mon Jan  4 16:45:03 2016
FUNCTION: TXK::SQLPLUS::_doExecute [ Level 3 ]
SQLPLUS error: buffer=
SQL*Plus: Release - Production on Mon Jan 4 16:45:03 2016
Copyright (c) 1982, 2005, Oracle.  All rights reserved.
SQL> SQL> Connected.
SQL> SELECT clone_status||',' FROM ad_adop_session_patches WHERE status in ('R','F','N') AND bug_number = 'CLONE' AND node_name = 'oraapdev' AND adop_session_id =
ERROR at line 1:
ORA-00936: missing expression
Disconnected from Oracle Database 11g Enterprise Edition Release - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
 at /oa01/oradata/fs1/EBSapps/appl/au/12.0.0/perl/TXK/ line 168
        TXK::Error::abort('TXK::Error', 'HASH(0xb12ca0)') called at /oa01/oradata/fs1/EBSapps/appl/au/12.0.0/perl/TXK/ line 299
        TXK::Common::doError('TXK::SQLPLUS=HASH(0x24f4958)', 'SQLPLUS error: buffer=\x{a}\x{a}SQL*Plus: Release - Produc...', undef) called at /oa01/oradata/fs1/EBSapps/appl/au/12.0.0/perl/TXK/ line 314
        TXK::Common::setError('TXK::SQLPLUS=HASH(0x24f4958)', 'SQLPLUS error: buffer=\x{a}\x{a}SQL*Plus: Release - Produc...') called at /oa01/oradata/fs1/EBSapps/appl/au/12.0.0/perl/TXK/ line 832
        TXK::SQLPLUS::_doExecute('TXK::SQLPLUS=HASH(0x24f4958)', 0) called at /oa01/oradata/fs1/EBSapps/appl/au/12.0.0/perl/TXK/ line 234
        TXK::SQLPLUS::execute('TXK::SQLPLUS=HASH(0x24f4958)', 'HASH(0x229cd08)') called at /oa01/oradata/fs1/EBSapps/appl/au/12.0.0/perl/TXK/ line 618
        TXK::TechstackDB::_getSQLValue('TXK::TechstackDB=HASH(0x2542af0)', 'SELECT clone_status||\',\' FROM ad_adop_session_patches WHERE...') called at /oa01/oradata/fs1/EBSapps/appl/au/12.0.0/perl/TXK/ line 573
        TXK::TechstackDB::getSQLValue('TXK::TechstackDB=HASH(0x2542af0)', 'SELECT clone_status||\',\' FROM ad_adop_session_patches WHERE...') called at /oa01/oradata/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/ line 3327
        main::getCloneStatus() called at /oa01/oradata/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/ line 1364
        main::checkCloneStatus('STARTED') called at /oa01/oradata/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/ line 5975
        main::startCloneProcess() called at /oa01/oradata/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/ line 2085
        main::createPatchApplTop() called at /oa01/oradata/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/ line 629
    [UNEXPECTED]Error occurred running "perl /oa01/oradata/fs1/EBSapps/appl/ad/12.0.0/patch/115/bin/ -contextfile=/oa01/oradata/fs1/inst/apps/DEV_oraapdev/appl/admin/DEV_oraapdev.xml -patchcontextfile=/oa01/oradata/fs2/inst/apps/DEV_oraapdev/appl/admin/DEV_oraapdev.xml -promptmsg=hide -console=off -mode=create -sessionid=11 -timestamp=20160104_164228 -outdir=/oa01/oradata/fs_ne/EBSapps/log/adop/11/fs_clone_20160104_164228/DEV_oraapdev"

I had aborted the previous session but not run cleanup in full mode. Well lesson learnt but I still needed to somehow move forward with this one and apply the patch. It was not getting the session id from the file. I started digging and made the following updates to get it working. I would not recommend this on PROD but to get things moving along this definitely helped me.

set status = 'C'
where ADOP_SESSION_ID =11;
update  APPLSYS.ad_adop_session_patches
set bug_number = 'CLONE'
where ADOP_SESSION_ID =11;



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…