When you have corruption with a disk entry and you want to run an audit to
clear things to allow you to remove a volume, you will really want to do...
1) write a macro to delete all other disk volumes (other than the
hosed up one)
2) write a macro to define back all your disk volumes
3) using migration, clear all your disk volumes
4) run your delete vol macro
5) back up your data base (incr is fine, this is just to CYA)
6) halt TSM
7) run dsmserv auditdb diskstorage fix=yes
8) start TSM
9) now you should be able to delete your bad volume
10) run your macro to define back all your disk volumes and all is
well ;-)
BY REMOVING ALL OTHER DISK VOLUMES YOU WILL REDUCE YOUR AUDIT TIME FROM
HOURS DOWN TO MINUTES !
Really... I've seen reductions along the line of 1.75 hours down to
minutes...
that was back in my 3.2 3.7 days, haven't had any problem volumes in 4.1
yet...
hope this helps...
DWight
-Original Message-
From: Oscar Kolsteren [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 21, 2002 5:04 AM
To: [EMAIL PROTECTED]
Subject: Entries in database
Hi all,
I want to do an audit on my database because I've got a problem of throwing
away
an disk volume.
How can I find out how many entries i've got in my database, so I know how
many
entries the audit must do ?
When I know this I can predict how long the audit will last (!!!)
Thanx
Oscar Kolsteren
-
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.
Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-
