DEFINE DBVOL creates a file, formats its and assigns it to be a DB-volume, but
DEFINE DBCOPY just tries to assign an existing formatted file to de group of
mirrorvolumes.
DELETE DBVOL deletes the file from the DB-volumes, but outside ADSM the file
still exists.
So my trick is: define an extra dbvolume, delete it and then do the 'define
dbcopy'

david de leeuw schreef:
>
> We just extended the adsm database with a db volume
> (/adsm_database/db.dsm03).
>
> When creating a mirror copy of the database volume using:
>
> define dbcopy /adsm_database/db.dsm03 /users/adsm/db.dsm03
>
> we get:
>
> ANR2404E DEFINE DBCOPY: Volume /users/adsm/db.dsm03 is not available.
>
> (Of course the /users/adsm directory is accesible)
>
> Any ideas ?
>
> David
> ------------------------------------------------------------------------
> internet:  david AT bgumail.bgu.ac DOT il   __o   David de Leeuw
> phone:     +972-7-6 47 7398        _`\<,_  Head, Medical Computing Unit
> phone BGU: 7398 Soroka: 62 7398   (_)/ (_) Ben Gurion Univ. of the Negev
> fax:       +972-7-6 47 7630                POB 653 Beer Sheva Israel
> ------------------------------------------------------------------------
>   save the environment and your health: re- and bi- cycle !
> ------------------------------------------------------------------------