Re: R12.2.4 adcfgclone on taret - unable to delete managed servers, OHS Config errors

Posted by Bhaskar on Jun 01, 2016; 9:16pm
URL: http://erman-arslan-s-oracle-forum.124.s1.nabble.com/R12-2-4-adcfgclone-on-taret-unable-to-delete-managed-servers-OHS-Config-errors-tp1031p1050.html

Hi Erman,

Thank you for the response !

The error was resolved after we removed certain portion of ADF code from moveplan.xml in clone directory.  I sent you the moveplan.xml before and after making changes.(changed host names to dummy names)  Modified the moveplan.xml in clone/FMW/OHS directory and executed adcfgclone for the first time.


<value>/ADF</value>       
<itemMetadata>       
<dataType>STRING</dataType>       
<scope>READ_ONLY</scope>       
</itemMetadata>       
<configProperty>       
<name>WebLogicCluster</name>       
<value>ex-amp-le1.planet.com:7209,ex-amp-le2.planet.com:7209,ex-amp-le1.planet.com:7210,ex-amp-le2.planet.com:7210</value>       
<itemMetadata>       
<dataType>STRING</dataType>       
<scope>READ_WRITE</scope>       
</itemMetadata>       
</configProperty>       
</configProperty>       
<configProperty>       
<name>Location</name>

PS: We have an ADF application deployed in EBS source instance.  This ADF application is deployed on  same managed servers as EBS. Perhaps, this was causing an issue ?

adcfgclone completed successfully and we were able to clone patch FS and bring up services. However, login page was throwing 404 error and we noticed that requests are being redirected to source instance(production). Apparently, some config files like mod_wl_ohs had entries related to source. We resolved the issues by manually deleting managed servers and modifying wl_mos_ohs files.

Issue resolution is still in progress.  We are trying to figure the right approach when ADF is deployed at source EBS instance. If you have any suggestions, please let me know !

Thanks, B