WAS startup fails and DB2 dies!
Mike
Just installed WAS 3.5 and DB2 UDB 7.2 on SuSE 7.0 running on a s/390.
Install went fine and I can successfully start the DB2 admin server and DB2,
but when I start WAS w/ the scrip I get this in the tracefile:
[01.11.01 11:42:47:935 MST] eebc08b2 CreateNsTable W Failed to create tables
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1224N A database agent
could not be started to service a request, or was terminated as a result of
a database system shutdown or a force command. SQLSTATE=55032
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGe
nerator.java:174)
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLExceptionGen
erator.java:431)
at COM.ibm.db2.jdbc.app.DB2Connection.connect(DB2Connection.java:432)
at COM.ibm.db2.jdbc.app.DB2Connection.<init>(DB2Connection.java:335)
at COM.ibm.db2.jdbc.app.DB2Driver.connect(DB2Driver.java:353)
at
com.ibm.ejs.cm.pool.JDBC1xConnectionFactory.createConnection(JDBC1xConnectio
nFactory.java:32)
at
com.ibm.ejs.cm.pool.ConnectionPool.createConnection(ConnectionPool.java:647)
at
com.ibm.ejs.cm.pool.ConnectionPool.createOrWaitForConnection(ConnectionPool.
java:600)
at
com.ibm.ejs.cm.pool.ConnectionPool.findFreeConnection(ConnectionPool.java:53
1)
at
com.ibm.ejs.cm.pool.ConnectionPool.findConnectionForTx(ConnectionPool.java:4
77)
at
com.ibm.ejs.cm.pool.ConnectionPool.allocateConnection(ConnectionPool.java:42
0)
at
com.ibm.ejs.cm.pool.ConnectionPool.getConnection(ConnectionPool.java:169)
at com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:113)
at com.ibm.ejs.cm.SMDataSource.getConnection(SMDataSource.java:83)
at com.ibm.ejs.ns.CosNaming.CreateNsTables.dbInit(CreateNsTables.java:135)
at com.ibm.ejs.ns.CosNaming.NameServer.init(NameServer.java:276)
at
com.ibm.ejs.sm.server.ManagedServer.initializeNameService(ManagedServer.java
:931)
at
com.ibm.ejs.sm.server.ManagedServer.initializeRuntime(ManagedServer.java:528
)
at
com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:969)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
[01.11.01 11:42:50:012 MST] eebc08b2 AdminServer A Initializing WebSphere
Administration server
[01.11.01 11:42:50:025 MST] eb8688b2 DrAdminServer A DrAdmin available on
port 1,116
[01.11.01 11:42:51:724 MST] eebc08b2 DBMgr F Failed to create a data
source: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1032N No start
database manager command was issued. SQLSTATE=57019
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGe
nerator.java:174)
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLExceptionGen
erator.java:431)
at COM.ibm.db2.jdbc.app.DB2Connection.connect(DB2Connection.java:432)
at COM.ibm.db2.jdbc.app.DB2Connection.<init>(DB2Connection.java:335)
at COM.ibm.db2.jdbc.app.DB2Driver.connect(DB2Driver.java:353)
at
com.ibm.ejs.cm.pool.JDBC1xConnectionFactory.createConnection(JDBC1xConnectio
nFactory.java:32)
at
com.ibm.ejs.cm.pool.ConnectionPool.createConnection(ConnectionPool.java:647)
at
com.ibm.ejs.cm.pool.ConnectionPool.createOrWaitForConnection(ConnectionPool.
java:600)
at
com.ibm.ejs.cm.pool.ConnectionPool.findFreeConnection(ConnectionPool.java:53
1)
at
com.ibm.ejs.cm.pool.ConnectionPool.findConnectionForTx(ConnectionPool.java:4
77)
at
com.ibm.ejs.cm.pool.ConnectionPool.allocateConnection(ConnectionPool.java:42
0)
at
com.ibm.ejs.cm.pool.ConnectionPool.getConnection(ConnectionPool.java:169)
at com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:113)
at com.ibm.ejs.cm.SMDataSource.getConnection(SMDataSource.java:83)
at com.ibm.ejs.sm.util.db.DBMgr.initialize(DBMgr.java:183)
at
com.ibm.ejs.sm.server.AdminServer.startConnectionMgr(AdminServer.java:1193)
at
com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:984)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
FATAL Failed to create a data source: {0} COM.ibm.db2.jdbc.DB2Exception:
[IBM][CLI Driver] SQL1032N No start database manager command was issued.
SQLSTATE=57019
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGe
nerator.java:174)
at
COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLExceptionGen
erator.java:431)
at COM.ibm.db2.jdbc.app.DB2Connection.connect(DB2Connection.java:432)
at COM.ibm.db2.jdbc.app.DB2Connection.<init>(DB2Connection.java:335)
at COM.ibm.db2.jdbc.app.DB2Driver.connect(DB2Driver.java:353)
at
com.ibm.ejs.cm.pool.JDBC1xConnectionFactory.createConnection(JDBC1xConnectio
nFactory.java:32)
at
com.ibm.ejs.cm.pool.ConnectionPool.createConnection(ConnectionPool.java:647)
at
com.ibm.ejs.cm.pool.ConnectionPool.createOrWaitForConnection(ConnectionPool.
java:600)
at
com.ibm.ejs.cm.pool.ConnectionPool.findFreeConnection(ConnectionPool.java:53
1)
at
com.ibm.ejs.cm.pool.ConnectionPool.findConnectionForTx(ConnectionPool.java:4
77)
at
com.ibm.ejs.cm.pool.ConnectionPool.allocateConnection(ConnectionPool.java:42
0)
at
com.ibm.ejs.cm.pool.ConnectionPool.getConnection(ConnectionPool.java:169)
at com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:113)
at com.ibm.ejs.cm.SMDataSource.getConnection(SMDataSource.java:83)
at com.ibm.ejs.sm.util.db.DBMgr.initialize(DBMgr.java:183)
at
com.ibm.ejs.sm.server.AdminServer.startConnectionMgr(AdminServer.java:1193)
at
com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:984)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
java.lang.Throwable
at com.ibm.ejs.ras.CBuffLogger.fatalEvent(CBuffLogger.java:420)
at com.ibm.ejs.ras.Tr.fireTraceEvent(Tr.java:502)
at com.ibm.ejs.ras.Tr.fatal(Tr.java:859)
at com.ibm.ejs.sm.util.db.DBMgr.initialize(DBMgr.java:192)
at
com.ibm.ejs.sm.server.AdminServer.startConnectionMgr(AdminServer.java:1193)
at
com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:984)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:353)
Looking in the DB2 db2diag.log I see this:
2001-11-01-11.42.44.099321 Instance:db2inst1 Node:000
PID:9856(db2ipccm) Appid:none
oper_system_services sqloEDUCodeTrapHandler Probe:10
********************************************************************
* *
* DB2 USERS : *
* ----------- *
* An internal processing error occurred on this DB2 instance. *
* *
* A stack trace-back for the process in which the error was *
* detected may be written to a trap file in the directory *
* containing this log. The name of the file will be 'tppppp.nnn' *
* where ppppp is the process id, and nnn is the node number. *
* *
* *
* ALL DB2 PROCESSES ASSOCIATED WITH *
* THIS INSTANCE HAVE BEEN SHUTDOWN. *
* *
* Contact your technical service representative with the *
* information from this log and from the auxiliary trace and dump *
* files in the same directory. *
********************************************************************
2001-11-01-11.42.44.105993 Instance:db2inst1 Node:000
PID:9856(db2ipccm) Appid:none
oper_system_services sqloEDUCodeTrapHandler Probe:20
Signal number received
0000 0006 ....
2001-11-01-11.42.46.529510 Instance:db2inst1 Node:000
PID:9846(db2sysc) Appid:none
base_sys_utilities sqleChildCrashHandler Probe:15
DiagData
416e 2045 4455 2063 7261 7368 6564 2e An EDU crashed.
2001-11-01-11.42.46.550693 Instance:db2inst1 Node:000
PID:9846(db2sysc) Appid:none
base_sys_utilities sqleChildCrashHandler Probe:16
DiagData
0000 2680 ..&.
2001-11-01-11.42.46.558182 Instance:db2inst1 Node:000
PID:9846(db2sysc) Appid:none
base_sys_utilities sqleChildCrashHandler Probe:17
DiagData
0000 0101 ....
2001-11-01-11.42.46.565821 Instance:db2inst1 Node:000
PID:9846(db2sysc) Appid:none
base_sys_utilities sqleChildCrashHandler Probe:18
DiagData
ffff ffff яяяя
2001-11-01-11.42.46.573441 Instance:db2inst1 Node:000
PID:9846(db2sysc) Appid:none
base_sys_utilities sqleChildCrashHandler Probe:19
DiagData
ffff fc88 яяь.
2001-11-01-11.42.46.581066 Instance:db2inst1 Node:000
PID:9846(db2sysc) Appid:none
base_sys_utilities sqle_sys_ctlr Probe:10
DiagData
0000 0001 ....
2001-11-01-11.42.46.606441 Instance:db2inst1 Node:000
PID:9845(db2wdog) Appid:none
oper_system_services sqloRunInstance Probe:102
DiagData
4372 6974 6963 616c 2045 7272 6f72 3a20 Critical Error:
5368 7574 7469 6e67 2064 6f77 6e20 7379 Shutting down sy
7374 656d 00 stem.
2001-11-01-11.42.46.622584 Instance:db2inst1 Node:000
PID:9845(db2wdog) Appid:none
oper_system_services sqloRunInstance Probe:105
DiagData
0000 0102 0000 0000 ........
2001-11-01-11.42.46.630236 Instance:db2inst1 Node:000
PID:9845(db2wdog) Appid:none
base_sys_utilities sqleCleanupResources Probe:5
DiagData
0000 0102 ....
2001-11-01-11.42.51.630497 Instance:db2inst1 Node:000
PID:10294(java) Appid:*LOCAL.db2inst1.011101184240
oper_system_services sqlo_access_listen_queue Probe:1
0000 0002 ....
2001-11-01-12.05.28.325044 Instance:db2inst1 Node:000
PID:15721(db2star2) Appid:none
oper_system_services licRequestAccess Probe:1
SQL8007W There are "89" day(s) left in the evaluation period for the
product
"DB2 Connect Enterprise Edition". For evaluation license terms and
conditions,
refer to the IBM Evaluation Agreement in the EVALUATE.AGR file, located in
the
following directory: "/usr/IBMdb2/V7.1/Readme/en_US".
2001-11-01-12.07.57.728212 Instance:db2inst1 Node:000
PID:16814(db2star2) Appid:none
oper_system_services licRequestAccess Probe:1
SQL8007W There are "89" day(s) left in the evaluation period for the
product
"DB2 Connect Enterprise Edition". For evaluation license terms and
conditions,
refer to the IBM Evaluation Agreement in the EVALUATE.AGR file, located in
the
following directory: "/usr/IBMdb2/V7.1/Readme/en_US".
Looks to me that DB2 died while the WAS was trying to do something. I have
no idea where to start diagnosing the problem, can anyone point me in the
right direction? Thanks a bunch.
Mike
Gourishankar Menon
Before you startup the was server could you try connect to the DB from the
command line ? If you can connect then please check the admin.config file
in the WebSphere bin dir for the db name & the passwd. I had a similar
problem but that was with Red Hat. Hope it solves your problem.
Gouri
"Mike" <supk...@us.ibm.com> wrote in message
news:9rse0p$cc6$1...@news.boulder.ibm.com...
Mike
command line and the db name and password is correct in the admin.config
file. Trying to start WAS definately crashes DB2. Any ideas why?
Mike
"Gourishankar Menon" <go...@us.ibm.com> wrote in message
news:9rshiv$1dd8$1...@news.boulder.ibm.com...
Gourishankar Menon
Could you try cataloging the DB so that WAS sees the db as remote instead of
local. Then connect to the new DB from command line. This is a known issue
with AIX. I did not see it as a problem when I installing on linux (Red
Hat), but with AIX I had to do it. Change the admin.config to reflect the
new DB Name. Also change the intial.config to true if it is false.
Thanksnews:9rsibe$vk6$1...@news.boulder.ibm.com...