DB2 - Problem description
Problem IC84553 | Status: Closed |
DRDA WRAPPER REPORTS SQL0206N WHEN ACCESSING NICKNAMES POINTING TO DB2 LUW V95 DATA SOURCE OR EARLY VERSION | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
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 Summary: | |
**************************************************************** * 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') | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Firstly fixed in DB2 Server V10.1 FP1. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.06.2012 01.11.2012 01.11.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |