I have this problem that once I drop a table, I can't create a new sequence object as the follwoing statements demonstrate.

db2 => create sequence seq_test1 as integer
DB20000I The SQL command completed successfully.
db2 => drop table raum
DB20000I The SQL command completed successfully.
db2 => create sequence seq_test2 as integer
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL0803N One or more values in the INSERT statement, UPDATE statement, or
foreign key update caused by a DELETE statement are not valid because the
primary key, unique constraint or unique index identified by "" constrains
table "" from having duplicate rows for those columns. SQLSTATE=23505


I spend the last two days searching the internet for help and it seems nobody had this problem before. Did anybody ever encountered this behaviour?

Any help is appreciated!

db2inst1# /opt/IBM/db2/V8.1/bin> db2level
DB21085I Instance "db2inst1" uses "32" bits and DB2 code release "SQL08016"
with level identifier "02070106".
Informational tokens are "DB2 v8.1.0.56", "s040616", "MI00080", and FixPak "6".
Product is installed at "/opt/IBM/db2/V8.1".

I can't reproduce it with db2 8.1.5 on Windows. Maybe it's a FP6 bug?

I produced this behaviour already with FP5. I was hoping it would disappear with FP6.

I created a new database and copied all the data via db2move from source db to the destination db and the above behaviour disappeard, meaning I can drop tables and create sequences again.

What troubles me is how/why my original database became corrupt after I drop a table.