Index problems

[Tim Fischer]

> [... "corrupted" data ...]
> > I know what you mean - I have seen that before.  Again, I 
> have 20,000 
> > records with 499 fields each.  There's really no way I can 
> go through 
> > each of those 9,980,000 fields to check for corruption.
> > 
> > Does anyone have a way to automate checking for this type of issue?
> 
> Well, if it were corrupted, I wouldn't expect you to be able 
> to find it by typing a longer key.

Personally, I don't think that's the problem, but at the same time, I can't
rule it out since I can't check it.  I'd imagine that an 8bit character in
the field as John was mentioning could cause some issues in the index.

> 
> You say you're on 5.0.13D4.  Have you verified that dxmaint 
> is also that version?
> 

I just verified this.

> Unless there is some unknown bug in the Solaris version, I'm 
> not sure what else would cause the symptoms you describe 
> using the 5.0.13 release.

I seem to be running into a lot of situations like this with Solaris.  We
had some major problems with the xfer program and then the licensing issue
(we had a 256 user license that was randomly converting itself to a 32 user
license and booting everyone out of the system).  Without trying to sound
rude, how much testing is/was done on the Solaris side?

Tim Fischer

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.736 / Virus Database: 490 - Release Date: 8/9/2004