Hi Kiran,

This assertion failure indicates that Berkeley DB's cache data
structures in shared memory have become inconsistent. In particular,
that page eviction priority in hash bucket in the cache is incorrect.

I don't know of any bugs in DB 4.3 that cause this assertion to fire,
but this kind of thing would probably go unnoticed in a release build
with assertions disabled (the only consequence of this problem is that
the wrong page might be selected for eviction).

Can you tell me more about what the application is doing when this
problem occurs? Also, is it possible to run the same application
against version 4.5 to see whether it has been fixed (the code in
question had considerable work to support multiversion concurrency
control).

Regards,
Michael Cahill, Oracle.