Edit File - File Manager

Edit File: log_stat.html

<html>
<head>
<title>Berkeley DB: DB_ENV-&gt;log_stat</title>
<meta name="description" content="Berkeley DB: An embedded database programmatic toolkit.">
<meta name="keywords" content="embedded,database,programmatic,toolkit,btree,hash,hashing,transaction,transactions,locking,logging,access method,access methods,Java,C,C++">
</head>
<body bgcolor=white>
<table width="100%"><tr valign=top>
<td>
DB_ENV-&gt;log_stat
</td>
<td align=right>
<a href="../../db4-devel-4.7.25/api_c/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a>
<a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a></td>
</tr></table>
<hr size=1 noshade>
<tt>
<pre>
#include &lt;db.h&gt;

int
DB_ENV-&gt;log_stat(DB_ENV *env, DB_LOG_STAT **statp, u_int32_t flags);

int
DB_ENV-&gt;log_stat_print(DB_ENV *env, u_int32_t flags);
</pre>
<hr size=1 noshade>
Description: DB_ENV-&gt;log_stat
The DB_ENV-&gt;log_stat method returns the logging subsystem statistics.
The DB_ENV-&gt;log_stat method creates a statistical structure of type
DB_LOG_STAT and copies a pointer to it into a user-specified memory
location.
Statistical structures are stored in allocated memory. If application-specific allocation
routines have been declared (see <a href="../../db4-devel-4.7.25/api_c/env_set_alloc.html">DB_ENV-&gt;set_alloc</a> for more
information), they are used to allocate the memory; otherwise, the
standard C library malloc(3) is used. The caller is
responsible for deallocating the memory. To deallocate the memory, free
the memory reference; references inside the returned memory need not be
individually freed.
The following DB_LOG_STAT fields will be filled in:
 
u_int32_t st_magic;<ul compact><li>The magic number that identifies a file as a log file.</ul>
u_int32_t st_version;<ul compact><li>The version of the log file type.</ul>
int st_mode;<ul compact><li>The mode of any created log files.</ul>
u_int32_t st_lg_bsize;<ul compact><li>The in-memory log record cache size.</ul>
u_int32_t st_lg_size;<ul compact><li>The log file size.</ul>
u_int32_t st_record;<ul compact><li>The number of records written to this log.</ul>
u_int32_t st_w_mbytes;<ul compact><li>The number of megabytes written to this log.</ul>
u_int32_t st_w_bytes;<ul compact><li>The number of bytes over and above st_w_mbytes written to this log.</ul>
u_int32_t st_wc_mbytes;<ul compact><li>The number of megabytes written to this log since the last checkpoint.</ul>
u_int32_t st_wc_bytes;<ul compact><li>The number of bytes over and above st_wc_mbytes written to this log
since the last checkpoint.</ul>
u_int32_t st_wcount;<ul compact><li>The number of times the log has been written to disk.</ul>
u_int32_t st_wcount_fill;<ul compact><li>The number of times the log has been written to disk because the
in-memory log record cache filled up.</ul>
u_int32_t st_rcount;<ul compact><li>The number of times the log has been read from disk.</ul>
u_int32_t st_scount;<ul compact><li>The number of times the log has been flushed to disk.</ul>
u_int32_t st_cur_file;<ul compact><li>The current log file number.</ul>
u_int32_t st_cur_offset;<ul compact><li>The byte offset in the current log file.</ul>
u_int32_t st_disk_file;<ul compact><li>The log file number of the last record known to be on disk.</ul>
u_int32_t st_disk_offset;<ul compact><li>The byte offset of the last record known to be on disk.</ul>
u_int32_t st_maxcommitperflush;<ul compact><li>The maximum number of commits contained in a single log flush.</ul>
u_int32_t st_mincommitperflush;<ul compact><li>The minimum number of commits contained in a single log flush that
contained a commit.</ul>
roff_t st_regsize;<ul compact><li>The size of the log region, in bytes.</ul>
u_int32_t st_region_wait;<ul compact><li>The number of times that a thread of control was forced to wait before
obtaining the log region mutex.</ul>
u_int32_t st_region_nowait;<ul compact><li>The number of times that a thread of control was able to obtain
the log region mutex without waiting.</ul>
 
The DB_ENV-&gt;log_stat method may not be called before the <a href="../../db4-devel-4.7.25/api_c/env_open.html">DB_ENV-&gt;open</a> method is called.
The DB_ENV-&gt;log_stat method
returns a non-zero error value on failure
and 0 on success.

Parameters 
 flags<ul compact><li>The flags parameter must be set to 0 or
the following value:
 
<a name="DB_STAT_CLEAR">DB_STAT_CLEAR</a><ul compact><li>Reset statistics after returning their values.</ul>
 </ul>
 statp<ul compact><li>The statp parameter references memory into which
a pointer to the allocated statistics structure is copied.</ul> 
 
 Errors
The DB_ENV-&gt;log_stat method
may fail and return one of the following non-zero errors:
 
EINVAL<ul compact><li>An
invalid flag value or parameter was specified.</ul>
 
<hr size=1 noshade>
Description: DB_ENV-&gt;log_stat_print
The DB_ENV-&gt;log_stat_print method displays the
logging subsystem statistical information, as described for the DB_ENV-&gt;log_stat method.
The information is printed to a specified output channel (see the
<a href="../../db4-devel-4.7.25/api_c/env_set_msgfile.html">DB_ENV-&gt;set_msgfile</a> method for more information), or passed to an
application callback function (see the <a href="../../db4-devel-4.7.25/api_c/env_set_msgcall.html">DB_ENV-&gt;set_msgcall</a> method for
more information).
The DB_ENV-&gt;log_stat_print method may not be called before the <a href="../../db4-devel-4.7.25/api_c/env_open.html">DB_ENV-&gt;open</a> method is called.
The DB_ENV-&gt;log_stat_print method
returns a non-zero error value on failure
and 0 on success.

Parameters 
 flags<ul compact><li>The flags parameter must be set to 0 or by bitwise inclusively OR'ing together one
or more of the following values:
 
<a name="DB_STAT_ALL">DB_STAT_ALL</a><ul compact><li>Display all available information.</ul>
<a name="DB_STAT_CLEAR">DB_STAT_CLEAR</a><ul compact><li>Reset statistics after displaying their values.</ul>
 </ul>
 
<hr size=1 noshade>
 Class
<a href="../../db4-devel-4.7.25/api_c/env_class.html">DB_ENV</a>, <a href="../../db4-devel-4.7.25/api_c/logc_class.html">DB_LOGC</a>, <a href="../../db4-devel-4.7.25/api_c/lsn_class.html">DB_LSN</a>
 See Also
<a href="../../db4-devel-4.7.25/api_c/log_list.html">Logging Subsystem and Related Methods</a>
</tt>
<table width="100%"><tr><td> </td><td align=right>
<a href="../../db4-devel-4.7.25/api_c/api_core.html"><img src="../../db4-devel-4.7.25/images/api.gif" alt="API"></a><a href="../../db4-devel-4.7.25/ref/toc.html"><img src="../../db4-devel-4.7.25/images/ref.gif" alt="Ref"></a>
</td></tr></table>
Copyright (c) 1996,2008 Oracle. All rights reserved.
</body>
</html>

Back to File Manager