From 780b92ada9afcf1d58085a83a0b9e6bc982203d1 Mon Sep 17 00:00:00 2001 From: Lorry Tar Creator Date: Tue, 17 Feb 2015 17:25:57 +0000 Subject: Imported from /home/lorry/working-area/delta_berkeleydb/db-6.1.23.tar.gz. --- docs/programmer_reference/log_limits.html | 78 +++++++++++++++++++------------ 1 file changed, 48 insertions(+), 30 deletions(-) (limited to 'docs/programmer_reference/log_limits.html') diff --git a/docs/programmer_reference/log_limits.html b/docs/programmer_reference/log_limits.html index 54f523d6..f29e3e44 100644 --- a/docs/programmer_reference/log_limits.html +++ b/docs/programmer_reference/log_limits.html @@ -14,7 +14,7 @@

Library Version 11.2.5.3

Library Version 12.1.6.1

@@ -22,9 +22,7 @@ - +

Prev	Chapter 17. - The Logging Subsystem -	Chapter 17. The Logging Subsystem	Next

@@ -38,32 +36,54 @@

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:

+ 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:

+ 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: +

Archive your databases as if to prepare for catastrophic failure (see -Database and log file archival -for more information).
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.)
Restart your application.
+ Archive your databases as if to prepare for + catastrophic failure (see Database and log file + archival for more + information). +
+ 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.) +
+ Restart your application. +

@@ -82,9 +102,7 @@ in all other cases, at least a single log file is retained.) Home - Chapter 18. - The Memory Pool Subsystem - + Chapter 18. The Memory Pool Subsystem -- cgit v1.2.1