Conference orarep::nomahs::rdb_60

5077.0. "Default recovery journal location" by 4177::MHAGE (M�rta Hage, Oracle Rdb Support,Sweden) Wed Feb 26 1997 10:32

When defining a default location for the ruj file, it's a no no
to change this location after a RMU/RESTORE of database to another
system if the disk defined doesn't exist on the restored system.

On system A:
alter database mf_personnel
recover journal (location is 'dua2:[rdmruj]');

$rmu/backup mf_personnel mf_pers

On system B where disk dua2 doesn't exist

$rmu/restore/nocdd/dire=<newdir> mf_pers

$ sql
alter database filename mf_personnel
recover journal (no location);
RDB-F-SYS_REQUEST, error from system services request
-RDMS-F-FILACCERR, error parsing file DUA2:[RDMRUJ]MF_PERSONNEL$0001038E62B3.RUJ
;
-COSI-I-NOTDISKFILE, file is not a disk file


I tried defining rdms$ruj before restore database - no luck!

I'd like a new option to rmu/restore where I can specify a new default
location for the RUJ file. I know, a suggested enhancement will be
entered.

Is there a way of resolving this problem after restore until then?
Can I change it with rmu/alter? 
It's not doable to change the recover journal to no location before
a rmu/backup.

M�rta

    

>Is there a way of resolving this problem after restore until then?
    
    If you don't have DUA2: on your new system, define a system logical
    called DUA2 to point to a disk you do have, then create the directory.
    
    Peter

And please submit BUG report so this can be fixed.

Ian

    
    Peter, that was too simple! I wanted to run RMU/ALTER...
    Bug 458415 
    
    /M�rta