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

DRDA WRAPPER REPORTS SQL0206N WHEN ACCESSING NICKNAMES POINTING TO DB2 LUW
V95 DATA SOURCE OR EARLY VERSION

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
Users may receive SQL0206N error while accessing DB2 LUW V95 
data source or early version via nicknames. The error message 
shows as below: 
 
SQL1822N  Unexpected error code "-206" received from data source 
"<your_server_name>". Associated text and tokens are " SQL0206N 
"NULL" is not valid in the context where it is".  SQLSTATE=560BD 
 
The error is caused by the incorrect setting of server option 
db2_null_in_select in wrapper. Because of the incorrect setting, 
remote SQL like "SELECT ..., NULL, ... FROM TABLE1" may be 
pushed down to the UDB data sources which do not support a 
statement like that. 
 
The problem only happens on Federation Server V95 with fixpack 8 
or higher,  V97 with fixpack 4 or higher.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* The user is using DRDA wrapper accessing a nickname pointing * 
* to db2 LUW data source v95 or early verions.                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Server V10.1 FP1.                             * 
****************************************************************
Local-Fix:
Set server option db2_null_in_select to 'N': 
 
ALTER SERVER <SERVER NAME> OPTIONS(ADD DB2_NULL_IN_SELECT 'N') 
OR 
ALTER SERVER <SERVER NAME> OPTIONS(SET DB2_NULL_IN_SELECT 'N')
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
Firstly fixed in DB2 Server V10.1 FP1.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.06.2012
01.11.2012
01.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList