Recently came across an issue in SOA 11g cluster environment related to Plan.xml.
After creating a data source in Weblogic Admin console, when you update the DB adapter from deployments section, at the "Save Deployment Plan Assistant" screen the data gets stored in the Plan.xml (MW_HOME/ORACLE_SOA1/soa/connectors directory). In a SOA 11g Cluster (lets say 2 node env.) this Plan.xml file gets created on both the nodes first time. However any subsequent updates on the adapter like creation of new datasources or updation to existing ones dont get saved to both nodes. Only the Plan.xml on node where admin server runs gets updated.
This would cause datasource errors/missing JNDI name errors when the environment is load balanced and requests are routed to the 2nd node.
This is more of a cluster configuration issue. The Plan.xml should be kept in a location that is shared storage for all cluster nodes. If this hasn't been done while setting up the cluster then every time adapter updation happens, the Plan.xml only gets updated on Admin server node. In that case the solution is to manually copy the Plan.xml from admin server node to other nodes and restart the managed servers.
After creating a data source in Weblogic Admin console, when you update the DB adapter from deployments section, at the "Save Deployment Plan Assistant" screen the data gets stored in the Plan.xml (MW_HOME/ORACLE_SOA1/soa/connectors directory). In a SOA 11g Cluster (lets say 2 node env.) this Plan.xml file gets created on both the nodes first time. However any subsequent updates on the adapter like creation of new datasources or updation to existing ones dont get saved to both nodes. Only the Plan.xml on node where admin server runs gets updated.
This would cause datasource errors/missing JNDI name errors when the environment is load balanced and requests are routed to the 2nd node.
This is more of a cluster configuration issue. The Plan.xml should be kept in a location that is shared storage for all cluster nodes. If this hasn't been done while setting up the cluster then every time adapter updation happens, the Plan.xml only gets updated on Admin server node. In that case the solution is to manually copy the Plan.xml from admin server node to other nodes and restart the managed servers.
Recentely, i have faced same issue.Plan .xml got updated on managed server where Admin Server is running due to whcih soa_infra application stopped coming up. I was not able to start managed serverwhere Admin server was runnnng.
ReplyDeleteFinaaly i have to take back up from other manged server and move that to primary manged server.
Plan.xml has created big disater for me a week back.
It is really true.
ReplyDeleteEven the Oracle docs state this fact (#15): http://docs.oracle.com/cd/E15523_01/doc.1111/e17059/intro.htm