Thanks to :
cherkus_at_unimaster.com
trenta_at_decatl.alf.dec.com
Right after I sent the mail, I RTFM'ed and found the answer that was
suggested about "voldg -f". That's what happens when you're trying to fix
things at 9 pm.
I only got to test it on Friday and it worked fine. I got my disk
group back and replaced the disk. The description in Debbie Trenta's
mail is exactly what I did to fix the problem.
Thanks for all your help.
cherkus_at_unimaster.com
>The behaviour is due to a bug in the tool ASE uses to bring the LSM
>volumes back on line. I'll try to dig up the details on this, but
>if I were you, I would resist the urge to tinker with this system
>till DEC or someone from this list gives you the details on how to
>get the fix for the bug.
and,
trenta_at_decatl.alf.dec.com
>I don't know if you have gotten your answer yet, but the following
>procedure should work:
>
> 1) Force the import of the diskgroup
> voldg -f import <diskgroupname>
> example: voldg -f import oracledg
> 2) Remove the failed drive from LSM (voldisk list will show
> the diskaccess name)
> voldisk rm <diskaccessname>
> example: voldisk rm rz17
> 3) Label the new drive with the LSMpriv and LSMpubl areas.
> disklabel -e <disk>
> 4) Add the new disk
> voldisk -f init <diskaccessname>
> example: voldisk -f init rz17
> 5) Reconnect it to it's associated diskmedia name
> voldg -k adddisk <diskmedia>=<diskaccess>
> example: voldg -k adddisk ordsk01=rz17
> 6) Now start the recovery:
> volrecover -g <diskgroup> -sb
> example: volrecover -g oracledg -sb
> 7) Now in ASE you should be able to bring the service back
> on line.
Bye..
...Louis
----------------------------------------------------------------------------
| Louis Bouchard
J'aimes que ca cesse quand c'est fini. Quand | Ingenieur Systeme
ca recommence, ca me scie. | bouchard_l_at_decus.fr
R. Ducharme | Bouygues Telecom
----------------------------------------------------------------------------
Received on Mon Oct 21 1996 - 19:36:29 NZDT