Oracle RMAN re-registers the backup set to the Control File

I. Description

There are two types of RMAN backups: Catalog and Nocatalog. For Nocatalog, Oracle uses a control file to save some RMAN backup records. In fact, most of them also use Nocatalog for backup. It is easier to use Nocatalog.

However, when Nocatalog is used, it will enable RMAN to recover the backup information recorded in the dependency and control file. If they are inconsistent, the system cannot recover effectively.

Here we will demonstrate two cases:

(1) Use the nocatalog of RMAN for backup, and then transfer the backup to another directory for restoration.

(2) Use Nocatalog to back up, recreate the control file, and use RMAN backup for recovery.

Both methods use the catalog command to re-register the information of the RMAN backup set to the control file.

II. The backup set location has changed

When we perform remote recovery in RMAN, we will encounter path problems. If the paths are different, we will not be able to perform effective recovery. Let's take a look at how to solve this problem.

2.1 use RMAN Nocatalog for full database backup

Shell script for incremental RMAN backup under Nocatalog

2.2 view backup information

[Oracle @ dave scripts] $ exportNLS_DATE_FORMAT = "YYYY-MM-DD HH24: MI: SS"

[Oracle @ dave scripts] $ rman target/

Recovery Manager: Release 11.2.0.3.0-Production on Tue Apr 16 04:49:49 2013

Copyright (c) 1982,201 1, Oracle and/or itsaffiliates. All rights reserved.

Connected to target database: ANQING (DBID = 743034417)

RMAN> list backup summary;

Using target database control file insteadof recovery catalog

List of Backups

====================

Key ty lv s Device Type Completion Time # Pieces # Copies Compressed Tag

---------------------------------------------------------------------

18 B 0 A DISK 2013-04-16 04:25:53 1 1 NO DAVE_LEV0

19 B 0 A DISK 2013-04-16 04:26:01 1 1 NO DAVE_LEV0

21 B 0 A DISK 2013-04-16 04:26:16 1 1 NO DAVE_LEV0

22 B A DISK 2013-04-16 04:26:26 1 1 NO ARC_BAK

24 B F A DISK 2013-04-16 04:26:31 1 1 NO BAK_CTLFILE

 

 

You can use the list command or the following view to View Details:

V $ BACKUP_PIECE,

V $ BACKUP_SET,

V $ BACKUP_DATAFILE,

V $ BACKUP_REDOLOG,

V $ BACKUP_SPFILE.

 

Backup set queried by V $ BACKUP_PIECE:

/U01/backup/dave_lev0_0jo76nh7_1_20171_30416

/U01/backup/dave_lev0_0io76nh7_1_1_30416

/U01/backup/dave_lev0_0ko76nim_0000000020130416

/U01/backup/arch_0no76njh_1_20130416

/U01/backup/ctl_file_0oo76njm_0000000020130416

 

Here, the backup set stores the/u01/backup directory:

[Oracle @ dave admin] $ cd/u01/backup

[Oracle @ dave backup] $ ls

Arch_0no76njh_1_1_20130416 block_change_tracking.f dave_lev0_0io76nh7_1_1_20130416 dave_lev0_22o687qp_1_1_20130404

Arch_1ho6566m_20171000020130403 ctl_file_0oo76njm_2017100001_30416 dave_lev0_0jo76nh7_20171_20130416 dave_spfile_1mo65679_20171_20130403

Arch_1io6566n_0000000020130403 ctl_file_1lo65676_0000000020130403 dave_lev0_0ko76nim_0000000020130416 dave_spfile_29o687sc_0000000020130404

Arch_26o687rp_0000000020130404 ctl_file_28o687sa_0000000020130404 dave_lev0_20o687pl_0000000020130404

Arch_27o687s8_0000000020130404 ctl_file_2ao6vobb_0000000020130413 dave_lev0_21o687pl_0000000020130404

1 2 3 4 5 6 7 Next Page