Oracle8i Backup and Recovery Guide
Release 8.1.5

A67773-01

Library

Product

Contents

Index

Prev Prev Next


resync

Syntax


Purpose

To perform a full resynchronization of the recovery catalog. Resynchronizations can be full or partial.

In a full resynchronization, RMAN updates all changed records for the physical schema: datafiles, tablespaces, redo threads, and online redo logs. If the database is open, RMAN also obtains information about rollback segments.

In a partial resynchronization, RMAN reads the current control file to update changed information, but does not resynchronize metadata about the physical schema or rollback segments.

When resynchronizing, RMAN creates a snapshot control file in order to obtain a read-consistent view of the control file, then updates the catalog with any new information from the snapshot.

The resync catalog command updates these classes of records:

Record Type   Description  

Log history  

records that are created whenever a redo log switch occurs. Note that log history records describe an online log switch, not a log archival.  

Archived redo logs  

Records associated with archived logs that were created by archiving an online redo log, copying an existing archived redo log, or restoring backups of archived redo logs.  

Backups  

Records associated with backup sets, backup pieces, backup set members, proxy copies, and image copies.  

Physical schema  

Records associated with datafiles and tablespaces. If the target database is open, then rollback segment information is also updated.  

The following commands update the recovery catalog automatically when the target database control file is mounted and the recovery catalog database is available at command execution:

When you run these commands, RMAN automatically executes a full or partial resynchronization as needed. RMAN reads the current control file and does not resynchronize metadata about physical schema unless it determines that this information has changed. If RMAN does detect a change, it performs a full resynchronization.

Use resync catalog to perform manual full resynchronizations when:

Requirements

Keywords and Parameters

from controlfilecopy 'filename'  

specifies the name of the control file copy to use for reynchronization. Physical schema information is not updated when you use this option.  

Examples

Resynchronizing After a Structural Change

This example adds datafile sales.f to tablespace TBS_1 and then resynchronizes the recovery catalog to reflect the physical database change:

startup mount;
sql "ALTER TABLESPACE tbs_1 ADD DATAFILE ''sales.f'' NEXT 10K MAXSIZE 100K";
resync catalog;
Resynchronizing in ARCHIVELOG Mode

This example performs a manual full resync for an ARCHIVELOG database after archiving all unarchived redo logs:

sql "ALTER SYSTEM ARCHIVE LOG ALL";
resync catalog;



Prev

Top

Next
Oracle
Copyright © 1999 Oracle Corporation.

All Rights Reserved.

Library

Product

Contents

Index