Team,
OEM 13C has been running fine on a Linux server for sometime. Process suddenly died one fine morning. when attempting to start,
./emctl start oms
we get the following error: Appreciate if anyone has come across it.
<Dec 18, 2017 2:39:33 PM PST> <Info> <Management> <BEA-141298> <Could not register with the Administration Server: java.rmi.RemoteException: [Deployer:149147]Could not reach the Administration Server through any
of its URLs: "https://xx.xx.xxx.xxx:yyyy".>
<Dec 18, 2017 2:39:33 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 12.1.3.0.0 Wed May 21 18:53:34 PDT 2014 1604337 >
<Dec 18, 2017 2:40:16 PM PST> <Alert> <Management> <BEA-141151> <The Administration Server could not be reached at https://oms01.sj.tivo.com:7102.>
<Dec 18, 2017 2:40:17 PM PST> <Info> <Configuration Management> <BEA-150018> <This server is being started in Managed Server independence mode in the absence of the Administration Server.>
<Dec 18, 2017 2:40:17 PM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING.>
<Dec 18, 2017 2:40:17 PM PST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool.>
<Dec 18, 2017 2:40:18 PM PST> <Info> <WorkManager> <BEA-002942> <CMM memory level becomes 0. Setting standby thread pool size to 256.>
<Dec 18, 2017 2:40:26 PM PST> <Error> <Security> <BEA-090892> <The loading of an OPSS java security policy provider failed due to an exception. See the exception stack trace or the server log file for the root c
ause. If there is no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle/security/jps/az/internal/runtime/provider/PDPServiceProvider>
<Dec 18, 2017 2:40:38 PM PST> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: A MultiException has 10 exceptions. They are:
1. weblogic.security.SecurityInitializationException: The loading of an OPSS java security policy provider failed due to an exception. See the exception stack trace or the server log file for the root cause. If
there is no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: oracle/security/jps/az/internal/runtime/provider/PDPServiceProvider
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.security.PreSecurityService
3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.security.SecurityService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.security.SecurityService
5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.jndi.internal.RemoteNamingService errors were found
6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.jndi.internal.RemoteNamingService
7. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.management.mbeanservers.runtime.internal.RuntimeServerService errors were found
8. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.management.mbeanservers.runtime.internal.RuntimeServerService
9. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.cacheprovider.CacheProviderServerService errors were found
10. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.cacheprovider.CacheProviderServerService