Re: Data integrity problems...

Martin,

This can happen after a repair is run.  The repair tool will mark 
records and the index will update the next time Mckoi starts.  When the 
index is updated, you will see this message in the debug log and it's 
recommended you check the data in these tables.

If you see these messages frequently, it usually indicates that either 
you have turned journaling off (by setting io_safety_level=1) and are 
not closing the database cleanly, or you have multiple JVM's accessing 
the Mckoi data files at once.  These messages basically happen because 
the initial data scan has found some inconsistencies with the index and 
needs to correct them.  If this has started recently, is there anything 
you can think of that changed in your operation of Mckoi?

Toby.


Martin Cordova wrote:

> Toby, what can I do to fix this error, I am seeing lots of these in
> debug.log when McKoi starts. I already did a db-repair, reported no
> problems, finished OK. Then started the server.
> 
> % Starting Database Server
> 
>>com.mckoi.database.V2MasterTableDataSource ( lvl: 40 )
> 
>   Inconsistant: Row is indexed but marked as removed or uncommitted.
> 
>>com.mckoi.database.V2MasterTableDataSource ( lvl: 40 )
> 
>   Row: 12328 Type: 3 Table: ENVASADOS.cpe
> 
>>com.mckoi.database.V2MasterTableDataSource ( lvl: 40 )
> 
>   Inconsistant: Row is indexed but marked as removed or uncommitted.
> 
>>com.mckoi.database.V2MasterTableDataSource ( lvl: 40 )
> 
>   Row: 12329 Type: 3 Table: ENVASADOS.cpe
> ....
> 
> There are dozens of messages like these.
> 
> Best regards,
> Martin Cordova



---------------------------------------------------------------
Mckoi SQL Database mailing list  http://www.mckoi.com/database/
To unsubscribe, send a message to [email protected]