Re: Dup. index error in dbexport

Bryan Tonnet wrote: > > 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. > > 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. > > Thanks in advance > > Bryan Tonnet > batonnet@zeta.org.au Under SE 5.03 the dbexport is ordered by tabid. If SE 7.12 has tabid and tabname in systables then select tabname,tabid from systables order by tabid and see if that is the order of your export. It should be the table after that is bad. BTW we had a similar problem with SE and syscontraints having a duplicate. We got lucky since dbexport does all the constraints last so all the tables were unloaded we just had to patch up the constraints at the end of the sql file.