My Oracle Support Banner

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 DECEMBER 05, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 12.2.0.1 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.

Goal

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:

Database Name: ORCL
Database Unique Name: DUMMY
Catalog Schema:  RMAN

********

This document discusses about how to delete rman backups of old database Incarnations which have different database id  but same db name  from current active Incarnation

RMAN backups are stored on tapes and use Tivoli Storage Manager and Tivoli Data Protector for Oracle (TDPO).

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. Old db no longer exist

as refresh is done on regular basis.

Below 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


RMAN> list incarnation of database;

List of Database Incarnations
DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
------- ------- -------- ---------------- --- ---------- ----------
47055654 47056337 ORCL 4068596812 PARENT 103414663386 11-NOV-16
47055654 47055655 ORCL 4068596812 CURRENT 116619768923 28-SEP-18
48766624 48767306 ORCL 468494168 PARENT 103414663386 11-NOV-16
48766624 48766625 ORCL 468494168 CURRENT 116813449910 24-OCT-18
49631540 49632222 ORCL 469601900 PARENT 103414663386 11-NOV-16
49631540 49631541 ORCL 469601900 CURRENT 116876447922 06-NOV-18 << Current Active Incarnation

NAME DB_ID FIRST_BACKUP LAST_BACKUP
ORCL 4068596812 09-28-2018 14:08:16 10-22-2018 12:59:10
.
ORCL 469601900 12-16-2018 18:00:36 01-24-2019 10:12:34 << Current Active Incarnation


 

Solution

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
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.