Edit File - File Manager

Edit File: db_close.html

<html>
<head>
<title>Berkeley DB: db close</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 close
</td>
<td align=right>
<a href="../../db4-devel-4.7.25/api_tcl/api_tcl.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>db close
	[-nosync]
</pre>
Description(db close)
The db close command flushes any cached database information to
disk, closes any open cursors, frees any allocated resources, and closes
any underlying files. Because key/data pairs are cached in memory, failing
to sync the file with the db close or db sync command may
result in inconsistent or lost information.
The options are as follows:
 
-nosync<ul compact><li>Do not flush cached information to disk.
The -nosync flag is a dangerous option. It should only be set if the
application is doing logging (with transactions) so that the database is
recoverable after a system or application crash, or if the database is
always generated from scratch after any system or application crash.
It is important to understand that flushing cached information to disk
only minimizes the window of opportunity for corrupted data. Although
unlikely, it is possible for database corruption to happen if a system or
application crash occurs while writing data to the database. To ensure
that database corruption never occurs, applications must either use
transactions and logging with automatic recovery, use logging and
application-specific recovery, or edit a copy of the database; and after
all applications using the database have successfully called
db close, atomically replace the original database with the
updated copy.</ul>
 
After db close has been called, regardless of its return, the DB
handle may not be accessed again.
The db close command returns 0 on success, and in the case of error, a Tcl error
is thrown.
</tt>
<table width="100%"><tr><td> </td><td align=right>
<a href="../../db4-devel-4.7.25/api_tcl/api_tcl.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