Manual Completion of a Failed RMAN Backup Based Duplicate (Doc ID 360962.1)

Last updated on JUNE 12, 2024

Applies to:

Oracle Database Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Purpose

The purpose of this note is to provide details on how to resolve an incomplete RMAN duplicate.

For active RMAN duplicate, using FROM ACTIVE DATABASE, see:

Manual Completion of a Failed RMAN Duplicate FROM ACTIVE DATABASE (Doc ID 1602916.1)

For earlier RMAN versions, like 10g and 11.1, see:

Manual Completion of a Failed RMAN Backup based Duplicate 10g and Oracle 11.1 (Doc ID 2847672.1)

Scope

This article is meant for database administrators and backup and recovery specialists who are tasked
to complete a failed RMAN duplicate database.

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample schema(s), Public Documentation delivered with
an Oracle database product or other training material. Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:

Target (source) Database Name: PROD
Auxiliary (source) Database Name: AUX