Skip to Content
0
Former Member
Nov 14, 2007 at 03:51 AM

disp+work.exe failed with error "DB-Connect Failed, Return Code 000256"

629 Views

<b>OS: Windows 2003 SP2

DB: DB2 V9 PF3 (level is : "DB2 v9.1.300.257", "s070719", "WR21392", and Fix Pack"3".)

ECC 6.0 </b>

<b>When I tried to start up sap in sapmmc, disp+work.exe showed error info: J2EE status unavailable and stopped.

And got error info from syslog on sapmmc, shown below</b>

<i>SAP-Basis System: > 1 possible network problems detected - check tracefile and adjus

SAP-Basis System: Initialization DB-Connect Failed, Return Code 000256</i>

<b>But I got nothing from db2diag.log, could not find any error info from it.

From the trace file F:\usr\sap\ER1\DVEBMGS00\work\dev_disp, I got the following info, shown below:</b>

<i>Wed Nov 14 07:16:28 2007

CCMS: start to initalize 3.X shared alert area (first segment).

DpMsgAdmin: Set release to 7000, patchlevel 0

MBUF state PREPARED

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]

DpMsgAdmin: Set patchno for this platform to 75

Release check o.K.

DpJ2eeLogin: j2ee state = CONNECTED

Wed Nov 14 07:16:37 2007

***LOG Q0I=> NiIRead: recv (10054: WSAECONNRESET: Connection reset by peer) [nixxi.cpp 4235]

  • ERROR => NiIRead: SiRecv failed for hdl 4 / sock 1452

(SI_ECONN_BROKEN; I4; ST; 127.0.0.1:1074) [nixxi.cpp 4235]

DpJ2eeMsgProcess: j2ee state = CONNECTED (NIECONN_BROKEN)

DpIJ2eeShutdown: send SIGINT to SAP J2EE startup framework (pid=3172)

  • ERROR => DpProcKill: kill failed [dpntdisp.c 371]

DpIJ2eeShutdown: j2ee state = SHUTDOWN

Wed Nov 14 07:17:06 2007

  • ERROR => W0 (pid 1356) died [dpxxdisp.c 14241]

  • ERROR => W1 (pid 2824) died [dpxxdisp.c 14241]

  • ERROR => W2 (pid 3212) died [dpxxdisp.c 14241]

  • ERROR => W3 (pid 2672) died [dpxxdisp.c 14241]

  • ERROR => W4 (pid 3188) died [dpxxdisp.c 14241]

  • ERROR => W5 (pid 2944) died [dpxxdisp.c 14241]

my types changed after wp death/restart 0xbf --> 0xbe

  • ERROR => W6 (pid 1456) died [dpxxdisp.c 14241]

my types changed after wp death/restart 0xbe --> 0xbc

  • ERROR => W7 (pid 3316) died [dpxxdisp.c 14241]

my types changed after wp death/restart 0xbc --> 0xb8

  • ERROR => W8 (pid 2512) died [dpxxdisp.c 14241]

  • ERROR => W9 (pid 1864) died [dpxxdisp.c 14241]

  • ERROR => W10 (pid 2996) died [dpxxdisp.c 14241]

my types changed after wp death/restart 0xb8 --> 0xb0

  • ERROR => W11 (pid 3092) died [dpxxdisp.c 14241]

my types changed after wp death/restart 0xb0 --> 0xa0

  • ERROR => W12 (pid 3324) died [dpxxdisp.c 14241]

my types changed after wp death/restart 0xa0 --> 0x80

  • DP_FATAL_ERROR => DpWPCheck: no more work processes

  • DISPATCHER EMERGENCY SHUTDOWN ***</i>

<b>When I tried to start SAP J2EE engine, got an error: could not connect to DB, shown below</b>

<i>F:\usr\sap\ER1\DVEBMGS00\j2ee\configtool> configtool.bat

com.sap.engine.frame.core.configuration.ConfigurationException: Error while connecting to DB.

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:360)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.<init>(DBConnectionPool.java:125)

at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.<init>(PersistenceHandler.java:38)

at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.<init>(ConfigurationCache.java:149)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.init(ConfigurationManagerBootstrapImpl.java:236)

at com.sap.engine.core.configuration.bootstrap.ConfigurationManagerBootstrapImpl.<init>(ConfigurationManagerBootstrapImpl.java:49)

at com.sap.engine.configtool.visual.ConfigTool.loadClusterData(ConfigTool.java:99)

at com.sap.engine.configtool.visual.ConfigTool.initScan(ConfigTool.java:87)

at com.sap.engine.configtool.visual.ConfigTool.<init>(ConfigTool.java:82)

at com.sap.engine.configtool.visual.ConfigTool.main(ConfigTool.java:961)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:324)

at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)

Caused by: com.sap.sql.log.OpenSQLException: Error while accessing porting layer for DB2_UDB database via getDatabaseName().

at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:106)

at com.sap.sql.jdbc.direct.DirectConnectionFactory.createContextFactory(DirectConnectionFactory.java:660)

at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:251)

at com.sap.sql.jdbc.direct.DirectConnectionFactory.createDirectPooledConnection(DirectConnectionFactory.java:214)

at com.sap.sql.connect.OpenSQLDataSourceImpl.createPooledConnection(OpenSQLDataSourceImpl.java:617)

at com.sap.sql.connect.OpenSQLDataSourceImpl.getPooledConnection(OpenSQLDataSourceImpl.java:285)

at com.sap.engine.core.configuration.impl.persistence.rdbms.DBConnectionPool.createConnection(DBConnectionPool.java:302)

... 14 more

Caused by: com.ibm.db2.jcc.b.SqlException: DB2 SQL error: SQLCODE: -440, SQLSTATE: 42884, SQLERRMC: RTRIM;FUNCTION

at com.ibm.db2.jcc.b.hh.c(hh.java:1662)

at com.ibm.db2.jcc.b.hh.d(hh.java:1650)

at com.ibm.db2.jcc.b.hh.a(hh.java:1219)

at com.ibm.db2.jcc.c.db.g(db.java:139)

at com.ibm.db2.jcc.c.db.a(db.java:39)

at com.ibm.db2.jcc.c.t.a(t.java:34)

at com.ibm.db2.jcc.c.sb.f(sb.java:142)

at com.ibm.db2.jcc.b.hh.n(hh.java:1190)

at com.ibm.db2.jcc.b.hh.a(hh.java:1902)

at com.ibm.db2.jcc.b.hh.a(hh.java:491)

at com.ibm.db2.jcc.b.hh.executeQuery(hh.java:475)

at com.sap.sql.jdbc.db6.Db6PortingServices.getDatabaseName(Db6PortingServices.java:183)

at com.sap.sql.jdbc.direct.DirectConnectionFactory.createContextFactory(DirectConnectionFactory.java:652)

... 19 more</i>

<b>Another strange thing was, when I tried to view tablespace info by db2cc program using db2er1 account(in graphic mode), got the following info:</b>

<i>[IBM][CLI Driver][DB2/NT] SQL0440N No authorized routine named

"SNAP_GET_TBSP" of type "FUNCTION" having compatible arguments

was found. SQLSTATE=42884</i>

<b>Also, I could not open saper1 account info by db2cc, I could open and change other account by db2cc program.

How to solve it? Please advise. Thanks so much.</b>

Message was edited by:

James Hu