Thanks to Razzak and all for replies.  We have a tool that does a complete OUTPUT/INPUT each night, so the database is regularly maintained.  As I think more about it, another common factor is that these tables typically take a heavy load, with INSERTS and DELETES of 3 - 20 rows each from 10+ users at any given moment, usually done through a DECLARE CURSOR.   Maybe we're overloading the database with transactions.
 
Somewhere and somehow, some peice of the transaction is not completing - maybe the index is getting updated and the data is not getting written or vice versa.  Can't tell.  Have to try different settings, I guess.  Unfortunately, reloading and reindexing are not feasible solutions during the workday.  We can't control the crashing, it's become a fact of life for us and our users just deal with it, so if it is caused by a crash, there's little we can do.  Our crashes typically come when forms close - can't figure out why, though it is a lot less common on our W2K machines than our NT boxes.
 
If we learn anything else, I'll be sure to share.
 
wm
 
 
----- Original Message -----
Sent: Wednesday, May 29, 2002 5:33 AM
Subject: Re: Corrupt Indexes - Razzak's Reply


At 05:46 PM 5/28/2002 -0700,  William Mason wrote:

We have begun to encounter REPEATED index corruptions, resulting in a
scenario in which rows seem to both exist and not exist at the same time.


William,

Remember, things just don't happen automatically nor do rows
disappear without a possible cause.

There are thousands of installations out there running their mission
critical operations, 24x7x365 using R:BASE.

When was the last time that database maintenance such as RELOAD
or PACK INDEX were performed on your database?

I would also suggest, to spare some of your precious time to narrow
down the possible cause,  that you compare data as well as monitor
data input.

For complete details on "Finding and Fixing Broken Pointers/Indexes",
check out the technical document at:

From The Edge: http://www.razzak.com/fte

Choose "General Topics" from the drop-down list and then select
"Finding and Fixing Broken Indexes".

The PDF version of this document includes the following:

A. Definitions
B. How R:BASE Finds the Data
C. Common Causes for Broken Pointers/Indexes
D. Diagnosis (Signs and Symptoms)
E. Warning and Common Messages
F. Steps to Repair
G. Suggestions

Good Luck!

Very Best Regards,

Razzak.


Reply via email to