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 hope to write it down
At present, oracle 11G has gradually matured, But oracle 10g is still king. Recently, many people on the Internet are not very familiar with rman catrman, so I hope to write it down
Now Oracle 11G has gradually matured, But oracle 10g is still king. Recently, many people on the Internet have not very familiar with rman catrman, so I hope to write it down to help them.
Oracle's rman backup data includes:
Catalog Database is a directory database
Target database is the 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. The catalog Database is configured below for better understanding.
First, the database needs to enable archiving logs. If there are no special requirements for archiving logs, you only need to enable them;
Start the database mount stage
SQL> startup mount
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size 1218316 bytes
Variable Size 62916852 bytes
Database Buffers 100663296 bytes
Redo Buffers 2973696 bytes
Database mounted.
Modify archived logs
SQL> alter database archivelog;
Database altered.
The default path for archiving logs is under flash_recovery_area.
We can modify the custom location of this parameter db_recovery_file_dest.
The modification method is as follows:
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 separate tablespaces and dedicated users.
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;
Keywords cannot be used for the tablespace name. rman is often used. If rman prompts when creating the catalog tablespace
RMAN-01009: syntax error: found "rman": expecting one of: "double-quoted-string, identifier, single-quoted-string"
Grant Permissions
SQL> grant connect, resource, recovery_catalog_owner to rman;
Use rman User Login
Because both my catalog and target are on a server, I run the following statements:
[Oracle @ rhelrcp ~] $ Rman target/catalog rman/rman
Create a catalog tablespace
RMAN> create catalog tablespace rmans
Recovery catalog created
Register a database
RMAN> register database;
Database registered in recovery catalog
Starting full resync of recovery catalog
Full resync complete
Query Registration Information
Switch to the rman user to query rc_database
> Select * from rc_database;
DB_KEY DBINC_KEY dbid name RESETLOGS_CHANGE # RESETLOGS
----------------------------------------------------------------
1 2 1318222470 ORCL 446075 04-AUG-12
Registered Database
Displays the table space information of the target database in the recovery directory.
SQL> select * from rc_tablespace;
DB_KEY DBINC_KEY DB_NAME TS # NAME CREATION_CHANGE # CREATION _ DROP_CHANGE # DROP_TIME INC BIG TEM ENC
------------------------------------------------------------------------------------------------------------------------------
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 file information of the target database recorded in the recovery directory.
Select file #, name, bytes from rc_datafile;
The above timely configuration of rman using catalog