How To Delete Rman Backups Of Old Database Incarnations From TSM/TDPO/ Tape Backup Server With Different dbid but same db name
(Doc ID 2545757.1)
Last updated on MARCH 25, 2022
Applies to:Oracle Database - Enterprise Edition - Version 184.108.40.206 and later
Information in this document applies to any platform.
How To Delete Rman Backups Of Old Database Incarnations From TSM/TDPO/ Tape Backup Server.
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:
Database Name: ORCL
Database Unique Name: DUMMY
Catalog Schema: RMAN
Database ID: 4068596812
This document discusses about how to delete rman backups of old database incarnations which have different database id but same database name (db_name) from current active incarnation.
In the example below, the RMAN backups are stored on tapes and use Tivoli Storage Manager and Tivoli Data Protector for Oracle (TDPO). However, this procedure applies to all media managers and/or backups on disk.
From time to time the databases are refreshed using RMAN duplicate database. After each RMAN refresh there is new Incarnation with new database id created but same db name. an older database no longer exists. This often occurs when a database refresh is done on a regular basis.
The following backups are stored on tape.
In this example the database name is ORCL and there is a need to delete backups of databases with database id 4068596812.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document