|
Problem IC69929
|
Status: Closed |
CONNECTING TO DB2 TRANSACTION MANAGER (TM) DATABASE MAY FAIL. |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
This problem only exists in DB2 Type 2 connections to DB2
Transaction Manager (TM) database defined by database manager
configuration parameter TM_DATABASE, where you're using DB2
transaction manager.
Applications using XA-compliant transaction managers such as IBM
CICS, IBM WebSphere MQ are not affected.
If you once fail to establish DB2 Type 2 connection to a DB2 TM
database, subsequent attempts to connect to the DB2 TM database
from the same DB2 client may fail.
Here are some typical scenarios:
1) Connecting to the TM database using invalid user name or
password and encounters SQL0859N.
Subsequent attempts encounter SQL0859N even if using correct
user name and password.
2) Connecting to the TM database where database manager is not
started up and encounters SQL0859N.
Subsequent attempts encounter SQL0842N even if the database
manager has been started up.
The error code for subsequent failures varies depending on the
error code for the initial failure.
The fix of the issue resets connection attributes upon any
failure when connecting to DB2 TM database.
As a result, you would have to set the attributes prior to the
next CONNECT TO command, e.g. "SET CLIENT CONNECT 2" to enable
Type 2 connection attribute. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users of version 9.1 on Linux, Unix and Windows *
* platforms. *
****************************************************************
* PROBLEM DESCRIPTION: *
* This problem only exists in DB2 Type 2 connections to DB2 *
* Transaction Manager (TM) database defined by database *
* manager configuration parameter TM_DATABASE, where you're *
* using DB2 transaction manager. *
* Applications using XA-compliant transaction managers such as *
* IBM CICS, IBM WebSphere MQ are not affected. *
* *
* If you once fail to establish DB2 Type 2 connection to a DB2 *
* TM database, subsequent attempts to connect to the DB2 TM *
* database from the same DB2 client may fail. *
* Here are some typical scenarios: *
* 1) Connecting to the TM database using invalid user name or *
* password and encounters SQL0859N. *
* Subsequent attempts encounter SQL0859N even if using *
* correct user name and password. *
* 2) Connecting to the TM database where database manager is *
* not started up and encounters SQL0859N. *
* Subsequent attempts encounter SQL0842N even if the *
* database manager has been started up. *
* *
* The error code for subsequent failures varies depending on *
* the error code for the initial failure. *
* *
* The fix of the issue resets connection attributes upon any *
* failure when connecting to DB2 TM database. *
* As a result, you would have to set the attributes prior to *
* the next CONNECT TO command, e.g. "SET CLIENT CONNECT 2" to *
* enable Type 2 connection attribute. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB Version 9.1 FixPak 10 or higher levels. *
**************************************************************** |
| Local Fix: |
1. Terminate the DB2 client (e.g. terminate 'db2bp' process by
"TERMINATE" command) and restart a new one.
The new DB2 client will work well until next time you get a
failure and run into the same problem again.
2. Using XA-compliant transaction managers instead of DB2
transaction manager. |
| available fix packs: |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
First fixed in DB2 UDB Version 9.1 FixPak 10. |
| Workaround |
1. Terminate the DB2 client (e.g. terminate 'db2bp' process by
"TERMINATE" command) and restart a new one.
The new DB2 client will work well until next time you get a
failure and run into the same problem again.
2. Using XA-compliant transaction managers instead of DB2
transaction manager. |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC70267 IC70268 IC71530
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.07.2010
16.06.2011
16.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
