OAC: Unable to Start the Managed Server (bi_server1)
(Doc ID 2521595.1)
Last updated on JULY 11, 2022
Applies to:
Oracle Analytics Cloud - Classic - Version 17.1.3 and laterInformation in this document applies to any platform.
Symptoms
When trying to start the services the process fails, in the <DOMAIN_HOME>/servers/bi_server1/logs/bi_server1.out file this error is seen:
<timestamp> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: A MultiException has 2 exceptions. They are: 1. weblogic.ldap.EmbeddedLDAPException: [EmbeddedLDAP:171525]Error loading initial replica file. Check the EmbeddedLDAP log for more details. 2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.ldap.EmbeddedLDAP A MultiException has 2 exceptions. They are: 1. weblogic.ldap.EmbeddedLDAPException: [EmbeddedLDAP:171525]Error loading initial replica file. Check the EmbeddedLDAP log for more details. 2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.ldap.EmbeddedLDAP at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:392) at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487) at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:305) at org.glassfish.hk2.runlevel.RunLevelContext.findOrCreate(RunLevelContext.java:85) at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2126) Truncated. see log file for complete stacktrace Caused By: weblogic.ldap.EmbeddedLDAPException: [EmbeddedLDAP:171525]Error loading initial replica file. Check the EmbeddedLDAP log for more details. at weblogic.ldap.EmbeddedLDAP.loadInitialReplicaFile(EmbeddedLDAP.java:1030) at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:342) at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:76) at sun.reflect.GeneratedMethodAccessor7.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) Truncated. see log file for complete stacktrace > <timestamp> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED.> <timestamp> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.> <timestamp> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
This only happens on a non-IDCS enabled instance.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |