Tuesday, May 19, 2015

Configure RMAN


How to configure Oracle RMAN backup for the first time

Step # 1: Connect to Target database(Target DB: The database on which Backup & Recovery to be performed) as sysdba.


[oracle@centos ~]$ sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Fri Jan 3 11:28:24 2014
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>

Step # 2: Ensure the database has been configured with ARCHIVELOG mode or not?

SQL> select log_mode from v$database;
LOG_MODE
------------
NOARCHIVELOG

Database is in NOARCHIVELOG mode.


Step # 3: If the database has been configured with ARCHIVELOG mode then skip the Step number 3 to 6, If not then Shutdown the database.

SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.


Step # 4: Startup the database in mount state.

SQL> startup mount;
ORACLE instance started.
Total System Global Area 308981760 bytes
Fixed Size 2212896 bytes
Variable Size 163580896 bytes
Database Buffers 138412032 bytes
Redo Buffers 4775936 bytes
Database mounted.

Step # 5: Configure database in ARCHIVELOG mode.

SQL> alter database archivelog;
Database altered.

Step # 6: Alter database to open state.


SQL> alter database open;
Database altered.
SQL> select open_mode from v$database;

OPEN_MODE
--------------------
READ WRITE

Step # 7: Ensure ARCHIVELOG destination.

SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 2
Next log sequence to archive 4
Current log sequence 4

In case you wish to change default archive log destination then issue the following command.

SQL> alter system set log_archive_dest_1='location=/home/oracle/arch' scope=both;
System altered.
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /home/oracle/arch
Oldest online log sequence 2
Next log sequence to archive 4
Current log sequence 4

Step # 8: Ensure the flash/fast recovery area location.

SQL> show parameter db_recovery_file_dest

Step # 9: Connect to RMAN prompt with target database.

[oracle@centos ~]$ rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Jan 3 11:46:22 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1363580714)

RMAN>

Step # 10: Configure RMAN with controlfile auto-backup feature that will be auto-backup controlfile in case of major changes done in database.

RMAN> configure controlfile autobackup on;

Step # 11: To enable backup optimization run the following command, by default backup optimization has been configured OFF.


RMAN> configure backup optimization on;

Step # 12: Configure retention policy for backup.


RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;

Step # 13: Connect to the recovery catalog database(RMAN Repository) & Create a tablespace to store RMAN catalog database objects.


[oracle@centos ~]$ sqlplus "/ as sysdba"
SQL> select global_name from global_name;

GLOBAL_NAME
--------------------------------------------------------------------------------
CATALOGD

SQL> create tablespace catalogtbs datafile '/home/oracle/dbfile/catalogtbs1.dbf' size 100M autoextend on maxsize unlimited;

Tablespace created.

Step # 14: Create a RMAN user, assign RMAN tablespace to RMAN user as a default & grant recovery catalog owner,connect & resource privileges to RMAN user.


SQL> create user recoveryman identified by recoveryman;

User created.

SQL> alter user recoveryman default tablespace catalogtbs temporary tablespace temp;

User altered.

SQL> grant recovery_catalog_owner to recoveryman;

Grant succeeded.

SQL> grant connect,resource to recoveryman;

Grant succeeded.

Step # 15: Connect to RMAN on target and recovery catalog database.


[oracle@oracle ~]$ rman target / catalog recoveryman/recoveryman@catalogdb
Recovery Manager: Release 11.2.0.1.0 - Production on Sat Jan 4 14:30:28 2014
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: ORCL (DBID=1363580714)
connected to recovery catalog database

Step # 16: create catalog by issuing the following command in RMAN prompt.


RMAN> create catalog;

recovery catalog created

Step # 17: After creating catalog, Ensure RMAN repository tables by logging into repository database as RMAN user. This is only for the first time.

[oracle@oracle ~]$ sqlplus "recoveryman/recoveryman@catalogdb"
SQL> show user;

USER is "RECOVERYMAN"

SQL> select table_name from user_tables;


Step # 18: Register database with recovery catalog.

RMAN> register database;

database registered in recovery catalog

starting full resync of recovery catalog

full resync complete


Step # 19: Check whether registration was successful.

RMAN> report schema;

Report of database schema for database with db_unique_name ORCL

List of Permanent Datafiles

===========================

File Size(MB) Tablespace           RB segs Datafile Name

---- -------- -------------------- ------- ------------------------

1    670      SYSTEM               YES     /home/oracle/app/oracle/oradata/orcl/system01.dbf

2    490      SYSAUX               NO      /home/oracle/app/oracle/oradata/orcl/sysaux01.dbf

3    30       UNDOTBS1             YES     /home/oracle/app/oracle/oradata/orcl/undotbs01.dbf

4    5        USERS                NO      /home/oracle/app/oracle/oradata/orcl/users01.dbf

List of Temporary Files

=======================

File Size(MB) Tablespace  Maxsize(MB) Tempfile Name

---- -------- ----------- ---------   -------------------------------

1    20       TEMP        32767       /home/oracle/app/oracle/oradata/orcl/temp01.dbf

OR

RMAN> LIST INCARNATION OF DATABASE;

List of Database Incarnations

DB Key  Inc Key DB Name  DB ID            STATUS Reset SCN    Reset Time

------- ------- -------- ---------------- ------------ ---    --------

89      102     ORCL     1363580714       PARENT       1      15-AUG-09

89      90      ORCL     1363580714       CURRENT      945184 02-JAN-14

Target database is registered with the RMAN.

Now you can backup your target(registered) database as per your convenience.

No comments:

Post a Comment