What do I do in Berkeley DB XML when I get an error such as “Lock table is out of available locker entries,” or “Lock table is out of locks?
In Berkeley DB terminlogy, a “locker” is something like a database, a transaction or a cursor. Berkeley DB “locks” are owned by a “locker” and generally lock pages of a database. There are other kinds of locks. Translating to BDB XML, lockers are associated with Containers, which own database handles, as well as documents, which may own cursors. Lockers and locks only exist if you are creating and using a Berkeley DB environment, and they exist even if your application does not use transactions, in order to support some level of concurrent access. You can change the number of lockers by (re)creating the environment, using the proper arguments: C++: DbEnv::set_lk_max_lockers(u_int32_t) DbEnv::set_lk_max_locks(u_int32_t) Java: EnvironmentConfig.setMaxLockers(int) EnvironmentConfig.setMaxLocks(int) These must be set *before* you create your environment using the open method. The obvious question is “what number should I use?” For lockers, you should use at least the maximum number of simu
Related Questions
- What do I do in Berkeley DB XML when I get an error such as "Lock table is out of available locker entries," or "Lock table is out of locks?
- What exactly is a Berkeley DB database? Is it the same as a relational (SQL) database table?
- Can the users not specify primary key when create a table in Berkeley DB 11gR2?
