<p>After opening the database, we can use the <ahref="../api_reference/C/db_stat.html"class="olink">db_stat</a> utility to
display information about a database we have created:</p>
<preclass="programlisting">prompt> db_stat -h TXNAPP -d color
53162 Btree magic number.
8 Btree version number.
Flags:
2 Minimum keys per-page.
8192 Underlying database page size.
1 Number of levels in the tree.
0 Number of unique keys in the tree.
0 Number of data items in the tree.
0 Number of tree internal pages.
0 Number of bytes free in tree internal pages (0% ff).
1 Number of tree leaf pages.
8166 Number of bytes free in tree leaf pages (0.% ff).
0 Number of tree duplicate pages.
0 Number of bytes free in tree duplicate pages (0% ff).
0 Number of tree overflow pages.
0 Number of bytes free in tree overflow pages (0% ff).
0 Number of pages on the free list.</pre>
<p>The database open must be enclosed within a transaction in order to be
recoverable. The transaction will ensure that created files are
re-created in recovered environments (or do not appear at all).
Additional database operations or operations on other databases can be
included in the same transaction, of course. In the simple case, where
the open is the only operation in the transaction, an application can
set the <ahref="../api_reference/C/envset_flags.html#envset_flags_DB_AUTO_COMMIT"class="olink">DB_AUTO_COMMIT</a> flag instead of creating and managing
its own transaction handle. The <ahref="../api_reference/C/envset_flags.html#envset_flags_DB_AUTO_COMMIT"class="olink">DB_AUTO_COMMIT</a> flag will
internally wrap the operation in a transaction, simplifying application
code.</p>
<p>The previous example is the simplest case of transaction protection for
database open. Obviously, additional database operations can be done
in the scope of the same transaction. For example, an application
maintaining a list of the databases in a database environment in a
well-known file might include an update of the list in the same
transaction in which the database is created. Or, an application might
create both a primary and secondary database in a single transaction.</p>
<p><ahref="../api_reference/C/db.html"class="olink">DB</a> handles that will later be used for transactionally protected
database operations must be opened within a transaction. Specifying a
transaction handle to database operations using <ahref="../api_reference/C/db.html"class="olink">DB</a> handles not
opened within a transaction will return an error. Similarly, not
specifying a transaction handle to database operations that will modify
the database, using handles that were opened within a transaction, will
