RC-50004: Fatal: Error occurred in ApplyAppsTier

Error: While running perl adcfgclone.pl appsTier, encountered the following error somewhere near 74% progress..

RC-50004: Fatal: Error occurred in ApplyAppsTier


StackTrace -
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccesso
rImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructo
rAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at
oracle.apps.ad.clone.util.CloneProcessor.run(CloneProcessor.java:67)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NoSuchMethodError:
oracle.apps.ad.autoconfig.InstantiateFile.writeReport(Ljava/util/Vector;Loracl
e/apps/ad/util/LogFile;I)V
at
oracle.apps.ad.clone.ApplyApplTop.checkAutoConfigErr(ApplyApplTop.java:590)
at
oracle.apps.ad.clone.ApplyApplTop.runAutoConfig(ApplyApplTop.java:558)
at oracle.apps.ad.clone.ApplyApplTop.doConf(ApplyApplTop.java:339)
at oracle.apps.ad.clone.ApplyApplTop.doApply(ApplyApplTop.java:382)
at oracle.apps.ad.clone.ApplyApplTop.(ApplyApplTop.java:267)
at oracle.apps.ad.clone.ApplyAppsTier.(ApplyAppsTier.java:105)
... 6 more


ERROR while running Apply...


Troubleshooting tips:

1. Metalink suggested that this is due to mid-tier and db-tier servers not being in the same domain / not entering fully qualified domain name while entering the db host name.
2. The above suggestion did not help in our case.
3. The following was recorded in "$INST_TOP/admin/logApplyAppsTier_06170114.log"

DECLARE
*
ERROR at line 1:
ORA-02019: connection description for remote database not found
ORA-06512: at "XXXX_DBLINKADM.CHK_DBLNK_CREATION", line 156
ORA-06512: at line 2
ORA-06512: at "SYS.DBMS_SYS_SQL", line 909
ORA-06512: at "SYS.DBMS_SQL", line 39
ORA-06512: at line 33


Error encountered while running $INST_TOP/admin/install/bisdblrp.sql
ERRORCODE = 256 ERRORCODE_END
.end std out.


Solution:

Actually, we have a custom solution comprising of database triggers that are meant to prevent creation of db links from production to non-production and vice-versa.One of the checks this custom solution does is to validate if the source and target databases are indeed non-prod. In this case, it turned out that since I was creating a new environment, the new environment information was not available in the repository. By the way, bisdblrp.sql creates EDW_APPS_TO_WH db link in which case,
the source and target db name will be the same (the target instance for which rapid clone is being run). This custom trigger was preventing the creation the db link
due to which autoconfig was reporting an error which in turn was reported by Rapid Clone as mentioned above.

So, the solution is to ensure that bisdblpr.sql successfully creates the db link.

-Aravind Kamath Posral