diehn.net/blog

We rebooted the computer on which we have OID, OVD installed. When it started up, we noticed the AdminServer wasn’t running. We have our system configured to start Nodemanager which should start the AdminServer.  So when it didn’t, I went to the DOS prompt and used startWeblogic.cmd so I could easily see the output.  Here’s the relevant bit:

<Aug 14, 2012 11:58:27 AM EDT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
Enter username to boot WebLogic server:weblogic
Enter password to boot WebLogic server:
<Aug 14, 2012 11:58:33 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Aug 14, 2012 11:58:33 AM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
Error at line:990 col:27 ' ' expected a valid beginning name character
   at weblogic.xml.babel.scanner.Name.read(Name.java:33)
   at weblogic.xml.babel.scanner.Name.read(Name.java:20)
   at weblogic.xml.babel.scanner.OpenTag.read(OpenTag.java:58)
   at weblogic.xml.babel.scanner.Scanner.startState(Scanner.java:251)
   at weblogic.xml.babel.scanner.Scanner.scan(Scanner.java:178)

There was a whole slew of crud like this, miles and miles of java spew.  I did find this also, though, that helped:

weblogic.security.SecurityInitializationException: The loading of OPSS java security policy provider 
failed due to exception, see the exception stack trace or the server log file for root cause. If 
still see no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. 
Error message: oracle.security.jps.JpsException: [PolicyUtil] Exception while getting default policy Provider

After searching Google for a while, I found myself reading about jazn-data.xml at this post by Kavita (thanks!)  That lead me to search our computer’s file system below C:\Oracle for “jazn-data.xml.”  I found many of them.  I noticed, though, that there were a bunch named system-jazn-data.xml and there was one in C:\Oracle\Middleware\user_projects\domains\ANSYSPROD\config\fmwconfig.  I opened that one and found that it was truncated about halfway down.

Noticing that all the other system-jazn-data.xml files I’d seen in the search results were dated the same and were the same size, I took an chance and copied one of them into place, after backing up the truncated version, and voila!  It worked!