Step 1: First of all your must mount point out your database using ORACLE_SID in windows ORAENV in linux.
C:>set oracle_sid=samdb
C:>sqlplus “/as sysdba”
SQL*Plus: Release 10.2.0.1.0 – Production on Thu Jan 6 19:51:53 2011 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – Production With the Partitioning, OLAPand Data Mining options
SQL> select log_mode from v$database; LOG_MODE ———— ARCHIVELOG
C:>set oracle_sid=samdb
C:>sqlplus “/as sysdba”
SQL*Plus: Release 10.2.0.1.0 – Production on Thu Jan 6 19:51:53 2011 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 – Production With the Partitioning, OLAPand Data Mining options
SQL> select log_mode from v$database; LOG_MODE ———— ARCHIVELOG
Step2 : Create Rman Tablespace
SQL> CREATE TABLESPACE RMAN01 DATAFILE ‘F:oracleproduct10.2.0oradatasamdbRMAN01.DBF’ SIZE 100M REUSE AUTOEXTEND ON; Tablespace created.
SQL> CREATE TABLESPACE RMAN01 DATAFILE ‘F:oracleproduct10.2.0oradatasamdbRMAN01.DBF’ SIZE 100M REUSE AUTOEXTEND ON; Tablespace created.
Step 3: Create RMAN user and password. Here i have been using rman01 and rman01 and assign default tablespace RMAN01 and temporary tablespace TEMP.
SQL> CREATE USER RMAN01 IDENTIFIED BY RMAN01 DEFAULT TABLESPACE RMAN01 TEMPORARY TABLESPACE TEMP;
User created.
SQL> CREATE USER RMAN01 IDENTIFIED BY RMAN01 DEFAULT TABLESPACE RMAN01 TEMPORARY TABLESPACE TEMP;
User created.
Step 4: Grant appropriate permission to rman user (the above user)
SQL> GRANT CONNECT, RESOURCE, RECOVERY_CATALOG_OWNER TO RMAN01;
Grant succeeded.
SQL> GRANT CONNECT, RESOURCE, RECOVERY_CATALOG_OWNER TO RMAN01;
Grant succeeded.
Step 5: Lanch rman tool.
C:>RMAN
Recovery Manager: Release 10.2.0.1.0 – Production on Thu Jan 6 20:51:53 2011 Copyright (c) 1982, 2005, Oracle. All rights reserved.
C:>RMAN
Recovery Manager: Release 10.2.0.1.0 – Production on Thu Jan 6 20:51:53 2011 Copyright (c) 1982, 2005, Oracle. All rights reserved.
Step 6: Connect catalog database using the above rman user.
RMAN> CONNECT CATALOG RMAN01/RMAN01@samdb connected to recovery catalog database
RMAN> CONNECT CATALOG RMAN01/RMAN01@samdb connected to recovery catalog database
Step 7: Once you connect catalog database immediately run the following query using the given tablespace. RMAN> CREATE CATALOG TABLESPACE RMAN01;
recovery catalog created The recovery catalog will store information about target database.
Step 8: Once connect target databse immediately Register your database. this is called incornation database (reference for the catalog database). Once incarnation database register there are some steps configre targer databaes. The target database that will store information about bacup’s and recovery.
C:> RMAN TARGET / CATALOG RMAN01/RMAN01@ADAPTIME Recovery Manager: Release 10.2.0.1.0 – Production on Thu Jan 6 22:51:53 2011 Copyright (c) 1982, 2005, Oracle. All rights reserved. connected to target database: KEYSTONE (DBID=3390662877) connected to recovery catalog database
RMAN> REGISTER DATABASE; database registered in recovery catalog starting full resync of recovery catalog full resync complete
RMAN> SHOW ALL; RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK;#default CONFIGURE CONTROLFILE AUTOBACKUP OFF; # default CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO ‘%F’; # default CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE ENCRYPTION FOR DATABASE OFF; # default CONFIGURE ENCRYPTION ALGORITHM ‘AES128′; # default CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO ‘F:ORACLEPRODUCT10.2.0DB_1DATABASES NCFKEYSTONE.ORA’; # default RMAN> CONFIGURE CONTROLFILE AUTOBACKUP ON; new RMAN configuration parameters: CONFIGURE CONTROLFILE AUTOBACKUP ON; new RMAN configuration parameters are successfully stored starting full resync of recovery catalog full resync complete
No comments:
Post a Comment