DB2 - Problem description
Problem IC77853 | Status: Closed |
MISSING CONDITION IN THE DEFINE OF SYSCAT.SEQUENCES LEADS TO DUPLICATE ENTRIES | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
missing condition in the define of syscat.sequences leads to duplicate entries | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * DB2 users on 9.7 FP 4 or prior * **************************************************************** * PROBLEM DESCRIPTION: * * MISSING CONDITION IN THE DEFINE OF SYSCAT.SEQUENCES LEADS TO * * DUPLICATE ENTRIES * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 9.7 FP5 * **************************************************************** | |
Local Fix: | |
Use the following query instead select a.seqschema, a.seqname, a.definer, a.definertype, a.owner, a.ownertype, a.seqid, a.seqtype, a.base_seqschema, a.base_seqname, a.increment, a.start, a.maxvalue, a.minvalue, case when a.lastassignedval + a.increment > a.maxvalue and a.increment > 0 then case when a.cycle = 'Y' then a.minvalue else null end when a.lastassignedval + a.increment < a.minvalue and a.increment < 0 then case when a.cycle = 'Y' then a.maxvalue else null end else coalesce(a.lastassignedval + a.increment, a.start) end, a.cycle, a.cache, a.order, a.datatypeid, a.sourcetypeid, a.create_time, a.alter_time, a.precision, a.origin, b.remarks from sysibm.syssequences as a left outer join sysibm.syscomments as b on a.seqid = b.objectid and b.objecttype = 'Q' | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.07.2011 19.09.2011 19.09.2011 |
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 |