|
Problem(Abstract) |
A data source is configured in WebSphere Application
Server V5 or V6 to connect to a DB2 V8 database with the DB2 Universal
JDBC driver. An attempt to test the connection using the Test Connection
button in the WebSphere Admin Console or a call to getConnection() from an
application running in WebSphere Application Server fails with the
following error:
DSRA8041I: Failed to connect to the DataSource. Encountered SQLException
with SQL State = 58015, Error Code = -4,499 : The DDM object is not
supported. Current offset: 0x6 Length: 0x20 Unsupported DDM object code
point: 0x221d DB2ConnectionCorrelator: G91B2676.B410.050922203900.
com.ibm.db2.jcc.b.DisconnectException: The DDM object is not supported.
Current offset: 0x6 Length: 0x20 Unsupported DDM object code point: 0x221d
DB2ConnectionCorrelator: G91B2676.B410.050922203900
...
The problem will only occur when the data source is XA-enabled (the
implementation class of the JDBC Provider is
com.ibm.db2.jcc.DB2XADataSource). |
|
|
|
Cause |
The problem is caused by a defect in the version of the
DB2 Universal JDBC driver that is installed with DB2 V8 Fix Pack 9. The
problem will occur if this version of the DB2 Universal JDBC driver is
used to connect to a DB2 V8 database that is at the Fix Pack 7, 8, or 9
level. In addition, it must be an XA connection and federated database
system support must be enabled on the database server. The problem is
addressed by APAR
IY72191. |
|
|
Resolving the
problem |
The fix for IY72191 is included in Fix Pack
10 for DB2 V8. There are two ways to resolve the problem:
- Install Fix Pack 10 for DB2 V8. Then copy the updated
db2jcc.jar, db2jcc_license_cu.jar, and db2jcc_license_cisuz.jar from the
SQLLIB/java directory to the directory specified in the
DB2UNIVERSAL_JDBC_DRIVER_PATH environment variable in your
WebSphere Application Server configuration. You can identify the directory
by using the Admin Console. Expand Environment and select Manage
WebSphere Variables (V5) or WebSphere Variables (V6). You must
restart the application server so that the updated classes will be loaded.
This is the preferred way to resolve the problem.
- Run the command db2 update dbm cfg using federated
no from a DB2 command line processor on the DB2 database server. This
work-around will fix the problem because the problem only occurs when
federated database system support is enabled in DB2. If you need federated
database system support to be enabled, the only solution is to install Fix
Pack 10.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Data & Information Management |
DB2 Universal Database for Linux- UNIX and Windows |
DB2 Programming Interfaces - JCC |
AIX, HP-UX, Linux, Linux pSeries, Linux zSeries, Solaris, Windows |
8 |
Enterprise |
Application Servers |
Runtimes for Java Technology |
Java SDK |
|
|
|
|
|
|