Welcome to my blog...

Hello

I created this blog to share my minimal knowledge with others on the issues I came across, the POC's I did, Installations & Configurations I did on Oracle Fusion Middleware, OBIEE and Oracle Primavera Applications.
LinkedIn: https://in.linkedin.com/pub/vinoth-kumar-subramani/18/260/7b9

Technical Issues and Solutions

Tuesday, June 2, 2015

Not able to bring up the Weblogic Admin server - [Store:280105]The persistent file store "WLS_DIAGNOSTICS" cannot open file WLS_DIAGNOSTICS000000.DAT.


If you are not able to bring up the Weblogic Server and it throws the below exception, follow the given solution.

No matching store mbean found for =WLS_DIAGNOSTICS, must be a default store.
<Jun 2, 2015 12:51:43 PM SAST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:

There are 1 nested errors:

weblogic.diagnostics.lifecycle.DiagnosticComponentLifecycleException: weblogic.store.PersistentStoreFatalException: [Store:280105]The persistent file store "WLS_DIAGNOSTICS" cannot open file WLS_DIAGNOSTICS000000.DAT.
        at weblogic.diagnostics.lifecycle.ArchiveLifecycleImpl.initialize(ArchiveLifecycleImpl.java:97)
        at weblogic.diagnostics.lifecycle.DiagnosticFoundationService.start(DiagnosticFoundationService.java:108)
        at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)
Caused by: weblogic.store.PersistentStoreFatalException: [Store:280105]The persistent file store "WLS_DIAGNOSTICS" cannot open file WLS_DIAGNOSTICS000000.DAT

<Jun 2, 2015 12:51:43 PM SAST> <Critical> <Health> <BEA-310006> <Critical subsystem PersistentStore.WLS_DIAGNOSTICS has failed. Setting server state to FAILED.
Reason: weblogic.store.PersistentStoreFatalException: [Store:280105]The persistent file store "WLS_DIAGNOSTICS" cannot open file WLS_DIAGNOSTICS000000.DAT.>
***************************************************************************
The WebLogic Server encountered a critical failure
Reason: Assertion violated
***************************************************************************
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize class weblogic.protocol.ServerIdentityManager$Initializer


Solution:

  1. Go to DOMAIN_HOME/servers/<SERVERNAME>/data/ldap/ldapfiles and remove the EmbeddedLDAP.lok lock file
  2. Delete the *.dat file under  DOMAIN_HOME/servers/<SERVERNAME>/data /store/default and DOMAIN_HOME/servers/<SERVERNAME>/data /store/diagnostics/
  3. Remove the contents under  DOMAIN_HOME/servers/<SERVERNAME>/ tmp and DOMAIN_HOME/servers/<SERVERNAME>/ cache
  4. Now start the server


Posted by at
Labels:

29 comments:

  1. Vishal BansodOctober 1, 2015 at 12:44 PM

    Thanks buddy for this post. It really saved me :-)

    ReplyDelete
  2. UnknownFebruary 9, 2016 at 4:09 PM

    Thanks a lot :-)

    ReplyDelete
  3. UnknownJanuary 25, 2017 at 2:43 PM

    ThankS Lot Dude.. :)

    ReplyDelete
  4. AnonymousMarch 27, 2017 at 9:30 PM

    Thank you!

    ReplyDelete
  5. UnknownApril 5, 2017 at 7:46 PM

    Thanks a lot Vinoth !

    ReplyDelete
  6. AnonymousMay 15, 2017 at 7:23 PM

    Thanks dude

    ReplyDelete
  7. ZakJuly 11, 2017 at 9:03 PM

    do you know if there is a way to turn off this .

    ReplyDelete
  8. AnonymousAugust 16, 2017 at 3:13 PM

    Thanks this works with WLS 12.2.1 as well

    ReplyDelete
  9. UnknownOctober 10, 2017 at 7:47 AM

    thank you a lot.

    ReplyDelete
  10. Test BlogNovember 9, 2017 at 1:23 PM

    thanks, it worked.

    ReplyDelete
  11. Satish MaleNovember 9, 2017 at 7:37 PM

    Thanks a Lot.

    ReplyDelete
  12. UnknownMarch 5, 2018 at 7:54 PM

    Thanks a ton !! helped to bring up prod

    ReplyDelete
  13. UnknownMarch 19, 2018 at 11:15 PM

    Thanks man, very helpful

    ReplyDelete
  14. UnknownApril 23, 2018 at 6:19 PM

    I already tried this but I'm still having the same error :(

    ReplyDelete
  15. AnonymousMay 25, 2018 at 8:28 PM

    Thank you so much for the information!!!

    ReplyDelete
  16. AnonymousJune 13, 2018 at 1:27 PM

    Thanks a lot buddy!

    ReplyDelete
  17. UnknownJuly 2, 2018 at 11:34 AM

    It says some port is in use already....same ipaddress but different port numbers

    ReplyDelete
  18. AnonymousJuly 27, 2018 at 7:04 PM

    Thank You Vinoth.

    ReplyDelete
  19. AnonymousSeptember 17, 2018 at 7:05 AM

    Thanks a lot, it's really helpful!

    ReplyDelete
  20. LuzApril 26, 2019 at 10:12 PM

    excelente muchas gracias!

    ReplyDelete
  21. MikeJuly 22, 2019 at 8:14 PM

    In our case it was a missing DNS entry for the soa node that cause this error.

    Ran nslookup on the ip address of the node and no dns entry was found. I would start here before deleting any files etc

    ReplyDelete
  22. Serdar KuzucuAugust 7, 2019 at 6:52 PM

    God bless you, it works :)

    ReplyDelete
  23. ChristopherSeptember 10, 2019 at 1:35 AM

    great!

    ReplyDelete
  24. AnonymousSeptember 18, 2019 at 12:18 AM

    Exactly what i needed!

    ReplyDelete
  25. PriyaFebruary 3, 2020 at 6:26 PM

    Thanks a lot!! It helped

    ReplyDelete
  26. Pravesh ChoureyJuly 2, 2020 at 4:00 PM

    Thanks man...you saved the day. it worked

    ReplyDelete
  27. LeugiDecember 8, 2020 at 3:58 PM

    Thanks, you saved my day !

    ReplyDelete
  28. UnknownAugust 20, 2021 at 10:12 AM

    Thanks heaps! We tried everything else but your solution worked very well.

    ReplyDelete
  29. UnknownJanuary 13, 2022 at 12:55 PM

    Thanks man...you saved the day. it worked

    ReplyDelete

Subscribe to: Post Comments (Atom)