DB2 - Problembeschreibung
| Problem IC78916 | Status: Geschlossen |
WHEN SEQUENCE IS DROPPED, ITS COMMENT IS NOT AUTOMATICALLY DELETED FROM SYSIBM.SYSCOMMENTS | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
| Problembeschreibung: | |
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-Zusammenfassung: | |
Fixed in v9.7 fixpack 6 | |
| Local-Fix: | |
| verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
| Lösung | |
Issue fixed in v9.7 fixpack 6 | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Bug-Verfolgung | |
Vorgänger : APAR is sysrouted TO one or more of the following: IC84426 Nachfolger : | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 26.09.2011 12.06.2012 12.06.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP6 | |
| Problem behoben lt. FixList in der Version | |
| 9.7.0.6 |
|