DbEnv.log_archive
DbEnv.log_archive |
|
import com.sleepycat.db.*;public String[] log_archive(int flags) throws DbException;
The DbEnv.log_archive method returns an array of log or database filenames.
By default, DbEnv.log_archive returns the names of all of the log files that are no longer in use (for example, that are no longer involved in active transactions), and that may safely be archived for catastrophic recovery and then removed from the system. If there are no filenames to return, DbEnv.log_archive returns null.
The flags value must be set to 0 or by bitwise inclusively OR'ing together one or more of the following values:
The Db.DB_ARCH_DATA and Db.DB_ARCH_LOG flags are mutually exclusive.
See the db_archive manual page for more information on database archival procedures.
The DbEnv.log_archive method throws an exception that encapsulates a non-zero error value on failure.
In a threaded application (that is, one where the environment was created with the DB_THREAD flag specified), calling DbEnv.log_archive with the DB_ARCH_DATA flag will fail, returning EINVAL. To work around this problem, reopen the log explicitly without specifying DB_THREAD. This restriction is expected to be removed in a future version of Berkeley DB.
The DbEnv.log_archive method may fail and throw an exception encapsulating a non-zero error for the following conditions:
The log was corrupted.
The DbEnv.log_archive method may fail and throw an exception for errors specified for other Berkeley DB and C library or system methods. If a catastrophic error has occurred, the DbEnv.log_archive method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.
|
|
Copyright Sleepycat Software
@
1.1
log
@Initial revision
@
text
@d1 1
a1 1
@
1.1.1.1
log
@Import: RPM 4.0.3
@
text
@@
1.1.1.2
log
@Import: RPM 4.0.4
@
text
@d1 1
a1 1
d17 1
a17 1
d25 1
a25 1
throws DbException;
a51 15
Log cursor handles (returned by the DbEnv.log_cursor method) may have open
file descriptors for log files in the database environment. Also, the
Berkeley DB interfaces to the database environment logging subsystem (for
example, DbEnv.log_put and DbTxn.abort) may allocate log cursors
and have open file descriptors for log files as well. On operating
systems where filesystem related system calls (for example, rename and
unlink on Windows/NT) can fail if a process has an open file descriptor
for the affected file, attempting to move or remove the log files listed
by DbEnv.log_archive may fail. All Berkeley DB internal use of log cursors
operates on active log files only and furthermore, is short-lived in
nature. So, an application seeing such a failure should be restructured
to close any open log cursors it may have, and otherwise to retry the
operation until it succeeds. (Although the latter is not likely to be
necessary; it is hard to imagine a reason to move or rename a log file
in which transactions are being logged or aborted.)
a80 1
DbEnv.log_cursor,
d83 1
a86 2
DbEnv.log_unregister,
DbLogc.logc_close
d88 1
a88 1
DbLogc.logc_get.
d91 1
a91 1
@
1.1.1.3
log
@Import: RPM 4.0.5
@
text
@d1 2
a2 2
a3 1
d71 6
d84 3
a86 3
If a catastrophic error has occurred, the DbEnv.log_archive method may fail and
throw a DbRunRecoveryException,
in which case all subsequent Berkeley DB calls will fail in the same way.
d88 1
a88 1
DbEnv, DbLogc, DbLsn
d90 16
a105 1
Logging Subsystem and Related Methods
@
1.1.1.4
log
@Import: RPM 4.1
@
text
@d1 2
a2 2
d4 1
a71 6
In a threaded application (that is, one where the environment was created with the DB_THREAD flag specified), calling DbEnv.log_archive with the DB_ARCH_DATA flag will fail, returning EINVAL. To work around this problem, reopen the log explicitly without specifying DB_THREAD. This restriction is expected to be removed in a future version of Berkeley DB. d79 3 a81 3 If a catastrophic error has occurred, the DbEnv.log_archive method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d83 1 a83 1 DbEnv d85 1 a85 16 DbEnv.set_lg_bsize, DbEnv.set_lg_dir, DbEnv.set_lg_max, DbEnv.set_lg_regionmax, DbEnv.log_archive, DbEnv.log_compare, DbEnv.log_cursor, DbEnv.log_file, DbEnv.log_flush, DbEnv.log_put, DbEnv.log_register, DbEnv.log_stat, DbEnv.log_unregister, DbLogc.logc_close and DbLogc.logc_get. @ 1.1.1.5 log @Import: RPM 4.1.1 @ text @d1 2 a2 2 a3 1 d71 6 d84 3 a86 3 If a catastrophic error has occurred, the DbEnv.log_archive method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way. d88 1 a88 1 DbEnv, DbLogc, DbLsn d90 16 a105 1 Logging Subsystem and Related Methods @