RC-50013: Fatal: Failed to instantiate driver regclone.drv on R12.2.4

R12 Cloning 'adcfgclone.pl appsTier' fails with error RC-50013: Fatal: Failed to instantiate driver .../regclone.drv (Doc ID 725995.1)

Log file detailed:-
AutoConfig is exiting with status 1

ERROR: RC-50013: Fatal: Instantiate driver did not complete successfully.
/u02/apps/fs1/EBSapps/10.1.2/appsutil/driver/regclone.drv

ERROR: RC-50004: Fatal: Error occurred in ApplyAppsTechStack:


RC-50013: Fatal: Failed to instantiate driver /u02/apps/fs1/EBSapps/10.1.2/appsutil/driver/regclone.drv

APPLIES TO:

Oracle Applications Manager - Version 12.0.6 to 12.1.3 [Release 12 to 12.1]
IBM AIX on POWER Systems (64-bit)
HP-UX Itanium (32-bit)
***Checked for relevance on 10-Dec-2013*** 

SYMPTOMS

When attempting to clone using "perl adcfgclone.pl appsTier"
The following error occurs:

...
  /      3% completed       RC-50004: Fatal: Error occurred in ApplyAppsTechStack:
RC-50013: Fatal: Failed to instantiate driver <10.1.2 ORACLE_HOME>/appsutil/driver/regclone.drv

ERROR while running Apply...
<Date Time>

 ERROR: Failed to execute <$COMMON_TOP>/clone/bin/adclone.pl
...

In the logfile $INST_TOP/admin/log/ApplyAppsTier_<DATE_TIME>.log following details are reported :

...

script returned:
****************************************************
Timed out( 3750000 ): Interrupted Exception

Beginning OUI CLI cloning for s_tools_oh <Date Time>
<10.1.3 ORACLE_HOME>/jdk/bin/java -classpath <COMMON_TOP>/clone/jlib/java:<10.1.2 ORACLE_HOME>/oui/jlib/OraInstaller.jar:<COMMON_TOP>/clone/jlib/xmlparserv2.jar:<COMMON_TOP>/clone/jlib/ojdbc14.jar  oracle.apps.ad.clone.util.OracleHomeCloner  -OUICLI -e  <INST_TOP>/appl/admin/<CONTEXT_NAME>.xml -nolink -oaVar s_tools_oh -homestub tools -log <INST_TOP>/admin/log/ohclone.log
running OUI CLI home cloning:
<10.1.2 ORACLE_HOME>/oui/bin/runInstaller -debug -clone -silent -force -nolink -waitForCompletion -invPtrLoc /var/opt/oracle/oraInst.loc session:ORACLE_HOME=/<10.1.2 ORACLE_HOME> oracle.as.j2ee.top:s_asInstanceName=<SID>_TOOLS__apps_oracle_apps_tech_st_10_1_2 oracle.as.j2ee.top:s_adminName=ias_admin oracle.as.j2ee.top:s_adminPassword=welcome ORACLE_HOME_NAME=<SID>_TOOLS__apps_oracle_apps_tech_st_10_1_2 -J-Doracle.installer.noLink=true

...

CAUSE

During the Configuration of the APPS-Tier Technology Stack the opmn process tries to stop the Services. As opmn is not used in this case for the 10.1.2 ORACLE_HOME it should not have been started. The OUI (Oracle Universal Installer) is waiting for a failure or error of the opmn, which is not happening. As a result the OUI Cloning process is failing with a timeout, without touching the Technology Stack.

This issue is reported in unpublished Bug 5697740 - 'OPMN START FAILED DURING OH10.1.2 CLONING.'

SOLUTION

To implement the solution/workaround, please execute the following steps :

Workaround 1 :
1. Start the adcfgclone again :
1. Start the adcfgclone again :
2. When it appears to hang again, check if opmn processes have been started :
ps -ef | grep opmn
If following result is presented, please follow next steps :
<user> <PID> 28462  0 <Time> pts/ta   0:00 <10.1.2 ORACLE_HOME>/opmn/bin/opmn -a -q ping
<user> <PID> 28459  0 <Time> pts/ta   0:00 <10.1.2 ORACLE_HOME>/opmn/bin/opmnctl stopall
<user> <PID> 28459  0 <Time> pts/ta   0:00 <10.1.2 ORACLE_HOME>/opmn/bin/opmnctl status

3. Kill the "opmn -a -q ping" and the "opmnctl stopall" using the PID's presented in step 2 :
3.1 kill -9 <PID of opmn -a -q ping>
3.2 kill -9 <PID of opmnctl stopall>
3.3 kill -9 <PID of opmnctl status>

The clone should continue now, in case it appears to hang again check if the opmn processes are started again and kill them until the clone continues.


Workaround 2:
1 - cat <10.1.2 ORACLE_HOME>/opmn/conf/opmn.xml | grep remote (and write down the remote number)

2 - edit <10.1.2 ORACLE_HOME>/opmn/conf/ons.conf

Change :

nodes=ap6004bld.us.oracle.com:15007

Into:

nodes=<AppsTier Hostname>:<Remote port number from 1>

3 - execute perl  adcfgclone.pl appsTier again

No comments:

SHRD0014: GLLEZL - process exiting with failure

  SYMPTOMS Journal Import completes with the following error: Error ------ ORA-01653 : unable to extend table GL.GL_IMPORT_REFERENCES ORA-01...