I have, but not with ndbd --initial. Did you use --initial?
Next steps (in order) that I intend to try (only the first can be done without downtime):
- ndbd --initial/rolling restart
- full shutdown/startup
- full shutdown/ndbd --initial/ndb_restore
- mysqldump
> -----Original Message-----
> From: Hendrik Woltersdorf [mailto:hendrik.woltersdorf@stripped]
> Sent: Wednesday, July 01, 2009 9:38 AM
> To: Cluster
> Subject: Antwort: RE: Cannot drop or create NDB table
>
> Have you tried a (rolling?) restart of the cluster (including the SQL
> nodes) ?
> That solved such problems for me in some 6.3 versions.
>
> Hendrik Woltersdorf
>
> Jeff Sturm <jeff.sturm@stripped> schrieb am 01.07.2009 15:24:35:
>
> > Jeff Sturm <jeff.sturm@stripped>
> > 01.07.2009 15:24
> >
> > An
> >
> > <Jonas.Oreland@stripped>
> >
> > Kopie
> >
> > <cluster@stripped>
> >
> > Thema
> >
> > RE: Cannot drop or create NDB table
> >
> > We did give that a try, yes:
> >
> > [root@dbs01 ~]# /opt/mysql/bin/ndb_drop_table contest_entry -d
> > promodb
> > Dropping table contest_entry...
> > 723: No such table existed
> >
> > NDBT_ProgramExit: 1 - Failed
> >
> > One of the API nodes is also logging an error:
> >
> > 090630 22:51:39 [ERROR] NDB: failed to setup table
> > promodb.contest_entry, error: 723, No such table existed
> >
> > Related or not, all our problems seemed to start after this error:
> >
> > 090630 12:00:20 [ERROR] NDB Binlog: logging of table
> > ./fsdb/bonus_audit_log with BLOB attribute and no PK is not supported
> >
> > Other ideas? This isn't a production system, so I know I can mysqldump
> > what's there, shut down and rebuild. But I'm afraid of what happens if
> > I encounter the same problem on a critical system.
> >
> >
> > > -----Original Message-----
> > > From: Jonas.Oreland@stripped [mailto:Jonas.Oreland@stripped]
> > > Sent: Wednesday, July 01, 2009 2:22 AM
> > > To: Jeff Sturm
> > > Cc: cluster@stripped
> > > Subject: Re: Cannot drop or create NDB table
> > >
> > > have you tried ndb_drop_table ?
> > >
> > > /Jonas
> > >
> > > Jeff Sturm wrote:
> > > > I have an NDB table (6.2.15) that appears to have been partially
> > > > created. My problem is getting rid of it so I can re-create
> > properly.
> > > >
> > > >
> > > >
> > > > In mysql, I see:
> > > >
> > > >
> > > >
> > > > mysql> create table contest_entry (id integer primary key);
> > > >
> > > > ERROR 1050 (42S01): Table 'contest_entry' already exists
> > > >
> > > >
> > > >
> > > > mysql> drop table contest_entry;
> > > >
> > > > ERROR 1051 (42S02): Unknown table 'contest_entry'
> > > >
> > > >
> > > >
> > > > Hmm. Trying from NDBAPI:
> > > >
> > > >
> > > >
> > > > [root@dbs02 ~]# ndb_show_tables | grep promodb | grep contest_entry
> > > >
> > > > 929 UserTable Online Yes promodb def
> > > > contest_entry
> > > >
> > > >
> > > >
> > > > So the table does exist, has id 929, is online, etc. However,
> > unlike
> > > > the other tables, it is lacking a TableEvent, and I still can't drop
> > it:
> > > >
> > > >
> > > >
> > > > [root@dbs02 ~]# ndb_drop_table -d promodb contest_entry
> > > >
> > > > Dropping table contest_entry...
> > > >
> > > > 723: No such table existed
> > > >
> > > >
> > > >
> > > > NDBT_ProgramExit: 1 - Failed
> > > >
> > > >
> > > >
> > > > I'd fiile a bug report if I had any idea how to reproduce this. So
> > > > instead I'll ask: What might cause this? How can I repair? Is a
> > full
> > > > shutdown likely to help, or do I have to resort to ndb_restore, or
> > > > worse?
> > > >
> > > >
> > > >
> > > > Grateful for any help,
> > > >
> > > >
> > > >
> > > > Jeff
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > MySQL Cluster Mailing List
> > For list archives: http://lists.mysql.com/cluster
> > To unsubscribe: http://lists.mysql.com/cluster?
> > unsub=Hendrik.Woltersdorf@stripped
> >
>
>
>
>
> *** XCOM AG Legal Disclaimer ***
>
> Diese E-Mail einschliesslich ihrer Anhaenge ist vertraulich und ist allein
> für den Gebrauch durch den vorgesehenen Empfaenger bestimmt. Dritten ist
> das Lesen, Verteilen oder Weiterleiten dieser E-Mail untersagt. Wir bitten,
> eine fehlgeleitete E-Mail unverzueglich vollstaendig zu loeschen und uns
> eine Nachricht zukommen zu lassen.
>
> This email may contain material that is confidential and for the sole use
> of the intended recipient. Any review, distribution by others or forwarding
> without express permission is strictly prohibited. If you are not the
> intended recipient, please contact the sender and delete all copies.
>
> Hauptsitz: Bahnstrasse 37, D-47877 Willich, USt-IdNr.: DE 812 885 664
> Kommunikation: Telefon +49 2154 9209-70, Telefax +49 2154 9209-900,
> www.xcom.de
> Handelsregister: Amtsgericht Krefeld, HRB 10340
> Vorstand: Matthias Albrecht, Marco Marty, Dr. Rainer Fuchs, Dirk Werner
> Vorsitzender des Aufsichtsrates: Stefan H. Tarach
