This discussion is archived
2 Replies Latest reply: Feb 11, 2013 9:54 PM by AkshayS90 RSS

OBIEE wsm-pm service (AdminServer) failed to start

AkshayS90 Newbie
Currently Being Moderated
Hi All,

I have OBIEE 11g, for which earlier database was locally installed.
Now database is uninstalled from same machine and BI repository associated with installation is gone
Now I have installed BI schemas (i.e. DEV_BIPLATFORM, DEV_MDS ) on different server and Managed to start Oracle_RTD and bipublisher service by changing database connection string in files on path /Middleware/user_projects/domains/bifoundation_domain/config/jdbc

After doing so my localhost:9704/analytics page is opening and working
But now wsm-pm application deployed for Admin_server is down as per localhost:7001/em

log when i try to restart application is as follows:

Invoking Start Up operation for application wsm-pm on target AdminServer.
[Deployer:149192]Operation 'start' on application 'wsm-pm' is in progress on 'AdminServer'
[Deployer:149193]Operation 'start' on application 'wsm-pm' has failed on 'AdminServer'
[Deployer:149034]An exception occurred for task [Deployer:149026]start application wsm-pm on AdminServer.: [HTTP:101216]Servlet: "PolicyManagerValidator" failed to preload on startup in Web application: "/wsm-pm".
oracle.adf.share.ADFShareException: MDSConfigurationException encountered in parseADFConfiguration
     at oracle.adf.share.config.ADFMDSConfig.parseADFConfiguration(ADFMDSConfig.java:180)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at oracle.adf.share.config.ADFConfigImpl.getResultFromComponent(ADFConfigImpl.java:497)
     at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.java:568)
     at oracle.adf.share.config.ADFConfigImpl.getConfigObject(ADFConfigImpl.java:546)
     at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.java:611)
     at oracle.adf.share.config.ADFConfigImpl.getMDSInstance(ADFConfigImpl.java:606)
     at oracle.adf.share.config.ADFContextMDSConfigHelperImpl.getMDSInstance(ADFContextMDSConfigHelperImpl.java:277)
     at oracle.adf.share.ADFContext.getMDSInstanceAsObject(ADFContext.java:1674)
     at oracle.wsm.repository.mds.MDSInstanceFactory.getMDSInstance(MDSInstanceFactory.java:98)
     at oracle.wsm.policymanager.bean.AbstractBean.getRepository(AbstractBean.java:350)
     at oracle.wsm.policymanager.bean.AbstractBean.createSession(AbstractBean.java:233)
     at oracle.wsm.policymanager.bean.UpgradeManagerBean.seedWSMPolicyRepository(UpgradeManagerBean.java:588)
     at oracle.wsm.policymanager.web.PolicyManagerValidator.init(PolicyManagerValidator.java:113)
     at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
     at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
     at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
     at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
     at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
     at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
     at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.java:140)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
     at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused by: oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
MDS-01377: Unable to get database connection from data source configured with JNDI name "jdbc/mds/owsm".
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: The Network Adapter could not establish the connection

     at oracle.mds.config.PConfig.loadFromBean(PConfig.java:959)
     at oracle.mds.config.PConfig.<init>(PConfig.java:758)
     at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:787)
     at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:848)
     at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:491)
     at oracle.mds.core.MDSInstance.getMDSConfigFromDocument(MDSInstance.java:2690)
     at oracle.mds.core.MDSInstance.findAndStoreMDSInstanceWithCustConfig(MDSInstance.java:2523)
     at oracle.mds.core.MDSInstance.getOrCreateInstanceInternal(MDSInstance.java:2031)
     at oracle.mds.core.MDSInstance.getOrCreateInstance(MDSInstance.java:740)
     at oracle.adf.share.config.ADFMDSConfig.parseADFConfiguration(ADFMDSConfig.java:139)
     ... 59 more
Caused by: oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
MDS-01377: Unable to get database connection from data source configured with JNDI name "jdbc/mds/owsm".
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: The Network Adapter could not establish the connection

     at oracle.mds.config.PConfig.loadFromBean(PConfig.java:953)
     ... 68 more
:oracle.mds.exception.MDSExceptionList:MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
MDS-01377: Unable to get database connection from data source configured with JNDI name "jdbc/mds/owsm".
weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: The Network Adapter could not establish the connection
.
Operation Start Up on target wsm-pm Failed. Please see error logs for details.

wsm-pm application is running for bi_server1 instance

in localhost:7000/console >services> data sources> mds-owsm> testing ... Admin server deployment testing is failed with connectioon and bi_server1 connection is successful..
please suggest to make connection successful... :)

thank you in advance
  • 1. Re: OBIEE wsm-pm service (AdminServer) failed to start
    987709 Newbie
    Currently Being Moderated
    Hi,

    Please check following url.

    Unable to Sign In _  wsm-pm [AdminServer] down

    it will help you.

    Thank you,
    Nitin
  • 2. Re: OBIEE wsm-pm service (AdminServer) failed to start
    AkshayS90 Newbie
    Currently Being Moderated
    Hi All,

    The main problem lies in database connection and credentials in scheduler service in coreapplication page of host:port/em page

    for resolving problem do the following steps:

    1. Check dattabase coonection properties in XML files at following path
    /Middleware/user_projects/domain/bifoundation_domain/config/jdbc

    2. Check DB connection string and credentials in localhost:7001/em page > coreapplication > Deployment > scheduler page

    for oracle DB:
    Database: Oracle 11g
    Call interface : Oracle 10g R1/R2
    Datasource: (DESCRIPTION =(ADDRESS_LIST =(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521)))(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = orcl)))
    Username: DEV_BIPLATFORM
    Password: _________

    3. Restart Server
    4. Start BI using Stat > Oracle Business Intelligence > Start BI service

    Ideally All the services should come up if database credentials are correct!!! :)

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points