IMO, I think this is a moot issue.  The 1st thing 'delete dbvol' does is
move any db data from the subject dbvol (both mirror-halves, because they are 
still sync'd) to another dbvol - but not to the other
mirror-half.  Both of the mirror-halves be empty when the 1st 'delete
dbvol' completes.  The primary is defined, but is empty and won't really
be part of the DB until another 'extend db' has been performed.

Kent Monthei
GlaxoSmithKline






"Roger Deschner" <rogerd AT UIC DOT EDU>

Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09-May-2002 16:10
Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>




        To:     ADSM-L

        cc:
        Subject:        Mirrored DELETE DBVOL, LOGVOL?

Oh, I guess it's just my paranoid mind at work again, but DELETE DBVOL
scares me. I'm using it to migrate the TSM Database from old disks to
new, faster disks.

So, I attached the new dbvol and its mirror, fiddled with EXTEND DB and
REDUCE DB to make it right, and did DELETE DBVOL on the old mirror. Then
I did DELETE DBVOL on the old primary copy.

Oops! Now I'm really exposed! There is only one copy of the old database
volume, while this rather lengthly copying process proceeds.

Is there any way to do a DELETE DBVOL in a mirrored way - that is delete
all mirrored copies of a DBVOL at once, so that if a disk crashes in the
middle of it, I will not lose my Database? That's the whole point of
Database mirroring, isn't it?

I'm starting to think AIX JFS mirroring might have some advantages over
TSM Database/Log mirroring.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu