DB2 - Problem description
| Problem IC78916 | Status: Closed |
WHEN SEQUENCE IS DROPPED, ITS COMMENT IS NOT AUTOMATICALLY DELETED FROM SYSIBM.SYSCOMMENTS | |
| product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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: | |
Fixed in v9.7 fixpack 6 | |
| Local Fix: | |
| available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Solution | |
Issue fixed in v9.7 fixpack 6 | |
| Workaround | |
not known / see Local fix | |
| BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84426 follow-up : | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.09.2011 12.06.2012 12.06.2012 |
| Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 9.7.0.6 |
|