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

SQL0901N GETS RETURNED WHEN EXECUTING GRANT, REVOKE OR TRANSFER OWNERSHIP
COMMAND ON A MODULE PROCEDURE THAT DOES NOT EXIST

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When executing a GRANT, REVOKE or TRANSFER OWNERSHIP statement 
against a non-existent module procedure by specifying the 3-part 
name, SQL0901N will be returned if the module does not exist. 
Here is an example of the 
error as seen by a user: 
 
db2 "grant execute on procedure mypsch..mymod.myproc() to public 
 
with grant option" 
DB21034E The command was processed as an SQL statement because 
it was not a valid Command Line Processer command.  During SQL 
processing it returned: 
SQL0901N The SQL statement failed because of a non-severe system 
error.  Subsequent SQL statements can be processed.  (Reason 
"".) SQLSTATE=58004 
 
The sqlcode and message should be: 
 
db2 "grant execute on procedure mypsch.mymod.myproc() to public 
with grant option" 
DB21034E The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it returned: 
SQL0204N "MYPSCH.MYMOD" is an undefined name.  SQLSTATE=42704
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* ALL                                                          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5                        * 
****************************************************************
Local-Fix:
N/A
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
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

Lösung
First fixed in DB2 Version 9.7 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.04.2011
19.12.2011
19.12.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP5
Problem behoben lt. FixList in der Version
9.7.0.5 FixList