|
Problem IT19165
|
Status: Closed |
FETCH-FIRST-CLAUSE RESULTS IN SQL0104N |
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
A SQL104N error is returned if a fetch-first-clause is specified
after an isolation-clause or
concurrent-access-resolution-clause. For example:
select * from T optimize for 1 row fetch first 1 row only
SQL0104N  An unexpected token "select * from T" was found
following "BEGIN-OF-STATEMENT".  Expected tokens may include:
"<query_expr_body>".  SQLSTATE=42601 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users prior to Db2 v11.1 m3 fp3. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade Db2 to v11.1 m3 fp3. *
**************************************************************** |
| Local Fix: |
Change the SQL statement such that the fetch-first-clause
precedes isolation-clause and/or
concurrent-access-resolution-clause, e.g.:
select * from T fetch first 1 row only optimize for 1 row |
| available fix packs: |
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
Problem is first fixed in Db2 v11.1 m3 fp3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 08.02.2017
15.03.2018
15.03.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
