home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC91794 Status: Geschlossen

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

Produkt:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* CLI applications using Array In chain.                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.3                                * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Please upgrade to v101 FP3, users can observe the correct error 
message.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.04.2013
08.10.2013
08.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList