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 IC65322 Status: Geschlossen

JCC CONNECTION TO A NON-EXISTENT DATABASE SOMETIMES GETS SQLSTATE
08001 INSTEAD OF SQLSTATE 08004

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
An attempt to connect to a non-existing database using JCC type 
4 connection sometimes gets SQL error -4499 with SQL state 08001 
instead of SQL state 08004. 
 
SQL state 08001 is misleading here as it indicates a general 
communication issue: 
 
08001 The application requester is unable to establish the 
      connection. 
 
08004 The application server rejected establishment of the 
      connection. 
 
 
This APAR will address transparent error handling and ensure SQL 
state 08004 is returned.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All using JCC type 4 connectivity                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* An attempt to connect to a non-existing database using       * 
* JCCtype4 connection sometimes gets SQL error -4499 with SQL  * 
* state08001instead of SQL state 08004.SQL state 08001 is      * 
* misleading here as it indicates a generalcommunication       * 
* issue:08001 The application requester is unable to establish * 
* theconnection.08004 The application server rejected          * 
* establishment of theconnection.This APAR will address        * 
* transparent error handling and ensureSQLstate 08004 is       * 
* returned.                                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 9.7 FP2                               * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 version 9.7 FP2
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
05.01.2010
31.05.2010
31.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList