set your archive log on
SQL> shutdown abort ;
SQL> startup mount;
SQL>alter database archivelog;
you got an error cose we use shutdown abort so never use shutdown abort if u wanna set archive log
SQL>shutdown immediate ;
SQL>startup mount ;
SQL >alter database archivelog;
SQL>alter database open;
SQL>alter system switch logfile;
SQL>exit
SQL>rman target/
RMAN> backup database plus archivelog;
done
-------------------------------------------------------------------------------
Restore database
SQL > SHUTDOWN
SQL > EXIT
C:/>RMAN TARGET /
RMAN> ALTER DATABASE NOMOUNT ;
RMAN> RESTORE CONTROLFILE FROM 'D:\BACKUP\C-33354'
** 'D:\BACKUP\C-33354' this is the path where u store ur backup .and C-33354 this the controll file use ur contoll file name .
controll file name always start with 'c-'
RMAN>ALTER DATABASE MOUNT ;
RMAN>RESTORE DATABASE;
RMAN> RECOVER DATABASE;
RMAN>ALTER DATABASE OPEN RESETLOGS;
any mistake is there or u wanna give any suggestion so please write to me ............
Below are the details which i found advantages of rman backup :
ReplyDelete1.Direct backup to tape is possible.
2.Flexibility to first backup to disk and then use a DVD writer.
3.Speed. It's the second quickest after OS file copy. In the examples shown, the speed was close to 4.5 MB per sec. The whole database was backed up in 2'01" flat!
Flexibility to use multiple channels (in Enterprise version only). Even without, RMAN is very quick.
Very clean procedure, no nagging details such as in export.
There are some disadvantages also, such as
Disadvantages :
The RMAN procedure cannot be used on a live database.
It cannot get any smaller than a datafile. No option to backup a table.
Does not check for errors, as export does.
@viji ..thanks for your valuable comment .....
ReplyDeleteBut can you please tell use why RMAN is not used in live database ????