NNAAMMEE db_log - log management functions SSYYNNOOPPSSIISS ##iinncclluuddee <> iinntt lloogg__ooppeenn((ccoonnsstt cchhaarr **ddiirr,, uu__iinntt3322__tt ffllaaggss,, iinntt mmooddee,, DDBB__EENNVV **ddbbeennvv,, DDBB__LLOOGG ****rreeggiioonnpp));; iinntt lloogg__cclloossee((DDBB__LLOOGG **llooggpp));; iinntt lloogg__fflluusshh((DDBB__LLOOGG **llooggpp,, ccoonnsstt DDBB__LLSSNN **llssnn));; iinntt lloogg__ggeett((DDBB__LLOOGG **llooggpp,, DDBB__LLSSNN **llssnn,, DDBBTT **ddaattaa,, uu__iinntt3322__tt ffllaaggss));; iinntt lloogg__ccoommppaarree((ccoonnsstt DDBB__LLSSNN **llssnn00,, ccoonnsstt DDBB__LLSSNN **llssnn11));; iinntt lloogg__ffiillee((DDBB__LLOOGG **llooggpp,, ccoonnsstt DDBB__LLSSNN **llssnn,, cchhaarr **nnaammeepp,, ssiizzee__tt lleenn));; iinntt lloogg__ppuutt((DDBB__LLOOGG **llooggpp,, DDBB__LLSSNN **llssnn,, ccoonnsstt DDBBTT **ddaattaa,, uu__iinntt3322__tt ffllaaggss));; iinntt lloogg__uunnlliinnkk((ccoonnsstt cchhaarr **ddiirr,, iinntt ffoorrccee,, DDBB__EENNVV **));; iinntt lloogg__aarrcchhiivvee((DDBB__LLOOGG **llooggpp,, cchhaarr ****lliisstt[[]],, uu__iinntt3322__tt ffllaaggss,, vvooiidd **((**ddbb__mmaalllloocc))((ssiizzee__tt))));; iinntt lloogg__rreeggiisstteerr((DDBB__LLOOGG **llooggpp,, ccoonnsstt DDBB **ddbbpp,, ccoonnsstt cchhaarr **nnaammee,, DDBBTTYYPPEE ttyyppee,, uu__iinntt3322__tt **ffiiddpp));; iinntt lloogg__uunnrreeggiisstteerr((DDBB__LLOOGG **llooggpp,, uu__iinntt3322__tt ffiidd));; iinntt lloogg__ssttaatt((DDBB__LLOOGG **llooggpp,, DDBB__LLOOGG__SSTTAATT ****sspppp,, vvooiidd **((**ddbb__mmaalllloocc))((ssiizzee__tt))));; DDEESSCCRRIIPPTTIIOONN The DB library is a family of groups of functions that provides a modular programming interface to transactions and record-oriented file access. The library includes support for transactions, locking, logging and file page caching, as well as various indexed access methods. Many of the functional groups (e.g., the file page caching functions) are useful independent of the other DB func- tions, although some functional groups are explicitly based on other functional groups (e.g., transactions and logging). For a general description of the DB package, see _d_b___i_n_t_r_o(3). This manual page describes the specific details of the log manager. These functions provide a general-purpose logging facility sufficient for transaction management. Logs can be shared by multiple processes. The DB transaction log is represented by a directory con- taining a set of files. The log is a record-oriented, append-only file, with records identified and accessed via _D_B___L_S_N's (database log sequence numbers). DB_LSN's are returned on each _l_o_g___p_u_t operation, and only those DB_LSN's returned by _l_o_g___p_u_t can later be used to retrieve records from the log. _l_o_g___o_p_e_n The _l_o_g___o_p_e_n function copies a pointer, to the log identi- fied by the ddiirreeccttoorryy _d_i_r, into the memory location refer- enced by _r_e_g_i_o_n_p. If the _d_b_e_n_v argument to _l_o_g___o_p_e_n was initialized using _d_b___a_p_p_i_n_i_t, _d_i_r is interpreted as described by _d_b___a_p_p_i_n_i_t(3). Otherwise, if _d_i_r is not NULL, it is interpreted relative to the current working directory of the process. If _d_i_r is NULL, the following environment variables are checked in order: ``TMPDIR'', ``TEMP'', and ``TMP''. If one of them is set, log files are created relative to the direc- tory it specifies. If none of them are set, the first possible one of the following directories is used: _/_v_a_r_/_t_m_p, _/_u_s_r_/_t_m_p, _/_t_e_m_p, _/_t_m_p, _C_:_/_t_e_m_p and _C_:_/_t_m_p. All files associated with the log are created in this directory. This directory must already exist when log_open is called. If the log already exists, the pro- cess must have permission to read and write the existing files. If the log does not already exist, it is option- ally created and initialized. If the log region is being created and log files are already present, the log files are ``recovered'' and sub- sequent log writes are appended to the end of the log. The log is stored in one or more files in the specified directory. Each file is named using the format log.NNNNN where ``NNNNN'' is the sequence number of the file within the log. The _f_l_a_g_s and _m_o_d_e arguments specify how files will be opened and/or created when they don't already exist. The flags value is specified by oorr'ing together one or more of the following values: DB_CREATE Create any underlying files, as necessary. If the files do not already exist and the DB_CREATE flag is not specified, the call will fail. DB_THREAD Cause the DB_LOG handle returned by the _l_o_g___o_p_e_n function to be useable by multiple threads within a single address space, i.e., to be ``free-threaded''. All files created by the log subsystem are created with mode _m_o_d_e (as described in _c_h_m_o_d(2)) and modified by the process' umask value at the time of creation (see _u_m_a_s_k(2)). The group ownership of created files is based on the system and directory defaults, and is not further specified by DB. The logging subsystem is configured based on the _d_b_e_n_v argument to _l_o_g___o_p_e_n, which is a pointer to a structure of type DB_ENV (typedef'd in ). Applications will nor- mally use the same DB_ENV structure (initialized by _d_b___a_p_p_i_n_i_t(3)), as an argument to all of the subsystems in the DB package. References to the DB_ENV structure are maintained by DB, so it may not be discarded until the last close function, corresponding to an open function for which it was an argument, has returned. In order to ensure compatibility with future releases of DB, all fields of the DB_ENV structure that are not explicitly set should be initial- ized to 0 before the first time the structure is used. Do this by declaring the structure external or static, or by calling the C library routine _b_z_e_r_o(3) or _m_e_m_s_e_t(3). The fields of the DB_ENV structure used by _l_o_g___o_p_e_n are described below. If _d_b_e_n_v is NULL or any of its fields are set to 0, defaults appropriate for the system are used where possible. The following fields in the DB_ENV structure may be ini- tialized before calling _l_o_g___o_p_e_n: void *(*db_errcall)(char *db_errpfx, char *buffer); FILE *db_errfile; const char *db_errpfx; int db_verbose; The error fields of the DB_ENV behave as described for _d_b___a_p_p_i_n_i_t(3). u_int32_t lg_max; The maximum size of a single file in the log. Because DB_LSN file offsets are unsigned 4-byte val- ues, _l_g___m_a_x may not be larger than the maximum unsigned 4-byte value. If _l_g___m_a_x is 0, a default value is used. See the section "LOG FILE LIMITS" below, for further information. The _l_o_g___o_p_e_n function returns the value of _e_r_r_n_o on fail- ure and 0 on success. _l_o_g___c_l_o_s_e The _l_o_g___c_l_o_s_e function closes the log specified by the _l_o_g_p argument. In addition, if the _d_i_r argument to _l_o_g___o_p_e_n was NULL and _d_b_e_n_v was not initialized using _d_b___a_p_p_i_n_i_t, all files cre- ated for this shared region will be removed, as if _l_o_g___u_n_l_i_n_k were called. When multiple threads are using the DB_LOG handle concur- rently, only a single thread may call the _l_o_g___c_l_o_s_e func- tion. The _l_o_g___c_l_o_s_e function returns the value of _e_r_r_n_o on fail- ure and 0 on success. _l_o_g___f_l_u_s_h The _l_o_g___f_l_u_s_h function guarantees that all log records whose LSNs are less than or equal to the _l_s_n parameter have been written to disk. If _l_s_n is NULL, all records in the log are flushed. The _l_o_g___f_l_u_s_h function returns the value of _e_r_r_n_o on fail- ure and 0 on success. _l_o_g___g_e_t The _l_o_g___g_e_t function implements a cursor inside of the log, retrieving records from the log according to the _l_s_n and _f_l_a_g_s parameters. The data field of the _d_a_t_a structure is set to the record retrieved and the size field indicates the number of bytes in the record. See _d_b___d_b_t(3) for a description of other fields in the _d_a_t_a structure. WWhheenn mmuullttiippllee tthhrreeaaddss aarree uussiinngg tthhee rreettuurrnneedd DDBB__LLOOGG hhaannddllee ccoonnccuurrrreennttllyy,, eeiitthheerr tthhee DDBB__DDBBTT__MMAALLLLOOCC oorr DDBB__DDBBTT__UUSSEERRMMEEMM ffllaaggss mmuusstt bbee ssppeecciiffiieedd ffoorr aannyy DDBBTT uusseedd ffoorr ddaattaa rreettrriieevvaall.. The _f_l_a_g_s parameter must be set to exactly one of the fol- lowing values: DB_CHECKPOINT The last record written with the DB_CHECKPOINT flag specified to the _l_o_g___p_u_t function is returned in the _d_a_t_a argument. The _l_s_n argument is overwritten with the DB_LSN of the record returned. If no record has been previously written with the DB_CHECKPOINT flag specified, the first record in the log is returned. If the log is empty the _l_o_g___g_e_t function will return DB_NOTFOUND. DB_FIRST The first record from any of the log files found in the log directory is returned in the _d_a_t_a argument. The _l_s_n argument is overwritten with the DB_LSN of the record returned. If the log is empty the _l_o_g___g_e_t function will return DB_NOTFOUND. DB_LAST The last record in the log is returned in the _d_a_t_a argument. The _l_s_n argument is overwritten with the DB_LSN of the record returned. If the log is empty, the _l_o_g___g_e_t function will return DB_NOTFOUND. DB_NEXT The current log position is advanced to the next record in the log and that record is returned in the _d_a_t_a argument. The _l_s_n argument is overwritten with the DB_LSN of the record returned. If the pointer has not been initialized via DB_FIRST, DB_LAST, DB_SET, DB_NEXT, or DB_PREV, _l_o_g___g_e_t will return the first record in the log. If the last log record has already been returned or the log is empty, the _l_o_g___g_e_t function will return DB_NOTFOUND. If the log was opened with the DB_THREAD flag set, calls to _l_o_g___g_e_t with the DB_NEXT flag set will return EINVAL. DB_PREV The current log position is moved to the previous record in the log and that record is returned in the _d_a_t_a argument. The _l_s_n argument is overwritten with the DB_LSN of the record returned. If the pointer has not been initialized via DB_FIRST, DB_LAST, DB_SET, DB_NEXT, or DB_PREV, _l_o_g___g_e_t will return the last record in the log. If the first log record has already been returned or the log is empty, the _l_o_g___g_e_t function will return DB_NOTFOUND. If the log was opened with the DB_THREAD flag set, calls to _l_o_g___g_e_t with the DB_PREV flag set will return EINVAL. DB_CURRENT Return the log record currently referenced by the log. If the log pointer has not been initialized via DB_FIRST, DB_LAST, DB_SET, DB_NEXT, or DB_PREV, or if the log was opened with the DB_THREAD flag set, _l_o_g___g_e_t will return EINVAL. DB_SET Retrieve the record specified by the _l_s_n argument. If the specified DB_LSN is invalid (e.g., does not appear in the log) _l_o_g___g_e_t will return EINVAL. Otherwise, the _l_o_g___g_e_t function returns the value of _e_r_r_n_o on failure and 0 on success. _l_o_g___c_o_m_p_a_r_e The _l_o_g___c_o_m_p_a_r_e function allows the caller to compare two DB_LSN's. _L_o_g___c_o_m_p_a_r_e returns 0 if the two DB_LSN's are equal, 1 if _l_s_n_0 is greater than _l_s_n_1, and -1 if _l_s_n_0 is less than _l_s_n_1. _l_o_g___f_i_l_e The _l_o_g___f_i_l_e function maps DB_LSN's to file names. The _l_o_g___f_i_l_e function copies the name of the file containing the record named by _l_s_n into the memory location refer- enced by _n_a_m_e_p. (This mapping of DB_LSN to file is needed for database administration. For example, a transaction manager typically records the earliest DB_LSN needed for restart, and the database administrator may want to archive log files to tape when they contain only DB_LSN's before the earliest one needed for restart.) The _l_e_n argument is the length of the _n_a_m_e_p buffer in bytes. If _n_a_m_e_p is too short to hold the file name, _l_o_g___f_i_l_e will return ENOMEM. Note, as described above, log file names are quite short, on the order of 10 charac- ters. The _l_o_g___f_i_l_e function returns the value of _e_r_r_n_o on fail- ure and 0 on success. _l_o_g___p_u_t The _l_o_g___p_u_t function appends records to the log. The DB_LSN of the put record is returned in the _l_s_n parameter. The _f_l_a_g_s parameter may be set to one of the following values: DB_CHECKPOINT The log should write a checkpoint record, recording any information necessary to make the log structures recoverable after a crash. DB_CURLSN The DB_LSN of the next record to be put is returned in the _l_s_n parameter. DB_FLUSH The log is forced to disk after this record is writ- ten, guaranteeing that all records with DB_LSNs less than or equal to the one being put are on disk before this function returns (this function is most often used for a transaction commit, see _d_b___t_x_n(3)). The caller is responsible for providing any necessary structure to _d_a_t_a. (For example, in a write-ahead logging protocol, the application must understand what part of _d_a_t_a is an operation code, what part is redo information, and what part is undo information. In addition, most transaction managers will store in _d_a_t_a the DB_LSN of the previous log record for the same transaction, to support chaining back through the transaction's log records during undo.) The _l_o_g___p_u_t function returns the value of _e_r_r_n_o on failure and 0 on success. _l_o_g___u_n_l_i_n_k The _l_o_g___u_n_l_i_n_k function destroys the log region identified by the directory _d_i_r, removing all files used to implement the log region. (The log files themselves and the direc- tory _d_i_r are not removed.) If there are processes that have called _l_o_g___o_p_e_n without calling _l_o_g___c_l_o_s_e (i.e., there are processes currently using the log region), _l_o_g___u_n_l_i_n_k will fail without further action, unless the force flag is set, in which case _l_o_g___u_n_l_i_n_k will attempt to remove the log region files regardless of any processes still using the log region. The result of attempting to forcibly destroy the region when a process has the region open is unspecified. Pro- cesses using a shared memory region maintain an open file descriptor for it. On UNIX systems, the region removal should succeed and processes that have already joined the region should continue to run in the region without change, however processes attempting to join the log region will either fail or attempt to create a new region. On other systems, e.g., WNT, where the _u_n_l_i_n_k(2) system call will fail if any process has an open file descriptor for the file, the region removal will fail. In the case of catastrophic or system failure, database recovery must be performed (see _d_b___r_e_c_o_v_e_r(1) or the DB_RECOVER and DB_RECOVER_FATAL flags to _d_b___a_p_p_i_n_i_t(3)). Alternatively, if recovery is not required because no database state is maintained across failures, it is possi- ble to clean up a log region by removing all of the files in the directory specified to the _l_o_g___o_p_e_n function, as log region files are never created in any directory other than the one specified to _l_o_g___o_p_e_n. Note, however, that this has the potential to remove files created by the other DB subsystems in this database environment. The _l_o_g___u_n_l_i_n_k function returns the value of _e_r_r_n_o on failure and 0 on success. _l_o_g___a_r_c_h_i_v_e The _l_o_g___a_r_c_h_i_v_e function creates a NULL-terminated array of log or database file names and copies a pointer to them into the user-specified memory location _l_i_s_t. By default, _l_o_g___a_r_c_h_i_v_e returns the names of all of the log files that are no longer in use (e.g., no longer involved in active transactions), and that may be archived for catastrophic recovery and then removed from the sys- tem. If there were no file names to return, _l_i_s_t will be set to NULL. Arrays of log file names are created in allocated memory. If _d_b___m_a_l_l_o_c is non-NULL, it is called to allocate the memory, otherwise, the library function _m_a_l_l_o_c(3) is used. The function _d_b___m_a_l_l_o_c must match the calling conventions of the _m_a_l_l_o_c(3) library routine. Regardless, the caller is responsible for deallocating the returned memory. To deallocate the returned memory, free each returned memory pointer; pointers inside the memory do not need to be individually freed. The _f_l_a_g_s argument is specified by oorr'ing together one or more of the following values: DB_ARCH_ABS All pathnames are returned as absolute pathnames, instead of relative to the database home directory. DB_ARCH_DATA Return the database files that need to be archived in order to recover the database from catastrophic fail- ure. If any of the database files have not been accessed during the lifetime of the current log files, _l_o_g___a_r_c_h_i_v_e will not include them in this list. It is also possible that some of the files referenced in the log have since been deleted from the system. DB_ARCH_LOG Return all the log file names regardless of whether or not they are in use. The DB_ARCH_DATA and DB_ARCH_LOG flags are mutually exclu- sive. The _l_o_g___a_r_c_h_i_v_e function returns the value of _e_r_r_n_o on failure and 0 on success. The _l_o_g___a_r_c_h_i_v_e function is the underlying function used by the _d_b___a_r_c_h_i_v_e(1) utility. See the source code for the _d_b___a_r_c_h_i_v_e utility for an example of using _l_o_g___a_r_c_h_i_v_e in a UNIX environment. See the _d_b___a_r_c_h_i_v_e(1) manual page for more information on database archival procedures. _l_o_g___r_e_g_i_s_t_e_r The _l_o_g___r_e_g_i_s_t_e_r function registers a file name with the log manager and copies a file identification number into the memory location referenced by _f_i_d_p. This file identi- fication number should be used in all subsequent log mes- sages that refer to operations on this file. The log man- ager records all file name to file identification number mappings at each checkpoint so that a recovery process can identify the file to which a record in the log refers. The _l_o_g___r_e_g_i_s_t_e_r function is called when an access method registers the open of a file. The _d_b_p parameter should be a pointer to the DB structure which is being returned by the access method. The _t_y_p_e parameter should be one of the DB types specified in _d_b___o_p_e_n(3), e.g., DB_HASH. The _l_o_g___r_e_g_i_s_t_e_r function returns the value of _e_r_r_n_o on failure and 0 on success. _l_o_g___u_n_r_e_g_i_s_t_e_r The _l_o_g___u_n_r_e_g_i_s_t_e_r function disassociates the file name to file identification number mapping for the file identifi- cation number specified by the _f_i_d parameter. The file identification number may then be reused. The _l_o_g___u_n_r_e_g_i_s_t_e_r function returns the value of _e_r_r_n_o on failure and 0 on success. _l_o_g___s_t_a_t The _l_o_g___s_t_a_t function creates a statistical structure and copies a pointer to it into the user-specified memory location. Statistical structure are created in allocated memory. If _d_b___m_a_l_l_o_c is non-NULL, it is called to allocate the mem- ory, otherwise, the library function _m_a_l_l_o_c(3) is used. The function _d_b___m_a_l_l_o_c must match the calling conventions of the _m_a_l_l_o_c(3) library routine. Regardless, the caller is responsible for deallocating the returned memory. To deallocate the returned memory, free each returned memory pointer; pointers inside the memory do not need to be individually freed. The log region statistics are stored in a structure of type DB_LOG_STAT (typedef'd in ). The following DB_LOG_STAT fields will be filled in: u_int32_t st_magic; The magic number that identifies a file as a log file. u_int32_t st_version; The version of the log file type. u_int32_t st_refcnt; The number of references to the region. u_int32_t st_regsize; The size of the region. int st_mode; The mode of any created log files. u_int32_t st_lg_max; The maximum size of any individual file comprising the log. u_int32_t st_w_mbytes; The number of megabytes written to this log. u_int32_t st_w_bytes; The number of bytes over and above _s_t___w___m_b_y_t_e_s writ- ten to this log. u_int32_t st_wc_mbytes; The number of megabytes written to this log since the last checkpoint. u_int32_t st_wc_bytes; The number of bytes over and above _s_t___w_c___m_b_y_t_e_s writ- ten to this log since the last checkpoint. u_int32_t st_cur_file; The current log file number. u_int32_t st_cur_offset; The byte offset in the current log file. u_int32_t st_region_wait; The number of times that a thread of control was forced to wait before obtaining the region lock. u_int32_t st_region_nowait; The number of times that a thread of control was able to obtain the region lock without waiting. LLOOGG FFIILLEE LLIIMMIITTSS Log file sizes impose a time limit on the length of time a database may be accessed under transaction protection, before it needs to be dumped and reloaded (see _d_b___d_u_m_p_(_3_) and _d_b___l_o_a_d_(_3_)_)_. Unfortunately, the limits are poten- tially difficult to calculate. The log file name consists of "log." followed by 5 digits, resulting in a maximum of 99,999 log files. Consider an application performing 600 transactions per second, for 15 hours a day, logged into 10Mb log files, where each trans- action is logging approximately 100 bytes of data. The calculation: (10 * 2^20 * 99999) / (600 * 60 * 60 * 15 * 100) = 323.63 indicates that the system will run out of log file space in roughly 324 days. If we increase the maximum size of the files from 10Mb to 100Mb, the same calculation indi- cates that the application will run out of log file space in roughly 9 years. There is no way to reset the log file name space in Berke- ley DB. If your application is reaching the end of its log file name space, you should: 1. Archive your databases as if to prepare for catas- trophic failure (see _d_b___a_r_c_h_i_v_e(1) for more informa- tion). 2. Dump and re-load aallll your databases (see _d_b___d_u_m_p(1) and _d_b___l_o_a_d(1) for more information). 3. Remove all of the log files from the database envi- ronment (see _d_b___a_r_c_h_i_v_e(1) for more information). 4. Restart your applications. EENNVVIIRROONNMMEENNTT VVAARRIIAABBLLEESS The following environment variables affect the execution of _d_b___l_o_g: DB_HOME If the _d_b_e_n_v argument to _l_o_g___o_p_e_n was initialized using _d_b___a_p_p_i_n_i_t, the environment variable DB_HOME may be used as the path of the database home for the interpretation of the _d_i_r argument to _l_o_g___o_p_e_n, as described in _d_b___a_p_p_i_n_i_t(3). Specifically, _l_o_g___o_p_e_n is affected by the configuration string value of DB_LOG_DIR. TMPDIR If the _d_b_e_n_v argument to _l_o_g___o_p_e_n was NULL or not initialized using _d_b___a_p_p_i_n_i_t, the environment vari- able TMPDIR may be used as the directory in which to create the log, as described in the _l_o_g___o_p_e_n section above. EERRRROORRSS The _l_o_g___o_p_e_n function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: atoi(3), close(2), db_version(3), fcntl(2), fflush(3), log_close(3), log_unlink(3), lseek(2), mal- loc(3), memcpy(3), memset(3), mmap(2), munmap(2), open(2), opendir(3), read(2), readdir(3), realloc(3), sig- fillset(3), sigprocmask(2), stat(2), strchr(3), strcpy(3), strdup(3), strerror(3), strlen(3), strncmp(3), unlink(2), and write(2). In addition, the _l_o_g___o_p_e_n function may fail and return _e_r_r_n_o for the following conditions: [EAGAIN] The shared memory region was locked and (repeatedly) unavailable. [EINVAL] An invalid flag value or parameter was specified. The DB_THREAD flag was specified and spinlocks are not implemented for this architecture. The specified file size was too large. The _l_o_g___c_l_o_s_e function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: close(2), fcntl(2), fflush(3), munmap(2), and strerror(3). The _l_o_g___f_l_u_s_h function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: close(2), fcntl(2), fflush(3), fsync(2), lseek(2), malloc(3), memcpy(3), memset(3), open(2), sig- fillset(3), sigprocmask(2), stat(2), strcpy(3), strdup(3), strerror(3), strlen(3), unlink(2), and write(2). In addition, the _l_o_g___f_l_u_s_h function may fail and return _e_r_r_n_o for the following conditions: [EINVAL] An invalid flag value or parameter was specified. The _l_o_g___g_e_t function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: atoi(3), close(2), fcntl(2), fflush(3), lseek(2), malloc(3), memcpy(3), memset(3), open(2), opendir(3), read(2), readdir(3), realloc(3), sig- fillset(3), sigprocmask(2), stat(2), strchr(3), strcpy(3), strdup(3), strerror(3), strlen(3), strncmp(3), and unlink(2). In addition, the _l_o_g___g_e_t function may fail and return _e_r_r_n_o for the following conditions: [EINVAL] An invalid flag value or parameter was specified. The DB_FIRST flag was specified and no log files were found. The _l_o_g___f_i_l_e function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: close(2), fcntl(2), fflush(3), malloc(3), mem- cpy(3), memset(3), open(2), sigfillset(3), sigprocmask(2), stat(2), strcpy(3), strdup(3), strerror(3), strlen(3), and unlink(2). In addition, the _l_o_g___f_i_l_e function may fail and return _e_r_r_n_o for the following conditions: [ENOMEM] The supplied buffer was too small to hold the log file name. The _l_o_g___p_u_t function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: close(2), fcntl(2), fflush(3), fsync(2), lseek(2), malloc(3), memcpy(3), memset(3), open(2), sig- fillset(3), sigprocmask(2), stat(2), strcpy(3), strdup(3), strerror(3), strlen(3), time(3), unlink(2), and write(2). In addition, the _l_o_g___p_u_t function may fail and return _e_r_r_n_o for the following conditions: [EINVAL] An invalid flag value or parameter was specified. The record to be logged is larger than the maximum log record. The _l_o_g___u_n_l_i_n_k function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: close(2), fcntl(2), fflush(3), malloc(3), mem- cpy(3), memset(3), mmap(2), munmap(2), open(2), sig- fillset(3), sigprocmask(2), stat(2), strcpy(3), strdup(3), strerror(3), strlen(3), and unlink(2). In addition, the _l_o_g___u_n_l_i_n_k function may fail and return _e_r_r_n_o for the following conditions: [EBUSY] The shared memory region was in use and the force flag was not set. The _l_o_g___a_r_c_h_i_v_e function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: close(2), fcntl(2), fflush(3), getcwd(3), log_compare(3), log_get(3), malloc(3), memcpy(3), mem- set(3), open(2), qsort(3), realloc(3), sigfillset(3), sig- procmask(2), stat(2), strchr(3), strcmp(3), strcpy(3), strdup(3), strerror(3), strlen(3), and unlink(2). In addition, the _l_o_g___a_r_c_h_i_v_e function may fail and return _e_r_r_n_o for the following conditions: [EINVAL] An invalid flag value or parameter was specified. The log was corrupted. The _l_o_g___r_e_g_i_s_t_e_r function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: close(2), fcntl(2), fflush(3), fsync(2), lseek(2), malloc(3), memcmp(3), memcpy(3), mem- set(3), open(2), realloc(3), sigfillset(3), sigproc- mask(2), stat(2), strcpy(3), strdup(3), strerror(3), strlen(3), time(3), unlink(2), and write(2). In addition, the _l_o_g___r_e_g_i_s_t_e_r function may fail and return _e_r_r_n_o for the following conditions: [EINVAL] An invalid flag value or parameter was specified. The _l_o_g___u_n_r_e_g_i_s_t_e_r function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: close(2), fcntl(2), fflush(3), fsync(2), lseek(2), malloc(3), memcpy(3), memset(3), open(2), sigfillset(3), sigprocmask(2), stat(2), str- cpy(3), strdup(3), strerror(3), strlen(3), time(3), unlink(2), and write(2). In addition, the _l_o_g___u_n_r_e_g_i_s_t_e_r function may fail and return _e_r_r_n_o for the following conditions: [EINVAL] An invalid flag value or parameter was specified. The _l_o_g___s_t_a_t function may fail and return _e_r_r_n_o for any of the errors specified for the following DB and library functions: fcntl(2), and malloc(3). BBUUGGSS The log files are not machine architecture independent. Specifically, log file metadata is not stored in a fixed byte order. SSEEEE AALLSSOO _d_b___a_r_c_h_i_v_e(1), _d_b___c_h_e_c_k_p_o_i_n_t(1), _d_b___d_e_a_d_l_o_c_k(1), _d_b___d_u_m_p(1), _d_b___l_o_a_d(1), _d_b___r_e_c_o_v_e_r(1), _d_b___s_t_a_t(1), _d_b___i_n_t_r_o(3), _d_b___a_p_p_i_n_i_t(3), _d_b___c_u_r_s_o_r(3), _d_b___d_b_m(3), _d_b___i_n_t_e_r_n_a_l(3), _d_b___l_o_c_k(3), _d_b___l_o_g(3), _d_b___m_p_o_o_l(3), _d_b___o_p_e_n(3), _d_b___t_h_r_e_a_d(3), _d_b___t_x_n(3)