import com.sleepycat.db.*;

public void set_verbose(int which, boolean onoff);

Description

The DbEnv.set_verbose method turns additional informational and debugging messages in the Berkeley DB message output on and off. If onoff is set to true, the additional messages are output.

The which parameter must be set to one of the following values:

Db.DB_VERB_CHKPOINT

Display checkpoint location information when searching the log for checkpoints.

Db.DB_VERB_DEADLOCK

Display additional information when doing deadlock detection.

Db.DB_VERB_RECOVERY

Display additional information when performing recovery.

Db.DB_VERB_REPLICATION

Display additional information when processing replication messages.

Db.DB_VERB_WAITSFOR

Display the waits-for table when doing deadlock detection.

The DbEnv.set_verbose method configures operations performed using the specified DbEnv handle, not all operations performed on the underlying database environment.

The DbEnv.set_verbose interface may be called at any time during the life of the application.

The DbEnv.set_verbose method throws an exception that encapsulates a non-zero error value on failure.

The database environment's verbosity may also be set using the environment's DB_CONFIG file. The syntax of the entry in that file is a single line with the string "set_verbose", one or more whitespace characters, and the interface which argument as a string; for example, "set_verbose DB_VERB_CHKPOINT". Because the DB_CONFIG file is read when the database environment is opened, it will silently overrule configuration done before that time.

Errors

The DbEnv.set_verbose method may fail and throw an exception encapsulating a non-zero error for the following conditions:

EINVAL

An invalid flag value or parameter was specified.

The DbEnv.set_verbose 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.set_verbose method may fail and throw a DbRunRecoveryException, in which case all subsequent Berkeley DB calls will fail in the same way.

Class

See Also