DB2 - Problembeschreibung
Problem IC72358 | Status: Geschlossen |
SQL0551N CAUSED BY TWO USERS CREATING THE SAME SEQUENCE NAME | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problembeschreibung: | |
Two users User1 and User2 create the same sequence name as indicated below. User1 issues the following commands: User1 ----- db2 connect to testdb user user1 using xxxxxxxx db2 create sequence myseq1 db2 select myseq1.nextval from sysibm.sysdummy1 1 ----------- 1 1 record(s) selected. Now, Users 2 issues the following commands: User2 ----- db2 connect to testdb user user2 using xxxxxxxx db2 create sequence myseq1 db2 select myseq1.nextval from sysibm.sysdummy1 SQL0551N "user2" does not have the required authorization or privilege to perform operation "USAGE" on object "USER1.MYSEQ1". SQLSTATE=42501 Note: when User2 tries to access myseq1.nextval, SQL0551N will be returned as indicated above. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Users trying to create the same sequence name. * **************************************************************** * PROBLEM DESCRIPTION: * * Without this APAR, customer is exposed to the issue as * * described in the "ERROR DESCRIPTION" section. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.5, Fixpack 8. * **************************************************************** | |
Local-Fix: | |
- Fully qualify the sequence: user2.myseq1.nextval - Since the following expressions are not affected, they can be used as a workaround i.e. o NEXT VALUE FOR <sequence> o PREVIOUS VALUE FOR <sequence> o NEXTVAL FOR <sequence> o PREVVAL FOR <sequence> | |
verfügbare FixPacks: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Lösung | |
First fixed in DB2 Version 9.5, Fixpack 8. | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 02.11.2010 06.07.2011 06.07.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.5.FP8 | |
Problem behoben lt. FixList in der Version | |
9.5.0.8 |