home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC71385 Status: Closed

DB2 CRASH WITH SQLO_QUE_BAD_HANDLE - EINVAL (22) ERROR MESSAGE IN
DB2DIAG.LOG DUE WHEN TSM MAKES MORE THAN 1024 CONNECTIONS.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A condition exist when TSM (installed with DB2 database) 
encounters a DB2 crash issue when more than 1024 connections 
are made. 
In the db2diag.log we would see errors indicating a 
SQLO_QUE_BAD_HANDLE - EINVAL(22) error message. 
This APAR will address a better error messaging/handling when 
the problem occurs.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* General                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The error returned was not accurate.                         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v97fp4                                            * 
****************************************************************
Local Fix:
To avoid the crash and to allow more than 1024 connections a 
workaround is to create a TCPIP looback node. 
Steps to this are as follows... 
1. db2 uncatalog database <dbname> 
2. db2 catalog tcpip node <nodename> remote 127.0.0.1 
   server <server name> 
3. db2 catalog database <dbname> as <alias dbname> on 
   <db directory path> 
4. db2 catalog <alias dbname> as <dbname> at node <nodename> 
5. db2 update dbm cfg using AUTHENTICATION CLIENT 
6. db2 update dbm cfg using TRUST_CLNTAUTH CLIENT
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
v97fp4 has the fix , The customer will receive appropriate 
error message to identify the problem
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.09.2010
03.05.2011
03.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList