Sun Java System Application Server Enterprise Edition 8.1 2005Q2 High Availability Administration Guide

- Previous: To perform unplanned maintenance in the event of a failure
- Next: Chapter 4 Configuring Load Balancing and Failover

## Clearing and Archiving History Files

HADB history files record all database operations and error messages. HADB appends to the end of existing history files, so the files grow over time. To save disk space and prevent files from getting too large, periodically clear and archive history files.

To clear a database’s history files, use the `hadbm clearhistory` command.

The command syntax is:

    hadbm clearhistory
    [--saveto=path]
    [dbname]
    [--adminpassword=password | --adminpasswordfile=file]
    [--agent=maurl]

The dbname operand specifies the database name. The default is `hadb`.

Use the `--saveto` option (short form `-o`) to specify the directory in which to store the old history files. This directory must have appropriate write permissions. See General Options for a description of other command options.

For more information, see hadbm-clearhistory(1).

The `--historypath` option of the `hadbm create` command determines the location of the history files. The names of the history files are of the format dbname`.out.` nodeno. For information on `hadbm create`, see Creating a Database

### History File Format

Each message in the history file contains the following information:

- The abbreviated name of the HADB process that produced the message.

- The type of message:

  - `INF` - general information

  - `WRN` - warnings

  - `ERR` - errors

  - `DBG` - debug information

- A timestamp. The time is obtained from the host machine system clock.

- The service set changes occurring in the system when a node stops or starts.

Messages about resource shortages contain the string “HIGH LOAD.”

You do not need a detailed knowledge of all entries in the history file. If for any reason you need to study a history file in greater detail, contact Sun customer support.

- Previous: To perform unplanned maintenance in the event of a failure
- Next: Chapter 4 Configuring Load Balancing and Failover

- © 2010, Oracle Corporation and/or its affiliates