Announcement

Collapse
No announcement yet.

OAS not starting after OTM is installed

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • OAS not starting after OTM is installed

    Hi All,

    We have installed OTM on a Windows 2003 server platform.When we tried to start it the tomcat didnot start throwing error1067.We checked the OAS console.logs to find the following errors.

    INFO | jvm 1 | 2008/01/14 11:46:55 | 08/01/14 11:46:55 Fatal Error: Realm Initialization failed!!
    INFO | jvm 1 | 2008/01/14 11:46:55 | 08/01/14 11:46:55 Shutting down OC4J...
    INFO | jvm 1 | 2008/01/14 11:46:55 | [Full GC
    INFO | jvm 1 | 2008/01/14 11:46:56 | 87764K->23493K(1023424K), 0.5586558 secs]
    INFO | jvm 1 | 2008/01/14 11:46:58 | 08/01/14 11:46:58 Error: Unable to find java:comp/ServerAdministrator: java:comp/ServerAdministrator not found
    ERROR | wrapper | 2008/01/14 11:48:59 | Shutdown failed: Timed out waiting for signal from JVM.
    ERROR | wrapper | 2008/01/14 11:48:59 | JVM did not exit on request, terminated
    STATUS | wrapper | 2008/01/14 11:49:00 | <-- Wrapper Stopped

    So we concluded that there are some errors with the OAS which needs to be running smoothly before Tomcat can start.Can anybody tell us whats the problem and how to fix it up.

    regards
    Soumya.

  • #2
    Re: Tomcat not starting after OTM is installed

    The key part of your error appears to be the following:

    INFO | jvm 1 | 2008/01/14 11:46:55 | 08/01/14 11:46:55 Fatal Error: Realm Initialization failed!!

    This indicates that OAS is unable to initialize your Security realm. This can be caused by any of the following:
    • Your OTM DB is not configured correctly -- this could be a problem with the import or post-import scripts. I'd recommend going back to the DB setup section of the OTM Administration guide and running the verification scripts.
    • Your OTM DB is not running -- check to ensure that the DB is up, that the listener is running and that you can connect to it via sqlplus from the OTM App server.
    • Your OTM App server is mis-configured and not able to connect to the DB -- check the DB settings in the glog.properties file ($OTM_HOME/glog/config/glog.properties).

    --Chris

    Comment

    Working...
    X