|
Problem IC85898
|
Status: Closed |
ALTER NICKNAME GENERATED BY DB2LOOK CAUSED SQL0104N AN UNEXPECTED TOKEN ")" WAS FOUND |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
db2look can be used to generate DDLs for nicknames. However the
generated SQLs may cause DB21034E
once executed.
The following is an example.
$ db2look -d db1 -e -fedonly
The output has the following:
ALTER NICKNAME "DB2INST1"."DRDATX1" ADD CONSTRAINT FKC1
FOREIGN KEY(C1) REFERENCES "DB2INST1"."DRDATX2" (C1) NOT
ENFORCED ENABLE QUERY OPTIMIZATION ADD CONSTRAINT FKC2 FOREIGN
KEY(C2) REFERENCES "DB2INST1"."DRDATX2" (C1) NOT
ENFORCED ENABLE QUERY OPTIMIZATION) NOT ENFORCED ENABLE QUERY
OPTIMIZATION;
DB21034E The command was processed as an SQL statement because
it was not a
valid Command Line Processor command. During SQL processing it
returned:
SQL0104N An unexpected token ")" was found following "E QUERY
OPTIMIZATION".
Expected tokens may include: "<space>". SQLSTATE=42601 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 8 *
**************************************************************** |
| Local Fix: |
Remove ") NOT ENFORCED ENABLE QUERY OPTIMIZATION" from the
generated "ALTER NICKNAME" SQLs |
| available fix packs: |
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Fixed in Version 9.7 Fix Pack 8 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.08.2012
02.04.2013
02.04.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.8
|
 |
