Thanks.
The logical volume that went bad was /dbaa1dk3 so I assumed since /dbaa1dk3/db 
was on the bad disk I could use the naming convention.   The bottom note was 
from initial information from 1 of the UNIX admins, I went in and verified the 
information myself and found it to be different.
Last questions since I'm a little confused but I'm sure that will pass.
Why do you delete the volume before you mirror the data from the other disk?
Also I see the GUI under Database volumes and there is a create data base 
volume, delete database volume and copy database volume.  Is it better to use 
the command line over the GUI or does it not matter.

Thanks again, this has been a great help.

Eric


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Mark D. Rodriguez
Sent: Tuesday, April 26, 2005 1:18 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Disk gone bad, need help


Eric,

Here you go, from a TSM command prompt issue the following.

del dbv /dbaa1dk3/db
def dbv /dbaa1dk3/db f=/size_in_MB/
del dbv /dbaa1dk3/db
def dbc /dbaa1dk7/db /dbaa1dk3/db

That should do it.  The only thing you need to decide is how big to make
it in the second command.  Remember it is in MBs and it most be as big
as the /dbaa1dk7/db volume.

NOTE: I have noticed that you are not consistent as to which volume was
on the failed drive as well as which volumes were mirrored.  Please be
certain about this before you proceed.  If you are not sure then repost
the output of the  following commands:

q dbv f=d
q db f=d

--
Regards,
Mark D. Rodriguez
President MDR Consulting, Inc.

===============================================================================
MDR Consulting
The very best in Technical Training and Consulting.
IBM Advanced Business Partner
SAIR Linux and GNU Authorized Center for Education
IBM Certified Advanced Technical Expert, CATE
AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
Red Hat Certified Engineer, RHCE
===============================================================================



Jones, Eric J wrote:

>Thanks.  Would you mind the full syntax.  This is my 1st time through this and 
>nobody around me seems to know about it.
>1:  The disk that went bad is being replaced as I write
>2:  I was going to keep the logical volume/db name(/dbaa1dk3/db) the same so 
>all the documentation stays the same.
>3:  The bad logical volume/file was  -->  /dbaa1dk3/db and it was mirrored to 
>/dbaa1dk7/db
>
>This is the 1st failure we have seen.
>thanks for all your help,
>Eric
>
>-----Original Message-----
>From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
>Mark D. Rodriguez
>Sent: Tuesday, April 26, 2005 11:43 AM
>To: ADSM-L AT VM.MARIST DOT EDU
>Subject: Re: Disk gone bad, need help
>
>
>Eric,
>
>I am going to assume you know the syntax of the following commands so I
>will just give my answer at a high level if not post back and I will
>give the exact syntax,
>
>1. Remove the failed volume from tsm by doing either a del dbv.
>2. Then define a new DB vol with the def dbv command, you can use the
>f=XXX to format it to the size you need.
>3. I know this sounds funny by now you need to delete the volume you
>just created.  This will leave the formatted file on the OS file system.
>4. Now you can use the def dbc command to get your self remirrored.
>
>BTW, as an alternative to steps 2 and 3 you could go to the OS level and
>do a dsmfmt command to create the DB volume as well, but I generally
>like to do it all with in TSM.
>
>As I said before, if you need the exact syntax please repost.  I will
>need the exact filenames of the bad volume, the volume name it was
>mirrored to, and the name of the new volume.
>
>I hope that helps.
>
>--
>Regards,
>Mark D. Rodriguez
>President MDR Consulting, Inc.
>
>===============================================================================
>MDR Consulting
>The very best in Technical Training and Consulting.
>IBM Advanced Business Partner
>SAIR Linux and GNU Authorized Center for Education
>IBM Certified Advanced Technical Expert, CATE
>AIX Support and Performance Tuning, RS6000 SP, TSM/ADSM and Linux
>Red Hat Certified Engineer, RHCE
>===============================================================================
>
>
>
>Jones, Eric J wrote:
>
>
>
>>Good Morning.
>>We are running AIX 4.3.3 with TSM 4.1.3  (going into retirement soon)
>>We have a DB that is made up of 6 disk which are mirrored.
>>We had a disk go bad that was part of that pool of disk.
>>My question is what do I need to do after the disk is replaced to recover, 
>>TSM stayed up no problem(very small DB, being retired soon).
>>Do I (logical volume/DB name on disk that went bad  -->  /dbaa1dk2/db 
>>mirrored to /dbaa1dk8/db)
>>*       DSMFMT -m -db /dbaa1dk2/db 3404
>>              *         (not sure what to do about the DSMSERV FORMAT)
>>              *         define dbcopy /dbaa1dk3/db /dbaa1dk8/db
>>
>>Have a Great Day,
>>Eric Jones
>>
>>
>>
>>
>>>*  eric.j.jones AT lmco DOT com
>>>*:   607-751-4133
>>>
>>>
>>>
>>>
>>Cell : 607-972-7621
>>
>>
>>
>>
>>
>
>
>