Archive log: 69468.1 744632.1 AGC: log_archive_format=arch%t%s%r.arc log_archive_dest="/proddbs/arch" log_archive_format = arch_%t_%s_%r.

arc log_archive_dest = "/oracle/PROD/db/arch" startup mount alter database archivelog; alter database open; archive log list; alter system switch logfile; select LOG_MODE from v$database; RMAN Setting: 1. Run Environment $ rman target=sys/manager nocatalog RMAN> show all; To Configure backup path use the configure command but first check the available space on the target path: RMAN> configure channel device type disk format = /mnt/backup/df0_%d_%s_%t; RMAN> configuration parameters are successfully stored. RMAN> show all; Check the configure channel device type disk format = /mnt/backup/df0_%d_%s_%t RMAN> backup database; Starting backup at 16-JUL-09 Allocated channel: ORA_DISK_1 . Recovery: 1. Run Environment $ sqlplus /nolog SQL> connect /as sysdba SQL> startup mount SQL> exit $ rman target sys/manager RMAN> restore database

Starting restore at 16-JUL-09 Restoring datafile..system1.dbf .. Finished restore at 16-JUL-09 After restore recover database: SQL> recover database; .. Log applied. Media recovery complete. SQL> alter database open; Database altered. Note: This backup recover only dbf files it will not take backup of control, redolog and temp files. CONFIGURE CONTROLFILE AUTOBACKUP ON; restore controlfile from autobackup; recover database using backup controlfile until cancel 1. Startup nomount your new instance. 2. Restore the controlfile: RMAN> restore controlfile from autobackup; 3. Mount the database from the restored controlfile: RMAN> alter database mount; 4. Restore datafiles: RMAN> restore database; 10. After restoring the files, you can perform a recovery. Because we have lost the online redo logfiles, and we are using a backup controlfile, you will need to set an 'until time' clause to specify when to end recovery and open the database: RMAN> run { set until time=<time stamp>; recover database; alter database open resetlogs; } Create an RMAN Catalog We strongly recommend using an RMAN catalog when performing a backup. It offers the best protection possible because RMAN stores all relative backup information in this catalog. Without the catalog, RMAN will rely only on control files to manage backups. This is very risky because if all the control files are lost, RMAN will not be able to restore the database. In addition, you will not be able to restore your control files

and your database will be lost. To remind you that you should be using the RMAN catalog, a message will display every time you run a job without a catalog. Important! If you are not using an RMAN catalog, you need to manage your control files on your own either by using a file system backup or by mirroring the control files for fault tolerance. To create an RMAN catalog, follow these steps: Note: Because RMAN relies heavily on this catalog when restoring, you should create it in a separate database (that is, a database other than the one being backed up). 1. Create a new tablespace using this SQLPlus command: * create tablespace <RMAN catalog tablespace> datafile <datafile name> size <datafile size> m; Create tablespace RMAN_CATALOG datafile /proddbs/prod/db/apps_st/data/rman_catalog01.dbf size 100 M 2. Create the user who will be the owner of the RMAN catalog by entering this command: * create user <RMAN catalog owner> identified by <password> default tablespace <RMAN catalog tablespace> quota unlimited on <RMAN catalog tablespace>; create user rmancat identified by rmancat default tablespace RMAN_CATALOG quota unlimited on RMAN_CATALOG; 3. Assign the correct privileges to this user by using the following command: * grant recovery_catalog_owner to <RMAN catalog owner>; Grant recovery_catalog_owner to rmancat 4. For Oracle 8i and later users, create the catalog using these commands: * rman catalog <RMAN catalog owner>/<RMAN catalog password> * create catalog; [devdbs@advgrpdb 10.2.0]$ . ./DEV_advgrpdb.env [devdbs@advgrpdb 10.2.0]$ rman catalog rmancat/rmancat Recovery Manager: Release 10.2.0.3.0 - Production on Sun Jul 11 10:48:32 2010 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to recovery catalog database RMAN> create catalog; recovery catalog created RMAN>