Monday, August 6, 2012

The recovery Catalog creation



THE RECOVERY CATALOG CREATION




I am using two servers

first server: oracle@e1lab1pc001 this is having my target database “APPLE”

second server: oracle@e1lab2pc004 this is where I will be creating recovery catalog “KOMAL”








At first server: oracle@e1lab1pc001 a entry is done in tnsnames.ora regarding the database at second server

At second server: oracle@e1lab2pc004 listener.ora is up and listening to recovery catalog “KOMAL”








At first server: oracle@e1lab1pc001 tnsping komal was executed

second server: oracle@e1lab2pc004 following commands were executed

create tablespace rmants datafile '/u01/app/oracle/oradata/komal/rman01.dbf' size 100M;
create user rms identified by rms default tablespace rmants;
grant connect,resource,recovery_catalog_owner to rms;







At first server: oracle@e1lab1pc001 tnsping komal was executed

second server: oracle@e1lab2pc004 following commands were executed

rman catalog rms/rms
create catalog;







At first server: oracle@e1lab1pc001 following commands were executed

rman target / catalog rms/rms@komal
register database;

second server: oracle@e1lab2pc004





the output of the show all command


 backup of the tablespace was taken and it went to FRA by default.




Here we can see the output at /u01/app/oracle/flash_recovery_area/APPLE/backupset/2012_08_07/








Here we can see the output at /u01/app/oracle/flash_recovery_area/APPLE/backupset/2012_08_07/
but this time we can see the backupset created have a tag in their name.




Here we can see the output of the backup send to the directory /u01/myrmanbkp and we have used the %U format specifier.

No comments:

Post a Comment

ORA-12519: TNS:no appropriate service handler found error

ORA-12519: TNS: no appropriate service handler found error The real problem lies in the PROCESSES parameter All you need ...