Hang on Db Rename On A Subdatabase When the Environment Is Configured with Locking, and without Transactions and Logging
(Doc ID 396492.1)
Last updated on JANUARY 08, 2020
Applies to:Berkeley DB - Version 4.2 to 4.5
Information in this document applies to any platform.
The application hangs when trying to rename a subdatabase (a logical database stored in a physical file along with other databases). The environment is configured for Locking but without Transactions and Logging.
After the 4.1 release __db_dbopen was dropped. Things were reffactored as to have __db_open_pp and db_open. This implied that internally generated DB handles were not created with DB_THREAD in threaded environments.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document