Target is the source database for backup operations. All the objects we perform backup and restoration are in this database. By default, the backup set information is saved in controlfile,
Target is the source database for backup operations. All the objects we perform backup and restoration are in this database. By default, the backup set information is saved in controlfile,
The Oracle RMAN tool has three source database objects: target, catalog, and auxiliary.
Target is the source database for backup operations. All the objects we perform backup and restoration are in this database. By default, backup set information is stored in controlfile, and catalog is an optional database. Backup metadata can be stored separately in catalog Database. Auxiliary is used as an auxiliary operation. Some operations related to backup and restoration can be completed on auxiliary.
This article starts with a 10 Gb database and builds different clone databases on the same host. Note: The clone operations on other hosts are identical.
Recommended reading:
RMAN: Configure an archive log deletion policy
Basic Oracle tutorial-copying a database through RMAN
Reference for RMAN backup policy formulation
RMAN backup learning notes
Oracle Database Backup encryption RMAN Encryption
1. Environment Introduction
We chose Oracle 10gR2 for testing and host in Linux.
SQL> select * from v $ version;
BANNER
---------------------------------
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0-Prod
PL/SQL Release 10.2.0.1.0-Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0-Production
NLSRTL Version 10.2.0.1.0-Production
2. Target Database Backup
Catalog is not selected for the current database. controlfile is used for backup files. The database instance name is oratest and serves as the data source. The backup information is as follows:
RMAN> list backup;
List of Backup Sets
==============================
BS Key Type LV Size Device Type Elapsed Time Completion Time
-------------------------------------------------------------
13 Full 595.90 m disk 00:00:30 05-MAR-14
BP Key: 13 Status: AVAILABLE Compressed: NO Tag: TAG20140305T111526
Piece Name:/u01/app/oracle/flash_recovery_area/ORATEST/backupset/2014_03_05/o1_mf_nnndf_TAG20140305T111526_9kf5pgf2 _. bkp
(Space reasons, omitted ......)
BS Key Size Device Type Elapsed Time Completion Time
-------------------------------------------------------
15 15.07 m disk 00:00:02 05-MAR-14
BP Key: 15 Status: AVAILABLE Compressed: NO Tag: TAG20140305T112405
Piece Name:/u01/app/oracle/flash_recovery_area/ORATEST/backupset/2014_03_05/o1_mf_annnn_tag20140305t112405_9kf66bp_. bkp
List of Archived Logs in backup set 15
Thrd Seq Low SCN Low Time Next SCN Next Time
-------------------------------------------------
1 2 576174 04-MAR-14 578638 05-MAR-14
1 3 578638 05-MAR-14 578643 05-MAR-14
1 4 578643 05-MAR-14 578677 05-MAR-14
BS Key Type LV Size Device Type Elapsed Time Completion Time
-------------------------------------------------------------
16 Full 6.80 m disk 00:00:01 05-MAR-14
BP Key: 16 Status: AVAILABLE Compressed: NO Tag: TAG20140305T112407
Piece Name:/u01/app/oracle/flash_recovery_area/ORATEST/autobackup/2014_03_05/o1_mf_s_841401_7_9kf66qvs _. bkp
Control File Included: Ckp SCN: 578684 Ckp time: 05-MAR-14
SPFILE Included: Modification time: 05-MAR-14
Note: During the backup process, you must have a separate backup archivelog all process to save the archived logs as a separate backup set. If you do not perform this operation, an error occurs during duplicate.
RMAN> backup archivelog all;
Starting backup at 05-MAR-14
(Space reasons, omitted ......)
Starting Control File and SPFILE Autobackup at 05-MAR-14
Piece handle =/u01/app/oracle/flash_recovery_area/ORATEST/autobackup/2014_03_05/o1_mf_s_841401_7_9kf66qvs _. bkp comment = NONE
Finished Control File and SPFILE Autobackup at 05-MAR-14
During the duplicate operation, it is best to maintain the mount status of the target database!
3. Network Configuration
It is important to ensure the interconnection between target and auxiliary whether duplicate is built locally or remotely. Therefore, the configuration process is required for TNS connections.
Oracle Net configuration files: listener. ora, tnsnames. ora, and sqlnet. ora. At least ensure the interconnection configuration of tnsnames. ora.
[Oracle @ SimpleLinuxUp admin] $ cat tnsnames. ora
# Tnsnames. ora Network Configuration File:/u01/app/oracle/product/10.2.0/db_1/network/admin/tnsnames. ora
# Generated by Oracle configuration tools.
ORATEST = -- target
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = 127.0.0.1) (PORT = 1521 ))
)
(CONNECT_DATA =
(SERVICE_NAME = oratest)
)
)
ORAAUX = -- target aupoliciary
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP) (HOST = 127.0.0.1) (PORT = 1521 ))
)
(CONNECT_DATA =
(SERVICE_NAME = oraaux)
)
)