Query RMAN catalog to view my controlfile backup in backup piece

version: 11.1.0.7
We need to restore an year old database and its backup is availble in TAPE, RMAN directly takes backup to TAPE.
we have dropped the database, Now there is a requirement to restore the database.
we Know DBID, I can restore the db once i can restore the contolfile.
However we did not have controlfile auto backup. whenever there is FULL/incremental backup cotnrolfile is included in that backup. now we have the rman catalog for that database. so How I can query rman catalog to find which backup piece containing the latest controlfile? once we know the backuppiece info, we can restore controlfile from that piece
any help on this?

user8860934 wrote:
version: 11.1.0.7
We need to restore an year old database and its backup is availble in TAPE, RMAN directly takes backup to TAPE.
we have dropped the database, Now there is a requirement to restore the database.
we Know DBID, I can restore the db once i can restore the contolfile.
However we did not have controlfile auto backup. whenever there is FULL/incremental backup cotnrolfile is included in that backup. now we have the rman catalog for that database. so How I can query rman catalog to find which backup piece containing the latest controlfile? once we know the backuppiece info, we can restore controlfile from that piece
any help on this?Connect with recovery catalog through rman and
set dbid <yourdbid>
list backup of controlfile;In this case you will see all backups of controlfile.And according time this backup you can restore database using
rman>restore controlfile from 'backupset_location';

Similar Messages

Controlfile vs. RMAN Catalog

Hey, my controlfile is increasing really fast. So I have to recreate the the controlfile on a regular basis. Its growing nearly 150 MB in one month.
Therefore the backups are getting slow, also a logswitch is impacting my database performance. I am using a physical standby so the db parameter archive_lag_target is set to 600 (sec), so every 10 minutes a logswitch occurs.
v$controlfile_record_section is showing archivelogs are the most space consuming part.
Now the question:
Is it an appriopate way to switch from controlfile to rman catalog ? Will this help me to keep the controlfile tiny ?
Chris

Hi Christian,
Why is the size of the controlfile a problem for you?
There are other points to keep in mind if you use controlfile or rman catalog.
For example if you would like to use standby databases so Oracle recommend to use an rman catalog.
For me it is not a problem of the size it is your decision to make a matrix and look about the pros and cons
between controlfile and rman catalog.
But if it is a production environment it is a good idea to use a rman catalog.
regards
SPA2

RMAN Backup using Rman Catalog

Hi
can we take backup of oracle9i database using oracle10g RMAN Catalog?
Thanks
With Regards
OH

I guess this is related to backward compatibility support principle. Target database's controlfile and RMAN catalog is synchronized and different version may have different structure and feature. When we need to completely restore an Oracle instance from backup, RMAN catalog must be able to support target database, and it may not be possible if RMAN catalog version is lower than target database. I hope I get the message across.
Pls anybody correct me if I am wrong

Backup rman catalog

Hi
my RMAN catalog db is is non archive log mode
and we never back it up
for better protection , i will convert it to archive mode and hotbackup it and use controlfile as catalog
am i in the right way to backup my rman catalog db?
Thanks

user9145417 wrote:
Hi
my RMAN catalog db is is non archive log mode
and we never back it up
for better protection , i will convert it to archive mode and hotbackup it and use controlfile as catalog
am i in the right way to backup my rman catalog db?
Yes , you should take a hot backup of catalog DB and also configure controlfile auto backup.
Regards
Rajesh

Doubt in taking backup using RMAN CATALOG

Hi,
when i was using RMAN CATALOG.
can i create separate database for catalog on server machin/backup server?
if create separate database for catalog?
how to create a separate database for catalog and plz give clear instruction one by one.
thanks

can i create separate database for catalog on server machin/backup server?
Yes.
and
also you create separate user to "recovery catalog" and "separate tablespace" for recovery catalog.
1.creation of recovery database catalog some like normal database catalog.
but after creation of database you create one user for recovery catalog.
Note :
"User that owns the recovery catalog schema. This is a user defined in the recovery catalog database that has been granted the RECOVERY_CATALOG_OWNER role."
http://download-west.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmcnctg002.htm

Unregistering of a database from RMAN Catalog

Hello,
We had set up RMAN backup though RMAN Catalog for one of our database.
We later decided not to take the backups of this particular database. One of the DBA did something but what we can see now is that -
1. Target database is not registered in the catalog so no information can be gathered rman prompt after connecting to catalog through target database
2. But the recovery catalog "rc_backup_datafile" is showing as if it has old backups
We know that the tapes don't have the backup of this database.
Question - How to remove information from recovery catalog for a database in such a situation where although the database is not registered in the catalog but somehow the information related to old backups still persists in the catalog tables.
Thanks!

Thanks Tycho, for my purpose DBMS_RCVCAT.UNREGISTERDATABASE worked fine.
I have another question though -
We have compressed backup for one of the database/
If I look at backupset by executing "list backupset xxxxxxx;" command it shows the correct compressed value (in GB) of the backup set.
BUT when I look at the rc_backup_datafile table of the rman catalog for the size of of the backupset, it shows the uncompresses size of the backupset. I am using following query -
select BS_KEY,SUM(blocks*block_size)/1024/1024/1024 GB from rc_backup_datafile where DB_NAME='CCSTG04' and BS_KEY=1 group by BS_KEY;
Question - How to check the compressed size of the backupset from the Catalog tables/views?
Thanks for your help on this!
Thanks!
,

Our RMAN Catalog Problem

Hello
We have 7 major oracle instances on 2 servers and we have created a RMAN catalog on another server
Our principal databases are Standard Oracle 10g (10.2.0.2.0) under linux , and the catalog is Enterprise Oracle 10g (10.2.0.2.0) in Windows all the databases are registered in catalog when I query RC_DATABSE view it shows all
instances informations , in all RMAN login commands the "CATALOG" clause has been written
Now my problem is that just two of databases backups are recorded in catalog for example when I query "RC_BACKUP_SET" view it only contains backups of two databases while are backups have been performed completely without any error
Do you know what is problem ?
thank you

select dbid,name from rman_user.rc_database;
DBID        NAME
<h4>----------------  ----------------</h4>
1498968931       SCSDB
4293064263        SSTDB
861276728         SUBDB
2404423160        SAM
3976246282        SFIDB
1760672514    SCEDB
817528985        S900NS1
select t.name,t1.db_id,bs_key
from rman_user.RC_BACKUP_SET t1,rman_user.rc_database t
where t1.db_id=t.dbid;
NAME        DB_ID        BS_KEY
<h4>----------------  ----------------  ----------------</h4>
SUBDB        861276728        14366
SUBDB        861276728        14365
SUBDB        861276728        14364
SAM        2404423160        14491
SAM        2404423160        14490
SAM        2404423160       14489
select name, max(START_TIME)
from rman_user.rc_database d,
rman_user.rc_backup_set s
where db_id(+) = dbid
group by name
order by 2 desc;
NAME        MAX(START_TIME)
<h4>----------------  ----------------</h4>
SCEDB
S900NS1
SCSDB
SFIDB
SSTDB
SAM        6/14/2008 1:06:15 AM
SUBDB        6/13/2008 9:02:43 PM
This date (6/14/2008) is old because I haven't used the catalog for a long time, due to the problem I've mentioned above.
Edited by: TakhteJamshid on Jan 10, 2010 2:49 AM
Edited by: TakhteJamshid on Jan 10, 2010 3:00 AM

Resync or any other maintenace work on RMAN catalog....

I have inherited RMAN catalog created in Oracle 10g R2 to take the backup of 10g databases.
1.I want to check what are all the databases backed up. What query I should run? Like view names.
2.Is there any command I should run to make sure RMAN catalog is up to date. Like synchronizing. Wants to make sure my backup is recoverable.
Thank you,
Smith

1. Use RC_DATABASES view to get registered databases in recovery catalog and RC_BACKUP_SET view to get registered backup sets.
See http://download.oracle.com/docs/cd/B28359_01/backup.111/b28270/rcmreprt.htm#CHDIJDEF
2. see RESYNC CATALOG in http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta052.htm#RCMRF150
which says:
>
RMAN automatically executes a full or partial resynchronization of the recovery catalog as needed when you execute RMAN commands, so long as the control file is mounted and the recovery catalog database is available at command execution.
>
Note however that database control file is always the source repository even if you use a recovery catalog.
Even if you loose recovery catalog you should be be able to retrieve RMAN backups. See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmrecov.htm#BRADV156.
Edited by: P. Forstmann on 25 févr. 2010 20:15

To Find the instance name in RMAN catalog

Hi ,
I have rman catalog which got registered 150 databases. Am able to get the dbname,id for the 150 databases but not able to get the server name (host name) of the correspoding databases in catalog views as well as in db views.
Kindly revert us if you know any other analyisis or way to find the server names.
Regards
Krishnan

What does RMAN care if RAC is involved or not?
Oracle provides RMAN for backing up and restoring the database. RMAN enables you to back up, copy, restore, and recover datafiles, control files, SPFILEs, and archived redo logs. RMAN is included with the Oracle server and it is installed by default. You can run RMAN from the command line or you can use it from the Backup Manager in Oracle Enterprise Manager. The procedures for using RMAN in RAC environments do not differ substantially from those for Oracle single-instance environments. Refer to the Oracle Backup and Recovery documentation set for more information about single-instance RMAN backup procedures.

Restore controlfile from tape backup without autobackup setting on

I am testing a scenraio of restoring control file if we loose all control files.
My RMAN settings for CONTROLFILE AUTOBACKUP is OFF. But, I have taken a backup of controlfile using 'BACKUP CURRENT CONTROL FILE' .
When I tried to restore control file. I am receiving following error:
RMAN> run {
2> allocate channel c101 type sbt_tape;
3> restore controlfile ;
4> }
allocated channel: c101
channel c101: sid=153 devtype=SBT_TAPE
channel c101: VERITAS NetBackup for Oracle - Release 6.0 (2006110304)
Starting restore at 24-MAY-2007 13:44:59
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 05/24/2007 13:44:59
RMAN-06563: control file or SPFILE must be restored using FROM AUTOBACKUP
My question is, How can I restore control file from tape backup without CONTROLFILE AUTOBACKUP setting ON.
It sounds like, There is no way we can restore control file from tape backup if you've not set the CONTROLFILE AUTOBACKUP is ON.
Please advice

When all controlfiles are lost and a recovery catalog is NOT used, RMAN has no information , where to find the controlfile backup. It's not enough to specify the channel, such a channel could hold many different backups from many different databases. You have tell , which database and which backupset. Modify your run block:
SET DBID <DBID of the database,for which you want to restore the controlfile>;
RESTORE CONTROLFILE FROM <name_of_backupiece_which_contains_the_controlfile backup>';
Werner

New RMAN catalog in existing EMREP database - new user and tablespace?

Hi all,
I am FINALLY getting "with the times" and trying to get my databases to back up with RMAN. I already have a dedicated server that is running Oracle Enterprise Manager 10g Grid Control, so it already has the OMS database on it, called EMREP. I was hoping to just use this database as my RMAN catalog, is that considered good practice or not?
So assuming this practice is considered OK, I know that I need to create a new user (which I'll just call RMAN) in this database. Would it be best to also create a separate tablespace for this user? I have no idea how big I should expect this RMAN schema to get. I'm sure it all depends on the number of databases I'm backing up, but can anyone give me some realistic size expectations that I could start with?
Any advice/info is greatly appreciated!

I think that the catalog is only applicable if you will have several databases to manage.
If you he will have only one, I dont see necessity to use the catalog, therefore with backups of controlfiles only, you can to execute the tasks of backup/restore/recovery.
But, for catalog creation information, see
RMAN CATALOG CREATION STEP BY STEP by Joel Pérez
RMAN ( CATALOG CREATION ) STEP BY STEP by Joel Pérez
Message was edited by:
ARF

Need a create db script to manually create a 10g rman catalog db on unix

Hi, Gurus:
I would like to manually create a rman catalog database (Oracle 10g) on a HP-UX environment. Could anyone share a sql script to do that?
It is going to be used to backup about 15 databases directly to tape and the retention policy is going to be 35 days. How big the database should be?
Thanks in advance.

I can't find any documentation supporting Oracle support's theory.And who writes the Oracle documentation? People in this forum?
You got the "Best Practice" advise.
If you have rman catalog on the same server or on the same database, it is like storing your backup on the same server you took it from.
So, the idea od RMAN catalog is to have your catalog available for any recovery. If you cannot recover your recovery catalog, then you are better off using the controlfile as the repository.

Set RMAN catalog default setting for all databases

Hi,
I am running a 11gR1 RMAN catalog.
I am wondering if is it possible to change a default configuration setting in the RMAN catalog so that all the new databases will inherit it.
For example, I would like all the new databases registered to the catalog to have:
BACKUP OPTIMIZATION ON
RETENTION POLICY TO REDUNDANCY 7
Thanks,
massi

No, the catalog cannot "dictate" configurations for databases. Each database retains configuration in the controlfile and this can be updated only by an rman connection (i.e. rman connecting to the database as a target). The CONFIGURE command in rman is used to set a "permanent" configuration parameter for a database but must be issued for each database individually.
Hemant K Chitale

Rman catalog files

We have 11g rac one node implemented on windows 2008, i took complete backup using rman from the production database and I copied the files to the test server and when am doing
restore database validate it is still pointing to production backup location :
c:\rman\ (test location)
e:rman (production location)
Am getting the error :
channel ORA_DISK_1: reading from backup piece E:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
channel ORA_DISK_2: reading from backup piece E:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
Wondering why am getting the above error as I didn't catalog any backup piece on that location and the location is taken from production.
test worklog
RMAN> restore controlfile from 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
Starting restore at 26-JAN-12
using channel ORA_DISK_1
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
output file name=C:\APP\ADMINISTRATOR\ORADATA\medt\CONTROL\CONTROL01.CTL
output file name=C:\APP\ADMINISTRATOR\ORADATA\medt\CONTROL\CONTROL02.CTL
Finished restore at 26-JAN-12
RMAN> catalog backuppiece 'C:\rman\DATA_73_1_29N1OG00_1_1.BAK';
released channel: ORA_DISK_1
cataloged backup piece
backup piece handle=C:\RMAN\DATA_73_1_29N1OG00_1_1.BAK RECID=34 STAMP=773622357
RMAN> catalog backuppiece 'C:\rman\'DATA_74_1_2AN1OG00_1_1.BAK';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "identifier": expecting one of: "comma, ;"
RMAN-01008: the bad identifier was: DATA_74_1_2AN1OG00_1_1
RMAN-01007: at line 1 column 31 file: standard input
RMAN> catalog backuppiece 'C:\rman\DATA_74_1_2AN1OG00_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_74_1_2AN1OG00_1_1.BAK RECID=35 STAMP=773622388
RMAN> catalog backuppiece 'C:\rman\DATA_75_1_2BN1OG00_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_75_1_2BN1OG00_1_1.BAK RECID=36 STAMP=773622401
RMAN> catalog backuppiece 'C:\rman\DATA_76_1_2CN1OG01_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK RECID=37 STAMP=773622413
RMAN> catalog backuppiece 'C:\rman\DATA_77_1_2DN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK RECID=38 STAMP=773622427
RMAN> catalog backuppiece 'C:\rman\DATA_78_1_2EN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK RECID=39 STAMP=773622439
RMAN> catalog backuppiece 'C:\rman\DATA_79_1_2FN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK RECID=40 STAMP=773622501
RMAN> catalog backuppiece 'C:\rman\DATA_80_1_2GN1OG02_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK RECID=41 STAMP=773622513
RMAN> catalog backuppiece 'C:\rman\DATA_81_1_2HN1OG03_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK RECID=42 STAMP=773622525
RMAN> catalog backuppiece 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_82_1_2IN1OG3N_1_1.BAK RECID=43 STAMP=773622546
RMAN> catalog backuppiece 'C:\rman\DATA_83_1_2JN1OG3N_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_83_1_2JN1OG3N_1_1.BAK RECID=44 STAMP=773622560
RMAN> catalog backuppiece 'C:\rman\DATA_84_1_2KN1OG75_1_1.BAK';
cataloged backup piece
backup piece handle=C:\RMAN\DATA_84_1_2KN1OG75_1_1.BAK RECID=45 STAMP=773622574
RMAN> restore database validate;
Starting restore at 26-JAN-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=350 device type=DISK
allocated channel: ORA_DISK_2
channel ORA_DISK_2: SID=407 device type=DISK
allocated channel: ORA_DISK_3
channel ORA_DISK_3: SID=466 device type=DISK
allocated channel: ORA_DISK_4
channel ORA_DISK_4: SID=524 device type=DISK
allocated channel: ORA_DISK_5
channel ORA_DISK_5: SID=582 device type=DISK
allocated channel: ORA_DISK_6
channel ORA_DISK_6: SID=640 device type=DISK
channel ORA_DISK_1: starting validation of datafile backup set
channel ORA_DISK_2: starting validation of datafile backup set
channel ORA_DISK_3: starting validation of datafile backup set
channel ORA_DISK_4: starting validation of datafile backup set
channel ORA_DISK_5: starting validation of datafile backup set
channel ORA_DISK_6: starting validation of datafile backup set
channel ORA_DISK_1: reading from backup piece E:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
channel ORA_DISK_2: reading from backup piece E:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
channel ORA_DISK_3: reading from backup piece C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK
channel ORA_DISK_4: reading from backup piece C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK
channel ORA_DISK_5: reading from backup piece C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK
channel ORA_DISK_6: reading from backup piece C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK
channel ORA_DISK_1: errors found reading piece handle=E:\RMAN\DATA_80_1_2GN1OG02
_1_1.BAK
channel ORA_DISK_1: failover to piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
tag=TAG20120126T174849
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: validation complete, elapsed time: 00:00:46
channel ORA_DISK_2: errors found reading piece handle=E:\RMAN\DATA_81_1_2HN1OG03
_1_1.BAK
channel ORA_DISK_2: failover to piece handle=C:\RMAN\DATA_81_1_2HN1OG03_1_1.BAK
tag=TAG20120126T174849
channel ORA_DISK_2: restored backup piece 1
channel ORA_DISK_2: validation complete, elapsed time: 00:00:56
channel ORA_DISK_6: piece handle=C:\RMAN\DATA_79_1_2FN1OG02_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_6: restored backup piece 1
channel ORA_DISK_6: validation complete, elapsed time: 00:01:26
channel ORA_DISK_3: piece handle=C:\RMAN\DATA_76_1_2CN1OG01_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_3: restored backup piece 1
channel ORA_DISK_3: validation complete, elapsed time: 00:01:36
channel ORA_DISK_5: piece handle=C:\RMAN\DATA_78_1_2EN1OG02_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_5: restored backup piece 1
channel ORA_DISK_5: validation complete, elapsed time: 00:01:36
channel ORA_DISK_4: piece handle=C:\RMAN\DATA_77_1_2DN1OG02_1_1.BAK tag=TAG20120
126T174849
channel ORA_DISK_4: restored backup piece 1
channel ORA_DISK_4: validation complete, elapsed time: 00:02:07
Finished restore at 26-JAN-12Kai

Those "prod" locations are found in the backup controlfile:
>
RMAN> restore controlfile from 'C:\rman\DATA_82_1_2IN1OG3N_1_1.BAK';
>
>
channel ORA_DISK_1: errors found reading piece handle=E:\RMAN\DATA_80_1_2GN1OG02
_1_1.BAK
channel ORA_DISK_1: failover to piece handle=C:\RMAN\DATA_80_1_2GN1OG02_1_1.BAK
tag=TAG20120126T174849
>
You can see how RMAN noticed it couldn't find that piece and then found one that you had previously cataloged. Looks good to me.

RMAN CATALOG에서 TARGET DB를 UNREGISTER하는 방법

제품 : RMAN
작성날짜 : 2001-05-28
RMAN CATALOG에서 TARGET DB를 UNREGISTER하는 방법
===============================================
1) UNREGISTER 하고자 하는 Database를 RMAN CATALOG에서 확인한다.
SELECT * FROM RC_DATABASE;
2) UNREGISTER하고자 하는 DATABASE에 속한 BACKUPSET들을 모두 제거한다.
- 제거하고자 하는 BACKUPSET을 알아내는 방법
RMAN> list backupset of database;
- BACKUPSET을 제거하는 방법
RMAN> allocate channel for delete type disk;
RMAN> change backupset XXX delete;
* 위에서는 DISK에대해 CHANNEL을 설정하였지만 TAPE에 대해 CHANNEL설정을
하려면 아래와 같은 COMMAND를 수행한다.
RMAN> allocate channel for delete type 'sbt_tape';
또한 XXX는 'list backupset of database'의 결과 중에서 'LIST OF KEY'의
값을 의미한다.
3) 다음과 같은 PROCEDURE를 RECOVERY CATALOG에서 수행함으로써 DATABASE를 UNREGISTER한다.
execute dbms_rcvcat.unregisterdatabase (db_key, db_id)
* DB_KEY와 DB_ID는 다음과 같은 QUERY문에서 알아낼 수 있다.
SVRMGR> select * from rc_database;
EXAMPLE:
========
Unregistering ORCL database:
1) The following will list the backupset for the database that we want to
uncatlog.
RMAN> list backupset of database;
RMAN-03022: compiling command: list
RMAN-06230: List of Datafile Backups
RMAN-06231: Key File Type LV Completion_time Ckp SCN Ckp Time
RMAN-06232: ------- ---- ------------ -- --------------- ---------
RMAN-06233: 858 1 Full 16-SEP-98 253487 16-SEP-98
RMAN-06233: 858 2 Full 16-SEP-98 253487 16-SEP-98
RMAN-06233: 858 3 Full 16-SEP-98 253487 16-SEP-98
RMAN-06233: 858 4 Full 16-SEP-98 253487 16-SEP-98
==================================
2) The following will show allocation of a delte channel, deleting the
backupset, and running the list command to confirm that the backupsets were
removed. The delete command will remove the backupsets from the backup location.
RMAN> allocate channel for delete type disk;
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: delete
RMAN-08500: channel delete: sid=10 devtype=DISK
RMAN> change backupset 858 delete;
RMAN-03022: compiling command: change
RMAN-03023: executing command: change
RMAN-08073: deleted backup piece
RMAN-08517: backup piece handle=C:\ORANT\DATABASE\RMANORCLBACKUP\DF_344180532_30
_1 recid=27 stamp=344180538
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN> list backupset of database;
RMAN-03022: compiling command: list
RMAN-06230: List of Datafile Backups
RMAN-06231: Key File Type LV Completion_time Ckp SCN Ckp Time
RMAN-06232: ------- ---- ------------ -- --------------- ----------
================================
3) From the recovery catalog:
SVRMGR> select * from rc_database;
DB_KEY DBINC_KEY DBID NAMERESETLOGS_ RESETLOGS
584 585 868345165 ORCL 192881 18-AUG-98
1 row selected.
SVRMGR> execute dbms_rcvcat.unregisterdatabase(584,868345165);
Statement processed.
SVRMGR> select * from rc_database;
DB_KEY DBINC_KEY DBID NAME RESETLOGS_ RESETLOGS
0 rows selected.

Query RMAN catalog to view my controlfile backup in backup piece

Similar Messages

Maybe you are looking for