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

SQL1822N ERROR WHEN QUERYING CURRENT DATE OR TIMESTAMP FROM NICKNAME

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
A query that has "current date" or "current timestamp" in its 
select-list may result in SQL1822N error, e.g. 
 
select distinct current date, col1 from nick 
 
SQL1822N  Unexpected error code "-418" received from data source 
"AHE_LPDB_SERVER". Associated text and tokens are " SQL0418N  A 
statement
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all platforms, all relational data sources                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v101fp3                                           * 
****************************************************************
Local-Fix:
Remove "current date" or "current timestamp" from the 
select-list
verfügbare FixPacks:
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
v101fp3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
26.09.2013
31.10.2013
31.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList