Hi Mark,
1) when issuing q logvol f=d, you see the main and copy volumes.
just delete the copy vols as normal volumes. In your case, it seems your
copy vols are damaged ...
adsm > del logvol h:\tsmdata\log_copy.dsm
If you can't do this, do a FULL backup db before, it will free some locks on
the log,
2) define a new log vol different size (say sizeof(log3)+10), extend log
with new size
then reduce log of sizeof(log3) and delete the log3.dsm vol. TSM will copy
the pages to the new volume
2bis) try to vary off the corrupted volume if you can ont delete it (you
must had a second one before varying
off the first one)
3) You can also stop TSM and do a dsmserv auditdb (but it could be VERY
long) depending
on your TSM DB size
Rv
----- Original Message -----
From: "Remeta, Mark" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 03, 2001 11:05 PM
Subject: Problem with log volume
> G'day all. I am trying to move my database recovery log volumes from one
> disk to anotha. I got them all moved but one pesky volume doesn't want to
> go. I keep getting the following whenever I try and define a logcopy or
when
> I try to delete it (after reducing the recovery log size):
>
> ANR0249E Error reading logical page 625584 (physical page 101552) from
> recovery log volume H:\TSMDATA\LOG3.DSM.
> ANR0251E Unable to read recovery log page 625584 from any alternate copy.
> ANR0231E Synchronization process failed for recovery log volume
>
> How can I get rid of this logvolume??? I tried removing the disk
> alltogether, but then my server won't start :)
>
>
> Thanks in advance,
>
> Mark Remeta
> Seligman Data Corp.
> 100 Park Avenue
> New York, NY 10017
>
