The database server
42
If there is no transaction log, the database server carries out a checkpoint
recovery of the database and then terminates—it does not continue to run.
You can then restart the database server without the
-f option for normal
operation.
If there is a transaction log in the same directory as the database, the database
server carries out a checkpoint recovery, and a recovery using the transaction
log, and then terminates—it does not continue to run. You can then restart
the database server without the
-f option for normal operation.
$ For more information see "Backup and Data Recovery" on page 645 of
the book ASA User’s Guide.
Database switches
These switches are entered after the database name, and apply only to that
database.
–m command-line option
Truncate the transaction log when a checkpoint is done.
[ dbsrv7 | dbeng7 ] [ server-switches ].
database-file
-m ..
All operating systems and servers.
Truncate (delete) the transaction log when a checkpoint is done, either at
shutdown or as a result of a checkpoint scheduled by the server. This
provides a way to automatically limit the growth of the transaction log.
Checkpoint frequency is still controlled by the CHECKPOINT_TIME and
RECOVERY_TIME options (which you can also define on the command
line).
The
-m option is useful where high volume transactions requiring fast
response times are being processed, and the contents of the transaction log
are not being relied upon for recovery or replication. When this option is
selected, there is no protection against media failure on the device that
contains the database files.
To avoid database file fragmentation, it is recommended that where this
option is used, the transaction log be placed on a separate device or partition
from the database itself.
This switch is the same as the
-m server switch, but applies only to the
current database or the database identified by the database-file command-
line variable.
Description
Function
Syntax
Applies to
Description
To Next Page
Loading...