RMAN backup - space exhausted

Similar Questions

• RMAN backup space free after compression subpartition

  Hello!
  
  I have a strange situation. I have a table with partitions of range and 8 subpartitions. I compressed subpartitions according to this trick:
  [http://husnusensoy.wordpress.com/2008/01/23/compressing-subpartition-segments/]
  with excellent results. I released half of the disk space. But written rman still the same number of bytes to bands. Can someone explain why?
  
  My Oracle is company 10.2.0.4@itanium with HP - UX 11.23.
  
  Thans in advance.
  
  Table structure:

  CREATE TABLE tab
  (
    STREAM_ID                     NUMBER(38)      NOT NULL,
    STREAMROW                     NUMBER(38)      NOT NULL,
    EVENTBEGINDATE                DATE
    [...]
  )
  TABLESPACE DATA
  PCTUSED    0
  PCTFREE    10
  INITRANS   1
  MAXTRANS   255
  LOGGING
  PARTITION BY RANGE (EVENTBEGINDATE)
  SUBPARTITION BY HASH (STREAM_ID, STREAMROW)
  (  
    PARTITION P_MIN VALUES LESS THAN (TO_DATE(' 2006-11-01 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
      NOLOGGING
      COMPRESS
      TABLESPACE TYTAN_UDATA
      PCTFREE    0
      INITRANS   1
      MAXTRANS   255
      STORAGE    (
                  BUFFER_POOL      DEFAULT
                 )
      SUBPARTITIONS 8 STORE IN (DATA,DATA,UDATA,DATA,DATA,DATA,DATA,DATA),  
    PARTITION P_2006_11_01 VALUES LESS THAN (TO_DATE(' 2006-11-02 00:00:00', 'SYYYY-MM-DD HH24:MI:SS', 'NLS_CALENDAR=GREGORIAN'))
      NOLOGGING
      COMPRESS
      TABLESPACE DATA
      PCTFREE    0
      INITRANS   1
      MAXTRANS   255
      STORAGE    (
                  BUFFER_POOL      DEFAULT
                 )
  [...]

  It is a documented feature. Only unused blocks of RMAN backups if:

  -you are backing up to disk (NOT) - or
  -blocks were never used by any measure

  See here for more details: http://oradbatips.blogspot.com/2010/02/tip-86-what-it-is-missed-when-rman.html

  --
  Ronny Egner
  My Blog: http://blog.ronnyegner-consulting.de

  Published by: Ronny Egner on June 16, 2010 16:07

• 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

• 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

• RMAN backup command gets failure

  
  

  Hello;

  
  

  Merry Christmas to all
  

  
  

  It's the test database (10.2.0.1) on RHEL 4.8, Rman backup command was already.

  I don't understand why I got the error? What was the reason?
  

  
  

  RMAN > backup the database archivelog;

  From backup 25 December 14

  Current archived log

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

  allocated channel: ORA_DISK_1

  channel ORA_DISK_1: sid = 141 devtype = DISK

  channel ORA_DISK_1: from archive newspaper backupset

  channel ORA_DISK_1: specification of archive log backup set

  archive log entry thread = 1 sequence 2 recid = 1 stamp = 867230647 =

  archive log entry thread = 1 = 3 = 2 = 867233039 stamp recid sequence

  archive log entry thread = 1 sequence 4 recid = 3 = 867233044 stamp =

  archive log entry thread = 1 sequence 5 recid = 4 = 867233122 stamp =

  archive log entry thread = 1 sequence = recid 6 = 5 = 867233128 stamp

  archive log entry thread = 1 sequence = recid 7 = 6 = 867233214 stamp

  archive log entry thread = 1 sequence 8 recid = 7 = 867233453 stamp =

  archive log entry thread = 1 sequence 9 recid = 8 = 867233493 stamp =

  archive log entry thread = 1 sequence 10 recid = 9 = 867233559 stamp =

  channel ORA_DISK_1: starting piece 1 to December 25, 14

  channel ORA_DISK_1: finished piece 1 to December 25, 14

  piece handle=/home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/ORCL/backupset/2014_12_25/o1_mf_annnn_TAG20141225T101241_b9q5g4jo_.bkp tag = TAG20141225T101241 comment = NONE

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

  Backup over at December 25, 14

  From backup 25 December 14

  using channel ORA_DISK_1

  channel ORA_DISK_1: from full datafile backupset

  channel ORA_DISK_1: specifying datafile (s) in backupset

  input datafile fno = 00001 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/system01.dbf

  input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/sysaux01.dbf 00003

  input datafile fno = 00005 name=/home/oracle/oracle/product/10.2.0/oradata/orcl/example01.dbf

  input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/undotbs01.dbf 00002

  input datafile fno = name=/home/oracle/oracle/product/10.2.0/oradata/orcl/users01.dbf 00004

  channel ORA_DISK_1: starting piece 1 to December 25, 14

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

  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.

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

  RMAN-03002: failure of command thus backup archivelog to 2014/12/25 10:13:54

  ORA-19502: write error on file ' / home/oracle/oracle/product/10.2.0/db_1/flash_recovery_area/ORCL/backupset/2014_12_25/o1_mf_nnndf_TAG20141225T101301_%u_.bkp ', blockno 8833 (blocksize = 8192)

  ORA-27072: IO file error

  Linux error: 2: no such file or directory

  Additional information: 4

  Additional information: 8833

  Additional information: 348160

  > > Physical directories are available

  $ pwd

  /Home/Oracle/Oracle/product/10.2.0/Db_1/flash_recovery_area/ORCL

  [oracle@RAC1 ORCL] $ ls-l

  total 12

  drwxr-x - 3 oracle oinstall 4096 Dec 25 09:24 archivelog

  drwxr-x - 3 oracle oinstall 4096 Dec 25 09:18 backupset

  drwxr-x - 2 oracle oinstall 4096 Dec 24 17:16 onlinelog

  ORA-19502: write error on file ' / home/oracle/oracle/flash_recovery_area/ORCL/backupset/2014_12_26/o1_mf_nnndf_TAG20141226T233412_%u_.bkp ', blockno 37505 (blocks ize = 8192)

  I don't understand why is it taking over as "%u" rather than place a unique value for him. Is it the file with System FRA has enough space?

  DF h/home/oracle/oracle/flash_recovery_area/ORCL/backupset.

  Kind regards

  Shivananda

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

• Hot RMAN backup fails every time in R12.

  Hi experts,

  Please suggest me that I have to plan rman backup hot. I have "write" command to perform hot backup. When I take backup hot of 1st time the backup completed successfully. but when I run the same command resume backup for the second day. it is impossible to give space issue I havhot e calendar for daily use rman backup.

  I had to take the backup hot daily and I want backup overwrite the backup file according to the daily backup.

  Please suggest me what I need to make changes in the configuration of rman and the rman command.

  OS - réhèl 5.6

  Database - 11.1

  EBS - r12.3

  configuration of RMAN:

  RMAN > show all.
  
  Database with db_unique_name UAT RMAN configuration parameters are:
  CONFIGURE RETENTION POLICY TO RECOVERY OF 7-DAY WINDOW;
  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;
  CONFIGURE BACKUP ARCHIVELOG FOR DEVICE TYPE DISK TO 1;
  CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT ' / d06/UAT/rman_hot_backup/Backup_daily%d_DB_%u_%s_%p';
  CONFIGURE MAXSETSIZE TO UNLIMITED; # by default
  CONFIGURE ENCRYPTION OF DATABASE # by default
  CONFIGURE THE ENCRYPTION ALGORITHM "AES128"; # by default
  CONFIGURE COMPRESSION ALGORITHM 'BZIP2 '; # by default
  CONFIGURE THE NONE ARCHIVELOG DELETION POLICY; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' / d06/UAT/db/tech_st/11.1.0/dbs/snapcf_UAT.f'; # by default
  
  RMAN >

  
  

  ##############################################################################################################

  
  

  RMAN command that I used to make hot extra strength 0 cumulative backup.

  
  RMAN > run
  {
  allocate channels c1 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
  allocate channel c2 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
  allocate channels c3 device type disk format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
  allocate channel c4 device type disc format ' / d06/UAT/rman_hot_backup/Daily_backup%d_DB_%u_%s_%p_%c';
  cumulative incremental database backup level 1 more archivelog;
  output channel c1;
  output channel c2.
  output channel c3.
  output channel c4.
  }
  

  If something bad in the configuration of rman and my order please suggest me to take the backup hot every day with success.

  
  

  concerning

  pritesh Rodriguez
  

  Hi Pritesh, thanks for the update. You can mark this thread as answered if your questions have been answered. cordially Karan

• Error of RMAN backup full

  Hi all
  
  I take a daily ful backup DB backup directly on the Strip.
  
  Due to a problem yesterday I deleted 2 days old files to archive my server.
  Today, I got following error message in my log RMAN backup.
  
  I'm surprised, how is it, RMAN are looking for an old file to archive, when I take a full backup.
  
  Can someone answer me above concern
  
  My version of DB is 11.2.0.3
  OPERATING SYSTEM: AIX 6.1
  
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03002: failure of the backup command to the 2013/05/29 04:28:54
  RMAN-06059: expected found archived newspaper, loss of archived newspaper compromised recoverability
  ORA-19625: error identification of file /prdarch/prdarch1/PALLMO_83504_696657779.arc
  ORA-27037: unable to get file status
  IBM AIX RISC System/6000 error: 2: a file or a directory in the path name does not exist.
  Additional information: 3
  
  The script that is used for the backup:
  run
  {
  allocate channel t1 type 'sbt_tape' parms 'ENV=(TDPO_OPTFILE=/usr/tivoli/tsm/client/oracle/bin64/tdpo.opt) ';
  SQL 'alter system archive log current';
  overlap archivelog all;
  backup
  filesperset 5
  (database) format "df_ % %%p s_ t_";
  SQL 'alter system archive log current';
  ARCHIVELOG backup all the format "af_ % %%p s_ t_";
  output channel t1;
  }
  
  
  Thanks in advnace

  any backup archivelog

  The BACKUP ARCHIVELOG command is independent of the BACKUP DATABASE command.
  This command waits all archivelogs known are available and can be backed up. In fact, your backup logs should show the same old archivelogs (most recent) being backed up every day!

  If you use non-RMAN commands to purge the archivelogs, RMAN knows not the archivelogs aren't available. He'll wait although they are present. You must run

  CROSSCHECK ARCHIVELOG ALL;
  DELETE EXPIRED ARCHIVELOG ALL;
  

  for RMAN to identify them as having been purged and remove them from its "list of the archivelogs expected."

  If you simply, have BACKUP ARCHIVELOG ALL and not to operate the ARCHIVELOG DELETE of RMAN, how do you maintain the archivelog file system space?

  How long have you been running this backup script? How were you purge archivelogs earlier?

  Hemant K Collette

• Remove all AVAILABLE by RMAN command valid RMAN backup

  Hello
  We take RMAN full backup to disk every day. But for now, we don't have enough space on the RMAN backup media. If we want to delete all AVAILABLE by RMAN command valid RMAN backup.
  
  Please guide to remove all AVAILABLE by RMAN command valid RMAN backup.
  -Thank you
  
  Published by: Fazlul Kabir Mahfuz on May 13, 2013 11:06

  If you haven't tried:
  DELETE THE BACKUP
  ?

  I suggest that you run also
  BACKUP DUPLICATION
  which will list the safeguards that are supposed to be present on the drive, but not found. You can then delete those with
  DELETE EXPIRED BACKUP

  Hemant K Collette

• RMAN backup Linux drivers shared on windows 2008 Server.

  Hi all
  
  I want to know is - it possible to rman backup to shared disk windows 2008 for a database of runnig under Linux.
  
  I tried it and getting rman-03002 followed by ORA-19504, error Ora-27040 and linux-x86_64.
  
  I used the following command to mount my windows share
  Mount-t cifs/o username = administrator, password = "XXXXXX" //172.16.1.50/files/MNT
  
  
  Concerning
  Nidsh
  
  Edited by: 883687 August 15, 2012 23:08

  Hello;

  It should be possible. The ORA-27040 is

  "O/S-Error: (OS 3) The system cannot find the path specified."
  

  and the second error ORA-27040 seems to be an effect of the first.

   File create error, unable to create file
  

  Could be a permissions problem, so if you can mount the disk space windows, but cannot write to it (yet)

  There is a note of support Oracle that covers this:

  ORA-19504 ORA-27040 during Rman backup in a Directory Windows mounted under Linux [464267.1 ID]

  Which confirms, in my view, the answer is Yes.

  Further that:

  RMAN fail with ORA-19504 ORA-27040 when backup remote server linux [726858.1 ID] Windows Mount Volume

  Best regards

  mseberg

  Published by: mseberg on August 16, 2012 04:33

• 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

• Fusion RMAN backup

  posted here. Can you please take a look?
  
  RMAN backup fusion

  Hello
  There are 2 types of rman backup
  (1) Backupset
  Copy of image 2)
  (1) Backupset: this is the default used block rman backup, it will be having the data used for this will occupy less space on disk or on tape.

  Copy of image 2): is the physical copy of the data file, here it consists of data used and unused, similar to the hot backup.

  It will be useful.
  Please mark this thread as a response if you feel that your request is answererd for the other OPs can take advantage.

  Best regards

  Rafi.

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