Forum Stats

  • 3,769,708 Users
  • 2,253,013 Discussions
  • 7,875,157 Comments

Discussions

"EPMSystemRegistry" failed with exception: "java.sql.SQLRecoverableException: No more data to read f

User_2E55J
User_2E55J Member Posts: 5 Red Ribbon
edited Oct 24, 2019 7:15AM in EPM System Infrastructure

Dear Everybody,

We are actually installing High Availability Hyperion System in Linux where we have a distributed architecture ( Linux Box 1 & 2: Foundation Components, Calc Manager and FDMEE; Linux Box 3 & 4: Planning and Financial Reporting ; Linux Box 5 & 6 : Essbase Server, EAS and APS).OTD is used as load balance. Its our Production System. Two nodes are there for each components as this is HA.

After installation and Configuration, when I am going to start of both nodes of Linux Box 1 and Linux Box 2, ErpIntegrator1 is getting failed for 2nd only. In First node its running fine.

pastedImage_0.png

Node 1 is started before Node 2. Facing the same issue for node 2 if I start node 2 first and node 1 later.

In Node 1 log(erpIntegrator0) , we are facing below error:

####<Oct 24, 2019 12:45:03 PM AST> <Error> <JDBC> <servername> <ErpIntegrator0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000Mrx9vrHFg42LzqG7yW1Tg0GE0000ks> <1571910303185> <BEA-001112> <Test "select count(*) from SNP_LOC_REP" set up for pool "odiMasterRepository" failed with exception: "java.sql.SQLRecoverableException: No more data to read from socket".>

####<Oct 24, 2019 12:49:03 PM AST> <Error> <JDBC> <servername> <ErpIntegrator0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000MrxAqTHFg42LzqG7yW1Tg0GE0000l0> <1571910543185> <BEA-001112> <Test "select count(*) from SNP_LOC_REP" set up for pool "odiMasterRepository" failed with exception: "java.sql.SQLRecoverableException: No more data to read from socket".>

####<Oct 24, 2019 12:45:03 PM AST> <Error> <JDBC> <servername> <ErpIntegrator0> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000Mrx9voZFg42LzqG7yW1Tg0GE0000kq> <1571910303013> <BEA-001112> <Test "SELECT 1 FROM HSS_COMPONENT_TYPES WHERE 1 = 0" set up for pool "EPMSystemRegistry" failed with exception: "java.sql.SQLRecoverableException: No more data to read from socket".>

In Node 2 log(erpIntegrator1), we are facing below error:

####<Oct 24, 2019 12:58:47 PM AST> <Error> <HTTP> <servername> <ErpIntegrator1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <4920eee3e4313625:6fdf3e24:16dfd3339e6:-8000-0000000000000003> <1571911127499> <BEA-101216> <Servlet: "AgentServlet" failed to preload on startup in Web application: "oraclediagent".

ODI-1400: Agent OracleDIAgent start failure: JDBC connection error occurs while connecting to the master repository.

Caused by: java.security.AccessControlException: access denied (oracle.security.jps.service.credstore.CredentialAccessPermission context=SYSTEM,mapName=oracle.odi.credmap,keyName=SUPERVISOR read)

at oracle.odi.runtime.agent.servlet.AgentServlet.startup(AgentServlet.java:411)

at oracle.odi.runtime.agent.servlet.AgentServlet.init(AgentServlet.java:250)

at javax.servlet.GenericServlet.init(GenericServlet.java:242)

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:1981)

at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)

at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)

at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)

at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)

at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)

at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)

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:201)

at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)

at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)

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:28)

at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:672)

at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)

at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)

at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)

at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)

at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)

at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)

at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)

at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)

at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)

at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)

at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)

at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)

at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)

at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)

at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)

at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)

Caused By: java.security.AccessControlException: access denied (oracle.security.jps.service.credstore.CredentialAccessPermission context=SYSTEM,mapName=oracle.odi.credmap,keyName=SUPERVISOR read)

Although its running fine in node1 and getting in ADMIN state in node 2.

Please suggest.

Thanks & Regards,

Prit

Answers

  • JohnGoodwin
    JohnGoodwin Member Posts: 30,471 Blue Diamond
    edited Oct 24, 2019 7:15AM

    Go to Oracle support, search for "Agent OracleDIAgent start failure: JDBC connection error occurs while connecting to the master repository", Lots of articles to read through.

    Looks like issues with accessing the credential store - "access denied (oracle.security.jps.service.credstore.CredentialAccessPermission context=SYSTEM,mapName=oracle.odi.credmap,keyName=SUPERVISOR read)"

    Cheers

    John

  • JVEJ
    JVEJ Member Posts: 14 Blue Ribbon

    Hi ,

    Could you kindly let us know how you fixed it .

    Thanks,

    Joel