|
Problem IC96275
|
Status: Closed |
SQL1822N ERROR WHEN QUERYING CURRENT DATE OR TIMESTAMP FROM NICKNAME |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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 |
| available fix packs: |
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
|
| Solution |
v101fp3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.09.2013
31.10.2013
31.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
