Is there no solution workaround for newspaper LNs in unalterable env. UNEXPECTED_STATE

I'm for 5.0.43 and meet the same problem mentioned in The Berkeley DB Java Edition package: BDB I Library Version 11.2.5.0 (version 5.0.55) change log

Fixed a bug that caused an exception similar to the following, when opening a read-only environment. Happened in certain circumstances, when a clean shutdown (final control point) were made when the environment last used by a process of read-write.


I have here are 2 questions:


(1) I want to know if there is no work around to this problem without having to upgrade the BDB-I.


(2) want to ensure that we will not compatible from data if we upgrade to the latest version


Thanks for your help.

It is a transitory problem when opening in read-only mode.  It does not cause corruption or a compatibility issue.

If you open the environment of reading / writing and perform a normal shutdown (Environment.close), then it should be possible to open the environment of read-only again.

However, it is possible that it could happen again if the process of reading / writing closes without calling Environment.close.  The only way to guarantee that it won't happen again is to always call Environment.close in the process of reading / writing before you open it read-only, or upgrade to the latest version of 5 I.

-mark

Tags: Database

Similar Questions

Maybe you are looking for