ADSM-L

Re: Volhistory errors

1998-07-15 12:28:34
Subject: Re: Volhistory errors
From: Carol Trible <trible AT VNET.IBM DOT COM>
Date: Wed, 15 Jul 1998 09:28:34 PDT
Hello,

QUERY VOLHISTORY will display the contents of the volume history through
ADSM. You can also use the sql SELECT xxx from VOLHISTORY to get information on
what is in the file, or a count of records - SELECT COUNT(*) STGVOLS FROM
VOLHISTORY WHERE TYPE LIKE 'STG%' will show you how many stgvolume records you
have.

A large volume history file can cause problems, and there are a lot of
other records in the file. You can delete your STGNEW and STGREUSE entries at
the same time you delete the others.  There is no reason to keep any STG or DB
entries after you have gotten rid of the database backup.  The ADSM database
tracks all the volumes that are in use by storagepools, so you only need
volhistory information on STGNEW, STGREUSE and STGDELETE if you are restoring
the database.  The volume history can help you know what volumes may need an
audit because of changes since the database backup.  You probably don't need any
old export records either, so unless you have some reason for wanting those
(they aren't tracked in the database outside the volume history file), you can
change your 7 day delete to a TYPE=ALL.

Carol Trible
ADSM Development
<Prev in Thread] Current Thread [Next in Thread>