Unable to set the activation state to true for the application JDBC Data Source-rac8

Scenario:

One of the ManagedServer was going to Admin State whenever it was tried to start. From the log files it was clear that it is due to some kind of corruption/wrong configuration with one of the eight data sources.

"<Jul 31, 2013 6:30:29 AM PDT> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'ManServer1 JDBC Data Source-rac8'.
weblogic.application.ModuleException: at weblogic.jdbc.module.JDBCModule.activate(JDBCModule.java:388) at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227) at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:541) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:175)
        Truncated. see log file for complete stacktrace
Caused By: weblogic.common.ResourceException: Failed to bind remote object (ClusterableRemoteRef(7480293907351086147S:host02.mydomain:base_domain:ManServ1 null)/297    [weblogic.jdbc.common.internal.RemoteDataSource]) to replica aware stub at ManServ1-rac7(ClusterableRemoteRef(7480293907351086147S:host02.mydomain:base_domain:ManServ1 [7480293907351086147S:host02.mydomain:bas_domain:ManServ1/296])/296        [weblogic.jdbc.common.internal.RemoteDataSource])"


Reason:

Permission issue with a jdbc config file for one of the data sources. During startup weblogic was unable to read the respective configuration file from $DOMAIN_HOME/config/jdbc location. Because of that during startup of the managed server it got updated to a different JNDI Name ( This we can see from Weblogic console page => Services => DataSources => Check for the failing data source name and its respective JNDI Name).


Solution:


Update the JNDI Name in the console and activate changes.

Then change the ownership of the corresponding .xml file in $DOMAIN_HOME/config/jdbc to the WLS S/W owner.

Stop the managed Server which is in Admin state and restart it.

It should be back to Running mode now