Rman :: report backup tag= ??

hello all,
few weeks back i took a full backup of my database using rman and specified a tag like ' %weekly.......%' . Now i dont remember the name of the tag.
how would i find the TAG ?. I checked the TAG column in v$backup_piece, but to no use.
TIA,
JJ

but list backup summary did not get me the tag !!How no??
The 'list backup summary' show the TAG yes...
LIST BACKUP SUMMARY;
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Tag
35 B A A SBT_TAPE FEB 08 2002 05:37:37 1 1 TAG20020208T053733
42 B F A SBT_TAPE FEB 08 2002 05:38:21 1 1 TAG20020208T053744

Similar Messages

RMAN report need backup

We have an incremental level-1 backup Mon-Sat and cold full backup on Sundays with retention policy of 7 days. While troubleshooting some backup issues (space issue, expired backups) I ran the following commands and trying to understand the output.
RMAN> report need backup database;
RMAN retention policy will be applied to the command
RMAN retention policy is set to recovery window of 7 days
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
100 146 /orahprdidx/hprd/psindex05.dbf
RMAN> report unrecoverable;
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
RMAN> report need backup days = 7 database;
Report of files whose recovery needs more than 7 days of archived logs
File Days Name
100 146 /orahprdidx/hprd/psindex05.dbf
RMAN> report obsolete recovery window of 7 days;
no obsolete backups found
RMAN>
I looks like I need 146 days worth of archive log files to recover the psindex05.dbf. If so, what I could do to bring that into the 7 days policy?
The database is fine, I am not trying to recover the database.
This was setup by someone and now I am taking over with minimum RMAN experience.
I appreciate any help in this subject.

The datafile was offline. I guess it was created my mistake and hanging in there. Once I do the cleanup it should go away.

RMAN backup tag question

I am little confused even after I read the RMAN doc. If I have a full level 0 backup tag "mybk$level_0" database, then my level 1 incremental backup tag has to be the same - "mybk$level_1" or "mybk$level_0".
I just run the incremental backup through the whole weekend and noticed the each run would generated two identical "spfile, controlefile" backup, one before the archivelog backup, one after it. Why?

The tag name can be the same as what you set. Tag names can be of different names and different formats, does not need to be a specific name. You can replace mybk with myarchive if you think that is more meaningful. You can also attach date and time variable with the tags to make them more meaning full.
It doesn't have to be this way,
{ backup incremental level 1 cumulative device type disk tag 'mybk%LEVEL_1' database;
recover copy of database;
backup device type disk tag 'mrarchive' archivelog all not backed up; }
If you are calling the rman backup from shell script you can attach the dates to tags as below.
export TDATE=`date +%a%m%d%y`
tag="Archive_${TDATE}"
or
tag "Archive_${TDATE}"
Below note if from one of the online resources available:
Tags for Backups and Image CopiesYou can assign a user-specified character string called a tag to backup sets and image copies (either copies created by RMAN or copies created by an operating system utility). A tag is a case-insensitive symbolic name for a backup set or file copy such as weekly_backup. You can specify the tag rather than the filename when executing the RESTORE or CHANGE command. The maximum length of a tag is 30 characters.
If you do not specify a tag name, then by default RMAN creates a tag for backups and copies (except for control file autobackups) in the format TAGYYYYMMDDTHHMMSS, where YYYY is the year, MM is the month, DD is the day, HH is the hour (in 24-hour format), MM is the minutes, and SS is the seconds. For example, a backup of datafile 1 may receive the tag TAG20020208T133437. The date and time refer to when RMAN started the backup. If multiple backup sets are created by one BACKUP command, then each backup piece is assigned the same default tag.
When applied to a backup set, a tag applies to a specific copy of the backup set. If you do not duplex a backup set, that is, make multiple identical copies of it, then a one-to-one correspondence exists between the tag and the backup set. For example, BACKUP COPIES 1 DATAFILE 7 TAG foo creates one backup set with tag foo. However, you can back up this backup set and give this new copy of the backup set the tag bar. So, the backup set has two identical copies: one tagged foo and the other tagged bar.
Tags do not need to be unique, so multiple backup sets or image copies can have the same tag name, for example, weekly_backup. When a tag is not unique, then with respect to a given datafile, the tag refers to the most current suitable file. By default, RMAN selects the most recent backups to restore unless qualified by a tag or a SET UNTIL command. The most current suitable backup containing the specified file may not be the most recent backup, as can occur in point-in-time recovery.
For example, if datafile copies are created each Monday evening and are always tagged mondaypmcopy, then the tag refers to the most recent copy (assuming that no SET UNTIL command is issued before restore or recovery). Thus, if complete recovery is desired, this command switches datafile 3 to the most recent Monday evening copy:
SWITCH DATAFILE 3 TO DATAFILECOPY TAG mondaypmcopy;
Tags can indicate the intended purpose or usage of different classes of backups or file copies. For example, datafile copies that are suitable for use in a SWITCH can be tagged differently from file copies that should be used only for RESTORE.
Note:
If you specify a tag when specifying input files to a RESTORE or SWITCH command, then RMAN considers only backup sets with a matching tag when choosing which backup to use

RMAN LIST BACKUP COMMAND

I am using the following commands.
RMAN> sql "alter session set nls_date_format=''dd-mon-yyyy HH24:MI:SS''";
2> report unrecoverable database;
3> report need backup days 2 database;
4> list backup;
5> EXIT;
BS Key Type LV Size Device Type Elapsed Time Completion Time------- ---- -- ---------- ----------- ------------ ---------------
6249525 Full 68G SBT_TAPE 01:38:05 *25-OCT-2010*
BP Key: 6249547 Status: AVAILABLE Tag: TAG20101025T040741
Even after setting nls_date_format, completion time in list backup command is not returning exact time..it is returning just the date..
how to get completion time in RMAN LIST BACKUP COMMAND with hour,minute and second details...please let me know
I am using catalog database...target database version 9i and catalog db version is 10g.
Thanks,
db

NLS_DATE_FORMAT at OS level
I tied this export NLS_DATE_FORMAT=DD-MON-YYYY HH24:MI:SS is throwing error
NLS_DATE_FORMAT=DD-MON-YYYY: is not an identifier, please tell me what i am missing?

Unrecoverable_change# and rman report unrecoverable

I am running a test db oracle 11gR2 on windows server 2008.
I am running oracle suggested backup strategy for my backup operation.
So every night i run incremental backup and apply the previous incremental to image copies.
I am confused on why when i run a query like
select file#,name,unrecoverable_change#,unrecoverable_time from v$datafile
i have atleast one or two datafiles whose unrecoverable_change# and unrecoverable_time value is not 0.
Whether the operation was in nologging or not, since i have a incremental backup, why is the above value not 0??
However when i run in rman,
report unrecoverable;
rman does not report anything. So whats the difference b/w rman unrecoverable and the one from v$datafile??
can someone help me understand the correct concept of unrecoverable_change#??
Thanks.

Yes , this is right. At least with Oracle XE as show in following test case:
SQL> select name, unrecoverable_change#, unrecoverable_time from v$datafile where file#=1;
NAME
UNRECOVERABLE_CHANGE# UNRECOVER
C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
                    0
SQL> select name, unrecoverable_change# UC, unrecoverable_time UT from v$datafile where file#=1;
NAME
        UC UT
C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
         0
SQL> desc t;
ERROR:
ORA-04043: object t does not exist
SQL> create table t(x int) nologging;
Table created.
SQL> insert /*+ APPEND */ into t select object_id from dba_objects;
12616 rows created.
SQL> commit;
Commit complete.
SQL> select name, unrecoverable_change# UC, unrecoverable_time UT from v$datafile where file#=1;
NAME
        UC UT
C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
   2004176 16-SEP-10
SQL> exit
Disconnected from Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
C:\>rman target /
Recovery Manager: Release 10.2.0.1.0 - Production on Thu Sep 16 20:59:51 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: XE (DBID=2607125346)
RMAN> report unrecoverable;
using target database control file instead of recovery catalog
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
1    full or incremental     C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
RMAN> backup incremental level 1 datafile 1;
Starting backup at 16-SEP-10
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=25 devtype=DISK
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
channel ORA_DISK_1: starting piece 1 at 16-SEP-10
channel ORA_DISK_1: finished piece 1 at 16-SEP-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_09_16\
O1_MF_NNND1_TAG20100916T210031_694TBHLT_.BKP tag=TAG20100916T210031 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15
channel ORA_DISK_1: starting incremental level 1 datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 16-SEP-10
channel ORA_DISK_1: finished piece 1 at 16-SEP-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_09_16\
O1_MF_NCSN1_TAG20100916T210031_694TC04T_.BKP tag=TAG20100916T210031 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:03
Finished backup at 16-SEP-10
RMAN> report unrecoverable;
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
RMAN>And you still have:
C:\>sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Sep 16 21:08:27 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Express Edition Release 10.2.0.1.0 - Production
SQL> select name, unrecoverable_change# UC, unrecoverable_time UT from v$datafile where file#=1;
NAME
        UC UT
C:\ORACLEXE\ORADATA\XE\SYSTEM.DBF
   2004176 16-SEP-10Edited by: P. Forstmann on 16 sept. 2010 21:07

Got error when creating a standby DB from rman: no backup or copy... Why?

We try to create standby database from a production DB on another server (10.2.0.4). The RMAN backup is in the nfs file system which is also mounted to the target server (the DR box). So, the access path for the rman backup is the same look from primary DB server and DR DB server. I started the RMAN run:
RMAN> RUN
2> {
3> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE DISK;
4> ALLOCATE AUXILIARY CHANNEL aux2 DEVICE TYPE DISK;
5> DUPLICATE TARGET DATABASE for standby
6> nofilenamecheck
7> dorecover;
8> }
9>
10> exit
using target database control file instead of recovery catalog
allocated channel: aux1
channel aux1: sid=582 devtype=DISK
allocated channel: aux2
channel aux2: sid=584 devtype=DISK
Starting Duplicate Db at 21-JUN-12
contents of Memory Script:
set until scn 12198261770353;
restore clone standby controlfile;
sql clone 'alter database mount standby database';
executing Memory Script
executing command: SET until clause
Starting restore at 21-JUN-12
released channel: aux1
released channel: aux2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 06/21/2012 16:33:36
RMAN-03015: error occurred in stored script Memory Script
RMAN-06026: some targets not found - aborting restore
RMAN-06024: no backup or copy of the control file found to restore
===========================================================================
The backups should have controlfile. There is rman show all display:
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
CONFIGURE BACKUP OPTIMIZATION OFF;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/inbound/online/controlfile_auto%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/backup/inbound/online/%d_%T_%t_%s';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/backup/inbound/online/snapcf_inbound.f';
Why and how to fix? Thanks for help!

Here is the list of command:
RMAN> list backup of controlfile ;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
5518 Full 4.57M DISK 00:00:07 17-JUN-12
BP Key: 5518 Status: AVAILABLE Compressed: NO Tag: TAG20120617T035926
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120617-00
Control File Included: Ckp SCN: 12197994840698 Ckp time: 17-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5522 Full 4.57M DISK 00:00:00 18-JUN-12
BP Key: 5522 Status: AVAILABLE Compressed: NO Tag: TAG20120618T010158
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120618-00
Control File Included: Ckp SCN: 12198041382572 Ckp time: 18-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5526 Full 4.57M DISK 00:00:01 19-JUN-12
BP Key: 5526 Status: AVAILABLE Compressed: NO Tag: TAG20120619T010352
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120619-00
Control File Included: Ckp SCN: 12198090424606 Ckp time: 19-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5530 Full 4.57M DISK 00:00:02 20-JUN-12
BP Key: 5530 Status: AVAILABLE Compressed: NO Tag: TAG20120620T010304
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120620-00
Control File Included: Ckp SCN: 12198146424201 Ckp time: 20-JUN-12
BS Key Type LV Size Device Type Elapsed Time Completion Time
5534 Full 4.57M DISK 00:00:02 21-JUN-12
BP Key: 5534 Status: AVAILABLE Compressed: NO Tag: TAG20120621T010357
Piece Name: /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
Control File Included: Ckp SCN: 12198210334547 Ckp time: 21-JUN-12
==================================================================
I tried to catalog the controlfile:
RMAN> catalog controlfilecopy '/backup/inbound/online/controlfile_autoc-2080040856-20120621-00';
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of catalog command on default channel at 06/21/2012 17:24:32
ORA-19563: control file header validation failed for file /backup/inbound/online/controlfile_autoc-2080040856-20120621-00
====================================================================
We have level 1 backup everyday, except Sunday. I have level 0 backup on Sunday. I alos tried the metalink note RMAN Duplicate For Standby Fails with Rman-06024: No Backup Or Copy Of The Control File Found To Restore [ID 466321.1]. It does not work.
Thanks for help!

RMAN cold backup taking more time than usual

Hi everybody.. please help me resolving below issue..
I have configured the RMAN in one of the production database with separate catalogue database six months earlier. I have sceduled weekly cold backup through RMAN on sunday 6pm. Normally it used to take one hour to complete the cold backup and database goes down soon as the job starts.
But since from then every week the time taken to just initiate the database shutdown continuosly increasing and recently when i checked it is taking 1 hour to initiate the database shutdown. Once the initiation starts it hardly take 1 to 3 min to shutdown.
Database is up and running during that one Hour. I was in the assumption that RMAN takes some time to execute its internal packages.
Please help
Regards,
Arun Kumar

Hi John and Tychos,
Thank you very much for your valuable inputs.
Yesterday there was cold backup and i have monitored the CPU usage. But there was no load on the CPU at that time and CPU usage was 0%
I have tried connecting to RMAN manually and it connects within a second. And also noticed in prstat -a that rman connects as soon as the job starts.
So i think that its taking time at the deleting obsolete backups.
But I have observerd following observation.
Before executing the delete obsolete command as mentioned before
RMAN> REPORT OBSOLETE RECOVERY WINDOW OF 35 DAYS DEVICE TYPE 'SBT_TAPE';
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 83409 25-JUL-09
Backup Piece 83587 25-JUL-09 arc_SID_20090725_557_1
Backup Set 83410 25-JUL-09
Backup Piece 83588 25-JUL-09 arc_SID_20090725_558_1
Backup Set 83411 25-JUL-09
Backup Piece 83589 25-JUL-09 arc_SID_20090725_559_1
After executing the delete obsolete command
RMAN> REPORT OBSOLETE RECOVERY WINDOW OF 35 DAYS DEVICE TYPE 'SBT_TAPE';
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
Backup Set 83409 25-JUL-09
Backup Piece 83587 25-JUL-09 arc_SID_20090725_557_1
Backup Set 83410 25-JUL-09
Backup Piece 83588 25-JUL-09 arc_SID_20090725_558_1
Backup Set 83411 25-JUL-09
Backup Piece 83589 25-JUL-09 arc_SID_20090725_559_1
Please advice me on the following.
1. Why its not deleting the obsolete BACKUP SETS?
2. Is it normal that RMAN takes this much deleting obsolete backup sets? How can i minimize the time taking for deleting obsolete files.
Thanks and Regards,
Arun Kumar

11g RMAN UNDO backup optimization

Hi all?
I have tested 11g RMAN UNDO backup optimization
1st I fill the undo tablespace by sql manipulations and not commiting
2nd backed undo_ts up by RMAN (size 24m)
3rd I made a commit
Then backed undo tablespace again but backup_size didn’t change (24m)
Then I made some more manipulations and backed undo_ts again. This time backup_size reduced. (11m)
Then I restarted db and backed up undo_ts again. This time backup size became what I expected (600K)
The question is why 11g rman undo tablespace backup size didn’t reduce after commit?
according to 11g undo optimization it had to
SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
SUM(BYTES)
13172736
SQL> begin
for i in 1..100000 loop
insert into testundo values(i);
end loop;
end;
2 3 4 5 6
PL/SQL procedure successfully completed.
SQL> SQL> update testundo set
id=2 where id>0;
2
update testundo set
ERROR at line 1:
ORA-30036: unable to extend segment by 8 in undo tablespace 'UNDOTBS2'
SQL> select sum(bytes) from dba_free_space where tablespace_name = 'UNDOTBS2';
SUM(BYTES)RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
10 Full *24.54M* DISK 00:00:04 10-JUN-10
BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142437
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T142437_611ctr1f_.bkp
List of Datafiles in backup set 10
File LV Type Ckp SCN Ckp Time Name
6 Full 577669 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
SQL> commit;
Commit complete.RMAN> backup datafile 6 format 'after commit.backup';
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
11 Full *24.54M* DISK 00:00:02 10-JUN-10
BP Key: 11 Status: AVAILABLE Compressed: NO Tag: TAG20100610T142541
Piece Name: /home/oracle/product/11/Db_1/dbs/after commit.backup
List of Datafiles in backup set 11
File LV Type Ckp SCN Ckp Time Name
6 Full 577705 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
SQL> alter system archive log current;
System altered.
SQL> commit;
Commit complete.
SQL> select count(*) from testundo;
COUNT(*)
100000
SQL> delete from testundo;
100000 rows deleted.
SQL> commit;
Commit complete.
SQL> insert into testundo values(1);
1 row created.
SQL> commit;
Commit complete.
SQL> alter system flush buffer_cache;
System altered.RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
13 Full *11.03M* DISK 00:00:01 10-JUN-10
BP Key: 13 Status: AVAILABLE Compressed: NO Tag: TAG20100610T143359
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T143359_611dd8sz_.bkp
List of Datafiles in backup set 13
File LV Type Ckp SCN Ckp Time Name
6 Full 578410 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
RMAN>
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 393375744 bytes
Fixed Size 1300156 bytes
Variable Size 352323908 bytes
Database Buffers 33554432 bytes
Redo Buffers 6197248 bytes
Database mounted.
Database opened.
SQL> RMAN> backup datafile 6;
RMAN> list backup of datafile 6;
List of Backup Sets
===================
BS Key Type LV Size Device Type Elapsed Time Completion Time
14 Full *600.00K* DISK 00:00:02 10-JUN-10
BP Key: 14 Status: AVAILABLE Compressed: NO Tag: TAG20100610T152843
Piece Name: /home/oracle/flash_recovery_area/11GR1/backupset/2010_06_10/o1_mf_nnndf_TAG20100610T152843_611hlwmv_.bkp
List of Datafiles in backup set 14
File LV Type Ckp SCN Ckp Time Name
6 Full 580347 10-JUN-10 /home/oracle/oradata/11GR1/datafile/undotbs2.dbf
Thanks in advance
Turkel

Hi Turkel,
The space used for undo is also related to the undo retention setting.
As it seems you do a test update and proceed with backups on:
- 14:24:37 (-> 25M)
- 14:25:41 (-> 25M)
- 14:33:59 (-> 11M)
- 15:28:43 (-> 600K)
The first two backups probably are still within the undo retention period for the update.
The third backup shows a partly empty undo (is your setting 900?).
The last falls outside the retention period for the update resulting in the small backup size.
Regards,
Tycho

Cloning DB on a different server from RMAN Tape backup

RDBMS version           : 11.2.0.2 on Solaris 10
Media Management Layer : Netbackup v7
I have done only backups to Tape. I have never done restore,recovery from Tape.
We have a production DB named NEHPROD running on server qualmh214. Every Monday morning an RMAN Full backup for NEHPROD is taken to Tape.
Production server : qualmh214        DB Name:NEHPROD
run
ALLOCATE CHANNEL c1 TYPE 'SBT_TAPE';
SEND 'NB_ORA_CLIENT=qualmh214,NB_ORA_POLICY=qualmh214_rman,NB_ORA_SERV=qualmh238,NB_ORA_SCHED=Daily';
backup database   FORMAT 'NEHPROD_%d_%U_%t.rbk' tag='NEHPROD_full';
}I need to create a Test DB in a different server (qualmh199) by restoring directly from NEHPROD's Full backup in tape .
From qualmh199, how can I connect to the Tape Media server ?
Even If I do connect to the Tape media server, how can i get access to tape backups of another DB? In the RMAN run block you can't specify a DB name. Right?
Even if I get access to another DB's backup , How can i specify which Date's Full backup I need to use to restore ?

From qualmh199, how can I connect to the Tape Media server ?You have to allocate channels to tape & need to mention NB parameters as example below.
in RMAN script
ALLOCATE CHANNEL CH1 DEVICE TYPE SBT_TAPE PARMS 'SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64';
SEND 'NB_ORA_SERV=<server.com>, NB_ORA_CLIENT=<target.server>';
Even If I do connect to the Tape media server, how can i get access to tape backups of another DB? In the RMAN run block you can't specify a DB name. Right?If the libraries are installed and you able to perform, you can go for either duplicate database or simple RMAN restore. You can mention other DB names also
Ex: duplicate target database to 'test';
Even if I get access to another DB's backup , How can i specify which Date's Full backup I need to use to restore ?You can mention TAG's if you are using RMAN restore.

Rman hot backup script gives error in R12.

hi experts
i m facing following prob when run the backup script. 1 day before the same script runs correctily but now it gives me error at the allocatioion of channel rest of command run correctly.
[root@testerp rman_log]# cat UAT_daily_rman_hot_bkp_01-11-14_140301.log
-bash: /root/.bash_profile: Permission denied
Recovery Manager: Release 11.1.0.7.0 - Production on Sat Jan 11 14:03:01 2014
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: UAT (DBID=2855851979)
connected to recovery catalog database
RMAN> 2> 3> 4> 5> 6> 7> 8> 9> 10> 11> 12>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01009: syntax error: found "end-of-file": expecting one of: "allocate, alter, advise, backup, beginline, blockrecover, catalog, change, copy, convert, crosscheck, configure, duplicate, debug, delete, execute, endinline, flashback, host, mount, open, plsql, recover, release, replicate, report, restore, resync, repair, }, set, setlimit, sql, switch, startup, shutdown, send, show, transport, validate"
RMAN-01007: at line 12 column 1 file: standard input
RMAN>
RMAN>
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: "for"
RMAN-01008: the bad identifier was: c2
RMAN-01007: at line 1 column 18 file: standard input
RMAN>
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: "for"
RMAN-01008: the bad identifier was: c3
RMAN-01007: at line 1 column 18 file: standard input
RMAN>
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: "for"
RMAN-01008: the bad identifier was: c4
RMAN-01007: at line 1 column 18 file: standard input
RMAN>
Starting backup at 11-JAN-14
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=362 device type=DISK
channel ORA_DISK_1: starting incremental level 1 datafile backup set
channel ORA_DISK_1: specifying datafile(s) in backup set
input datafile file number=00021 name=/d06/UAT/proddata/a_txn_data06.dbf
input datafile file number=00392 name=/d06/UAT/db/apps_st/data/a_txn_data01.dbf
input datafile file number=00401 name=/d06/UAT/db/apps_st/data/a_txn_data02.dbf
input datafile file number=00402 name=/d06/UAT/db/apps_st/data/a_txn_data03.dbf
input datafile file number=00022 name=/d06/UAT/proddata/a_txn_data07.dbf
input datafile file number=00014 name=/d06/UAT/db/apps_st/data/a_txn_data04.dbf
input datafile file number=00020 name=/d06/UAT/proddata/a_txn_data05.dbf
input datafile file number=00011 name=/d06/UAT/db/apps_st/data/sysaux01.dbf
input datafile file number=00018 name=/d06/UAT/db/apps_st/data/sysaux02.dbf
input datafile file number=00023 name=/d06/UAT/proddata/a_txn_data08.dbf
input datafile file number=00379 name=/d06/UAT/db/apps_st/data/undo01.dbf
input datafile file number=00024 name=/d06/UAT/proddata/sysaux03.dbf
input datafile file number=00025 name=/d06/UAT/proddata/sysaux04.dbf
input datafile file number=00033 name=/d06/UAT/proddata/a_txn_ind11.dbf
input datafile file number=00029 name=/d06/UAT/proddata/a_txn_ind09.dbf
input datafile file number=00030 name=/d06/UAT/proddata/a_txn_ind10.dbf
input datafile file number=00015 name=/d06/UAT/db/apps_st/data/a_txn_ind06.dbf
input datafile file number=00026 name=/d06/UAT/db/apps_st/data/a_txn_ind07.dbf
input datafile file number=00028 name=/d06/UAT/db/apps_st/data/a_txn_ind08.dbf
input datafile file number=00393 name=/d06/UAT/db/apps_st/data/a_txn_ind01.dbf
input datafile file number=00403 name=/d06/UAT/db/apps_st/data/a_txn_ind02.dbf
input datafile file number=00404 name=/d06/UAT/db/apps_st/data/a_txn_ind03.dbf
input datafile file number=00405 name=/d06/UAT/db/apps_st/data/a_txn_ind04.dbf
input datafile file number=00406 name=/d06/UAT/db/apps_st/data/a_txn_ind05.dbf
input datafile file number=00400 name=/d06/UAT/db/apps_st/data/a_media01.dbf
input datafile file number=00353 name=/d06/UAT/db/apps_st/data/system08.dbf
input datafile file number=00013 name=/d06/UAT/db/apps_st/data/system12.dbf
input datafile file number=00352 name=/d06/UAT/db/apps_st/data/system09.dbf
input datafile file number=00394 name=/d06/UAT/db/apps_st/data/a_ref01.dbf
input datafile file number=00407 name=/d06/UAT/db/apps_st/data/a_ref02.dbf
input datafile file number=00396 name=/d06/UAT/db/apps_st/data/a_summ01.dbf
input datafile file number=00395 name=/d06/UAT/db/apps_st/data/a_int01.dbf
input datafile file number=00008 name=/d06/UAT/db/apps_st/data/a_queue02.dbf
input datafile file number=00027 name=/d06/UAT/db/apps_st/data/a_queue03.dbf
input datafile file number=00031 name=/d06/UAT/db/apps_st/data/a_queue04.dbf
input datafile file number=00399 name=/d06/UAT/db/apps_st/data/a_queue01.dbf
input datafile file number=00001 name=/d06/UAT/db/apps_st/data/system01.dbf
input datafile file number=00002 name=/d06/UAT/db/apps_st/data/system02.dbf
input datafile file number=00003 name=/d06/UAT/db/apps_st/data/system03.dbf
input datafile file number=00004 name=/d06/UAT/db/apps_st/data/system04.dbf
input datafile file number=00005 name=/d06/UAT/db/apps_st/data/system05.dbf
input datafile file number=00398 name=/d06/UAT/db/apps_st/data/a_archive01.dbf
input datafile file number=00295 name=/d06/UAT/db/apps_st/data/system06.dbf
input datafile file number=00351 name=/d06/UAT/db/apps_st/data/system07.dbf
input datafile file number=00354 name=/d06/UAT/db/apps_st/data/system11.dbf
input datafile file number=00288 name=/d06/UAT/db/apps_st/data/system10.dbf
input datafile file number=00012 name=/d06/UAT/db/apps_st/data/apps_ts_tools01.dbf
input datafile file number=00016 name=/d06/UAT/db/apps_st/data/a_ref03.dbf
input datafile file number=00019 name=/d06/UAT/db/apps_st/data/MLSEIGL01.dbf
input datafile file number=00032 name=/d06/UAT/db/apps_st/data/RMAN01.dbf
input datafile file number=00397 name=/d06/UAT/db/apps_st/data/a_nolog01.dbf
input datafile file number=00314 name=/d06/UAT/db/apps_st/data/portal01.dbf
input datafile file number=00017 name=/d06/UAT/db/apps_st/data/a_int02.dbf
input datafile file number=00006 name=/d06/UAT/db/apps_st/data/ctxd01.dbf
input datafile file number=00010 name=/d06/UAT/db/apps_st/data/olap.dbf
input datafile file number=00009 name=/d06/UAT/db/apps_st/data/odm.dbf
input datafile file number=00007 name=/d06/UAT/db/apps_st/data/owad01.dbf
channel ORA_DISK_1: starting piece 1 at 11-JAN-14
[root@testerp rman_log]#
backup script is below:
in this script it returns error only at the channel allocaition rest of all backup command i run manually or with scirpt it runs correctly.4
i m not able to know why it returns error only at challnel allocation 1 day before it runs correctly.
[orauat@testerp rman_script]$ cat rman_backup.sh
#!/bin/sh
#ORACLE_SID=UAT
#BACKUP_START_TIME='date +"%y""%m""%d"_"%H""%M""%S"'
#ORACLE_HOME=/d06/UAT/db/tech_st/11.1.0
#PATH=$PATH:${ORACLE_HOME}:${ORACLE_HOME}/bin
#export ORACLE_SID
#export ORACLE_HOME
#export PATH
/d06/UAT/db/tech_st/11.1.0/bin/rman catalog rman/rman007 target sys/sysuat <<EOF
run
allocate channel c1 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_Arch_%c_%U';
sql 'alter system switch logfile';
sql 'alter system switch logfile';
sql 'alter system archive log current';
delete expired archivelog all;
crosscheck archivelog all;
backup archivelog all;
delete noprompt archivelog all completed before 'sysdate-4' backed up 1 times to disk;
allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
backup incremental level 1 database;
delete expired backup device type disk;
delete obsolete device type disk;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
exit
EOF
regards
pritesh ranjan

yes the script is edited
i have add some command line and edit it for take the full backup level=0 on the same directory with different formant name but location is same.
can i take full backup level 0 and incremental backup level 1 in the same directory with the different format name.
for exp:
allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Daily_backup%d_DB_%c_%U';
i allocate these three channel for incremental level 1 backup;
the backup is done successfully without any error.
after that i have change
allocate channel c2 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
allocate channel c3 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
allocate channel c4 device type disk format '/d06/UAT/rman_hot_backup/Weekly_backup%d_DB_%c_%U';
backup database incremental level 0
after doing the above changes it get the error. with the channel location.
i have to schedule daily incremental backup level 1 and weekly full backup level 0.
plz suggest me i have to take incremental 1 and full incremental level 0 backup on seperate directory for different format name.
regards
pritesh ranjan

RMAN REPORT OPTIONS

i do not really understand the 'redundancy' option of rman report command.
like the one below:
RMAN> REPORT NEED BACKUP REDUNDANCY 2;
please, i don't understand what the word 'redundancy' means here.
I need help please.
thank you

Think of redundancy as number of full backups.
Redundancy 1 is 1 backup ago.
Redundancy 2 is 2 backups ago.

RMAN Report

Hi,
I am using ORACLE 10.2 G. I have done the following on my pc :
ALTER TABLESPACE USERS BEGIN BACKUP;
CREATE TABLE NOTBACKEDUP(ID INTEGER, STR VARCHAR(16)) TABLESPACE USERS;
INSERT INTO NOTBACKEDUP VALUES(1, 'ROW 1');
INSERT INTO NOTBACKEDUP VALUES(2,'ROW 2);
COMMIT;
ALTER TABLESPACE USERS END BACKUP;
How do I view RMAN Report ? I need to print that report.
Thanks .

Hi,
I have never used RMAN before, I need to print a copy of RMAN report to show that work that I provided in my question. How do I start RMAN ? and How Do I print that report ? I am still in dilema with respect to above statement.
Take time and try to refer to the below oracle documentation
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup008.htm
Note:- Don't be in hurry

Rman - "report unrecoverable" concept

Hi
I am readin g a book on rman (rman recipes 11g from APress).
I m not able to understand what is the purpose of "report unrecoverable" command. Book says:
>
Ref: Section 8.3 - page# 229:
You want to identify which datafiles have been affected by unrecoverable operations, since RMAN needs to back up those files as soon as possible after you perform an unrecoverable operation.
Use the report unrecoverable command to find out which datafiles in the database have been marked unrecoverable because they’re part of an unrecoverable operation. Here’s an example showing how to use the report unrecoverable command:
RMAN> report unrecoverable;
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
1 full /u01/app/oracle/data/prod1/example01.dbf
RMAN>Could someone please give example of unrecoverable operation(s)? And how could rman/oracle know before hand if such an unrecoverable operation is going to be performed on certain datafile(s)?
Thanks

user12033597 wrote:
Hi
I am readin g a book on rman (rman recipes 11g from APress).
I m not able to understand what is the purpose of "report unrecoverable" command. Book says:
Ref: Section 8.3 - page# 229:
You want to identify which datafiles have been affected by unrecoverable operations, since RMAN needs to back up those files as soon as possible after you perform an unrecoverable operation.
Use the report unrecoverable command to find out which datafiles in the database have been marked unrecoverable because they’re part of an unrecoverable operation. Here’s an example showing how to use the report unrecoverable command:
RMAN> report unrecoverable;
Report of files that need backup due to unrecoverable operations
File Type of Backup Required Name
1 full /u01/app/oracle/data/prod1/example01.dbf
RMAN> Could someone please give example of unrecoverable operation(s)? And how could rman/oracle know before hand if such an unrecoverable operation is going to be performed on certain datafile(s)?
Thanks A datafile or tablespace are set to unrecoverable if any operation that had been performed (since the last backup taken on these datafiles) on datafile or tablespace that are unrecoverable.
A little explanation:
When ever a operation occurs on database i.e. any dml occurs on tables, these operation generates REDO information in redolog files. So when someone explicitly disable the logging information to redologfile(by hint no_logging), then datafile is marked as unrecoverable.
Oracle says it unrecoverable because oracle cannot perform recovery by reading from redologfile or archivefiles if datafile crashes and need a recovery. Thats why rman warns you about such operation which could have taken place and point you to datafile which had these operation performed. The operations which are unrecoverable are:
1) direct load/SQL load
2) direct-path inserts result from insert or merge statement
3) ALTER TABLE commands
4) CREATE and ALTER INDEX commands
5) INSERT /*+APPEND*/
6) partition manipulation
7) database object that has explicitly set with nologging option
8) Oracle eBusiness Suite concurrent job execution identified in Oracle metalink note: 216211.1
8) Oracle eBusiness Suite patches activities that involve database object manipulation
9) SQL*loader with nologging
So once you take the full backup of datafiles (which are affected by these operation) will clearout the Unrecoverable warning. Because now oracle has the backup of these files.
What preventions you can take for not making datafile to Unrecoverable?
Use force_logging
Also see
http://www.pythian.com/news/7401/oracle-what-is-an-unrecoverable-data-file/
Hope this help you in understanding

Resize online redolog files, make RMAN obsolute backups as usable

Dear Guru's,
I have following doubts, please clarify me on the same. thanks in advance
1. why can not we resize online redolog files instead of re-creating the same with large size and remove the older onces.
2. How can we make RMAN obsolute backups as usable ?
Thanks.

vasuoracledba wrote:
Hi Aman,
Thanks for replay...
Regarding RMAN, plz look into below issue.
I configured RMAN backup recovery window of 15 days. after 15 days the backupsets which were older then 15 days are obsolute. now i have to restore the backup of 15 days older(obsolute backupsets) backupsets to the database. but when i do restore it defaulty takes latest backupsets other then obsolute onces.
how do i restore older(obsolute backupsets) backupsets to the database?
If i used the CHANGE cmd, how to do that.
RMAN> change backupset tag weekly_backup_20052013_02:45 _______________
do i make latest backupsets unavaliable to restore the older once....
RMAN> change backupset tag weekly_backup_20062013_02:00;
Thanks in advance...........
Obsolete backups are always usable, until you delete them with DELETE OBSOLETE.
If you want to restore from a backup other than the latest, use an until clause:
run {set until time = 'sysdate - 15';
restore database;}

Rman list backup; until scn

Hello,
my question might be a little strange, but I would just like to confirm my understanding to be sure about my testing.
Consider the following:
RMAN> list backup
List of Backup Sets
===================
BS Key Size       Device Type Elapsed Time Completion Time
5520    396.79M    DISK        00:02:38     15-OCT-11
        BP Key: 5541   Status: AVAILABLE Compressed: YES Tag: TAG20111015T190048
        Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_ANNNN_TAG20111015T190048_79MKSH03_.BKP
List of Archived Logs in backup set 5520
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    37170   690296258 14-OCT-11 690301863 14-OCT-11
1    37171   690301863 14-OCT-11 690306944 14-OCT-11
1    37172   690306944 14-OCT-11 690312517 14-OCT-11
1    37173   690312517 14-OCT-11 690326343 14-OCT-11
1    37174   690326343 14-OCT-11 690328734 14-OCT-11
1    37175   690328734 14-OCT-11 690334332 14-OCT-11
1    37176   690334332 14-OCT-11 690354457 14-OCT-11
1    37177   690354457 14-OCT-11 690365309 14-OCT-11
1    37178   690365309 14-OCT-11 690383830 14-OCT-11
1    37179   690383830 14-OCT-11 690389381 14-OCT-11
1    37180   690389381 14-OCT-11 690399124 14-OCT-11
1    37181   690399124 14-OCT-11 690403117 14-OCT-11
1    37182   690403117 14-OCT-11 690408333 14-OCT-11
1    37183   690408333 14-OCT-11 690411748 14-OCT-11
1    37184   690411748 14-OCT-11 690417353 14-OCT-11
1    37185   690417353 14-OCT-11 690422345 14-OCT-11
1    37186   690422345 14-OCT-11 690428300 15-OCT-11
1    37187   690428300 15-OCT-11 690433347 15-OCT-11
1    37188   690433347 15-OCT-11 690439543 15-OCT-11
1    37189   690439543 15-OCT-11 690444502 15-OCT-11
1    37190   690444502 15-OCT-11 690450317 15-OCT-11
1    37191   690450317 15-OCT-11 690453707 15-OCT-11
1    37192   690453707 15-OCT-11 690457501 15-OCT-11
1    37193   690457501 15-OCT-11 690458775 15-OCT-11
1    37194   690458775 15-OCT-11 690464449 15-OCT-11
1    37195   690464449 15-OCT-11 690469446 15-OCT-11
1    37196   690469446 15-OCT-11 690474941 15-OCT-11
1    37197   690474941 15-OCT-11 690481459 15-OCT-11
1    37198   690481459 15-OCT-11 690484981 15-OCT-11
1    37199   690484981 15-OCT-11 690490292 15-OCT-11
1    37200   690490292 15-OCT-11 690495899 15-OCT-11
1    37201   690495899 15-OCT-11 690500991 15-OCT-11
1    37202   690500991 15-OCT-11 690508506 15-OCT-11
1    37203   690508506 15-OCT-11 690514835 15-OCT-11
1    37204   690514835 15-OCT-11 690519918 15-OCT-11
1    37205   690519918 15-OCT-11 690535732 15-OCT-11
1    37206   690535732 15-OCT-11 690626387 15-OCT-11
1    37207   690626387 15-OCT-11 690629393 15-OCT-11
1    37208   690629393 15-OCT-11 690634991 15-OCT-11
1    37209   690634991 15-OCT-11 690640154 15-OCT-11
1    37210   690640154 15-OCT-11 690646056 15-OCT-11
1    37211   690646056 15-OCT-11 690651236 15-OCT-11
1    37212   690651236 15-OCT-11 690656775 15-OCT-11
1    37213   690656775 15-OCT-11 690662593 15-OCT-11
1    37214   690662593 15-OCT-11 690668154 15-OCT-11
1    37215   690668154 15-OCT-11 690673574 15-OCT-11
1    37216   690673574 15-OCT-11 690677649 15-OCT-11
1    37217   690677649 15-OCT-11 690683129 15-OCT-11
1    37218   690683129 15-OCT-11 690688406 15-OCT-11
1    37219   690688406 15-OCT-11 690693988 15-OCT-11
1    37220   690693988 15-OCT-11 690698971 15-OCT-11
1    37221   690698971 15-OCT-11 690705146 15-OCT-11
1    37222   690705146 15-OCT-11 690710236 15-OCT-11
1    37223   690710236 15-OCT-11 690715886 15-OCT-11
1    37224   690715886 15-OCT-11 690719326 15-OCT-11
1    37225   690719326 15-OCT-11 690724866 15-OCT-11
1    37226   690724866 15-OCT-11 690729976 15-OCT-11
1    37227   690729976 15-OCT-11 690735596 15-OCT-11
1    37228   690735596 15-OCT-11 690740660 15-OCT-11
1    37229   690740660 15-OCT-11 690746167 15-OCT-11
1    37230   690746167 15-OCT-11 690751851 15-OCT-11
1    37231   690751851 15-OCT-11 690756900 15-OCT-11
1    37232   690756900 15-OCT-11 690759044 15-OCT-11
BS Key Type LV Size       Device Type Elapsed Time Completion Time
5521    Incr 0 494.68M    DISK        00:03:24     15-OCT-11
        BP Key: 5542   Status: AVAILABLE Compressed: YES Tag: TAG20111015T195017
        Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_NNND0_TAG20111015T195017_79MKZP6W_.BKP
List of Datafiles in backup set 5521
File LV Type Ckp SCN    Ckp Time Name
14   0 Incr 690768806 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\CCAPP.DBF
126 0 Incr 690768806 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\WAAPP.DBF
131 0 Incr 690768806 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\PSDEFAULT02.DBF
BS Key Type LV Size       Device Type Elapsed Time Completion Time
5522    Incr 0 193.66M    DISK        00:01:38     15-OCT-11
        BP Key: 5543   Status: AVAILABLE Compressed: YES Tag: TAG20111015T195017
        Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_NNND0_TAG20111015T195017_79ML6DXJ_.BKP
List of Datafiles in backup set 5522
File LV Type Ckp SCN    Ckp Time Name
3    0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\UNDOTBS01.DBF
4    0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\USERS01.DBF
128 0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSAUX02.DBF
132 0 Incr 690769344 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\UNDO3.DBF
BS Key Type LV Size       Device Type Elapsed Time Completion Time
5523    Incr 0 644.30M    DISK        00:04:11     15-OCT-11
        BP Key: 5544   Status: AVAILABLE Compressed: YES Tag: TAG20111015T195017
        Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_NNND0_TAG20111015T195017_79ML9NMK_.BKP
List of Datafiles in backup set 5523
File LV Type Ckp SCN    Ckp Time Name
1    0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSTEM01.DBF
2    0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSAUX01.DBF
127 0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSTEM02.DBF
129 0 Incr 690770341 15-OCT-11 E:\ORACLE\ORADATA\KPZP\DATAFILES\SYSAUX03.DBF
BS Key Size       Device Type Elapsed Time Completion Time
5524    18.86M     DISK        00:00:10     15-OCT-11
        BP Key: 5545   Status: AVAILABLE Compressed: YES Tag: TAG20111015T200023
        Piece Name: E:\KPZ\PROD_BACKUP\2011_10_15\O1_MF_ANNNN_TAG20111015T200023_79MLKTVM_.BKP
List of Archived Logs in backup set 5524
Thrd Seq     Low SCN    Low Time Next SCN   Next Time
1    37233   690759044 15-OCT-11 690764137 15-OCT-11
1    37234   690764137 15-OCT-11 690768526 15-OCT-11
1    37235   690768526 15-OCT-11 690770962 15-OCT-11
RMAN> /** I left out some lines that seemed duplicate for my question - lines with the same SCN and some older archived logs. I can post the whole thing if it should turn out to be relevant.
What SCN would be appropriate for me to use, taking into account this is a level 0 incremental backup, to restore to the point of a full backup?
I'm fairly sure i can do the following: (and yes, this will result in a successful restore/recover)
run{
set until scn 690770341;
restore database;
switch datafile all;
recover database;
}     But is that really the point that I should recover to? The other alternative would be to recover to the SCN of those archivelogs at the very bottom?
Thank you for any comments, whatever they are :-)

I am copying the backups between different hosts (or external tape applications) and building the database from backups. So I create a blank instance and catalog the backup files, then specify an SCN to restore/recover.
Would the SCN part be unneeded? I guess if I want to recover to the latest possible state, I do not need to specify any SCN :-). For testing purposes I only specified the full backup SCN to save time, but in the event this would be needed in a production environment, you are right that I would need to recover to the latest possible SCN. Thanks for pointing that out.

Rman :: report backup tag= ??

Similar Messages

Maybe you are looking for