OBIEE 11g Manged Server Does Not Start After Database Crash (Doc ID 2040714.1)

Last updated on OCTOBER 15, 2015

Applies to:

Business Intelligence Server Enterprise Edition - Version and later
Information in this document applies to any platform.


The OBIEE 11g was  running fine. The other night the database crashed and during this time, the services on the app server were restarted. When the restart happened, the services on managed server didn't start. There are no changes to database. The database crashed due to memory spike issue. Verified the database is up and running and verified that the RCU schemas are not locked.

Adminserver & Node manager start fine, but then when starting the managed server, it is in Admin status. After login to WLS console, tried to resume the managed server, and then the managed server can be started and run.

In the bi_server1.log, you found the error message as:
 <Warning> <oracle.wsm.resources.policymanager> <WSM-02312> <Failed to store resource usage information to underlying error "java.rmi.AccessException: [EJB:010160]Security Violation: User: 'OracleSystemUser' has insufficient permission to access EJB: type=<ejb>, application=wsm-pm, module=wsm-pmserver-wls.jar, ejb=UsageTracker, method=recordUsage, methodInterface=Remote, signature={java.lang.String,java.util.Map,java.util.Set}.". The operation will be retried.>

 <Info> <Deployer> <obiaappprod1.ussl.uhs> <bi_server1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KtkRCDQD4iG_yxw0yW1LbSs1000003> <1436405294911> <BEA-149059> <Module wsm-pmserver-wls.jar of application wsm-pm is transitioning from STATE_PREPARED to STATE_ADMIN on server bi_server1.>



Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms