I have an application that is using Berkeley DB 4.5.20 under Windows
2003.
One particular database has around 200,000 records and regularly
creates a cursor, positions at starting points and reads records until
the records go out of scope.
In one particular instance the application reads a set of records that
amount to over 50,000 records. Usually all is OK, but every few days
the read starts returning only exactly 40,000 records for the same
set. This continues to occur until the application is restarted and
the environment renewed. When the application is restarted the correct
number of records is returned.
Can anybody suggest what could be causing this error?
Gerard
