Oracle rman nocatalog and catalog

Oracle rman nocatalog and catalog 1. Check whether archive mode is Enabled [oracle @ test ~] $ Sqlplus/as sysdbaSQL * Plus: Release 10.2.0.1.0-Production on Wednesday April 17 03:15:57 2013 Copyright (c) 1982,200 5, Oracle. all rights reserved. connected to an idle instance. SQL> startup mount; ORACLE instance started. total System Global Area 285212672 bytesFixed Size 1218992 bytesVariable Size 117442128 bytesDatabase Buffers 163577856 bytesRedo Buffers 2973696 bytesDatabase mounted. SQL> archive log List; database log mode Archive ModeAutomatic archival EnabledArchive destination/opt/app/oracle/archiveOldest online log sequence 19 Next log sequence to archive 21 Current log sequence 212 and rman login local rman target/rman target sys/123456 rman target sys/123456 nocatalog remotely log on to rman target sys/123456 @ wolf nocatalog 2, catalog, nocatalog1, and nocatg1 using the control file as catalog, A lot of backup information is required when no backup is performed. More and more rman backup information is contained in the control file. (Suitable for small enterprises and a small number of databases) at this time, you must pay attention to backup control files. And set the retention time to a little longer. Because the rman backup records in the control file belong to the loop reuse record type, if the control file region containing these records is full, these records will be deleted, resulting in no backup records in the control file, that is to say, it is the same as never before. Of course, if the control file does not contain rman backup records, rman cannot be used for recovery. The initialization parameter control_file _ record_keep_time is used to set the backup information retention time. The previous backup information is automatically cleared at the specified time: SQL> show parameter controlNAME TYPE commandid VALUE implements control_file_record_keep_time integer7control_files string/opt/app/oracle/oradata/wolf/control01.ctl,/opt/app/oracle/oradata/wolf/control02.ctl, /opt/app/oracle/oradata/wolf/control03.ctlSQL> alt Er system set control_file_record_keep_time = 14 scope = both; System altered. SQL> show parameter control; NAME TYPE commandid VALUE ---------------------------- control_file_record_keep_time integer14control_files string/opt/app/oracle/oradata/wolf/control01.ctl, /opt/app/oracle/oradata/wolf/control02.ctl,/opt/app/oracle/oradata/wolf/control0 3. ctlSQL> select name, value, issys_modifiable from v $ parameter where name = 'control _ file_record_keep_time '; NAME--------------------------------------------------------------------------------VALUE--------------------------------------------------------------------------------ISSYS_MODIFIABLE ------------------------- catalog, catalog is the need to create a backup directory, establish a recovery directory, in this way, all the information is written to the backup directory. Generally, all rman backup information can be written as long as there is enough space. (Suitable for large enterprises and multiple databases) create catlog Directory: create Table space create tablespace rman_wolf '/opt/app // rmanwolf. dbf 'size 20 m; create user rman identified by rman default tablespace rman_wolf quota unlimited on rman_wolf; Authorize grant recovery_catalog_ower to rman; grant connect to rman; view role permissions select * from dba_sys_privs where grantee = 'reovery _ CATALOG_OWNER; Create recovery directory rman target/catalog rman/rmancreate catalog tablespace rman_wolf; reg Ister database; (target database to be backed up) Note: When Rman nocatalog is used for restoration, the database must be in the "mount" state, that is, the control file must be loaded first, otherwise, RMAN cannot find the recorded backup information. The precondition for Oracle startup mount is that control must exist. Therefore, you must restore controlfile Before restoring datafile. When using the Rman catalog method, you can start up nomount and restore controlfile. However, when using the Rman nocatalog method, you must restore the controlfile using the file method. Next, we will compare the restoration steps of Rman nocatalog and Rman catalog to establish a correct backup policy (the following recovery operations are performed online): Rman nocatalog recovery: 1) create an oracle runtime environment (including init or sp files) 2) restore controlfile to the specified location of the init file (or start NOMOUNT first, restore controlfile from autobackup in RMAN) 3) startup mount4) Rman, Rman, restore datafile, recover datafile5) alter database open resetlogsRman catalog recovery: 1) Create an oracle runtime environment (including init or sp files) 2) Rman, restore controfile3) alter database mount4) Rm An, restore datafile5) alter database open resetlogs we can see that during Rman nocatalog backup, controlfile must be backed up in file mode. In addition, because the controlfile is used to store backup information in nocatalog, we recommend that you increase the value of CONTROL_FILE_RECORD_KEEP_TIME in the Oracle parameter file (7 days by default). This parameter is set to $ ORACLE_HOME/dbs/initSID. ora (9i may also be in spfile and can only be changed using Oracle statements ).