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

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

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

ErmanArslansOracleBlog
Administrator
Hi Bhaskar,

I analzyed the log files;

here is the situation:

The problem is in "Modifying T2P plan"

You have a null pointer in provision_05301843.log

StackTrace: 
java.lang.NullPointerException
at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.updateModWLSDirectives(UpdateOhsT2PMovePlan.java:812)
at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.updateModWLSConfig(UpdateOhsT2PMovePlan.java:721)
at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.updateModWLSConfig(UpdateOhsT2PMovePlan.java:698)
at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.updateModWLSConfig(UpdateOhsT2PMovePlan.java:698)
at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.processMoveplan(UpdateOhsT2PMovePlan.java:631)
at oracle.apps.fnd.txk.util.UpdateOhsT2PMovePlan.main(UpdateOhsT2PMovePlan.java:1063)


2016-05-31 11:00 GMT+03:00 Bhaskar [via Erman Arslan's Oracle Forum] <[hidden email]>:
Thank you ! We tried the following steps earlier.

1. Renamed inventory.xml to inventory.xml.bkp
2. Removed FMW_Home directory
3. Removed inst directory.
4. From a brand new session(terminal) where nothing has been sourced, navigated to your COMMON_TOP/clone/bin directory
5.Without any env variables, reran adcfgclone.pl appsTier and hit the same error.*****

When we rename fmw_home and inst directories, will it not create them afresh by reading the JAR files already available in clone directory and hit the same issue again ? Will deleting the managed servers have any effect , if we rename the inst,fmwhome and re run the adcfg again ?

Can you provide more details on openport issue that you mentioned ?

Regards,
Bhaskar


To start a new topic under EBS 12.2, email [hidden email]
To unsubscribe from Erman Arslan's Oracle Forum, click here.
NAML



--

Erman Arslan 

Applications and Database Operations Manager


Oracle Certified Expert

Certified Exadata Administrator

Certified Linux Administrator

Author for Apress

MBA


Blog:      ermanarslan.blogspot.com

Forum:  http://ermanarslan.blogspot.com/p/forum.html

 

M: 05301567803

Reply | Threaded
Open this post in threaded view
|

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

Tarun
Has there been any solution to it ?
We are also facing exactly the same issue, and my searches are hitting all the time to this incomplete thread  :).
Reply | Threaded
Open this post in threaded view
|

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

ErmanArslansOracleBlog
Administrator
Hi Tarun,

I guess you don't see the complete thread.

Here is the solution that is shared by the issue owner ->

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 !