This code:

def _openDBEnv(cachesize):
    e = db.DBEnv()
    if cachesize is not None:
        if cachesize >= 20480:
            e.set_cachesize(0, cachesize)
        else:
            raise error, "cachesize must be >= 20480"
    e.set_lk_detect(db.DB_LOCK_DEFAULT)
    e.open('.', db.DB_PRIVATE | db.DB_CREATE | db.DB_THREAD | db.DB_INIT_LOCK | db.DB_INIT_MPOOL)
    return e

causes Berkeley DB to read the DB_CONFIG file from the current directory, which may have unexpected side effects.  Unfortunately, Berkeley DB still reads ./DB_CONFIG even if the first argument to DBEnv.open() is None/NULL, so the only way to suppress this behavior seems a non-existing or known-to-by-empty directory (such as "/var/empty").

This is a standard Berkeley DB behavior. Can I suggest you to report this "issue" to Oracle forums?

http://docs.oracle.com/cd/E17276_01/html/programmer_reference/env_db_config.html

https://forums.oracle.com/forums/forum.jspa?forumID=271

Closing as "invalid". if you disagree, please reopen.