V. Create a backup using RMAN

 

RMAN recovery catalog
RMAN recovery directory

1. Create another database to restore the directory database.
Dbca, netmgr not explained
2. Connect to the database instance to create an independent tablespace.
Create tablespace rmantbs datafile '/opt/ora10g/oradata/backup/rmantbs. dbf' size 20 m;
3. Create a user to grant necessary permissions
Grant connect, resource, recovery_catalog_owner to rmanct identified by rmanct;
4. Create a catalog tablespace
Create catalog tablespace rmantbs;

In this way, you can recover the directory database.
Here is the local test database. A problem occurs during Listener Configuration. RMAN target/CATALOG rmanct/rmanct @ backupdb.
When the database backupdb ORA-12541: TNS: No listener
Tnsping: the connection string is normal. listener.org tnsname.org seems to be okay, but it is unreachable. Restart the listener. Okay... @. @ oracle. you are selling again ..
Two minor questions are added:
1) At the beginning, sqlplus rmanct/rmanct @ backupdb is also reported as ORA-12541: TNS: No listener. But sqlplus rmanct/rmanct (oracle_sid is backupdb) is no problem at all.
Cause: listener and tnsname are not required for local login, As long as oracle_sid. In listener. ora and tnsname. after adding a listener to ora, The tnsping result is unreachable. Restart the listener .. actually, I don't know what's going on .... write it down for future reference, or give it to the students who encounter the same problem .. @. @
2) I used the virtual tiejina penguin of the virtual machine. I thought it would be okay if the network was disconnected from the local database. How can the tnsping be disconnected and I connected it again .. well .. okay... .....

Start RMAN target/CATALOG rmanct/rmanct @ backupdb and Start RMAN. \ (^ o ^ )/~

Backup with RMAN

My goal is to write a control file ..
Start to write RMAN and configure the parameter show all. If the command is wrong, A Cute title will be displayed.
RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================

Configure can be found through show all;
Exercise: Write a file, incre_lv0.rman, and restore the file as level 0.
Run {
Configure retention policy to recovery window of 14 days;
Configure controlfile autobackup on;
Configure controlfile autobackup format for device type disk to '/opt/ora10g/oradata/backup/% F ';
Allocate channel C1 device type disk format'/opt/ora10g/oradata/backup/incre_lv0_aegis _ % T _ % U ';
Backup as compressed backupset incremental level = 0 Database
Plus archivelog filesperset 20
Delete all input;
Release Channel C1;
}
Allocate channel for maintenance device type disk;
Crosscheck backupset;
Delete noprompt obsolete;

Then RMAN target/log/opt/ora10g/oradata/RMAN/log/bak. Log partition file =/opt/ora10g/oradata/RMAN/incre_lv0.rman
Complete Level 0 backup
Write another level 1 .. level 0: once a week, once a day, once a day. (I did not back up the database when I learned it. I deleted the file and broke the database without backing up the database, so distressed )..