Log file limits

Log filenames and sizes impose a limit on how long databases may be
used in a Berkeley DB database environment. It is quite unlikely that an
application will reach this limit; however, if the limit is reached,
the Berkeley DB environment's databases must be dumped and reloaded.

The log filename consists of log. followed by 10 digits, with
a maximum of 2,000,000,000 log files. Consider an application performing
6000 transactions per second for 24 hours a day, logged into 10MB log
files, in which each transaction is logging approximately 500 bytes of data.
The following calculation:

(10 * 2^20 * 2000000000) / (6000 * 500 * 365 * 60 * 60 * 24) = ~221

indicates that the system will run out of log filenames in roughly 221
years.

There is no way to reset the log filename space in Berkeley DB. If your
application is reaching the end of its log filename space, you must do
the following:

Reset the database's log sequence numbers (see the -r option
to the db_load utility for more information).

Remove all of the log files from the database environment. (This is the
only situation in which all the log files are removed from an environment;
in all other cases, at least a single log file is retained.)