WebLogic Server Not Starting in OBIEE 11g

While you were trying to start the WebLogic Server, it shutdown and you are getting the below error message in the nohup.out file.
__________________________________
<Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Could not obtain an exclusive lock to the embedded LDAP data files directory: /Middleware/user_projects/domains/bifoundation_domain/servers/AdminServer/data/ldap/ldapfiles because another WebLogic Server is already using this directory. Ensure that the first WebLogic Server is completely shutdown and restart the server.>
<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
__________________________________

Remove EmbeddedLDAP.lok file in the following directory
/opt/app/obi/Middleware/user_projects/domains/bifoundation_domain/servers/bi_server1/data/ldap/ldapfiles

Now, navigate to the following directory and execute the find command as in below.

/opt/app/obi/Middleware/user_projects/domains/bifoundation_domain
bifoundation_domain]$ find . -name "*DAT"
./servers/bi_server1/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
./servers/bi_server1/data/store/default/_WLS_BI_SERVER1000000.DAT
./servers/AdminServer/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT
./servers/AdminServer/data/store/default/_WLS_ADMINSERVER000000.DAT

Navigate to those directories and remove the files.

Reason for the above error. If you have used "KILL -9" command to kill any of the servers before you did the starting.

Unable to Sign into OBIEE 11g Analytics

More often, we will encounter this issue. Unable to Log into Analytics... That's the most annoying error and that too when it happens in the Production environment.. As an OBIEE admin, you have to be on your toes...

The above is a very generic issue and there are various factors that contribute to this issue.. You need to get to the core to get your issues resolved.. Remember - "One Size Does Not Fit All!"

I am planning to capture all the errors that is causing issue...

Syntax error in NQSConfig.ini file - Click here to read about the same.