At present, oracle11g has gradually matured, but oracle10g is still king. Recently, many people on the Internet have not very familiar with rman catalog, so I want to write down some data that will help them with oracle's rman backup, including: catalog Database, that is, directory database, target database, that is, target database.
The catalog database is used to store the information of the backup target database. It can be on a server with the target database or a separate server, next, configure the catalog Database to better understand. First, you need to enable archiving logs for the database. If there are no special requirements for archiving logs, you only need to enable it; start the database mount stage www.2cto.com SQL> startup mountORACLE instance started. total System Global Area 167772160 bytesFixed Size 1218316 bytesVariable Size 62916852 bytesDatabase Buffers 100663296 bytesRedo Buffers 2973696 bytesDatabase mounted.
Modify SQL> alter database archivelog; Database altered. the default path for archiving logs is under flash_recovery_area. We can modify the custom location db_recovery_file_dest using the following method: www.2cto.com alter system set db_recovery_file_dest = '/home/oracle/arch' scope = both; the default archive size is 2 GB. We can modify this parameter db_recovery_file_dest_size. The default control retention time is 7 days. We can modify this parameter control_file_record.
The above is about modifying the archive, next we will start to configure the catalog user. We recommend that you use a separate tablespace and a specific user create tablespace rman datafile '/opt/oracle/product/10.2.0/oradata/orcl/rman01.dbf' size 500 M; create temporary tablespace tmp tempfile '/opt/oracle/product/10.2.0/oradata/orcl/tmp01.dbf' size 10 m; create user rmans identified by rman default tablespace rman temporary tablespace tmp; table space name can not use keywords, often use rman, if it is rman when creating the catalog tablespace prompt RMAN-01009: syntax error: found "rman": expecting one: "double-quoted-string, identifier, single-quoted-string"
Grant permissions SQL> grant connect, resource, recovery_catalog_owner to rman; Use rman to log on. Because both my catalog and target are on a server, I run the following statement [oracle @ rhelrcp ~] $ Rman target/catalog rman/rman create catalog tablespace www.2cto.com RMAN> create catalog tablespace rmansrecovery catalog created register database RMAN> register database; database registered in recovery catalostarting full resync of recovery catgfaloull resync complete
Switch to rc_database> select * from rc_database under rman to query registration information; DB_KEY DBINC_KEY dbid name RESETLOGS_CHANGE # RESETLOGS ------------ -------- detail --------- 1 2 1318222470 ORCL 446075 04-AUG-12 the database in the registration shows information about the tablespace recorded in the target database in the recovery directory; DB_KEY DBINC_KEY DB_NAME TS # NAME CREATION_CHANGE # CREATION _ DROP_CHANGE # DROP_TIME inc big tem enc www.2cto.com ------------------------------------------------------------------------------------------------------------------------------
1 2 ORCL 0 SYSTEM 9 30-JUN-05 yes no 1 2 ORCL 1 UNDOTBS1 444079 30-JUN-05 yes no 1 2 ORCL 2 SYSAUX 6609 30-JUN-05 yes no 1 2 ORCL 3 TEMP 446208 04-AUG-12 NO YES 1 2 ORCL 4 USERS 10566 30-JUN-05 yes no 1 2 ORCL 6 RMANS 652267 24-AUG-12 yes no 1 2 ORCL 7 TMP 652320 24-AUG-12 no yes query the data of the target database recorded in the recovery directory select file #, name, bytes from rc_datafile; The above timely rman uses the catalog Configuration