DB2 - Problem description
Problem IC76747 | Status: Closed |
THE DB2 UPDATE COMMAND OPTIONS USING 'M' OFF/ON RESULTS IN SQL0104N ERROR | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
The db2 update command options using 'm' off/on results in SQL0104N error. Example 1: > db2 update command options using m off SQL0104N An unexpected token "off" was found following "OFF". Expected tokens may include: "A". SQLSTATE=42601 Example 2: > db2 update command options using m on SQL0104N An unexpected token "on" was found following "ON". Expected tokens may include: "A". SQLSTATE=42601 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 5 * **************************************************************** | |
Local Fix: | |
You could issue the command through an initeractive mode or through a script. db2 => update command options using m on Then you can see that all the changes done to the command option will be retained, because the frontend (db2=>) "db2 command line" process is still alive. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 01.06.2011 07.03.2012 07.03.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |