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

DB2 DROP STOGROUP <SGNAME> RESTRICT RETURNS SQL0104N AN UNEXPECTED
TOKEN "RESTRICT" WAS FOUND

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When the "restrict" keyword is used with the "drop stogroup" 
statement an error "SQL0104N  AN UNEXPECTED TOKEN "RESTRICT" WAS 
FOUND" is returned. 
 
db2 drop stogroup sg1 restrict 
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 "restrict" was found following 
"drop stogroup 
sg1 ".  Expected tokens may include:  "END-OF-STATEMENT". 
SQLSTATE=42601
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Galileo users on all platforms                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to product DB2 version 10 Fixpack 1                  * 
****************************************************************
Local-Fix:
Using "drop stogroup <sgname>" has the same behavior as "drop 
stogroup <sgname> restrict". Remove the keyword 'restrict' from 
the syntax.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
The problem is fixed in DB2 version 10 Fixpack 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
23.06.2012
31.10.2012
31.10.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList