|
| Problem | WebSphereŽ Application Server 3.5.x Repository comprises of 33 different tables. When building the new WebSphere repository for OracleŽ and all the tables are not created, the AdminServer fails to start. In some cases, the WebSphere Application Server repository's owner schema (EJSADMIN) has less than 33 tables created and the tracefile in the WAS_ROOT/logs directory has the following error stack:
[01.09.04 10:28:10:035 GMT+02:00] a4d01c0d AdminServer A ADMS0002I: Initializing WebSphere Administration server
[01.09.04 10:28:10:040 GMT+02:00] 36731c08 DrAdminServer A SMTL0018I: DrAdmin available on port 32 871
[01.09.04 10:28:16:259 GMT+02:00] a4d01c0d ActiveEnterpr W Failed to start the bean "TypeHome" javax.naming.NamingException: Error during resolve. Root exception is org.omg.CORBA.portable.UnknownException: minor code: 0 completed: Maybe
at com.ibm.ejs.ns.CosNaming.NsSessionDataStore.resolve(NsSessionDataStore.java:94)
at com.ibm.ejs.ns.CosNaming.NamingContextImpl.resolve(NamingContextImpl.java:313)
at com.ibm.ejs.ns.jndi.CNContextImpl.doLookup(CNContextImpl.java:744)
at com.ibm.ejs.ns.jndi.CNContextImpl.lookup(CNContextImpl.java:563)
at javax.naming.InitialContext.lookup(InitialContext.java:356)
at com.ibm.ejs.sm.active.ActiveEJBContainer.rebindHome(ActiveEJBContainer.java:630)
at com.ibm.ejs.sm.active.ActiveEJBContainer.startBean(ActiveEJBContainer.java:564)
at com.ibm.ejs.sm.active.ActiveEnterpriseBean.startAction(ActiveEnterpriseBean.java:55)
at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:682)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at com.ibm.ejs.sm.active.ActiveObject.operateOnContainedObjects(ActiveObject.java:584)
at com.ibm.ejs.sm.active.ActiveEJBContainer.startAction(ActiveEJBContainer.java:380)
at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:682)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at com.ibm.ejs.sm.active.ActiveObject.operateOnContainedObjects(ActiveObject.java:584)
at com.ibm.ejs.sm.active.ActiveEJBServer.startAction(ActiveEJBServer.java:96)
at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:682)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java(Compiled Code))
at com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java(Compiled Code))
at com.ibm.ejs.sm.server.AdminServer.startContainers(AdminServer.java(Compiled Code))
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:1090)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:365)
----- Begin backtrace for rootCause
org.omg.CORBA.portable.UnknownException: minor code: 0 completed: Maybe
at com.ibm.ejs.ns.CosNaming.NsSessionDataStore.resolve(NsSessionDataStore.java:94)
at com.ibm.ejs.ns.CosNaming.NamingContextImpl.resolve(NamingContextImpl.java:313)
at com.ibm.ejs.ns.jndi.CNContextImpl.doLookup(CNContextImpl.java:744)
at com.ibm.ejs.ns.jndi.CNContextImpl.lookup(CNContextImpl.java:563)
at javax.naming.InitialContext.lookup(InitialContext.java:356)
at com.ibm.ejs.sm.active.ActiveEJBContainer.rebindHome(ActiveEJBContainer.java:630)
at com.ibm.ejs.sm.active.ActiveEJBContainer.startBean(ActiveEJBContainer.java:564)
at com.ibm.ejs.sm.active.ActiveEnterpriseBean.startAction(ActiveEnterpriseBean.java:55)
at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:682)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at com.ibm.ejs.sm.active.ActiveObject.operateOnContainedObjects(ActiveObject.java:584)
at com.ibm.ejs.sm.active.ActiveEJBContainer.startAction(ActiveEJBContainer.java:380)
at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:682)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at com.ibm.ejs.sm.active.ActiveObject.operateOnContainedObjects(ActiveObject.java:584)
at com.ibm.ejs.sm.active.ActiveEJBServer.startAction(ActiveEJBServer.java:96)
at com.ibm.ejs.sm.active.ActiveObject.startObject(ActiveObject.java:682)
at com.ibm.ejs.sm.active.ActiveObject.start(ActiveObject.java:117)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ejs.sm.agent.AdminAgentImpl.activeObjectInvocation(AdminAgentImpl.java(Compiled Code))
at com.ibm.ejs.sm.agent.AdminAgentImpl.invokeActiveObject(AdminAgentImpl.java(Compiled Code))
at com.ibm.ejs.sm.server.AdminServer.startContainers(AdminServer.java(Compiled Code))
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:1090)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:365)
In WebSphere 4.0.x, this problem has also been reported as a "Network Adapter Unable to Establish Connection" to an Oracle database, as well as other database connection exceptions. | | | | Solution | The dbSchema attribute in the admin.config doesn't have the period at the end, for example,com.ibm.ejs.sm.adminServer.dbSchema=EJSADMIN It should be:
com.ibm.ejs.sm.adminServer.dbSchema=EJSADMIN. Type a period after the schema name EJSADMIN. | |
| |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Administrative Console (all non-scripting) Operating system(s): Multi-Platform Software version: 3.5, 4.0 Software edition: Standard, Advanced Reference #: 1055393 IBM Group: Software Group Modified date: 2004-08-30
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|