Re: Dup. index error in dbexport

In <5dmqs6$umu@godzilla.zeta.org.au> I wrote: Hmmm, it must be getting late. A followup to my original posting. >Using SE 7.12 on SCO 5.0.2d, dbexport falls over with a duplicate key >error about half way through my database. >The output from dbexport has listed the schema for table xyz just before >it halts with the error. The question is, is this the table currently >being unloaded (and therefore the one with the error), or is dbexport >unloading the next table (call it abc) and will then list its schema in the >output file? >I have dropped all indexes from table xyz (the one last listed in the output), >but the error still occurs. Therefore, I think dbexport must be unloading >a table not yet listed in the output...but which is it? The order of table >unloads does not appear to correlate with a select (no order by) on >systables, nor is it an alphanumeric order. Its in tabid order (of course). So I've got the next table in the sequence and dropped the indexes from it. However, the error persists. Starting to get annoyed. >I have secheck'ed all files which turned up nothing, so the error itself is >a little on the strange side, but this is a test database, so I can live >with a minor inconsistancy. >Haven't tried dbunload yet, that's the next step if noone here has any ideas. Or I would, if such a thing existed :/. I mean dbschema & unload. I tried dbschema which [surprise] falls over at the same point with the same error. Oh well. I dont want to "cp" the files if I can avoid it, and I dont have a full schema in any case. Starting to get panicky. >Thanks in advance Thanks in advance >Bryan Tonnet >batonnet@zeta.org.au Bryan Tonnet batonnet@zeta.org.au Is talking to yourself in Usenet considered a sign of impending insanity?