Purging the history

History information about each node and relationship is recorded in the datastore. This audit trail includes details of the changes made, the date and time of the changes and the user who made the changes. You can view the history of each object in the datastore and you can search for and display details of destroyed objects.

The purge history script

You can use the tw_ds_purgehistory script to purge the history. The command line options are described in the Table below.

Command line option



Specify a number of days over which the history is purged. The default is 30.

-h, --help

Displays help on standard options, some brief usage information, and exits.


Lists all partitions and exits.


The name of the log file into which log messages are written.


Logging level:

  • debug - log all messages
  • info - log critical, error, warning, and information messages.
  • warn - log critical, error, and warning messages.
  • error - log critical and error messages.
  • crit - log only critical messages.


The name of the partition to purge or 'All' for all partitions. The default is all partitions.

-p, --password=password

The password that corresponds to the user name entered after the --username switch.
Note that if you use this option your password is visible in clear text. You should avoid using this option; when you do not use it, you are prompted for the password and it is not echoed.

-u, --username=username

Username. This is a BMC Atrium Discovery command line user.

-v, --version

Displays BMC Atrium Discovery version information and exits.

Purge process

When it runs, the purge finds all historical entries older than the time specified with the --purge-older-than parameter. To ensure that the historical information is self-consistent, the creation time record for each node is maintained, and all state changes that occurred between the creation time and the purge time are rolled up into a single state change entry.

Was this page helpful? Yes No Submitting... Thank you