Latest versionsfixlist
11.1.0.6 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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26
Question in the chat LiveZilla Live Help

DB2 - Problem description

Problem IC72358 Status: Closed

SQL0551N CAUSED BY TWO USERS CREATING THE SAME SEQUENCE NAME

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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>
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 9.5, Fixpack 8.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.11.2010
06.07.2011
06.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.