Berkeley DB: db_stat
Description: Berkeley DB: An embedded database programmatic toolkit.
Keywords: embedded,database,programmatic,toolkit,b+tree,btr ee,hash,hashing,transaction,transactions,locking,logging,access method,access me thods,java,C,C++

# db_stat

`

###

    db_stat [-clmNt]
        [-C Acfhlmo] [-d file] [-h home] [-M Ahlm]

# Description

The db_stat utility displays statistics for Berkeley DB environments.

The options are as follows:

-C
  Display internal information about the lock region. (The output from this option is often both voluminous and meaningless, and is intended only for debugging.)

  A
    Display all information.
  c
    Display lock conflict matrix.
  f
    Display lock and object free lists.
  l
    Display lockers within hash chains.
  m
    Display region memory information.
  o
    Display objects within hash chains.

-c
  Display lock region statistics as described in lock_stat.

-d
  Display database statistics for the specified database, as described in db_open.

-h
  Specify a home directory for the database.

-l
  Display log region statistics as described in log_stat.

-M
  Display internal information about the shared memory buffer pool. (The output from this option is often both voluminous and meaningless, and is intended only for debugging.)

  A
    Display all information.
  h
    Display buffers within hash chains.
  l
    Display buffers within LRU chains.
  m
    Display region memory information.

-m
  Display shared memory buffer pool statistics as described in memp_stat.

-N
  Don't acquire shared region locks while accumulating the statistics. This option is intended only for debugging corrupt regions and should not be used under any other circumstances.

-t
  Display transaction region statistics as described in txn_stat.

Values smaller than 10 million are generally displayed without any special notation. Values larger than 10 million are normally displayed as M.

The db_stat utility attaches to one or more of the Berkeley DB shared memory regions. In order to avoid region corruption, it should always be given the chance to detach and exit gracefully. To cause db_stat to clean up after itself and exit, send it an interrupt signal (SIGINT).

The db_stat utility exits 0 on success, and >0 if an error occurs.

# Environment Variables

DB_HOME
  If the -h option is not specified and the environment variable DB_HOME is set, it is used as the path of the database home, as described in db_appinit.

# See Also

db_archive, db_checkpoint, db_deadlock, db_dump, db_load, db_recover, and db_stat.`