|
Problem IC84426
|
Status: Closed |
WHEN SEQUENCE IS DROPPED, ITS COMMENT IS NOT AUTOMATICALLY DELETED FROM SYSIBM.SYSCOMMENTS |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
Here are the steps that show this error :
D:\v9.7_Installation\SQLLIB\BIN>db2 create sequence MYSEQ AS
INTEGER
DB20000I The SQL command completed successfully.
D:\v9.7_Installation\SQLLIB\BIN>db2 comment on sequence MYSEQ IS
'1357900000'
DB20000I The SQL command completed successfully.
D:\v9.7_Installation\SQLLIB\BIN>db2 select * from
SYSIBM.SYSCOMMENTS WHERE REMAR
KS = '1357900000'
OBJECTID REMARKS
OBJECTTYPE
--------------------
-----------------------------------------------------------
----------------------------------------------------------------
----------------
----------------------------------------------------------------
----------------
----------------------------------- ----------
6 1357900000
Q
1 record(s) selected.
D:\v9.7_Installation\SQLLIB\BIN>db2 drop sequence MYSEQ
DB20000I The SQL command completed successfully.
D:\v9.7_Installation\SQLLIB\BIN>db2 select * from
SYSIBM.SYSCOMMENTS WHERE REMAR
KS = '1357900000'
OBJECTID REMARKS
OBJECTTYPE
--------------------
-----------------------------------------------------------
----------------------------------------------------------------
----------------
----------------------------------------------------------------
----------------
----------------------------------- ----------
6 1357900000
Q
1 record(s) selected. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10 fixpak 1 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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
|
| Solution |
First fixed in DB2 Version 10, fixpak 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
03.12.2012
03.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
