RMAN backup space free after compression subpartition

Similar Questions

• RMAN backup - space exhausted

  Hi, Im just playing with backups RMAN,
  
  IM using 11 GR 2 on OEL 5.5 with configured ASM,
  
  I have a diskgroup FRA that the full backup seems to be attempted to be saved
  
  When RMAN openeing and target the connection to the database, I have issued a "backup database" command to do a full backup, however I met the following error, everyone to make an idea how I can solve this problem? Please see below for Terminal Services session:
  

  RMAN> backup database;
  
  Starting backup at 15-NOV-10
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: SID=253 device type=DISK
  channel ORA_DISK_1: starting full datafile backup set
  channel ORA_DISK_1: specifying datafile(s) in backup set
  input datafile file number=00001 name=+DG1/orcl/datafile/system.256.734901431
  input datafile file number=00002 name=+DG1/orcl/datafile/sysaux.257.734901433
  input datafile file number=00003 name=+DG1/orcl/datafile/undotbs1.258.734901433
  input datafile file number=00005 name=+DG1/orcl/datafile/example.265.734901913
  input datafile file number=00006 name=+DG1/orcl/datafile/test1.267.734907043
  input datafile file number=00007 name=+DG1/orcl/datafile/test2.268.734909449
  input datafile file number=00004 name=+DG1/orcl/datafile/users.259.734901433
  channel ORA_DISK_1: starting piece 1 at 15-NOV-10
  
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03009: failure of backup command on ORA_DISK_1 channel at 11/15/2010 22:59:11
  ORA-19510: failed to set size of 121610 blocks for file "+FRA/orcl/backupset/2010_11_15/nnndf0_tag20101115t225424_0.279.735173667" (block size=8192)
  ORA-17505: ksfdrsz:1 Failed to resize file to size 121610 blocks
  ORA-15041: diskgroup "FRA" space exhausted
  
  RMAN> 

  FRA does not support automatic growth. So if you have exhausted the space, you have to check what backups you have on it and try to move to the tape and then drive delete or just delete using the delete backup command. To increase the space within the FRA, you must have with you the additional disks that would improve your FRA.

  Aman...

• RMAN: Backups not exipring after the window of redundancy.

  Hello

  I meet backup sbt_tape and the use of the slot block:

  run{
  ALLOCATE CHANNEL C1 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
  ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  ALLOCATE CHANNEL C2 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
  ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  ALLOCATE CHANNEL C3 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
  ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  ALLOCATE CHANNEL C4 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
  ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  backup incremental level 0 database filesperset=1 format '%d_L0_DF%f_%T_%u.dbf' tag 'DB_L0_DF_#_DT_UNQNO';
  backup current controlfile format '%d_L0_CF_%T_%u.ctl' tag 'DB_L0_CF_DT_UNQNO';
  backup incremental level 0 archivelog all filesperset=1 format '%d_L0_AL_%h_%e_%T_%u.arc' tag 'DB_L0_ARC#_DT_UNQNO';
  crosscheck backup of database;
  crosscheck backup of archivelog all;
  delete noprompt expired backup of database;
  delete noprompt expired backup of archivelog all;
  }
  

  My backups work perfectly, but for some reason, my backups expire even though my redudancy is set to 7 days.

  In my dest backup, I have backups as old as March 13, which should have been expired since a long time back.

  Any ideas what could be wrong?

  RMAN> show all;
  using target database control file instead of recovery catalog
  RMAN configuration parameters for database with db_unique_name IWTPR are:
  CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
  CONFIGURE BACKUP OPTIMIZATION ON;
  CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
  CONFIGURE CONTROLFILE AUTOBACKUP OFF;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # default
  CONFIGURE DEVICE TYPE DISK PARALLELISM 4 BACKUP TYPE TO COMPRESSED BACKUPSET;
  CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
  CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so, ENV=(STORAGE_UNIT=CH2-nwtdb-Oracle, BACKUP_HOST=172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  CONFIGURE MAXSETSIZE TO UNLIMITED;
  CONFIGURE ENCRYPTION FOR DATABASE OFF;
  CONFIGURE ENCRYPTION ALGORITHM 'AES128';
  CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
  CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+IWTPRFRA/IWTPR/snapcf_IWTPR.f';
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+IWTPRFRA/iwtpr/snapcf_iwtpr.f';
  

  Thanks in advance,

  aBBy.

  Details of env: RAC 4 node cluster running 11.2.0.3.4 GI/RDBMS on RHEL 5. 6

  AB007 wrote:

  Hello

  I meet backup sbt_tape and the use of the slot block:

  1. Run {}
  2. ALLOCATE CHANNELS C1 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so.
  3. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  4. ALLOCATE channel C2 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so,
  5. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  6. ALLOCATE CHANNELS C3 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so.
  7. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  8. ALLOCATE CHANNELS C4 TYPE SBT_TAPE PARMS='SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so.
  9. ENV = (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  10. filesperset database backup incremental level 0 = 1 format '% d_L0_DF%f_%T_%u.dbf' tag "DB_L0_DF_ #_DT_UNQNO";
  11. backup current controlfile '% d_L0_CF_%T_%u.ctl' format tag "DB_L0_CF_DT_UNQNO".
  12. incremental backup of level 0 archivelog all filesperset = 1 format '% d_L0_AL_%h_%e_%T_%u.arc' tag "DB_L0_ARC #_DT_UNQNO";
  13. cross-checking of backup of database;
  14. backup duplication of the archivelog all;
  15. delete noprompt expired backup of database;
  16. delete expired backup noprompt to archivelog all;
  17. }

  My backups work perfectly, but for some reason, my backups expire even though my redudancy is set to 7 days.

  In my dest backup, I have backups as old as March 13, which should have been expired since a long time back.

  Any ideas what could be wrong?

  1. RMAN > show all.
  2. using the control file of the target instead of recovery catalog database
  3. RMAN settings for database with db_unique_name IWTPR are:
  4. CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
  5. CONFIGURE BACKUP OPTIMIZATION
  6. CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';
  7. CONFIGURE CONTROLFILE AUTOBACKUP
  8. CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO "%F" # by default
  9. CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO "%F" # by default
  10. SET UP THE DEVICE TYPE DISK PARALLELISM 4 TYPE OF BACKUP TO COMPRESSED BACKUPSET;
  11. SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.
  12. CONFIGURE BACKUP OF DATA TO DISK FILE TYPE DEVICE TO 1;
  13. CONFIGURE BACKUP COPIES OF DATA FILE FOR THE 'SBT_TAPE' UNIT 1;
  14. CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1;
  15. CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE 'SBT_TAPE' 1;
  16. CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/u01/app/oracle/product/11.2.0.3/db1/lib/libddobk.so, ENV is (STORAGE_UNIT = CH2-nwtdb-Oracle, BACKUP_HOST = 172.28.136.50, ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/db1)';
  17. CONFIGURE MAXSETSIZE TO UNLIMITED;
  18. CONFIGURE THE DATABASE ENCRYPTION
  19. CONFIGURE THE ENCRYPTION ALGORITHM "AES128";
  20. CONFIGURE COMPRESSION ALGORITHM 'BASIC' AND 'DEFAULT' LIBERATION OPTIMIZE FOR TRUE LOAD;
  21. CONFIGURE THE NONE ARCHIVELOG DELETION POLICY;
  22. CONFIGURE the SNAPSHOT CONTROLFILE NAME to "+ IWTPRFRA/IWTPR/snapcf_IWTPR.f";
  23. CONFIGURE the SNAPSHOT CONTROLFILE NAME to "+ IWTPRFRA/iwtpr/snapcf_iwtpr.f";

  Thanks in advance,

  aBBy.

  Details of env: RAC 4 node cluster running 11.2.0.3.4 GI/RDBMS on RHEL 5. 6

  You are confusing "expired" with "obsolete".

  When a backupset is created, an account of which is placed in the control file.

  If you backup ' overlap ', rman checks these records against reaility.  If no backup turns out have disappeared, his file is marked as "expired".  That follow-up with a 'delete expired backup', and missing backups (expired) records will be deleted from the repository.

  What you want is "delete obsolete.  Which will remove any backup that is no longer necessary to enforce the retention period.

  BTW, "redundancy" and "x days" are mutually exclusive.

• Can RMAN backup in 2 places due to the lack of space?

  Oracle 11.2.0.4 on RHEL 6.4

  We have a DB production with RMAN backup (L0) enlarged with compression of 400 GB. We usually tape backup. But, today, I need to save this DB for the local file system.

  I don't have a single file with 400 GB of free space system. But, I

  /ora_backup with 300 GB freespace

  and
  

  /U04 with 150 GB freespace

  Is it possible to load RMAN instead of 300 GB of backup in the directory/ora_backup/rman pieces and the remaining items of backup to the directory/u04/rman ?

  Hello

  You can use a running script rman with two channels and write each channel on a different disk location, but be sure to choose the number of data file (size of the data file).

  RMAN > run

  {

  ALLOCATE CHANNEL c1 DEVICE TYPE DISK FORMAT ' / ora_backup/%U';

  ALLOCATE CHANNEL c2 DEVICE TYPE DISK FORMAT ' / u04/%U';

  BACKUP INCREMENTAL LEVEL = 0

  (CHANNEL DATAFILE 1,2,3,4 c1)

  (DATAFILE 5,6,7 CHANNEL c2);

  }

  In this example:

  I choose to backup datafile 1, 2, 3 and 4 on the /ora_backup directory, I choose to backup datafile 5, 6 and 7 on the /u04 directory.

  Best regards

• Post controls after you restore the RMAN backup to a new server

  Hi all
  
  Sorry to ask this fundamental question. But I want to confirm that I did all the checks after restoration.
  
  Total number of patterns
  Number of objects in diagrams
  Invalid objects
  Control over data objects
  Jobs
  Status of datafiles
  Status of log files
  
  Please let me know if something that let him...
  
  TIA,

  An RMAN backup is a physical backup. So, on the restore + restore, it is wise to check the physical objects:
  a. Controlfiles, data files, redo logs (resetlogs would recreate/reset redo logs)
  b. block corruption (see backup/restore logs, controls v$ block_corruption, dbv on each of the data files)

  Users, Tables, Segments, storage spaces are all the logical objects that RMAN is not aware of (with the exception of the w.r.t. DataFiles Tablespaces).

• AFTER dbid chanaged rman backup restore

  Hi all:
  
  I'm on 10.2.0.3.
  
  I need to do a restore from a tape that contains my RMAN backup (in a different database). The backup is in 2 weeks and I use redundancy 1, so I have to re-catalogue my backup items.
  
  All this is perfect until now, but there's a complication. DBID was changed on this database AFTER the backup was made, so the catalog command is get rejected:
  
  RMAN > Catalogue backuppiece ' / db/backup/HMTRN/25 Jul 09/c-3431719427-20090723-00 ";"
  
  ORA-19870: error reading backup total/db/backup/HMTRN/25 Jul 09/c-3431719427-20090723-00
  ORA-19691: / db/backup/HMTRN/25 Jul 09/c-3431719427-20090723-00 is different data base: id = 3431719427, name = HMTRN.
  
  Someone has an idea?
  
  Reset original database in a privious incarnation would work?
  
  Dear I don't see any of them:
  
  RMAN > list incarnation of database;
  
  
  RMAN > list incarnation;
  
  
  RMAN > exir
  
  Thanks in advance!

  Before you start the backuppieces of cataloging, you must restore the controlfile that correspond to this backup (with the correct DBID). CATALOGUE update the controlfile as well.

  Then

  STARTUP NOMOUNT
  RESTORE CONTROLFILE FROM '... location ';
  ALTER DATABASE MOUNT
  CATALOGUE...

• RMAN backup Compression algorithms?

  Hi Experts,

  Please help me, I'm a little confused here.

  1. which algorithm of Compression in RMAN needs license of Advanced Compression in the list below?

  • BASIC
  • LOW
  • MEDIUM
  • HIGH

  2. I'm under the impression that you don't need Advanced Compression license if you use BASIC ALGORITHM of COMPRESSION, but I could be wrong please advise.

  Kind regards

  ZKM

  Basic compression is not license required...

  http://docs.Oracle.com/database/121/BRADV/rcmconfa.htm#CHDEHCEB

  Supported Compression levels

  Oracle database provides two types of compression algorithms: a default compression algorithm and a group of algorithms of compression available with Oracle Advanced Compression option. The default algorithm is a standard Oracle database feature, while Oracle Advanced Compression option is sold separately.

  Default compression

  You can configure the default compression algorithm, which does not require Oracle Advanced Compression option.

• Full database backup time varies after you apply the hotfix.

  Hello gurus,
  
  I applied a patch last week to my database to 10.2.0.5, initially it was 10.2.0.1.Before the patch of the database took 10 hours to finish the job of backup rman through OEM and used to seize the 590 GB of data. After the patch, that the rman job complete in 2 hours and it is only win about 220 GB without errors
  
  The total size is 590 GB but 220 used space and free is 370 gb.
  
  Magic question is why it takes 2 hours to complete and only backup 220 GB in 10.2.0.5 compare to 10.2.0.1.
  
  
  I used this query to check the size of the database.
  
  SESSION_KEY, INPUT_TYPE, STATUS,
  TO_CHAR (START_TIME, "mm/dd/yy HH24 '") start_time,
  TO_CHAR (END_TIME, "mm/dd/yy HH24 '") end_time.
  elapsed_seconds/3600 hrs
  v $ RMAN_BACKUP_JOB_DETAILS
  order by session_key;

  There are several bugs fixed in 10.2.0.5 which can realize:

  6967455 RMAN BACKUP FILE may be slow
  7119336 backup backupset RMAN does not parallelize in multiple channels
  7173341 internal cleaning RMAN can be slow

  This note MOS can provide more details:

  10.2.0.5 Patch set - list of bug fixes by problem Type [ID 1088172.1]

  Best regards

  mseberg

• Purge the rman backup

  Hello, since the alert.log file find this error:
  
  Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc3_25352.trc file:
  ORA-19809: limit exceeded for file recovery
  ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
  ARC3: 19809 creation error archive log file ' DATA01'+.
  Sea 25 09:51:58 Jan 2012
  Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
  ORA-19815: WARNING: 59055800320 bytes db_recovery_file_dest_size is 100.00% used and has 0 bytes remaining available.
  ************************************************************************
  You have choice to free up space in the recovery area:
  + 1. Consider changing the RMAN RETENTION POLICY. If you are using Data Guard +.
  then consider changing POLICY of DELETE ARCHIVELOG RMAN.
  + 2. Back up files on a tertiary device such as a tape using RMAN.
  SAFEGUARDING RECOVERY AREA command.
  + 3. Add disk space and increase the db_recovery_file_dest_size setting to +.
  reflect the new space.
  + 4. Delete unnecessary files by using the RMAN DELETE command. If operation +.
  the system control has been used to remove the files, and then use the RMAN DUPLICATION and
  Commands DELETE has EXPIRED.
  ************************************************************************
  Errors in the /u01/oratest/diag/rdbms/test/TEST1/trace/TEST1_arc0_25306.trc file:
  ORA-19809: limit exceeded for file recovery
  ORA-19804: cannot retrieve 12582912 bytes limit 59055800320 disk space
  ARC0: error creating 19809 archive log file ' DATA01'+.
  
  So I'm trying to purge the rman backup, but I have an error message:
  
  
  rman target = oratest@oraprdlnx1:~$ /+.
  Recovery Manager: release 11.2.0.1.0 - Production on sea Jan 25 09:47:30 2012
  Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
  connected to target database: TEST (DBID = 2044700519)
  
  + RMAN > show all; +.
  
  using the control file of the target instead of recovery catalog database
  RMAN settings for database with db_unique_name TEST are:
  CONFIGURE REDUNDANCY 1 RETENTION STRATEGY; # by default
  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" # 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/oratest/product/11.2.0/dbhome_1/dbs/snapcf_TEST1.f'; # by default
  
  + RMAN > allocate channel for maintenance of type; disc +.
  
  allocated channel: ORA_MAINT_DISK_1
  channel ORA_MAINT_DISK_1: SID = 237 instance = type of TEST1 = DISK
  
  + RMAN > crosscheck backup; +.
  
  "" element of verified backup: turned out to be "AVAILABLE"
  backup handle piece = RECID = 68 = 758320264 STAMP DATA01/test/autobackup/2011_08_04/s_758320263.794.758320265 +.
  Cut objects 1
  
  RMAN > delete obsolete; ** +
  
  RMAN retention policy apply to the order
  RMAN retention policy is set to 1 redundancy
  Remove the following obsolete backups and copies:
  Making key time filename/handle type
  -------------------- ------ ------------------ --------------------
  Backup Set 25 July 4, 11
  Backup total 25 4 July 11 1omgk64v_1_1
  Backup Set 26 July 4, 11
  Backup total 26 July 4, 11 1pmgk650_1_1
  Backup Set 24 July 4, 11
  Total backup, 24 4 July 11 1qmgk650_1_1
  Backup Set 21 July 4, 11
  Backup total 21 4 July 11 1rmgk650_1_1
  Backup Set 28 July 4, 11
  28 1vmgk69v_1_1 July 4, 11 total backup
  Save game 29 July 4, 11
  Backup total 29 July 4, 11 20mgk6a0_1_1
  Backup Set 30 July 4, 11
  Backup total 30 4 July 11 21mgk6a0_1_1
  Save game 31 July 4, 11
  Backup total 31 July 4, 11 22mgk6a0_1_1
  Backup Set 34 4 July 11
  Backup total 34 4 July 11 c-2044700519-20110704-07
  Backup Set 35 July 4, 11
  Total backup, 35 26mgk8ib_1_1 4 July 11
  Backup Set 36 4 July 11
  Backup total 36 4 July 11 c-2044700519-20110704-08
  Backup Set 41 4 July 11
  Backup total 41 4 July 11 28mgk94i_1_1
  Backup Set 42 4 July 11
  Backup total 42 4 July 11 29mgk94j_1_1
  Backup Set 37 July 4, 11
  Backup total 37 4 July 11 2amgk94j_1_1
  Backup Set 40 July 4, 11
  Backup total 40 July 4, 11 2bmgk94j_1_1
  Backup Set 38 July 4, 11
  Backup total 38 4 July 11 2cmgk95c_1_1
  Backup Set 39 July 4, 11
  Backup total 39 4 July 11 2dmgk95k_1_1
  Backup Set 43 July 4, 11
  Backup total 43 July 4, 11 c-2044700519-20110704-09
  Backup Set 46 4 July 11
  Backup total 46 4 July 11 2fmgk99f_1_1
  Backup Set 47 July 4, 11
  Backup total 47 4 July 11 2gmgk99g_1_1
  Backup Set 44 4 July 11
  Backup total 44 4 July 11 2hmgk99g_1_1
  Backup Set 48 4 July 11
  Backup total 48 4 July 11 2imgk99g_1_1
  Backup Set 45 4 July 11
  Backup total 45 4 July 11 2jmgk9a9_1_1
  Backup Set 50 4 July 11
  Backup total 50 4 July 11 2kmgk9aq_1_1
  Backup Set 49 July 4, 11
  Backup total 49 4 July 11 2lmgk9aq_1_1
  Backup Set 51 4 July 11
  51 4 July total backup has 11 c-2044700519-20110704-0
  Backup Set 56 4 July 11
  Total backup 56 2rmgk9qb_1_1 July 4, 11
  Backup Set 55 July 4, 11
  Backup total 55 4 July 11 2smgk9qb_1_1
  Backup Set 58 4 July 11
  Backup total 58 4 July 11 b c-2044700519-20110704-0
  Backup Set 60 4 July 11
  Total backup 60 2umgk9tb_1_1 July 4, 11
  Backup Set 61 4 July 11
  Backup total 61 4 July 11 2vmgk9tc_1_1
  Backs up the entire 62 4 July 11
  Backup total 62 4 July 11 30mgk9tc_1_1
  Backup Set 66 4 July 11
  Backup total 66 4 July 11 34mgk9ua_1_1
  Backs up the entire 65 4 July 11
  Backup total 65 4 July 11 35mgk9ua_1_1
  Backup Set 67 4 July 11
  Total backup, July 4, 11 c-2044700519-20110704-0 67C
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
  RMAN-06091: any string allocated for maintenance (of a suitable type)
  
  How can I purge the db dest file recovery?
  
  Thank you!!!

  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the delete command to the 25/01/2012 09:48:42
  RMAN-06091: any string allocated for maintenance (of a suitable type)

  There is a metalink note that talks about this error.

  Met RMAN-03002 and RMAN-06091 when deleting obsolete backups [567555.1 ID]
  RMAN could not remove obsolete in right Backupsets change Sbt_tape to disk and again Server [ID 1287755.1]

  HTH

  Kind regards
  Nagendra Chillale

  Published by: NC on January 25, 2012 17:00

• RMAN backup with the smallest size of backup

  Oralce 11g 2 on Redhat 5. Disk space is our the tighter resource, and we want an incremental backup with Level0 Sunday and level 1 every day of the week and on Saturdays. I'm using the comamnds to do the job

  --Sunday
  backup incremental level 0 tag 'level_0' database plus archivelog;
  --Other days
  backup incremental level 1 database plus archivelog delete all input;

  I don't think that it is the best practice or produce smaller backup files.
  
  What are you comments and opinions. Thank you

  RMAN backup except for the backup copy will only backup blocks used, which is quite efficient. Backup incremental level 1 are set by default and the smallest of the incremental backup.

  However, you can enable compression reduce the size of the backupset (Oracle 10 g and more). You can also enable the block track the changes in the database only once, so that backup incremental level 1 do not need to analyze the data files for the changes - this allows saving a lot of time and IO.

  SQL > ALTER DATABASE ENABLE BLOCK CHANGE TRACKING;

  RMAN > run {sql 'alter system switch logfile' ;}}
  RMAN > BACKUP AS BACKUPSET INCREMENTAL LEVEL 0 COMPRESSED DATABASE MORE ARCHIVELOG DELETE ALL ENTRIES;
  RMAN > ACE COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 DATA BACKUP MORE ARCHIVELOG;

  I would prefer not to delete the archivelogs after each incremental backup of level 1 in order to make a point in time recovery without the need to restore the archivelogs.

  And don't forget to:
  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  I hope this helps.

• How to recover lost e-mails (partial) after compressing files

  I use windows XP sps, three days ago, I made an oulook express process of compressiom files, after that a windows command prompt I was asked to do.

  Unfortunately, some of the emails (Jan. 2011 - August 2011) was found missing in outmail storage file, after the file compression. I think they were

  automatically removed during the compression of files. Although I found a backup (master) folder in the trash, I still can not return emails lost after running

  recovery in the trash. Can someone help me recover lost emails?

  For your information: until the compression of files - outmail storage folder size is approx. 1.2 GB / after compression: 827 MB

  Thank you

  OE does not compress.  It compact, which means that it removes the space in the file.  This should be done regularly, otherwise it will be too fat and become corrupted, what happened to you.

  See point 2 here: www.oehelp.com/OETips.aspx#2 and you can try to manually import the file bak (just give it another name - see www.oehelp.com/backup.aspx#wm).  If this does not help, then my DBXpress program (www.oehelp.com/DBXpress/) may be able to recover lost messages.

  Steve

• RMAN backup location must change and remove obsolete

  Dear Experts,

  I'm working on the following environment,

  Operating system: Windows server 2012 R2

  Oracle version: 11.2.0.1.0 release

  Type of RMAN backup: Cumulative (preferred by the direction and I can't change it in differential backup)

  My current situation,

  I set up RMAN and H: drive for purposes of backup and G: for Archivelog.

  Recently, my city was covered by the flood waters and the server works not for a week so that we delete obsolete level 0 does not work.

  Currently there is not enough space to run a level 1 and level 0, while I should change the backup location.

  My Question is,

  (1) I need to change this location of drive H: to G: drive backup backup correctly without error not enough space.

  (2) after having taken a level 1 and level 0, depending on my 1 redundancy, RMAN mechanism should delete obsolete backup disk without failure G: and H:.

  Kindly help me how to get to my need. This will help me, thanks in advance

  You can

  1. replace the DB_RECOVERY_FILE_DEST G:

  2 run backups

  3. wait for the DELETE OBSOLETE delete obsolete backups of H:

  and then

  4. change the DB_RECOVERY_FILE_DEST return h as it was more early

  In this way, you don't have to use the FORMAT or CHANNEL of CONFIGURE commands (I was referring to CONFIGURE CHANNEL, not ALLOCATE CHANNEL) to change the destination of the backup

  Hemant K Collette

• content managed rman backup crushing and selection procedure of the tape media

  Hello Experts.

  I have a question about the backupset rman tape media manage tape of the osb.

  [ENV]

  Exadata rman backup assistance OSB(version: 10.4.0.3.0) SL500 LTO5 4 Tape Drive with rman scripts and full backup is working well.

  1 Appendix backup on OS crontab

  -Each backup full day at 00:00 AM

  2 rman view all:

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  using the control file of the target instead of recovery catalog database

  RMAN settings for database with db_unique_name TESTDW are:

  CONFIGURE RETENTION POLICY TO 3 DAY RECOVERY WINDOW;

  CONFIGURE BACKUP OPTIMIZATION # by default

  CONFIGURE THE TYPE OF DEFAULT DEVICE TO 'SBT_TAPE ';

  SET UP THE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 TYPE OF BACKUP BACKUPSET.

  CONFIGURE CONTROLFILE AUTOBACKUP ON;

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  3 rman backup scirpts

  Run {}

  allocate channels c01 type 'sbt_tape' connect 'sys/manager@testdw1';

  allocate channel c02 type 'sbt_tape' connect 'sys/manager@testdw2';

  allocate channel c03 type 'sbt_tape' connect 'sys/manager@testdw1';

  allocate channels c04 type 'sbt_tape' connect 'sys/manager@testdw2';

  Backup section size 900g database;

  output channel c01;

  output channel c02;

  output channel c03;

  output channel c04;

  }

  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  1st quarter > after several weeks and I run the command as "#obtool u admin Pei welcome1 lsvol-L lib1.

  and are used in many media of rman backup band (about 50EA media, perhaps 46EA are full and 4EA are appendble)

  So, I issue the command 'lsvol - a - c' and could not display expired on all media content.

  Why OSB no has not select and replace the tape media despite the rman rman default retention policy (3days) all show the setting.

  Why OSB does not have the expired status of rman content on tape media?

  -> I need the rman (delete expired, delete obsolete etc...) command to share the summary status of OSB and rman rman?

  Q2 > selection procedure for the tape media all backup rman

  Suppose the total number of tape media is 5EA. (1,2,3,4,5) with an available tape LTO5 drive.

  Status: 1 (full-rman content already expired), 2 (content integral-rman not expired), 3 (editable, remaining space), 4 (new media), 5 (currnet wring media)

  If OSB burn now 5 and reach at the end of the Strip and possibly another media, media to be selected by the OSB?

  Advanced thanks.

  If I place the order obsolete in the rman script as 'delete type 'SBT_TAPE' noprompt obsolete device;' the results will be the same as your

  the syntax because rman default setting (CONFIGURE RETENTION POLICY to RECOVERY WINDOW OF 3 DAYS ;) has already been fixed on the command "Show all", right? @)

  Yes.

  I use the catalog of recovery on a different database and backup script has catalog db connection string.

  And if I only use controlfile instead of recovery catalog to save the backup information and put in place "control_file_record_keep_time" a default of 7 days to 365 days, "remove obsolete" command to remove several weeks backupset works well, is it not?

  Possible problem are existing backups for several weeks if you left default control_file_record_keep_time. Change now will not help unless you catalog later manually all the old pieces not catalogued on tape backup.

  After you clean up the situation and particularly to remove obsolete in your script, rman, you will never make problems with control_file_record_keep_time from this moment. By default will do just fine because it is larger than your window of recovery.

  Kind regards

  Mitja

• How to restore RMAN backups

  Hello

  I tried to include works of RMAN Oracle 12 c

  If I use the following command, I should have the backuppiece and the archivelog saved in a folder:

  RMAN > BACKUP database DATA PLUS ARCHIVELOG;

  If I ran this command in 4 different days, which I ended up having 4 folders with different inside files

  I guess that, in these files, I have the data files and the archivelogs

  Now I move these folders to tape, re-cutting the backups and delete expired

  Say that in a month, I need one of these backups if I put a band records and I added start with 'c:\path_of _restored_folder _L', so I added all files in the folder that I restored from tape

  Now, if I try to restore the basis of all is well but when I run the recover, it is missing some archiving logs it says

  If I put all the files for 4 days then he finds the archivelog she needs and pick up without problem

  on this basis I understand that in the folder containing a backuppiece of a specific day there is the newspaper of archive that I needed to recover from the DB, is that true? How can I know if the backups folder I need to replace in order to have all the required log archiving?

  At the moment my DB retrieves only if I handed out the Ribbon last backup folder, if I handed out the previous, it restores, but is not recover

  Also I have this configuration of the oracle recovery 3 days window maintains backups in order to be able to restore and recover the last 3 days and he simply deletes all obsolete if the FRA is full

  I tried earlier to set up the window of 3 days as a test recovery

  I ran a few backups and after that I ran the 5th FRA leak out of space and the backup fails

  I expect rman to remove the old backup and make way for a new that I have 5 backuppiece and the FRA is full, why he not do?

  Thank you

  The default behavior of RECOVER is to make a full recovery - right until the transactions today.  So it must all archivelogs.

  If you want to restore and recover to a point in time, use the SET clause to THAT specify a sequence of the newspaper or time or SNA.  Oracle will then not get beyond that point in time - that is to say he will not seek further archiving logs.

  (Ideally, when you restore an old backup, I also begins to restore the old controlfile, then using this controlfile).

  If you use the FRA in this way

  a. set db_recovery_file_dest_size and db_recovery_file_dest

  b. * not * used a FORMAT clause in the BACKUP command

  Oracle will recognize all backups in the FRA (you can check by querying V$ FLASH_RECOVERY_AREA_USAGE before and after the backup).

  In this case, Oracle can and will automatically purge outdated backups - that is to say any backup older than the retention period, provided that there is at least a L0 or backup complete closest to the retention period.  You should see messages to this effect in the alert of the instance database log file.

  Hemant K Collette

• Oracle 10.2.0.3 move an rman backup

  We do a rman level 0 every weekend and level 1 every day. I want to keep away the last copies of weeks on another hard drive to save space. I guess that is done from rman? If so, can what commands I use?

  jdaniel1127 wrote:

  Currently have 10.2.0.3 on Windows Server 2008...

  I have configured the channels as follows:

  channel 1 device type disk format='f:\rman_backups\rman%u.bus' (this corresponds to the current files on g:\backups\)

  Channel 2 device type disk format='f:\archive_logs\arc%s%r.%t' (this corresponds to the current archive on g:\oracle\ora10gtemp\database\)

  I have 11 files in the backup (3 to 7/29, 1 for 7/30, 3 for 8/2, 2 for the 8/7 and 8/8 2) 8/7 and 8/8 are incremental...

  I had 80 files from 2012 until today of the archive logs (10 M each...)

  I'm moving all archive logs and files backup of G: that 652 g free to F: which has 4.6 free...

  RMAN > backup backupset disk device;

  From backup 8 August 14

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: sid = 146 devtype = DISK

  entry count = 4 = 787850080 = July 5, 12 creation_time stamp backupset

  channel ORA_DISK_1: starting piece 1 to August 8, 14

  channel ORA_DISK_1: backup G:\ORACLE\ORA10GTEMP\DATABASE\C-4285664692-2012 piece

  0705-00

  room handle=F:\RMAN_BACKUPS\RMAN04NFB8R0_1_4.BUS comment = NONE

  channel ORA_DISK_1: finished piece 1 to August 8, 14

  channel ORA_DISK_1: complete set of backups, time: 00:00:03

  entry count = 5 stamp = 787850384 = July 5, 12 creation_time backupset

  channel ORA_DISK_1: starting piece 1 to August 8, 14

  channel ORA_DISK_1: backup G:\BACKUPS\RMAN05NFB94G_1_1.BUS piece

  RMAN-00571: ===========================================================

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

  RMAN-00571: ===========================================================

  RMAN-03009: failure of the backup command on the channel ORA_DISK_1 at 11:40 08/08/2014:

  17

  ORA-19505: impossible to identify the file 'G:\BACKUPS\RMAN05NFB94G_1_1.BUS '.

  ORA-27041: could not open the file

  04002 - OSD: could not open the file

  S/O-error: (OS 2) the system cannot find the file specified.

  ORA-19600: input file is backup piece (G:\BACKUPS\RMAN05NFB94G_1_1.BUS)

  ORA-19601: output file is backup piece (F:\RMAN_BACKUPS\RMAN05NFB94G_1_2.BUS)

  It seems that your element of backup G:\BACKUPS\RMAN05NFB94G_1_1.BUS gone "bath of crowd".  In other words, a person removed at the OS level... and so rman always think it is, but finds then this isn't.