Re: Dbschema outputs -284 error in SE 7.24FC6 on Alpha 4.0d

In article <RumP3.25612$m4.92971987@news.magma.ca>, Lloyd AJ Wilson <lwilson@harriscomputer.com> writes >Hi All, > >Running dbschema -t <table> -d <database> -ss encounters the -284 error: A >subquery has returned not exactly one row > >Can some explain a bit what dbschema is trying to do here ... > >We also get the -100 Error: which is ISAM error: duplicate value for a >record with unique key > I have seen this too with corrupt tables. Index builds/alter tables under SE getting killed and leaving corrupt table/indexes. >We are encountering this all over the place for our client mostly running on >the Alpha servers. Most likely they are running version 4 and up. > >This problem has been documented with Informix as a bug I believe. Not sure >... in any case ... does anyone have a resolve to this issue. It is quite >cumbersome for these errors to occur on more than 100 tables in our database >which contains over 300 tables. > >I am running out of time ... and dropping and recreating tables and indexes >seems to resolve the duplicate error problem but does not always solve the >issue with the subquery problem. > >If you can ... it would be helpful to know a bit more about what dbschema is >trying to do ... the tables it pulls from and such ... because I am at a >lost to a resolve other than what I mentioned. > >TIA, > >Lloyd Aj Wilson > > -- David Williams