Look closely at the "q volhist t=dbb" and the libvols that show DbBackup !
you'll probably find the two lists don't match ! ! ! !
I've noticed that IF anything happens during the DB backup (that is, an
abnormal termination) that the libvol is left as private with last use of
DbBackup BUT the v
tapes that are like this - i.e., no
valid data but in PRIVATE status caused by a mount failure.
.
-Original Message-
From: Talafous, John G. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 4:46 PM
To: [EMAIL PROTECTED]
Subject: Re: Expiration of DbBackup, Volhist and L
>
> I wonder what made this happen hmmm.
>
> jt
I've seen it with db backups I've canceled.
.. joe.f.
, no
valid data but in PRIVATE status caused by a mount failure.
.
-Original Message-
From: Talafous, John G. [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 4:46 PM
To: [EMAIL PROTECTED]
Subject: Re: Expiration of DbBackup, Volhist and Libvolume status.
Thanks, Wanda. That'
us to
scratch.
Now, I guess I just watch and make sure they get used.'
I wonder what made this happen hmmm.
jt
-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 24, 2001 4:17 PM
To: [EMAIL PROTECTED]
Subject: Re: Expiration of DbBackup, V
Hi John,
I would just pull the volsers of the libvolumes that are defined as
DBBACKUP:
select volume_name from libvolumes where last_use='DbBackup'
Then look and see if they still live ANYWHERE in volume history:
select * from volhistory where volume_name='XX'
Assuming these are physicall
