Backup RMAN DB files

Hi all

I checked our rmanbackup file and we have these files:

-rw - 1 oracle dba 12517376 Aug 05 13:10 ctrl_g2oj3c9j_1_1

-rw - 1 oracle dba 12517376 Aug 05 13:10 ctrl_stby_g1oj3c9h_1_1

-rw - 1 oracle dba 1194496 Aug 05 13:10 db_g0oj3c9f_1_1

-rw - 1 oracle dba 1053146112 Aug 05 13:05 db_fooj3bmr_1_1

-rw - 1 oracle dba 17511424 Aug 05 13:05 db_fpoj3c0n_1_1

-rw - 1 oracle dba 1273348608 Aug 05 13:05 db_floj3bmr_1_1

-rw - 1 oracle dba 1197198336 Aug 05 13:05 db_fnoj3bmr_1_1

-rw - 1 oracle dba 1051112960 Aug 05 13:05 db_fmoj3bmr_1_1

I see that there is always a set of daily 4-files.

I understand that the first 2 is the backup controlfile.

I can understand the others are backup of the db. Why it is split into 6 parts? This means that we use 6 e/s disk parallel channel backup?

Thank you very much

zxy

RMAN takes the backup in the format of the backup piece. Depending on the size of the backup piece, if they are supposed to be multiplexed or not, the number of pieces would be. SB mentioned, you must spend time reading the backup and restore documentation guide.

HTH

Aman...

Tags: Database

Similar Questions

The front last backup RMAN delete file even if redundancy on 3 days
Dear Oracle gurus

My environment
Node 2 11g R2 Cluster with ASM
Database 11.2.0.3.0

I got to know that file below is delete by RMAN even if redundancy on 3 days
* 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 * is removed

can you please provide a reason or recommendations to correct the backup configuration

=========Before Backup========================================
917M rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
Rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 669M
Rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 101M
64M rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
116M rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
Rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 85M
1003M rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
689M rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
87M rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
Rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013 73M
110M rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
Rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013 103M
115M rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
88M rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
1011M rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
701M rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
226M rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
215M rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
* 230M rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
* 568M rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
* 19M rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 *.
===========================================================================

===================After Backup========================================================
-rw - r - 1 oracle oinstall 1049755648 12 May 20:05 rman_bkp_2bo9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
-rw - r - 1 oracle oinstall 720715776 12 May 20:05 rman_bkp_2co9fko2_1_1_ORCL_20130512_DATAFILE_LVL0_12_05_2013
-rw - r - 1 oracle oinstall 91013120 13 May 20:05 rman_bkp_2jo9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
-rw - r - 1 oracle oinstall 75726848 13 May 20:05 rman_bkp_2ko9i942_1_1_ORCL_20130513_DATAFILE_LVL1_13_05_2013
-rw - r - 1 oracle oinstall 114327552 14 May 20:05 rman_bkp_2so9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
-rw - r - 1 oracle oinstall 107782144 14 May 20:05 rman_bkp_2to9ktg1_1_1_ORCL_20130514_DATAFILE_LVL1_14_05_2013
-rw - r - 1 oracle oinstall 120307712 15 May 20:05 rman_bkp_34o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
-rw - r - 1 oracle oinstall 91226112 15 May 20:05 rman_bkp_35o9nhs2_1_1_ORCL_20130515_DATAFILE_LVL1_15_05_2013
-rw - r - 1 oracle oinstall 1058840576 16 May 20:05 rman_bkp_3co9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
-rw - r - 1 oracle oinstall 733757440 16 May 20:05 rman_bkp_3do9q682_1_1_ORCL_20130516_DATAFILE_LVL0_16_05_2013
-rw - r - 1 oracle oinstall 236716032 17 May 20:05 rman_bkp_3ko9sqkk_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
-rw - r - 1 oracle oinstall 224174080 17 May 20:05 rman_bkp_3lo9sqkl_1_1_ORCL_20130517_DATAFILE_LVL1_17_05_2013
-rw - r - 1 oracle oinstall 594411520 18 May 20:06 rman_bkp_3to9vf20_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
-rw - r - 1 oracle oinstall 240123904 18 May 20:06 rman_bkp_3so9vf1v_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
-rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 1073741824 19 May 20:06 rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 254590976 19 May 20:06 rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 709885952 19 May 20:07 rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
-rw - r - 1 oracle oinstall 19234816 19 May 20:07 rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013
==================================================================================

Configuration of RMAN
bash-$3.2 rman target /.

Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 14:34:26 2013

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

connected to target database: ORCL (DBID = 3171721304)

RMAN > show all.

using the control file of the target instead of recovery catalog database
RMAN settings for database with db_unique_name ORCLDR are:
CONFIGURE REDUNDANCY 3 RETENTION STRATEGY;
CONFIGURE BACKUP OPTIMIZATION
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_orcldr2.f'; # by default

RMAN > exit
=========================================================================================
RMAN Full Backup Script
RMAN level 0
#! / bin/bash
. /Home/Oracle/.bash_profile
logloc = 'date' + rman_backup_lvl0_orcldr_ %m %y hour %M %S %d ".log
Target of $ORACLE_HOME/bin/rman = / log = / backup/RMAN_Log / $logloc < < EOF
run
{
allocate channels ch1 type disk maxpiecesize = 1024 M;
allocate channel ch2 type disk maxpiecesize = 1024M;
database backup incremental level 0 FORMAT ' / backup/RMAN_Backup/rman_bkp_%U_%d_%T_DATAFILE_LVL0_%D_%M_%Y'
include current controlfile more archivelog delete all entries
tag 'datafile_full ';
}
delete noprompt obsolete;
EXIT;
EXPRESSIONS OF FOLKLORE
=========================================================================================

Backup logs
-bash-3, $ 2 cat rman_backup_lvl0_ORCLdr_190513200501.log

Recovery Manager: release 11.2.0.3.0 - Production the Sun may 19 20:05:01 2013

Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved.

connected to target database: ORCL (DBID = 3171721304)

RMAN >
RMAN > 2 > 3 > 4 > 5 > 6 > 7 > 8 >
using the control file of the target instead of recovery catalog database
allocated channel: ch1
channel ch1: SID = instance 1753 = ORCLdr2 = DISK device type

allocated channel: ch2
channel ch2: SID = 5 = device type ORCLdr2 = DISK instance

From backup may 19, 13
Current archived log
archived journal of wire 1 to jump with sequence 84; already saved
skip the journal archived thread 2 with sequence 79; already saved
channel ch1: Startup archived log backup set
channel ch1: specifying the newspapers archived in the backup set
archived journal entry thread = 2 sequence = 81 RECID = 388 STAMP = 815810424
archived journal entry thread = 1 sequence = 85 RECID = 385 STAMP = 815793508
archived journal entry thread = 1 sequence = 86 RECID = 389 STAMP = 815810426
archived journal entry thread = 1 sequence = 87 RECID = 391 STAMP = 815828071
channel ch1: from room 1 to May 19, 13
channel ch2: Startup archived log backup set
channel ch2: specifying the newspapers archived in the backup set
archived journal thread = sequence 2 = 82 entry RECID = 396 STAMP = 815861105
archived journal entry thread = 1 sequence = 88 RECID = 393 = 815846442 STAMP
archived journal entry thread = 1 sequence = 89 RECID = 397 STAMP = 815861108
channel ch2: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
channel ch1: from part 2 to May 19, 13
channel ch2: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_1_1 tag = DATAFILE_FULL comment = NONE
channel ch2: from part 2 to May 19, 13
channel ch1: finished part 2 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
channel ch1: from 3 to 19 May 13 piece
channel ch2: finished part 2 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/43oa23bp_2_1 tag = DATAFILE_FULL comment = NONE
channel ch2: complete set of backups, time: 00:01:10
channel ch2: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_82_814540431.arc RECID archived log file = 396 STAMP = 815861105
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_88_814540431.arc RECID archived log file = 393 = 815846442 STAMP
RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_89_814540431.arc thread = 1 sequence = 89
channel ch2: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_84_814540431.arc RECID archived log file = 383 STAMP = 815774802
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_79_814540431.arc RECID archived log file = 378 STAMP = 815774705
channel ch1: finished part 3 to 19 May 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/42oa23bp_3_1 tag = DATAFILE_FULL comment = NONE
channel ch1: complete set of backups, time: 00:01:25
channel ch1: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_81_814540431.arc RECID archived log file = 388 STAMP = 815810424
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_85_814540431.arc RECID archived log file = 385 STAMP = 815793508
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_86_814540431.arc RECID archived log file = 389 STAMP = 815810426
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_87_814540431.arc RECID archived log file = 391 STAMP = 815828071
Backup finished on 19 May 13

From backup may 19, 13
channel ch1: start the incremental level 0 datafile backup set
channel ch1: specification-datafile in the backup set (s)
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_5.dbf 00009
Enter a number of file datafile = 00001 name=+ORASYS/ORCLdr/datafile/system.257.814500985
Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/undotbs1.259.814500991 00003
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app2.dbf 00006
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/app.dbf 00008
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users01.dbf 00011
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users03.dbf 00013
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users05.dbf 00015
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users07.dbf 00017
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_5.dbf 00019
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_7.dbf 00021
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_9.dbf 00023
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_11.dbf 00025
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdrmaxdat.dbf 00027
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradcdr.dbf 00029
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_8.dbf 00031
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_10.dbf 00033
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_5.dbf 00037
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_7.dbf 00039
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/interimcdr2013_9.dbf 00041
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdr2013_11.dbf 00043
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/nterimcdrmaxdat.dbf 00045
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/sidradinterimcdr.dbf 00047
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/reports.dbf 00048
channel ch1: from room 1 to May 19, 13
channel ch2: start the incremental level 0 datafile backup set
channel ch2: specification-datafile in the backup set (s)
Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/sysaux.256.814500977 00002
Enter a number of file datafile = 00005 name=+ORASYS/ORCLdr/datafile/undotbs2.258.814500987
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/namestatistics.dbf 00035
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/gidstatistics.dbf 00036
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/stat01.dbf 00007
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_6.dbf 00010
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users02.dbf 00012
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users04.dbf 00014
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users06.dbf 00016
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/users08.dbf 00018
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_6.dbf 00020
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_8.dbf 00022
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_10.dbf 00024
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/cdr2013_12.dbf 00026
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/unameradcdr.dbf 00028
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_7.dbf 00030
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statistics2013_9.dbf 00032
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/statisticsmaxdate.dbf 00034
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radintdr2013_6.dbf 00038
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radiusintcdr2013_8.dbf 00040
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/radinterimcdr2013_10.dbf 00042
Enter a number of file datafile = name=+ORADATA1/ORCLdr/datafile/tb2013_12.dbf 00044
Enter a file datafile 00046 name=+ORADATA1/ORCLdr/datafile/tberimcdr.dbf = number
Enter a number of file datafile = name=+ORASYS/ORCLdr/datafile/users.260.814500995 00004
channel ch2: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch1: from part 2 to May 19, 13
channel ch2: finished piece 1 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch2: from part 2 to May 19, 13
channel ch1: finished part 2 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_44oa23eg_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch1: complete set of backups, time: 00:00:22
channel ch1: start the incremental level 0 datafile backup set
channel ch1: specification-datafile in the backup set (s)
channel ch2: finished part 2 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_45oa23eh_2_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch2: complete set of backups, time: 00:00:22
including the current control in the backup set file
channel ch1: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
total, handle = / backup/RMAN_Backup/rman_bkp_46oa23f7_1_1_ORCL_20130519_DATAFILE_LVL0_19_05_2013 tag = comment TAG20130519T200640 = NONE
channel ch1: complete set of backups, time: 00:00:01
Backup finished on 19 May 13

From backup may 19, 13
Current archived log
channel ch1: Startup archived log backup set
channel ch1: specifying the newspapers archived in the backup set
archived journal entry thread = 2 sequence = 83 RECID = 399 STAMP = 815861227
channel ch1: from room 1 to May 19, 13
channel ch2: Startup archived log backup set
channel ch2: specifying the newspapers archived in the backup set
archived journal entry thread = 1 sequence = 90 RECID = 401 STAMP = 815861227
channel ch2: from room 1 to May 19, 13
channel ch1: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/47oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
channel ch1: complete set of backups, time: 00:00:01
channel ch1: archived deletion or newspapers
name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_2_83_814540431.arc RECID archived log file = 399 STAMP = 815861227
channel ch2: finished piece 1 to May 19, 13
piece handle=/u01/app/oracle/product/11.2.0/db_1/dbs/48oa23fd_1_1 tag = DATAFILE_FULL comment = NONE
channel ch2: complete set of backups, time: 00:00:01
channel ch2: archived deletion or newspapers
RMAN-08137: WARNING: log archived not deleted, necessary for intelligence or upstream collection procedure
Archive log file name=+ORAFRA/ORCLdr/archivelog/logbd0ca058_1_90_814540431.arc thread = 1 sequence = 90
Backup finished on 19 May 13

From control file and SPFILE Autobackup 19 May 13
room handle=/u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130519-00 comment = NONE
File control finished and Autobackup SPFILE to 19 May 13
output channel: ch1
output channel: ch2

RMAN >
RMAN >
RMAN retention policy apply to the order
RMAN retention policy is set to 3 redundancy
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = instance 1753 = ORCLdr2 = DISK device type
Remove the following obsolete backups and copies:
Making key time filename/handle type
-------------------- ------ ------------------ --------------------
8 4 may control file copy 13 /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f
Game save 40 9 May 13
Save the piece 40 9 May 13/backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
Save game 39 may 9, 13
Save the song 39 9 May 13/backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013
Backs up the entire 42 9 May 13
Backup total 42 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1mo97nkl_1_1
Backs up the entire 43 9 May 13
Backup total 43 9 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1no97nkl_1_1
Save game 46 may 10, 13
Backup total 46 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1po9abvp_1_1
Game backup 45 may 10, 13
Backup total 45 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1qo9abvp_1_1
Save game 47 10 May 13
Save room 47 10 May 13/backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
Backs up the entire 48 may 10, 13
Save the piece 48 10 May 13/backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013
Backs up the entire 50 10 May 13
Backup total 50 10 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1uo9ac0l_1_1
Backs up the entire 51 may 10, 13
Backup total 51 may 10, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/1vo9ac0l_1_1
Backs up the entire 54 may 11, 13
Backup total 54 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/21o9d0bi_1_1
Save game 53 may 11, 13
Backup total 53 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/22o9d0bi_1_1
Save game 55 may 11, 13
Save the piece 55 may 11, 13/backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
Backs up the entire 56 may 11, 13
Save the song 56 11 May 13/backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013
Backs up the entire 58 may 11, 13
Backup total 58 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/26o9d0cj_1_1
Save game 59 may 11, 13
Backup total 59 may 11, 13 /u01/app/oracle/product/11.2.0/db_1/dbs/27o9d0cj_1_1
Backs up the entire 62 12 May 13
Backup total 62 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/29o9fknp_1_1
Save game 61 12 May 13
Backup total 61 12 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/2ao9fknp_1_1
Save game 77 14 May 13
Backup total 77 14 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00
Game backup 101 16 May 13
Backup total 101 16 May 13 /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130516-00
Backs up the entire 114 18 May 13
Save the song 117 may 18, 13/backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1jo97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = 40 STAMP = 814997122
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1ko97nk1_1_1_ORCL_20130509_DATAFILE_LVL0_09_05_2013 RECID = STAMP 39 = 814997122
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1mo97nkl_1_1 element of backup RECID = STAMP 42 = 814997141
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1no97nkl_1_1 element of backup RECID = STAMP 43 = 814997141
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1po9abvp_1_1 element of backup RECID = STAMP 46 = 815083513
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1qo9abvp_1_1 element of backup RECID = STAMP 45 = 815083514
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1ro9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = STAMP 47 = 815083522
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_1so9ac02_1_1_ORCL_20130510_DATAFILE_LVL1_10_05_2013 RECID = 48 STAMP = 815083522
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1uo9ac0l_1_1 element of backup RECID = STAMP 50 = 815083541
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/1vo9ac0l_1_1 element of backup RECID = STAMP 51 = 815083541
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/21o9d0bi_1_1 backup RECID piece = 54 STAMP = 815169906
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/22o9d0bi_1_1 element of backup RECID = STAMP 53 = 815169906
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_23o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 55 = 815169915
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_24o9d0br_1_1_ORCL_20130511_DATAFILE_LVL1_11_05_2013 RECID = STAMP 56 = 815169917
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/26o9d0cj_1_1 element of backup RECID = STAMP 58 = 815169939
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/27o9d0cj_1_1 element of backup RECID = 59 STAMP = 815169939
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/29o9fknp_1_1 element of backup RECID = 62 STAMP = 815256313
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/2ao9fknp_1_1 backup RECID piece = 61 = 815256313 STAMP
remove the item from backup
handle=/U01/app/Oracle/product/11.2.0/Db_1/DBS/c-3171721304-20130516-00 element of backup RECID = 101 STAMP = 815601943
remove the item from backup
backup piece handle = / backup/RMAN_Backup/rman_bkp_3uo9vf2f_1_1_ORCL_20130518_DATAFILE_LVL1_18_05_2013 RECID = 117 STAMP = 815774800
20 objects deleted

RMAN-06207: WARNING: 2 items could not be removed for DISC due channels
RMAN-06208: status do not match. Use the OVERLAP command to set status
RMAN-06210: list of relevant objects
RMAN-06211: =.
RMAN-06212: filename/Type object Handle
RMAN-06213: --------------- ---------------------------------------------------
RMAN-06214: copy of the data /u01/app/oracle/product/11.2.0/db_1/dbs/snapcf_ORCLdr1.f file
RMAN-06214: /u01/app/oracle/product/11.2.0/db_1/dbs/c-3171721304-20130514-00 piece of backup

RMAN >
RMAN >

Complete recovery manager.
-bash - $3.2

Concerning
Hitgon

Published by: hitgon on May 20, 2013 02:09

Published by: hitgon on May 20, 2013 02:15
It contained a real data file? Or was it a backup controlfile? A backup controlfile may be outdated if another backup controlfile does not capture the same information it contains.

Hemant K Collette

How to create the file controlf from scratch when there is no backup rman, catalog, or trace.

Hello
I am a beginner, I know that we can restore with RMAN control file configure automatic backup feature or by connecting the catalog
charge the Alter database backup controlfile to trace.
But suppose that there is no backup. You have the database running in nomount. I came across a blog which was responsible for creating the control file manually and when there is no planned block number error came, the blogger has used the forumale something as expected number of block * 1024 / something. Lost the link to this blog
was wondering is it possible to create a controlfile from scratch. with little information as the location of the data file, repeat the log size / location.
Please can someone let me know it in detail or shoot me this link!
Thank you

2638616 wrote:

Hello

I am a beginner, I know that we can restore with RMAN control file configure automatic backup feature or by connecting the catalog

charge the Alter database backup controlfile to trace.

But suppose that there is no backup. You have the database running in nomount. I came across a blog which was responsible for creating the control file manually and when there is no planned block number error came, the blogger has used the forumale something as expected number of block * 1024 / something. Lost the link to this blog

was wondering is it possible to create a controlfile from scratch. with little information as the location of the data file, repeat the log size / location.

Please can someone let me know it in detail or shoot me this link!

Thank you

1. Yes, you can do this

2 Controlfile script is standard... link doc oracle: http://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_5003.htm

3. prepare with the location of the data files and of redologs online then create it.

Note - If you have placed the name of the different database, then, it will check with datafile and it give error (if you need correct the name of the database)

As you have not indicated whether or not the last stop of database is compatible (we assume that there are his uniform and mandatory ORL and archives)

-Pavan Kumar N

Synchronization log during backup RMAN of archive file
Hello

I have a small question. I hope someone can answer.

Our database (cluster) needs an answer less than 0.5 seconds. Most of the time it works, except when running the RMAN backup.

During the week we run only once a full backup, each day of the week an incremental backup, each time a backup controlfile and every 15 minutes an archive backup.

During a backup response time can be much longer then this 0.5 seconds.
Below is a typical example of responsetime.

EVENT: log file sync
WAIT_CLASS: commit
TIME_WAITED: 10 774

It is obvious that it takes very long to get a validation. It comes in a few seconds. As you can see it's long. It is clearly linked to the RMAN backup, because this kind of responsetime appears when the backup is running.

I would like to ask why the response times are so high, even if I only backup the archivelog files? We did not have this problem before but suddenly 2 weeks, we have a problem and I can not find the problem.

-We use a 11.2 G on ASM RAC database. Redo logs and database files are on the same disks.
-Automatic backup of the controlfile is off.
-Dataguard: LogXptMode = 'arch '.

Greetings,
Hello

I don't know why you posted here, but I'm sure that you will get more responses in one of these forums:

{forum: id = 74}
{forum: id = 61}

Only the unused blocks backup RMAN as well?

DB version: 11.2.0.4
OS: RHEL 6.6
If I remember correctly, RMAN backs up only used blocks. I created a tablespace of 20 GB, as shown below. When I backed up, the backup piece is only 4MB in size, as shown below.
SQL > create tablespace TEST_TS3 datafile '+ DATA_DG' size 20 G
autoextend on
MaxSize 32767 m
Local extended management
single 4 M size
Auto segment space management;
Created tablespace.
SQL >
SQL > select tablespace_name, bytes/1024/1024 of dba_Data_Files where nom_tablespace = 'TEST_TS3 ';
BYTES/1024/1024 NOM_TABLESPACE
------------------------------ ---------------
TEST_TS3 20480
Backup tablespace TEST_TS3 that is not used by all segments (empty)
RMAN > backup tablespace TEST_TS3 format='/u05/RMAN_BKP/TBS_%U_%T.rmbk' tag = TEST_TS3_BKP;
From 18 February 16 backup
using the control file of the target instead of recovery catalog database
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 4941 instance = HMAGPRD2 = DISK device type
channel ORA_DISK_1: starting full datafile from backup set
channel ORA_DISK_1: specifying datafile (s) in the backup set
Enter a number of file datafile = name=+DATA_DG/hmagprd2/datafile/test_ts3.413.904152141 00144
channel ORA_DISK_1: starting piece 1-18 February 16
channel ORA_DISK_1: finished piece 1-18 February 16
piece handle=/u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk tag = TEST_TS3_BKP comment = NONE
channel ORA_DISK_1: complete set of backups, time: 00:00:01
Backup finished on 18 February 16
$
$ ls - lh /u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk
-rw - r - 1 oracle oinstall 4.1 M 18 Feb 17:29 /u05/RMAN_BKP/TBS_03qu8hg2_1_1_20160218.rmbk
But in the world of real output, size of the RMAN backups seems to be much higher.
The following production DB is 27.5 terabytes in size as evidenced by the physical layer (DBA_DATA_FILES. Column of BYTES)
SQL > select sum(bytes/1024/1024/1024) bytesGB from dba_Data_Files;
BYTESGB
----------
27885.3252
But at the level of the logic layer, the used space is only 16.5 TB as evidenced by DBA_EXTENTS. BYTES column
SQL > select sum(bytes/1024/1024/1024) bytesGB from dba_extents.
BYTESGB
----------
16621.316
But the size of RMAN backup came to 20 terabytes , become almost 4TB that space consumed at the level of the logical layer (DBA_EXTENTS. BYTES).
Why is this?

RMAN jump blocks that have never been used. If a block has been used in the past, it will be included in the same backup if currently is not used:

https://docs.Oracle.com/CD/B28359_01/backup.111/b28270/rcmcncpt.htm

Compression for backup sets

When you back up the data files of backup sets, RMAN can use unused block compression to skip blocks of data file. RMAN always ignores blocks that have never been used. Under certain conditions, which are listed in the BACKUP AS BACKUPSET entry in reference Oracle database backup and recovery, RMAN also ignores the blocks that are not currently used. Data file backup sets are generally smaller than copies of data file and take less time to write. Compression of the unused block is fundamental to how RMAN writes files of data in backup items and cannot be disabled.

Help remove backups rman (delete the repository)

Hi all.
I will soon be administering a few databases Oracle (11g Rel2). Currently these DBs area in log mode archive with a backup rman in place policy.

I don't like this policy and you want to use my own, incremental backups from updadateable, so this is the plan I have in mind.

(1) disable mode archive.

(2) a clean shutdown and take a backup to cold.

(3) since after you disable archiving, backups RMAN ALL will be unusable, I want to remove them (including newspapers archive and backup sets).

(4) after the correct deletion, set up some persistent RMAN settings, such as retention policy, controlfile autobackup and optimization.

(5) turn on archiving

(6) to set up the new policy based backups backup incremental updateable with duplex location for archiving logs.

Help is requested on the best way to clean all the backups (3).

I can manually delete the backups and do overlap, but according to the Oracle Documentation "Delete backup" will be delete all backups for data recorded in the RMAN Repository.

So which is the best way easier and faster? Will delete backup include the archive logs?

Thanks in advance. Luis!

myluism wrote:

Can I still use them?

I would say it is "the wrong answer to evil. When you disable log mode archive, you can only back up the database when it is stopped and only to restore and recover the database until the last stop.

Looking at your plan, I wonder what you are trying to accomplish first log mode archive disabling and then enabling archive mode log again. Why do you think that this is necessary and what you're trying to accomplish.

You need not disable and enable log mode archive in order to eliminate the obsolete achivelogs.

If you are not satisfied with the retention policy, simply change it. All backups that are outside your retention policy will be considered as obsolete and you can remove them using RMAN delete obsolete, which will remove all files as well as the appropriate data backup from the RMAN Repository.

For example you can archivelog delete all the entries backup and then delete the backupset or remove them at the OS level, do overlap and then use delete noprompt expired archivelog all.

The retention policy applies to backup and archivelogs. However, you can have a separate archivelog deletion policy that applies to archivelogs.

Full backup to optimize backup RMAN

Hi gurus,
I wanted to implement the functionality of rman backup optimization. I did a little test to verify its use and not found helpful whenever I do a full backup to backup all data files and nothing is ignored.
According to the ORACLE notes as below, ideally, once I backup the database, the backup else should jump not all files.

If you enable Backup Optimization and then the BACKUP command ignores backup files when the identical file has already been saved on the specified device type.

Please note that it's my test server and no connections are on the DB. Listener is broken. If no point of change Yvert. I'm missing here something?
Oracle - 11.2.0.4 version
RMAN > run
2 > {allocate channel ch1 type
3 > disc format ' / oraback/RMAN/%d_DB_%u_%s_%p';
4 > backup database;
{5 >}
allocated channel: ch1
channel ch1: SID = 172 type device = DISK
From April 28, 15 backup
channel ch1: start the backup set full datafile
channel ch1: specification-datafile in the backup set (s)
Enter a number of file datafile = 00001 name=/u01/oradata/nmsdata/system01.dbf
Enter a number of file datafile = name=/u04/oradata/nmsdata/NMSINFO_DATA01_02.dbf 00006
Enter a number of file datafile = 00005 name=/u04/oradata/nmsdata/NMSINFO_DATA01_01.dbf
Enter a number of file datafile = name=/u03/oradata/nmsdata/NMSINFO_INDX01.dbf 00007
Enter a number of file datafile = name=/u01/oradata/nmsdata/undotbs01.dbf 00003
Enter a number of file datafile = name=/u01/oradata/nmsdata/sysaux01.dbf 00002
channel ch1: from room 1 to 28 April 15
channel ch1: finished piece 1 at 28 April 15
total, handle = / oraback/RMAN/NMSDATA_DB_ngq5g2vv_71408_1 tag = comment TAG20150428T042431 = NONE
channel ch1: complete set of backups, time: 00:00:25
channel ch1: start the backup set full datafile
channel ch1: specification-datafile in the backup set (s)
Enter a number of file datafile = name=/u01/oradata/nmsdata/users01.dbf 00004
channel ch1: from room 1 to 28 April 15
channel ch1: finished piece 1 at 28 April 15
total, handle = / oraback/RMAN/NMSDATA_DB_nhq5g30o_71409_1 tag = comment TAG20150428T042431 = NONE
channel ch1: complete set of backups, time: 00:00:01
Backup finished April 28, 15
From control file and SPFILE Autobackup 28 April 15
room handle=/opt/app/oracle/product/11.2.0.4_ee/dbs/c-3349937142-20150428-00 comment = NONE
File control finished and Autobackup SPFILE to 28 April 15
output channel: ch1
RMAN > show all.
RMAN settings for database with db_unique_name CHNMCPRDB1_NMSDATA are:
CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
CONFIGURE BACKUP OPTIMIZATION # by default
SET UP DEFAULT DISK DEVICE TYPE; # by default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F"
SET UP THE DEVICE TYPE DISK PARALLELISM 1 BACKUP BACKUPSET TYPE; # by default
CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1; # by default
CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1; # by default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 1 ' ${backup_dir}/${ORACLE_SID}/%d_t%t_s%s_p%p';}
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / oraback/RMAN;
CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
CONFIGURE ENCRYPTION OF DATABASE # by default
CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD; # by default
CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / tmp/nmsdata_snapshot_arch.ctl ';
RMAN > set UP OPTIMIZATION BACKUP;
new RMAN configuration settings:
CONFIGURE BACKUP OPTIMIZATION
new RMAN configuration settings are stored successfully
RMAN > run
{allocate channel ch1 type
disc format ' / oraback/RMAN/%d_DB_%u_%s_%p';
backup database;
}
2 > 3 > 4 > 5 >
allocated channel: ch1
channel ch1: SID = 172 type device = DISK
From April 28, 15 backup
channel ch1: start the backup set full datafile
channel ch1: specification-datafile in the backup set (s)
Enter a number of file datafile = 00001 name=/u01/oradata/nmsdata/system01.dbf
Enter a number of file datafile = name=/u04/oradata/nmsdata/NMSINFO_DATA01_02.dbf 00006
Enter a number of file datafile = 00005 name=/u04/oradata/nmsdata/NMSINFO_DATA01_01.dbf
Enter a number of file datafile = name=/u03/oradata/nmsdata/NMSINFO_INDX01.dbf 00007
Enter a number of file datafile = name=/u01/oradata/nmsdata/undotbs01.dbf 00003
Enter a number of file datafile = name=/u01/oradata/nmsdata/sysaux01.dbf 00002
channel ch1: from room 1 to 28 April 15
channel ch1: finished piece 1 at 28 April 15
total, handle = / oraback/RMAN/NMSDATA_DB_njq5g509_71411_1 tag = comment TAG20150428T045849 = NONE
channel ch1: complete set of backups, time: 00:00:25
channel ch1: start the backup set full datafile
channel ch1: specification-datafile in the backup set (s)
Enter a number of file datafile = name=/u01/oradata/nmsdata/users01.dbf 00004
channel ch1: from room 1 to 28 April 15
channel ch1: finished piece 1 at 28 April 15
total, handle = / oraback/RMAN/NMSDATA_DB_nkq5g512_71412_1 tag = comment TAG20150428T045849 = NONE
channel ch1: complete set of backups, time: 00:00:01
Backup finished April 28, 15
From control file and SPFILE Autobackup 28 April 15
piece handle=/opt/app/oracle/product/11.2.0.4_ee/dbs/c-3349937142-20150428-01 comment = NONE
File control finished and Autobackup SPFILE to 28 April 15
output channel: ch1
RMAN > exit

LANCERIQUE wrote:

Hi Tom,

Well well, then that contradicts what oracle mentioned in the docs?

Not at all. It does that contradict your understanding of what constitutes a data file "changed."

Also, I pulled data backup and not backup tablespace.

Is not serious. The principle is the same.

Also check your statement my understand that if there are 100 files of data and rarely used, Yvert will be updated for each of them?

If they are not unalterable, then Yes. That's how oracle ensures consistency between the data files.

Kind regards

Nikhil Mehta.

How to run the rman output files, which are more days of retention

I use for my rman backup tasks.
I have format my output files of rman to a specific path, instead of the fast recovery area.
Also, I spend below command in RMAN
RMAN > CONFIGURE RETENTION POLICY to RECOVERY OF 7-DAY WINDOW;
And the "control_file_record_keep_time" parameter is also set to 7.
I've been running rman for 8 days. Everything seems good. But I find several rman output files are more than 7 days.
So, I just want to know how to handle the rman output, which is longer than 7 days files?
In fact, I assumed that these older files should be obsolete files, but rman is not to declare that they are obsolete.
So how do now?

user8710670 wrote:

I use for my rman backup tasks.

I have format my output files of rman to a specific path, instead of the fast recovery area.

Also, I spend below command in RMAN

RMAN > CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;

And the "control_file_record_keep_time" parameter is also set to 7.

I've been running rman for 8 days. Everything seems good. But I find several rman output files are more than 7 days.

So, I just want to know how to handle the rman output, which is longer than 7 days files?

In fact, I assumed that these older files should be obsolete files, but rman is not to declare that they are obsolete.

So how do now?

Windows 7 day average recovery rman will protect everything necessary for the recovery to any point in time in the last 7 days. In fact, in the last 604800 seconds. The same will mean that he need the files OLDER than that. Simply because a backupset is older that your recovery window does NOT as yet, it is obsolete. Any recovery begins with the last FULL or INCREMENTAL backup ZERO before the recovery point. And it does not matter how old the backup is, it will be obsolete. Suppose you take a level 0 backup, 1 January and for the rest of the year taking nothing but level 1 and backup archivelog. 31 December than and only the full backup will still not be obsolete, even though he is a year old.

============================================================================

removal of the obsolescence of RMAN

Day 1 - level 0

Day 2 - level 1

Day 3 - level 1

Day 4 - level 1

Day 5 - level 1

Day 6 - level 1

Day 7 - level 1

Day 8 - level 0

Day 9 - level 1

Day 10 - level 1

Day 11 - level 1

Day 12 - level 1

Day 13 - level 1

Day 14 - level 1

On day 14, your window of 7 days is up to date 7. A recovery to date must begin by restoring the backup of level 0 of the day 1. So it may be outdated. Some level 1 between 1 and 6 days backups might be obsolete, depending on if they are incremental or cumulative, and it also happens with archivelogs.

If you have access to MOS, you can review the notes 462978.1 and 463875.1.

============================================================================

Restoring a backup RMAN to a new instance of the database

Hi guys,.
I have a problem with restoring a backup RMAN I have with me a new instance of the database. I have with me are:
1. backup of the SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_. BKP)
2. backup of the control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_. BKP)
3. the full backup (O1_MF_NNSNF_FULLPROD_BU_92DVGW9H_. BKP)
I received these files to a client environment and I need to restore these to a new instance of the database on a local computer. I gave an attempt as follows (in Oracle 10 g):
1, creates a new instance of the (Test75) database using the Oracle Database Configuration Assistant
2 SET ORACLE_SID = Test75
3 connection to this instance with RMAN
4 tried to restore the SPFILE from the BKP file received.

I make mistakes and cannot continue. I don't know if I will carry out the correct steps. Please help me telling me how I should achieve this goal.

Thank you.

1. backup of the SPFile. (O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_. BKP)

2 backup of control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_. BKP)

The first backuppiece resembles a ControlFile and the other looks like a SPFILE'

> I get error and cannot continue

What is the error? (I assume that you have tried to restore the O1_MF_NNSNF_SPFILE_BU_92DVGW9H_ SPFILE. BKP

Note that you must also SET the DBID before restoring the controlfile

Hemant K Collette

case of disaster with backup rman and archivelogs
Salvation;

When the disk failure comes and drop everything on disks, if we have a cold backup and logs archiving ONLY after a cold backup up to disk failure, we can restore files (datafiles, controlfile and everything) and apply to these cold backup archive logs and make the database updated up to the failure of disks.

I had this case in real life, and it works.

but

What happens if you don't have backup rman online that was taken before the failure of disk instead of cold backup and archive logs that was created after the backup online up to the failure of the drive.

We can restore the online of rman backup files, but can we apply archive logs to these restored files to update the database to the disk failure?

Best regards
Use the SET clause UNTIL - for example the VALUE up to TIME - before running the command RECOVER the DATABASE.

See http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsubcl019.htm#i1000331

and example 4-38 on the same page.

Hemant K Collette

Backup RMAN ASM filesystem
Hi all

I have an rman backup (datafile and controlfile) who got caught in an instance of the DSO (not a RAC) ORACLE 11.2.0.2 on a server Linux, now I want to restore the backup into a new database under windows/Linux OS with storage system (single instance RDBMS) General files instead of ASM.

Is this possible?

I can restrore an rman backup ASM in a mechanisim of storage of file in a new server system?

Please clarify my question.

Thanks in advance...

Nonuday
Nonuday wrote:
Hi Levi,

Thank you for your invaluable script and the blog.

can you tell me about this query:

I have an RMAN backup, drawn from the ASM and the backup is the database and controlf backup file that contains the data files and controlfiles.
Now I need to restore this on my system and here I only use ASM or archive log, I use only one instance in any database log mode archive.

I restored the backup controfile RMAN control file.
Before you restore the control file, I checked the pfile orginal of the backup of database with parameters such as
"db_create_file_dest."
"db_create_online_log_dest,"
"db_recovery_file_dest_size."
"db_recovery_dest,"
'log_archive_dest '.

Since I'm not gng to create a database in any mode of newspaper archive, I do not use any of the above parameters and created a database.

Now my question is:
If I restore the database and the data file get restored and after rename all the log files, the database will be open.

I want to know if this is good or bad, and the database will work as he previously worked. Or need to create the db_file_recovery and also other settings for this database.

All parameter:
All these settings should reflect your current environment, any reference to the old environment must be changed.

All file system used:
No matter what you use the file (datafile/redolog/controlfile/archivelog/backuppiece) file system are created on binary Format that depend only on platform. Thus, the file binary (for example datafile) have same format and content on the device gross, ASM, ext3, ext2 and so on. Thus, for the database, it is just a place where the files are stored, but the file are the same. ASM has a different architecture of the regular file system and must be managed differently (IE with RMAN).

On the database:
Given that your database files are the same even different file system using what you need is rename your files from data/redofiles on controlfile during the restoration, the redo files will be recreated.
So, no matter if your database are noarchivelog or archivelog, in the same way you do a restore on ASM is the same way to restore the regular file system. (just rename the database during restore controlfile)

On blog post 'How to migrate all files on ASM to no - ASM (Unix/Linux)' is suddenly of system files to another folder. But you can change the script used for restore purposes;
```
## set newname tell to RMAN where file will be restored and keep this files location on memory buffer
RMAN> set newname for datafile 1 to ;

### swich get list of files from memory buffer (rman) and rename on controlfile the files already restored.
RMAN>switch datafile/tempfile all ;
```
With mounted database, use this script below:

I just commented on three lines that are not necessary in your case.
```
SET serveroutput ON;
DECLARE
  vcount  NUMBER:=0;
  vfname VARCHAR2(1024);
  CURSOR df
  IS
    SELECT file#,
      rtrim(REPLACE(name,'+DG_DATA/drop/datafile/','/u01/app/oracle/oradata/drop/'),'.0123456789') AS name
    FROM v$datafile;
  CURSOR tp
  IS
    SELECT file#,
      rtrim(REPLACE(name,'+DG_DATA/drop/tempfile/','/u01/app/oracle/oradata/drop/'),'.0123456789') AS name
    FROM v$tempfile;
BEGIN
--  dbms_output.put_line('CONFIGURE CONTROLFILE AUTOBACKUP ON;'); ### commented
  FOR dfrec IN df
  LOOP
    IF dfrec.name  != vfname THEN
      vcount      :=1;
      vfname     := dfrec.name;
    ELSE
      vcount := vcount+1;
      vfname:= dfrec.name;
    END IF;
  --  dbms_output.put_line('backup as copy datafile ' || dfrec.file# ||' format  "'||dfrec.name ||vcount||'.dbf";');  ### commented
  END LOOP;
  dbms_output.put_line('run');
  dbms_output.put_line('{');
  FOR dfrec IN df
  LOOP
    IF dfrec.name  != vfname THEN
      vcount      :=1;
      vfname     := dfrec.name;
    ELSE
      vcount := vcount+1;
      vfname:= dfrec.name;
    END IF;
    dbms_output.put_line('set newname for datafile ' || dfrec.file# ||'  to  '''||dfrec.name ||vcount||'.dbf'' ;');
  END LOOP;
  FOR tprec IN tp
  LOOP
    IF tprec.name  !=  vfname THEN
      vcount      :=1;
      vfname     := tprec.name;
    ELSE
      vcount := vcount+1;
      vfname:= tprec.name;
    END IF;
    dbms_output.put_line('set newname for tempfile ' || tprec.file# ||'  to  '''||tprec.name ||vcount||'.dbf'' ;');
    END LOOP;
      dbms_output.put_line('restore database;');
    dbms_output.put_line('switch tempfile all;');
    dbms_output.put_line('switch datafile all;');
    dbms_output.put_line('recover database;');
    dbms_output.put_line('}');
 ---   dbms_output.put_line('alter database open;');  ### comented because you need rename your redologs on controlfile before open database
    dbms_output.put_line('exit');
END;
/
```
After the restoration, you must rename your redologs on controlfile to old location to the new location:

for example
```
##  use this query to get current location of redolog
SQL>  select group#,member from v$logfile order by 1;

## and change from  to 

SQL > ALTER DATABASE
  RENAME FILE '+DG_TSM_DATA/tsm/onlinelog/group_3.263.720532229'
           TO  '/u01/app/oracle/oradata/logs/log3a.rdo'  
```
When you change all the redolog on question below controlfile command:
```
SQL> alter database open resetlogs;
```
PS: Always follow the database in real time using the alert log database file.

HTH,
Levi Pereira

ORA-00245: backup of control file failed; target is likely on a local file sys
Hello

our CARS (Linux 11.2.0.3.0) is relatively new and we are still on the acquisition of experiences with this system...

At the start of the backup with RMAN, we get the following error:

From control file and SPFILE Autobackup 4 July 12
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03009: failure of command of file control and SPFILE Autobackup on channel ORA_DISK_1 at 04/07/2012 16:41:48
ORA-00245: backup of control file failed; target is likely on a local file system

The reason for the error is clear ORA-00245 - in a CCR environment, the snapshot Controlfile location must be on a shared location.

When running the RMAN command "show all" on each node, we get
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/app/oracle/product/11.2.0.3/db/dbs/snapcf_PROD021.f'; # by default
for the #1 node
and
CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / u01/app/oracle/product/11.2.0.3/db/dbs/snapcf_PROD022.f'; # by default
for the #2 node

When using a shared location for the snapshot Controlfile make us still need 2 different names for this configuration file?

CONFIGURE SNAPSHOT CONTROLFILE NAME to ' / < shared location > / snapcf_PROD021.f'; # by default
for the #1 node and
CONFIGURE SNAPSHOT CONTROLFILE NAME to ' / < shared location > / snapcf_PROD022.f'; # by default
for the #2 node

Or should set us up as a single snapshot Controlfile?

RMAN installation for "CONFIGURE SNAPSHOT CONTROLFILE NAME TO... "must be changed on both nodes - correct?

I hope my question is clear enough--any help will be appreciated.

Rgds
JH

Published by: VivaLaVida on 05.07.2012 11:41
The controlfile is shared on the RAC database and having the backup of any node to shared mount point would meet the requirement.

Configure snapshot controlfile name to ' /snapcf_PROD0.f';

Anand

Backup RMAN HRTO
Oracle 11.2.0.2

Question: Via TSM I need to copy a backup rman since a TSM server to the disk.

I have rman backups who have written on tape SBT (TSM server). I can get the handle with the backup from the list, but how to find the path where it is written. Looking at the tdpo.opt file has a value for TDPO_FS, which is a virtual drive. I can't use backup because rman backup set which works only from disk to tape and NO tape on the disc. So I have to try to get this backupset through TSM commands.

Any help would be appreciated!
If you want to copy the TSM backups on disk, you can simulate a scenario to "restore to a new host. The TSM API knows where to find the tape backup.

http://docs.Oracle.com/CD/E11882_01/backup.112/e10642/rcmadvre.htm#i1007814

Otherwise, you have tom consult TSM staff, I am sure that 'somewhere' in the TSM environment that real places are stored. But who does not directly to RMAN/Oracle.

Werner

Logical backup RMAN containing unused blocks
Dear Experts

When I backup logic to the data file of the utility, RMAN that warn that this will be also saved all the unused blocks of datafile, so what I need to do, how to avoid this unused block to be backed up while you are taking a logical backup of data files.

System in detail as follows

HP Itanium server
OS - Linux Redhet 5
DB - Oracle10g

Suggest me urgent.
Ikram,

No I did not lack the full result. I noticed these lines, but I don't know which are the most recent. So I took the high ones.

For these lines, we must say that the data blocks have been used when the backup took. Maybe you populated tables with the lines of the sample and then deleted?

I changed the query to display backups the last 3 days:
```
SELECT
(SELECT NAME FROM V$DATAFILE WHERE FILE#=V$BACKUP_DATAFILE.FILE#) DFNAME,
DATAFILE_BLOCKS, BLOCKS,
DATAFILE_BLOCKS - BLOCKS DIFF,
COMPLETION_TIME
FROM V$BACKUP_DATAFILE WHERE COMPLETION_TIME > SYSDATE - 3
ORDER BY COMPLETION_TIME, DFNAME;
```
Could you run this query again?

Best regards

Gokhan Atil

-------------------------------------------------------
If you answer this question, please mark appropriate as correct/useful messages and the thread as closed. Thank you

Relationship between current incarnation & backup / RMAN-20011
Hello

I have

the following situation in RMAN:

Incarnations:

>
RMAN > list incarnation;

List of Incarnations of the database
DB key Inc key STATE ID DB name DB reset reset time SNA
------- ------- -------- ---------------- --- ---------- ----------
133 146 TESTDB 2528045035 PARENT 05-SEPT 1.-10
133 134 TESTDB 2528045035 CURRENT 972274 2 MARCH 11
133 548 TESTDB 2528045035 ORPHAN 996374 MARCH 2, 11
133 646 TESTDB 2528045035 ORPHAN 996490 4 MARCH 11
133 460 TESTDB 2528045035 ORPHAN 997986 MARCH 2, 11
>

Backups:

>
RMAN > list backup;

List of backup sets
===================

Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
56,57 M 176 00:00 DRIVE: 42 MARCH 2, 11
BP key: 177 situation: AVAILABLE Tablet: NO Tag: TAG20110302T100444
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66vht_1_1

List of newspapers archived in defined backup 176
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 2 977121 2 MARCH 11 988286 MARCH 2, 11
1 3 988286 2 MARCH 11 994189 MARCH 2, 11

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
Incr 187 0 M DISK 00:15:42 999,72 2 March 11
BP key: 190 situation: AVAILABLE Tablet: NO Tag: TAG20110302T100531
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/02m66vjc_1_1
List of defined backup data files 187
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
1 0 incr 994637 /CDATA/TESTDB/system01.dbf March 2, 11
2 0 994637 /CDATA/TESTDB/sysaux01.dbf incr 2 March 11
3 0 incr 994637 /CDATA/TESTDB/undotbs01.dbf March 2, 11
4 0 incr 994637 /CDATA/TESTDB/users01.dbf March 2, 11

Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
DISK 4,48 M 201 00:00: 01 MARCH 2, 11
BP key: 206 location: AVAILABLE Tablet: NO Tag: TAG20110302T102124
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/03m670h5_1_1

List of newspapers archived on backup the value 201
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 4 994189 2 MARCH 11 996336 MARCH 2, 11

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
214 full 9.36 M DISK 00:00:10 March 2, 11
BP key: 216 situation: AVAILABLE Tablet: NO Tag: TAG20110302T102129
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-00
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 996373 cash time: March 2, 11

Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
244 757,50 K DISK 00:00:01 MARCH 2, 11
BP key: 247 Situation: AVAILABLE Tablet: NO Tag: TAG20110302T103137
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/05m67149_1_1

List of newspapers archived in backup set 244
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 5 996336 2 MARCH 11 997210 MARCH 2, 11

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
261 incr 0 M DISK 00:13:29 1001,02 March 2, 11
BP key: 263 situation: AVAILABLE Tablet: NO Tag: TAG20110302T103138
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/06m6714b_1_1
List of defined backup data files 261
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
1 0 incr 997238 /CDATA/TESTDB/system01.dbf March 2, 11
2 0 997238 /CDATA/TESTDB/sysaux01.dbf incr 2 March 11
3 0 incr 997238 /CDATA/TESTDB/undotbs01.dbf March 2, 11
4 0 incr 997238 /CDATA/TESTDB/users01.dbf March 2, 11

Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
279 742,00 K DISK 00:00:01 MARCH 2, 11
BP key: 284 situation: AVAILABLE Tablet: NO Tag: TAG20110302T104517
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/07m671tt_1_1

List of newspapers archived on backup worth 279
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
1 6 997210 2 MARCH 11 997953 MARCH 2, 11

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
297 full 9.36 M DISK 00:00:10 March 2, 11
BP key: 299 situation: AVAILABLE Tablet: NO Tag: TAG20110302T104519
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-01
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 997985 cash time: March 2, 11

Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
* 342 438,00 K DISK 00:00:00 MARCH 2, 11 *.
BP key: 345 location: AVAILABLE Tablet: NO Tag: TAG20110302T104935
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/09m67260_1_1

List of newspapers archived on backup worth 342
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
* 1 7 997953 2 MARCH 11 998260 2 MARCH 11 *.

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
* 364 incr 0 M DISK 00:14:34 1001,65 2 March 11 *.
BP key: 366 situation: AVAILABLE Tablet: NO Tag: TAG20110302T104937
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
List of defined backup data files 364
Name of file LV Type cash SNA cash time
---- -- ---- ---------- --------- ----
* 1 0 incr 998289 /CDATA/TESTDB/system01.dbf* March 2, 11
* 2 0 998289 /CDATA/TESTDB/sysaux01.dbf* incr 2 March 11
* 3 0 incr 998289 /CDATA/TESTDB/undotbs01.dbf* March 2, 11
* 4 0 incr 998289 /CDATA/TESTDB/users01.dbf* March 2, 11

Time of accomplishment time BS key size Device Type
------- ---------- ----------- ------------ ---------------
* 7,58 M 387 00:00 DISK: 02 MARCH 2, 11 *.
BP key: 392 situation: AVAILABLE Tablet: NO Tag: TAG20110302T110421
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0bm6731m_1_1

List of newspapers archived in backup set 387
The next time that THRD Seq YVERT low low time next YVERT
---- ------- ---------- --------- ---------- ---------
* 1 8 998260 2 MARCH 11 1000465 2 MARCH 11 *.

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
* 410 full 9.36 M DISK 00:00:10 March 2, 11 *.
BP key: 412 situation: AVAILABLE Tablet: NO Tag: TAG20110302T110425
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 1000507 cash time: March 2, 11

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
483 full 9.36 M DISK 00:00:05 March 2, 11
BP key: 484 situation: AVAILABLE Tablet: NO Tag: TAG20110302T113759
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-03
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 998081 cash time: March 2, 11

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
571 full 9.36 M 04:00:00 disc 2 March 11
BP key: 572 situation: AVAILABLE Tablet: NO Tag: TAG20110302T121754
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-04
SPFILE included: Modification Date: March 2, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 996489 cash time: March 2, 11

Time of accomplishment BS key Type LV size device Type elapsed time
------- ---- -- ---------- ----------- ------------ ---------------
667 full 9.36 M DISK 00:00:18 March 4, 11
BP key: situation 668: AVAILABLE Tablet: NO Tag: TAG20110304T132050
Part name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110304-00
SPFILE included: Modification Date: March 4, 11
SPFILE db_unique_name: TESTDB
Control file included: cash SNA: 996596 cash time: March 4, 11

RMAN >
>

I want to rebuild the database with the backup (bold text).

And I get the error after you run the following script:

>
RMAN > RUN
2 > {}
3 > # STARTUP NOMOUNT;
4 > # RESTORE SPFILE to ' / u01/app/oracle/product/11.2.0.2/db_1/dbs/spfileTESTDB.ora' tag "TAG20110302T063849".
5 > # SHUTDOWN IMMEDIATE;
6 > STARTUP NOMOUNT;
7 > RESTORE CONTROLFILE tag "TAG20110302T110425".
8 > STARTUP MOUNT;
9 > SET up to this THAT SNA 1000507.
10 > RESTORE database;
11 > RECOVER DATABASE;
12 > ALTER DATABASE OPEN RESETLOGS;
{13 >}
database is already started

From restoration to March 4, 11
using channel ORA_DISK_1

channel ORA_DISK_1: from the restore backup set data file
channel ORA_DISK_1: restore the control file
channel ORA_DISK_1: backup /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02 piece reading
channel ORA_DISK_1: room handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02 tag = TAG20110302T110425
channel ORA_DISK_1: restored the backup part 1
channel ORA_DISK_1: restore complete, duration: 00:00:15
output file name=/CDATA/TESTDB/control01.ctl
output file name=/CFLASH/TESTDB/control02.ctl
Restoration finished in March 4, 11

database is already started
mounted database
output channel: ORA_DISK_1

executing command: SET until clause

From restoration to March 4, 11
From implicit overlapping backup 4 March 11
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID = 136 type of device = DISK
Cut 11 objects
Backup of implicit overlap finished March 4, 11

Starting copy of implicit intersection to March 4, 11
using channel ORA_DISK_1
Copy of implicit cross ended up at March 4, 11

the search for all files in the recovery area
cataloging files...
cataloging done

List of cataloged files
=======================
File name: /CFLASH/TESTDB/archivelog/2011_03_04/o1_mf_1_1_6q1k25xs_.arc

using channel ORA_DISK_1

channel ORA_DISK_1: from the restore backup set data file
channel ORA_DISK_1: specifying datafile (s) to restore from backup set
channel ORA_DISK_1: restore datafile 00001 to /CDATA/TESTDB/system01.dbf
channel ORA_DISK_1: restore datafile 00002 to /CDATA/TESTDB/sysaux01.dbf
channel ORA_DISK_1: restore datafile 00003 to /CDATA/TESTDB/undotbs01.dbf
channel ORA_DISK_1: restore datafile 00004 in /CDATA/TESTDB/users01.dbf
channel ORA_DISK_1: backup /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1 piece reading
channel ORA_DISK_1: room handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1 tag = TAG20110302T104937
channel ORA_DISK_1: restored the backup part 1
channel ORA_DISK_1: restore complete, duration: 00:13:45
Restoration finished in March 4, 11

From back to March 4, 11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
RMAN-00571: ===========================================================
RMAN-03002: failure of the command recover at 04/03/2011 13:47:17
RMAN-06004: error ORACLE recovery catalog database: RMAN-20011: target database incarnation is not common in the recovery catalog

>

How will I know the right embodiment to restore power?

Help, please

Reagards

hqr200475

Edited by: hqt200475 the 04.03.2011 06:19
To verify valid backups in the current version number:

recoverable backup list;

Definition of this statement:

/*
Specifies the data backups or copies file whose status in the repository is AVAILABLE and which can be used for restoration and recovery in the course of the incarnation target database. This list includes all backups and copies except the incremental backups that have no valid parent to which the differential can be applied.
*/

Werner

Backup RMAN DB files

Similar Questions

Compression for backup sets

Maybe you are looking for