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

DB2LOOK GENERATES "CREATE SERVER" STATEMENTS THAT LEADS TO
SQL1841N ERROR.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In a federated environment, db2look might generate "CREATE 
SERVER" statements which will set values for 
 
    DATE_COMPAT 
    NUMBER_COMPAT 
    SAME_DECFLT_ROUNDING 
    VARCHAR2_COMPAT 
 
As per documentation: 
In InfoSphereᄅ Federation Server Version 9.7 Fix Pack 2 and 
later, when you run the CREATE SERVER statement, the following 
server options are automatically configured based on the 
configuration of your data source: 
 
    DATE_COMPAT 
    NUMBER_COMPAT 
    SAME_DECFLT_ROUNDING 
    VARCHAR2_COMPAT 
 
If you attempt to manually configure these server options you 
receive the SQL1841N message. 
 
As such, db2look will no longer generate these CREATE SERVER 
options.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.1 fix pack 5                           * 
****************************************************************
Local Fix:
Solution
Fix fixed in version 10.1 fix pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
22.04.2014
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList