Backup RMAN when FRA is configured

Similar Questions

• backup rman design database with phsical ensures

  Hello

  12 c database, after physical expectation is created, I need backup rman configuration,

  The goal is: a) backup of database b) remove archivelogs that have been backed up, free up space FRA.

  Design as below:

  1:

  in RMAN (primary and standby):
  RMAN >
  Configure controlfile autobackup on;
  set the type of backup device type disk compressed backupset;
  CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;

  
  2: primary school:
  RMAN > CONFIGURE RETENTION POLICY to the 5 DAY RECOVERY WINDOW;

  3: in priamry, turn on track changes to block

  4: primary, implemented since rman level 0 (full backup) on Sunday.

  5: in the primary, the installation program rman level 1 backup from Monday to Saturday.

  6: primary, set up since rman "save archive backup delete them all obsolete" every hour;

  questions here:

  1. as in step 5, for the protection of the o and delete archivelog, the script using:

  Run {}
  allocate channel d1 type disk;
  SQL 'alter system archive log current';
  overlap archivelog all;
  backup AS COMPRESSED BACKUPSET archivelog all delete them all input;
  output channel d1;
  }

  I wonder if ' archivelog all delete all entries "will delete archivelog which was not taken on the eve of the database and broken standby database

  (hanging and out-of-sync with primary)... it is a concern, is that possible?

  2. If the primary database crashed, failover to standby mode, then restore/recovery primary, switch back to the primary, this design is just? If you have any good suggestions, please let me know.

  (to put it simply, I don't want to full/incremental backup to install standby, primary server CPU is good enough)

  Thank you very much!

  A few brief notes worth a visit:

  Based on Oracle 11 g Data Guard for the backup database and restore

  http://www.databasejournal.com/features/Oracle/article.php/3830766/leveraging-Oracle-11g-Data-Guard-for-database-backup-and-recovery.htm

  Standby database using RMAN

  http://Arup.blogspot.com/2007/07/standby-database-using-RMAN.html

  Best regards

  mseberg

• Management of the backups don't FRA not catalog

  Hi all

  I do backups RMAN in my database pending.

  I do not set up catalog FRA or rman.

  If I put a rman policy in my primary CONFIGURE ARCHIVELOG DELETION policy to APPLY ON ALL STANDBY;

  Archive logs are automatically removed or should I run an rman command to delete them?

  So if I understand correctly, in my first if I have political value to configure archivelog deletion apply pending all the

  the command delete archivelog all will remove them all the records that have been applied to all relief.

  Yes

  If I run the command delete obsolete and the retention policy is set UP RETENTION POLICY to RECOVERY WINDOW OF 3 DAYS;

  It will remove the archives more than 3 days

  In this case, he would check for both conditions - retention and deletion policy policy. If the two conditions to hold good, so only archive will be deleted from the primary. Moreover, if archive has not been applied to the wait since the last 3 days (retention period), then you can imagine that you have a huge gap in the standby database.

  -Jonathan Rolland

• 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 backup RMAN destinaion

  I'm configuration RMAN and make following steps

  1. Install 11 GR 2 software and create the database
  2. Create the repository, tablespace and rman user
  3. Save my two DB on two different servers
  4. Then I executed after script, by connecting one of the DB as target (rman target sys/pwd@pcba catalog=rman/protector@ameen)

  {code}

  SET UP DEFAULT DISK DEVICE TYPE;

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  SET UP THE DEVICE TYPE DISK PARALLELISM 4 TYPE OF BACKUP TO COMPRESSED BACKUPSET;

  CONFIGURE ARCHIVELOG DELETION POLICY TO SAVE 2 TIMES TO THE DISK.

  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / u01/app/oracle/fra/rman_backups/SBA_RMAN_BK_%t.%p.BAK'

  RUN

  {

  backup database archivelog with the tag "pcba_level0_backup".

  delete noprompt obsolete;

  }

  duplication of copy;

  cross-checking of backup;

  overlap archivelog all;

  quit smoking;

  {code}

  • I was of the opinion that this backup set will be save on my server where I will execute this script, where there is also this backup is saved on TARGET DB.
  • I will be very thank full if any brother help me in this respect and allow me to get it backed up on the server where the rman repository.

  An RMAN backup is always on the database server.  Server process run attached to the database and these create the backupsets.  Thus, they are created on filesystems which are 'local' on the database server.

  You can NFS mount a file system of your rman client server to the database server and then run the RMAN backup as if the file system is 'local' on the database server.

  Hemant K Collette

• last available retention policy backup RMAN

  Hi all
  
  I'm on 11.2 and had a question regarding the rman... my ploicy of retention is set to 22 days see below
  

  RMAN> show all;
  
  RMAN configuration parameters for database with db_unique_name TEST are:
  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 22 DAYS;
  CONFIGURE BACKUP OPTIMIZATION OFF; # default
  CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
  CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # default
  CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
  CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
  
  List of Backup Sets
  ===

  Published by: user8363520 on September 28, 2011 15:08
  
  Published by: user8363520 on September 28, 2011 15:09

  user8363520 wrote:
  Hi all

  I'm on 11.2 and had a question regarding the rman... my ploicy of retention is set to 8 days see below

  RMAN> show all;
  
  RMAN configuration parameters for database with db_unique_name TRGT are:
  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 8 DAYS;
  CONFIGURE BACKUP OPTIMIZATION OFF; # default
  CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backups/cont_spfile_%F';
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%d_ctl_spfile_%F';
  CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO BACKUPSET PARALLELISM 1;
  CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT   '/backups/%d_%t_%s_%p_%T';
  CONFIGURE MAXSETSIZE TO UNLIMITED; # default
  CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
  CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
  CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 2 TIMES TO 'SBT_TAPE';
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/112_64/dbs/snapcf_TRGT.f'; # default
  
  RMAN>
  

  but when I login and backup list... back were taken log time back still shows as AVAILABLE... I thought that it would be marked obsolete or expired... any reason why his does not like that? I had to change my couple of time format is why it dose not match the above... but just that I do not understand why his watch available?
  

  They are not 'marked' as outdated. They are "evaluated" as obsolete when necessary to meet demand for obsolete series. Notice what happens when I take three backups with a REDUNDANCY 2 retention policy

  RMAN> show retention policy;
  
  using target database control file instead of recovery catalog
  RMAN configuration parameters are:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
  
  RMAN> backup database;
  
  Starting backup at 27-SEP-11
  
  channel ORA_DISK_1: backup set complete, elapsed time: 00:01:25
  Finished backup at 27-SEP-11
  
  Starting Control File and SPFILE Autobackup at 27-SEP-11
  piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp comment=NONE
  Finished Control File and SPFILE Autobackup at 27-SEP-11
  
  RMAN> backup database;
  
  Starting backup at 27-SEP-11
  
  channel ORA_DISK_1: backup set complete, elapsed time: 00:01:45
  Finished backup at 27-SEP-11
  
  Starting Control File and SPFILE Autobackup at 27-SEP-11
  piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp comment=NONE
  Finished Control File and SPFILE Autobackup at 27-SEP-11
  
  RMAN> backup database;
  
  Starting backup at 27-SEP-11
  
  channel ORA_DISK_1: backup set complete, elapsed time: 00:01:55
  Finished backup at 27-SEP-11
  
  Starting Control File and SPFILE Autobackup at 27-SEP-11
  piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp comment=NONE
  Finished Control File and SPFILE Autobackup at 27-SEP-11
  
  RMAN> list backup;
  
  List of Backup Sets
  ===================
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  113     Full    94.59M     DISK        00:01:18     27-SEP-11
          BP Key: 113   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T194613
          Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
    List of Datafiles in backup set 113
  
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  114     Full    6.89M      DISK        00:00:01     27-SEP-11
          BP Key: 114   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T194739
          Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp
    Control File Included: Ckp SCN: 1185229      Ckp time: 27-SEP-11
    SPFILE Included: Modification time: 27-SEP-11
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  115     Full    94.59M     DISK        00:01:38     27-SEP-11
          BP Key: 115   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T194931
          Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp
  
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  116     Full    6.89M      DISK        00:00:02     27-SEP-11
          BP Key: 116   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T195116
          Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp
    Control File Included: Ckp SCN: 1185400      Ckp time: 27-SEP-11
    SPFILE Included: Modification time: 27-SEP-11
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  117     Full    94.59M     DISK        00:01:50     27-SEP-11
          BP Key: 117   Status: AVAILABLE  Compressed: YES  Tag: TAG20110927T195228
          Piece Name: /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T195228_784vydks_.bkp
  
  
  BS Key  Type LV Size       Device Type Elapsed Time Completion Time
  ------- ---- -- ---------- ----------- ------------ ---------------
  118     Full    6.89M      DISK        00:00:02     27-SEP-11
          BP Key: 118   Status: AVAILABLE  Compressed: NO  Tag: TAG20110927T195423
          Piece Name: /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp
    Control File Included: Ckp SCN: 1185555      Ckp time: 27-SEP-11
    SPFILE Included: Modification time: 27-SEP-11
  
  RMAN> report obsolete;
  
  RMAN retention policy will be applied to the command
  RMAN retention policy is set to redundancy 2
  Report of obsolete backups and copies
  Type                 Key    Completion Time    Filename/Handle
  -------------------- ------ ------------------ --------------------
  Backup Set           113    27-SEP-11
    Backup Piece       113    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
  Backup Set           114    27-SEP-11
    Backup Piece       114    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp
  
  RMAN> delete obsolete;
  
  RMAN retention policy will be applied to the command
  RMAN retention policy is set to redundancy 2
  using channel ORA_DISK_1
  Deleting the following obsolete backups and copies:
  Type                 Key    Completion Time    Filename/Handle
  -------------------- ------ ------------------ --------------------
  Backup Set           113    27-SEP-11
    Backup Piece       113    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp
  Backup Set           114    27-SEP-11
    Backup Piece       114    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp
  
  Do you really want to delete the above objects (enter YES or NO)? y
  deleted backup piece
  backup piece handle=/orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194613_784vlpho_.bkp recid=113 stamp=762983174
  deleted backup piece
  backup piece handle=/orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983259_784vod4r_.bkp recid=114 stamp=762983260
  Deleted 2 objects
  
  RMAN> exit
  

  or note this:

  RMAN> report obsolete;
  
  RMAN retention policy will be applied to the command
  RMAN retention policy is set to redundancy 2
  Report of obsolete backups and copies
  Type                 Key    Completion Time    Filename/Handle
  -------------------- ------ ------------------ --------------------
  Backup Set           115    27-SEP-11
    Backup Piece       115    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp
  Backup Set           116    27-SEP-11
    Backup Piece       116    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp
  
  RMAN> CONFIGURE RETENTION POLICY TO REdundancy 6;
  
  old RMAN configuration parameters:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
  new RMAN configuration parameters:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 6;
  new RMAN configuration parameters are successfully stored
  
  RMAN> report obsolete;
  
  RMAN retention policy will be applied to the command
  RMAN retention policy is set to redundancy 6
  no obsolete backups found
  
  RMAN> CONFIGURE RETENTION POLICY TO REdundancy 1;
  
  old RMAN configuration parameters:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 6;
  new RMAN configuration parameters:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 1;
  new RMAN configuration parameters are successfully stored
  
  RMAN> report obsolete;
  
  RMAN retention policy will be applied to the command
  RMAN retention policy is set to redundancy 1
  Report of obsolete backups and copies
  Type                 Key    Completion Time    Filename/Handle
  -------------------- ------ ------------------ --------------------
  Backup Set           115    27-SEP-11
    Backup Piece       115    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T194931_784vrvqb_.bkp
  Backup Set           116    27-SEP-11
    Backup Piece       116    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983476_784vw59k_.bkp
  Backup Set           117    27-SEP-11
    Backup Piece       117    27-SEP-11          /orafra/HOUSTON/backupset/2011_09_27/o1_mf_nnndf_TAG20110927T195228_784vydks_.bkp
  Backup Set           118    27-SEP-11
    Backup Piece       118    27-SEP-11          /orafra/HOUSTON/autobackup/2011_09_27/o1_mf_s_762983663_784w20hx_.bkp
  
  RMAN> exit
  

• Behavior of abnormal (Tag Date and place of automatic backup) RMAN script

  Hi all
  
  I have 11 GR 1 material running on Sun SOLARIS 10.
  
  The parameter default RMAN for backup of control file is on DISK (format: u02/oracle/backup/rman/control/%F.ctl)
  
  
  I have the RMAN script following (L0.rman):
  Run {}
  allocate channels ch1 type SBT_TAPE parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt) ';
  tag backup "${CURRENT_DATETIME}" additional 0 filesperset 3 format 'DB_%T_%U.dbf' database more archivelog;
  output channel ch1.
  }
  host ' cp /oracle/app/oracle/product/11.1.0/db_1/network/admin/tnsnames.ora/u02/oracle/backup/rman/$(echo $CURRENT_DATETIME) /';
  
  
  This is called by the following (L0.sh) script:
  #! / bin/bash
  CURRENT_DATETIME = "$(date + 20 %y %m %d %H %M)»;) export CURRENT_DATETIME
  export ORACLE_SID = EDWH
  export ORACLE_HOME=/oracle/app/oracle/product/11.1.0/db_1
  mkdir/u02/oracle/backup/rman/$(echo $CURRENT_DATETIME)
  RMAN nocatalog target / cmdfile = L0.rman log = L0_EDWH_$ CURRENT_DATETIME.log
  
  
  The anomalies are as follows:
  
  1. the backupsets are created with a literal tag "${CURRENT_DATETIME}" instead of "201010051915" - why?
  FYI, the command 'host' at the bottom of L0.rman successfully copies the file in the right directory (/ u02/oracle/backup/rman/201010051915 /).
  
  2. after the backup finishes, the automatic backup for the control and spfile is taken on SBT_TAPE instead of DISK - why?
  
  Any help will be appreciated.

  1. well, this $CURRENT_DATETIME is variable shell, RMAN does not interpret it (she can't and doesn't have to.) HOST calls the external commands by spawning the shell in non-interactive mode and when placing the order for her, and since you have exported the variable is available to all processes having engineered and develop properly, then files are copied in the expected location. If you remove the '; CURRENT_DATETIME export"from your shell script, you will see files copied in/u02/oracle/backup rman / / because the variable will not be in the environment of the layed shell (it will be local to the script) and will expand to the empty string. You must pass $CURRENT_DATETIME to the RMAN script as a variable substitution so that the shell expands it before calling RMAN, like this:

  L0. RMAN: {code}
  Run {}
  allocate channels ch1 type SBT_TAPE parms 'ENV=(TDPO_OPTFILE=/opt/tivoli/tsm/client/oracle/bin64/tdpo.opt) ';
  backup format tag & 1 extra strength 0 filesperset 3 'DB_%T_%U.dbf' database archivelog;
  output channel ch1.
  }
  host ' cp /oracle/app/oracle/product/11.1.0/db_1/network/admin/tnsnames.ora/u02/oracle/backup/rman / $ CURRENT_DATETIME /';
  {code}
  L0.sh: {code}
  #! / bin/bash
  CURRENT_DATETIME = "$(date + 20 %y %m %d %H %M)»;) export CURRENT_DATETIME
  export ORACLE_SID = EDWH
  export ORACLE_HOME=/oracle/app/oracle/product/11.1.0/db_1
  mkdir/u02/oracle/backup/rman / $ CURRENT_DATETIME
  RMAN nocatalog target / cmdfile = L0.rman using $CURRENT_DATETIME log = L0_EDWH_$ CURRENT_DATETIME.log
  {code}

  Note the * & 1 * variable substitution in the RMAN script and * using * keyword in the RMAN command line.

  2. control file record is taken to the same media, that the last backup, this is normal. You can't "CONFIGURE CONTROLFILE AUTOBACKUP ON the DISC" or something like that, you can only enable or disable it and specify format for various types of devices. Default device type does not play here, you are precisely the configured default device type substitution tape backup.

• Backup RMAN of TAR FULL after finishing.

  Hi all
  We plan backups RMAN from EMGC 10
  Databases / DB / availability / schedule backup / database backup schedule / all custom...
  I can add the line of tar in the RMAN script but the RMAN does not tar - czvf...
  
  How is it possible to tar backup after arriving? I can string a bash script?
  Thank you
  * T

  When you use the OEM GC configuration for running a scheduled backup, OEM GC run an RMAN session. You will not be able to change this option by inserting the shell commands.

  What you could do, is have the OEM GC to create the RMAN script for you (or creat it yourself), store the RMAN script in your catalog RMAN and create a BONE type Job. In this job, you can run a shell script, which first start RMAN session and run the RMAN script stored, that you created, and then run your command "tar".

  You can even think to do that with a multi step employment type, so that if your RMAN defective stage, you do not want the step of tar to execute.

  Concerning
  Rob

• Can store backups RMAN in a diskgroup in ASM?

  RDBMS version: 11.2.0.4

  OS: Oracle Linux 6.6

  RAC environment

  Can store backups RMAN in a diskgroup in ASM? If so, is it recommended?

  Yes, you can:

  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '+diskgroupname';
  

  It depends on your requirements and backup strategy.

• 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.

• Do not lock - automate the deletion of backups RMAN old day after a success

  Hi all

  Admin: Do not lock this thread. I moved here the database instance based on the suggestion of another Member, and the question to this forum. If you want to lock a thread, lock one in the forum of the database, not this one.

  I am looking for a way to automate the deletion of backups RMAN old days only after the occurrence of a success. At the present time, I have daily backups of L0 via crontab, and I need to create a script that can tell if a successful backup is done, then delete the old L0 if it has. Any suggestions on how to start? I'm stuck in code to see if a successful backup has been performed.

  Oracle 11.2.0.3

  Exadata (4 nodes)

  Linux 5.10

  * a from database forum

  A backup is completed when the backup command is complete.

  You have two 'blocks execution' in your rman script.

  Put the DELETE OBSOLETE between the end of the last execution block and EXIT:

  OUTPUT CHANNEL fs1b;
  OUTPUT CHANNEL fs2b;
  OUTPUT CHANNEL fs3b;
  CHANNEL fs4b;
  CHANNEL fs5b;
  CHANNEL fs6b;
  CHANNEL fs7b;
  CHANNEL fs8b;

  }

  remove the backup noprompt obsolete;
  "exit";

  You also want to do some other household:

  cross-checking of backup;

  delete expired backup noprompt.

  overlap archivelog all;

  delete noprompt expired archivelog all;

• backup rman Exadata with zfs

  Our company has recently decided to start backup rman ZFS instead of regular tape backup.

  I would like to know what is the right measures to check if ITS configured right device of ZFS, the implementation of rman backups, etc.

  I'd appreciate someone here can point me to the right document.  I read ZFS Q and A and backup using ZFS best practices. All very unclear and seems none of them provide a digital step step.

  I wonder if Oracle provides an instruction step by step for the DBA.

  9233598-

  Q documents & you examined include the "Oracle ZFS storage pool: FAQ: Exadata RMAN backup with Oracle ZFS Storage Appliance (Doc ID 1354980.1)" Note? This note has a lot of information and is updated regularly and includes information about configuring ZFS and RMAN backups to the device of ZFS.

  Some useful books of whites, an I have used in the past and has been updated again last year: Oracle Exadata with the Sun ZFS Storage Appliance protection: best practices in Configuration and backup and recovery Performance and best practices using Sun ZFS Storage Appliance with Oracle Exadata Database Machine

  These documents will in many details - including providing examples of scripts.

  HTH.

  Thank you

  Kasey

• 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

• 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