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 IC91794 Status: Closed

CLI EXTENDED DIAGNOSTICS, ARRAYINPUTCHAIN ENABLED AGAINST A BUSY DB2 ZOS
SERVER RETURNS SQL0904N-NO REASON CODE, RESOURCE NAME

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
When a CLI application with extended diagnostics and 
arrayinputchain enabled runs a SQL query against a DB2 z/OS 
database server when the resource is busy (example: table is 
pending state or out of locks) returns just the SQL0904N error, 
with no REASON CODE AND RESOURCE NAME information. 
or 
When we retrieve the error message from CLI , it may look like 
below text without any reason code or resource name in the 
message. 
SQLGetDiagRec( pszSqlState="57011", pfNativeError=-904, 
pszErrorMsg="[IBM][CLI Driver][DB2] SQL0904N  Unsuccessful 
execution caused by an unavailable resource.  Reason code: "", 
type of resource: "", and resource name: "".  SQLSTATE=57011
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI applications using Array In chain.                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.3                                * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Please upgrade to v101 FP3, users can observe the correct error 
message.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2013
08.10.2013
08.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList