|
Problem IC67627
|
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 / 950 - 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 : All
Problem Description :
DB2 crash with SQLO_QUE_BAD_HANDLE-EINVAL(22) error message in
db2diag.log when more than 1024 connections is made by TSM.
PROBLEM SUMMARY :
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. |
| 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.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in V9.5FP7 |
| Workaround |
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 |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC71385 IC71386
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.04.2010
10.01.2011
10.01.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP7
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.7
|
 |
| 9.5.0.7
|
|
