Bug #11355 server will not let me drop table with broken unique index
Submitted: 15 Jun 2005 16:07 Modified: 1 Aug 2005 15:17
Reporter: Tomas Ulin Email Updates:
Status: Closed Impact on me:
Category:MySQL Cluster: Cluster (NDB) storage engine Severity:S3 (Non-critical)
Version:5.0 bk src OS:Linux (linux)
Assigned to: Pekka Nousiainen CPU Architecture:Any

[15 Jun 2005 16:07] Tomas Ulin
mysql server will not let me drop a table that has a "broken" unique index

../ndb/tools/ndb_show_tables -c localhost:9350
id    type                 state    logging database     schema   name
0     SystemTable          Online   Yes     sys          def      SYSTAB_0
1     SystemTable          Online   Yes     sys          def      NDB$EVENTS_0
2     UserTable            Online   Yes     test         def      ippool
3     OrderedIndex         Online   No      test         def      ippool_idx
4     UserTable            Online   Yes     test         def      session
5     UniqueHashIndex      Broken   Yes     test         def      FRAMED_idx$unique

and also gives wrong error message:

master> drop table session;
ERROR 1051 (42S02): Unknown table 'session'

How to repeat:

don't know how to break the unique index... but if you can fake it...
[15 Jun 2005 16:14] Tomas Ulin
cannot drop with ndb_drop_table either

./ndb/tools/ndb_drop_table -c localhost:9350 -d test session
Dropping table session...
4238: Trigger not found

NDBT_ProgramExit: 1 - Failed
[15 Jun 2005 16:30] Tomas Ulin
could not get it to rebuild index correctly even after doing node restarts...

only after a system restart the index was ok again...
[19 Jul 2005 2:04] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[1 Aug 2005 15:17] Jon Stephens
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Bugfix documented for 5.0.10.