@OracleIMC Partner Resources & Training: Discover your Modernization options + Reach new potential through Innovation

Error Solving: Oracle WebLogic Server does not start after domain creation

Guest Author

During my
last WebLogic workshop, one of the participants encountered with the issue that
after installation of WebLogic binaries and creation of the simplest domain configuration
(only with Admin Server) from scratch, during the attempt of the first launch
of AdminServer it does not start after domain creation and 
it throws the following error exception: «A failure occurred attempting to load LDIF for provider…».

See bellow the log:

####<Mar 19, 2015 5:19:19 PM MSK> <Error>
<Security> <Unknown> <AdminServer> <[ACTIVE]
ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'>
<<WLS Kernel>> <> <> <1426771159618>
<BEA-090870> <The realm "myrealm" failed to be loaded:
weblogic.security.spi.ProviderInitializationException: A failure occurred
attempting to load LDIF for provider Authorizer from file

At the
first glance the problem is related to RDBMS security store. The possible
solution could be executing
rdbms_security_store_oracle.sql script which is placed under $WL_HOME/server/lib directory. But not in my case, as I
did not use RDBMS security store.

solution of my problem was much easier. You just need to check your
/etc/hosts configuration file (in my case I’ve
used OL6 OS) and ensure that you added the line with appropriate machine IP address and hostname as in example below:

~]# cat /etc/hosts ol6u5 ol6u5.ru.oracle.com

After this
action Admin Server was started successfully.

Be happy
with your WebLogic Server Configuration!

Facebook Google+ Twitter LinkedIn Pinterest Delicious Digg Addthis

Join the discussion

Comments ( 2 )
  • Michalis Argyriou Thursday, October 15, 2015

    Confirming that this worked for me. Thank you.

  • guest Thursday, November 10, 2016

    it worked for me too. Thanks

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.