Index Corruption

[FBM357]

I've an application which updates 2 databases every 20 minutes (retrieves data from mainframe then updates data). The problem I'm experiencing is index corruption. this same application runs at another site without problems. The environment is ... Novell 5.x, WAN, PC Anywhere (don't ask..LOL), Windows 2000 (for hosts and remotes) and 1 machine (where the corruption is detected via the program) running Windows 98 SE. Again, same setup is replicated at another site, yet no problems with corruption occur.

Could faulty connection be the culprit? If so, would a sniffer be a viable solution? The corruption is happening much too often.

Any help would be appreciated.

FBM

P.S. The stress from all of this has put me in the hospital. My next visit will be psychological instead of physical... LOL

 

[FBM357]

one more thing... indicies are CDX

 

[circes9]

Don't think a network sniffer will help you out with this.
Do you know at what point the index is getting corrupted?
You may need to narrow it down to the process thats corrupting it. Possibly rebuild the index, then check it after a few of the 20 minute updates to see if its corrupted. If so, other than the update process, what else has accessed the data. Anyone accessing the database without the index open? Adding or deleting records with the index closed will result in a corrupted index message when you finally open it.

 

[rob444]

What clipper version do you use and what indexdriver?

Rob.

 

[FBM357]

circes9,

thanks for your reply. I'll look into the application where adding/deleting records occur. Also take a look at whether the index is closed. I can honestly say i do not think the later is a problem as this app works great at another site.

____________________________________________________________


rob444,

I'm using version 5.2e and COMIX as my index driver. I'm more inclined to believe the problem is environment/hardware related rather than software.

 

[JockMullin]

Hi, Rob444

Have your win 2k machines been patched to disable op locking?

Assuming the Win 98 SE machine is doing the update, I'm thinking possibly file locks/updates are still pending from caches in the Win 2K machines. For best reliability, especially in an update situation, opportunistic locking should be disabled.

Jock