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

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to version 10.1 fix pack 5                           * 
****************************************************************
Local-Fix:
Lösung
Fix fixed in version 10.1 fix pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.04.2014
13.07.2015
13.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList