-I=Berkeley DB Reference Guide: Logging Subsystem[P7

Berkeley DB Reference Guide: Logging Subsystem



%

Log file limits



CLog file sizes impose a time limit on the length of time a databaseCmay be accessed under transaction protection, before it needs to be€dumped and reloaded (see db_dump and db_load).AUnfortunately, the limits are potentially difficult to calculate.

@The log file name consists of log. followed by 10 digits,*with a maximum of 2,000,000,000 log files.DConsider an application performing 3000 transactions per second, forB24 hours a day, logged into 10Mb log files, where each transaction=is logging approximately 500 bytes of data. The calculation:]

;indicates that the system will run out of log file names inroughly 443 years.

@There is no way to reset the log file name space in Berkeley DB.CIf your application is reaching the end of its log file name space, you should:

    L

  1. Archive your databases as if to prepare for catastrophic failure (seeMdb_archive for more information).6

  2. Dump and re-load all your databases (see|db_dump and db_load for more information).E

  3. Remove all of the log files from the database environment (seeMdb_archive for more information).!

  4. Restart your applications.
Aÿÿ