Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!mcnc!ecsgate!stat.appstate.edu!cookdl
From: cookdl@stat.appstate.edu
Newsgroups: comp.databases
Subject: Re: Little problem with Unify
Message-ID: <1991Apr17.075247.710@stat.appstate.edu>
Date: 17 Apr 91 11:52:47 GMT
References: <1991Apr5.004919.9136@aablue.com>
Organization: Appalachian State University
Lines: 26

In article <1991Apr5.004919.9136@aablue.com>, jb@aablue.aablue.com (John B Scalia) writes:
> (Posting this for a colleague, either post here or e-mail
> to clint@aablue.com, thanks!):
> 
> I ran into a problem two days ago. First, I executed an SQL statement to get
> the count of the total records in a specific table and then I ran another one
> to get the count of those with valid reference field which is 6 records short
> of the total count. So I dumped all the records from this table and ran a 
> delete statement in SQL mode to clean up the table. After I did that,
> I still got a record count of 6 in this supposedly empty table. I've concluded
> that I probably need to run SCOM on it, but I'd prefer a simpler way to
> get rid of these 6 bad records without spending another two and a half
> hours :).
> Any help will be appreciated.
> 
> Clint.
> --------------
> -- 
> Respond to:                     |
> jb@aablue.com       or          | "Here's my .sig ain't it weird"
> uunet!aablue!jb                 |

I ran into the same thing a couple of years back.  I cant find my notes on how
i fixed it but you seem to have the right idea.  Its a pain to fix but you may
as well go for it.  Unify's hotline is familiar with this i'm sure because they 
helped me fix this problem.