Dear All
I hope this can be resolved soon because our online date is
approaching. Let me describe our developing environment first (
hardware spec will not list. There is no matter about hardware)
============================================================================
Developing Machine OS: Windows 2000 Pro
DB Client : DB2 V7.2 EE with Fixpak 9
Developing IDE: IBM WebSphere Studio Application Developer V5
WAS Single Server within WSAD : Tested on 4.04/4.05/4.06
DB2 Server 1: AIX 4.3.3 , DB2 V6 with Fixpak 8 ( 11 tested also)
DB2 Server 2: AIX 4.3.3 , DB2 V7 with Fixpak 9
JDBC Driver: COM.ibm.db2.jdbc.DB2XADataSource
===========================================================================
DB2 Client has tested to bind with DB in V6 also.
We have to access a database in DB2 V6. There is no negotiation space
because customer's application is bundled with DB2 V6. There is no
chance to upgrade it to DB2 V7 in this moment.
Our program has no problem to access in pure DB2 V7 environment.
However, for accessing V6 it would appear this message in JDBC level.
============================================================================
--Caused by Exception : COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI
Driver] CLI0108E Communication link failure. SQLSTATE=40003
COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0108E
Communication link failure. SQLSTATE=40003
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:189)
at COM.ibm.db2.jdbc.app.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:446)
at COM.ibm.db2.jdbc.DB2XAConnection.<init>(DB2XAConnection.java:113)
at COM.ibm.db2.jdbc.DB2XADataSource.getXAConnection(DB2XADataSource.java:101)
at com.ibm.ejs.cm.portability.PortabilityLayerImpl.getInstance(PortabilityLayerImpl.java:1001)
at com.ibm.ejs.cm.portability.PortabilityLayerFactory.getPortabilityLayer(PortabilityLayerFactory.java:64)
at com.ibm.ejs.cm.JDBC2PhaseRF.createConnectionFactory(JDBC2PhaseRF.java:59)
at com.ibm.ejs.cm.JDBC2PhaseRF.getSource(JDBC2PhaseRF.java:167)
at com.ibm.ejs.cm.DataSourceImpl$1.run(DataSourceImpl.java:135)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:133)
at com.ibm.ejs.cm.DataSourceImpl.getConnection(DataSourceImpl.java:102)
at biz.smas.base.db.SQLExecuter.getConnection(SQLExecuter.java:225)
at biz.smas.base.db.SQLExecuter.execQuery(SQLExecuter.java:171)
at biz.smas.base.db.SQLExecuter.doQuery(SQLExecuter.java:359)
at biz.smas.base.db.SQLExecuter.doQuery(SQLExecuter.java:427)
at biz.tpas.session.user.UserManagementBean.getMESUser(UserManagementBean.java:181)
at biz.tpas.session.user.UserManagementBean.logon(UserManagementBean.java:499)
at biz.tpas.session.user.EJSRemoteStatelessUserManagement_0dfd92e4.logon(EJSRemoteStatelessUserManagement_0dfd92e4.java:467)
at biz.tpas.session.user._UserManagement_Stub.logon(_UserManagement_Stub.java:310)
at java.lang.reflect.Method.invoke(Native Method)
at biz.smas.base.ejb.wrapper.EJBWrapper.invoke(EJBWrapper.java:72)
at $Proxy13.logon(Unknown Source)
at biz.tpas.servlet.user.LogOn.doPost(LogOn.java:79)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at biz.smas.util.web.BaseServlet.service(BaseServlet.java:422)
at biz.smas.util.web.BaseServlet.service(BaseServlet.java:413)
at com.ibm.servlet.engine.webapp.StrictServletInstance.doService(ServletManager.java:827)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet._service(StrictLifecycleServlet.java:167)
at com.ibm.servlet.engine.webapp.IdleServletState.service(StrictLifecycleServlet.java:297)
at com.ibm.servlet.engine.webapp.StrictLifecycleServlet.service(StrictLifecycleServlet.java:110)
at com.ibm.servlet.engine.webapp.ServletInstance.service(ServletManager.java:472)
at com.ibm.servlet.engine.webapp.ValidServletReferenceState.dispatch(ServletManager.java:1012)
at com.ibm.servlet.engine.webapp.ServletInstanceReference.dispatch(ServletManager.java:913)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.handleWebAppDispatch(WebAppRequestDispatcher.java:721)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.dispatch(WebAppRequestDispatcher.java:374)
at com.ibm.servlet.engine.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:118)
at com.ibm.servlet.engine.srt.WebAppInvoker.doForward(WebAppInvoker.java:134)
at com.ibm.servlet.engine.srt.WebAppInvoker.handleInvocationHook(WebAppInvoker.java:239)
at com.ibm.servlet.engine.invocation.CachedInvocation.handleInvocation(CachedInvocation.java:67)
at com.ibm.servlet.engine.srp.ServletRequestProcessor.dispatchByURI(ServletRequestProcessor.java:151)
at com.ibm.servlet.engine.oselistener.OSEListenerDispatcher.service(OSEListener.java:317)
at com.ibm.servlet.engine.http11.HttpConnection.handleRequest(HttpConnection.java:60)
at com.ibm.ws.http.HttpConnection.readAndHandleRequest(HttpConnection.java:391)
at com.ibm.ws.http.HttpConnection.run(HttpConnection.java:274)
at com.ibm.ws.util.CachedThread.run(ThreadPool.java:144)
============================================================================
So, in our study, checked all Fixpak list from IBM
http://techsupport.service.ibm.com/ to check on all DB2 and Websphere
Fixpak level. All of them has been pulled to the latest version and
none of them works.
Therefore, we turned on the JDBC with more detail information. This is
what we got in db2diag.log
2003-06-03-16.32.55.125000 Instance:DB2 Node:000
PID:5432(javaw.exe) TID:5452 Appid:AC1C0E0A.0D74.030603082954
oper_system_services sqloopenp Probe:120
GetLastError: 0200 0000 ....
String Title:Path/Filename PID:5432 Node:000
C:\PROGRA~1\SQLLIB\cfg\db2udbse.lvl
Data Title:SQLCA PID:5432 TID:5452 Node:000
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1246 sqlerrml: 0
sqlerrmc:
sqlerrp : SQLEDBCN
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
(4) 0x00000000 (5) 0x00000000 (6) 0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
Data Title:DB2RA PID:5432 TID:5452 Node:000
5351 4c44 4232 5241 2c00 0000 0501 0100 SQLDB2RA,.......
0d00 0200 8800 0000 0900 0080 50e1 f62c ........ ...P..,
0400 0000 0400 0040 d8e1 f62c .......@...,
2003-06-03-16.33.45.046000 Instance:DB2 Node:000
PID:5624(javaw.exe) TID:5604 Appid:
oper_system_services sqloopenp Probe:120
GetLastError: 0200 0000 ....
String Title:Path/Filename PID:5624 Node:000
C:\PROGRA~1\SQLLIB\DB2\db2nodes.cfg
2003-06-03-16.33.56.187000 Instance:DB2 Node:000
PID:5624(javaw.exe) TID:5640 Appid:
oper_system_services sqloopenp Probe:120
GetLastError: 0300 0000 ....
String Title:Path/Filename PID:5624 Node:000
C:\PROGRA~1\SQLLIB\msg\C\db2sql.mo
2003-06-03-16.33.56.187002 Instance:DB2 Node:000
PID:5624(javaw.exe) TID:5640 Appid:
base_sys_utilities sqlenops_dx Probe:10
SQL3269N DB2 was not able to access information in the LDAP directory
because the LDAP server was not available.
2003-06-03-16.34.03.921000 Instance:DB2 Node:000
PID:5624(javaw.exe) TID:5640 Appid:
base_sys_utilities sqlenops_dx Probe:10
SQL3269N DB2 was not able to access information in the LDAP directory
because the LDAP server was not available.
2003-06-03-16.35.29.671000 Instance:DB2 Node:000
PID:5092(db2.exe) TID:5664 Appid:
oper_system_services sqloopenp Probe:120
GetLastError: 0300 0000 ....
String Title:Path/Filename PID:5092 Node:000
C:\PROGRA~1\SQLLIB\msg\C\db2sql.mo
2003-06-03-16.35.29.687001 Instance:DB2 Node:000
PID:5092(db2.exe) TID:5664 Appid:
oper_system_services sqloopenp Probe:120
GetLastError: 0200 0000 ....
String Title:Path/Filename PID:5092 Node:000
C:\PROGRA~1\SQLLIB\msg\\db2clp.mo
2003-06-03-16.35.29.937000 Instance:DB2 Node:000
PID:5680(db2bp.exe) TID:5676 Appid:
oper_system_services sqloopenp Probe:120
GetLastError: 0200 0000 ....
String Title:Path/Filename PID:5680 Node:000
C:\PROGRA~1\SQLLIB\DB2\db2nodes.cfg
2003-06-03-16.35.30.796000 Instance:DB2 Node:000
PID:5092(db2.exe) TID:5664 Appid:
oper_system_services sqloopenp Probe:120
GetLastError: 0200 0000 ....
String Title:Path/Filename PID:5092 Node:000
C:\PROGRA~1\SQLLIB\msg\\db2sqlh.mo
============================================================================
Any one can assist us to solve out this problem? |
