Database version 2.3.10 Corruption after query during insert.

Question

I am using DBXML Version 2.3.10. We recently discovered a problem when querying DBXML while inserting (concurrent). Below are the events that occur. I am in the process of getting more details, but I wanted post this in an effort to see what areas I need to concentrate on.
1. Begin inserting XML docs into DBXML. This process also used our unique ID to add a row into Berkeley DB. The insert rate is quite fast. We are real happy with this. We don't see any problems before we query.
2. We submit a query in another thread, as insertion continues. Some time after, we get an exception (FILE_NOTFOUND). However, insertion still seems to be ok, as well as query.
3. At some point thereafter when we run another query, we will encounter an uncaught C++ exception:
Uncaught exception from C++ API
com.sleepycat.dbxml.XmlException: Uncaught exception from C++ API, errcode = INTERNAL_ERROR at com.sleepycat.dbxml.dbxml_javaJNI.XmlContainer.putDocument__SWIG_2(Native Method) at com.sleepycat.dbxml.XmlContainer.putDocument XmlContainer.java:373)
From this point forward, insert fails as well as query. If I try to run a lookupindex()query the database in DBXML Shell, I get DB_PAGE_NOT_FOUND exception. The database is essentially corrupt. This data was collected at a test excercise, and I am desperately trying to recover the data.
If I back off to version 2.2.13, there are no problems. From some other threads of the forum, I noted increasing cache and locks might be helpful. Here are the current settings from the DB_CONFIG file:
set_cachesize 0 250000000 1
set_lk_max_lockers 100000
set_lk_max_locks 100000
set_lk_max_objects 100000
If anyone can offer any other suggestion, we would greatly appreciate it. Version 2.3.10 offers query interrupt/timeout, as well as excellent insert and query performance. We really cannot afford to back off to 2.2.13.
Anthony

Answer 1

Hi Anthony,
I get execeptions such as "configured environment flags incompatible with >existing environment"The error message above suggests an old environment existed prior to your creating the new one (for the Concurrent Data Store). You may want to remove/rename your config flags and just start out with the minimum flags to configure CDS. If there are old environment files delete/remove them (__db.00#).
EnvironmentConfig ec = new EnvironmentConfig
ec.setInitializeCDB(true);
ec.setAllowCreate(true);
ec.setInitializeCache(true);
You don't want to set flags that deal with transactions or the transactional lock system. Therefore do not call setInitializeLocking for example.
For Berkeley DB XML, it is recommeded that you turn on the lockAllDatabases flag:
http://www.oracle.com/technology/documentation/berkeley-db/db/java/com/sleepycat/db/EnvironmentConfig.html#setCDBLockAllDatabases(boolean)
For more information about the Concurrent Data Store:
http://www.oracle.com/technology/documentation/berkeley-db/db/ref/cam/intro.html
Ron Cohen
null