Deletion of backups of level 1 and archive logs

Similar Questions

• database backup and archiving log

  Hi all
  
  I have two scripts:
  
  Full_db_backup.sh
  ARCHIVELOG.sh
  
  Full_db_backup.sh I have the below
  

  backup incremental level 0 device type disk tag testTAG database plus archivelog; 

  in Archivelog.sh
  

  BACKUP ARCHIVELOG ALL tag  testTAGArch not backed up 2 times; 

  My question;
  
  can I have the below for the backup of the database?
  

  backup incremental level 0 device type disk tag testTAG database plus archivelog not backed up 2 times; 

  and if so the 'saved 2 times; not' it's only for the archivelog? or not 2 times for archivelog backups of database backed up?
  
  Kind regards

  NB wrote:
  Thank you

  I will still have the below question about backup of control file that you mentioned in the below:

  Other point:
  As you are making copy of your backupset using a padronized tag, I suggest you include current controlfile on your backup, because Autobackup have a default tag and we cannot change it.
  
  So I suggest you do this:
  
  backup incremental level 0 database INCLUDE CURRENT CONTROLFILE  tag 'my_backup' plus archivelog;
  

  I can't do: Configure auto backup device type disc format control in two different places?
  one on my site of the archive and the other at FRA?
  Currently, I have below:

  Configure the control auto backup disc format of type device to "%f".

  You can create a custom script to run at the end of your backup:
  This query above will create a command to get 2nd copy of your automatic backup;

  The below script check the backup strengthened to FRA on autobackup dir on the last 5 minutes... you can change it as you wish.

  SELECT 'backup backupset from tag '||TAG||' format ''/u01/app/oracle/'||TAG||'%U'';' FROM V$BACKUP_PIECE
  WHERE START_TIME > sysdate - 5 /(24*60) and HANDLE like '+FRA%autobackup%'
  

  Suggestion:
  Disable the automatic backup before making a 2nd automatic backup copy;
  Run the command to make automatic backup
  Enable autobackup after 2 do an automatic backup copy;

• Current archive log has been deleted, how to recover using the previous archive log?

  Hello
  
  My current log sequence #819 and it has been deleted and no other choice to get it back and I have previous newspapers archived with sequences #814 à 818.
  
  When I start my database is to show that the use ' MUST USE RESETLOGS or NORESETLOGS option of database open, then I used the command
  
  SQL > ALTER DATABASE OPEN RESETLOGS;
  ALTER DATABASE OPEN RESETLOGS
  *
  ERROR on line 1:
  ORA-01113: file 1 needs media recovery
  ORA-01110: data file 1: ' E:\APP\ADMINISTRATOR\ORADATA\ORCL\SYSTEM01. DBF'
  
  SQL > alter database recover;
  ALTER database recover
  *
  ERROR on line 1:
  ORA-00283: cool cancelled due to errors
  ORA-01610: recovery using BACKUP CONTROLFILE option must be
  SQL > alter database recovery using backup controlfile;
  change the database recovery using backup controlfile
  *
  ERROR on line 1:
  ORA-00279: change 8433746 September at 15/01/2013 19:51:59 needed to screw 1
  ORA-00289: suggestion:
  E:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\ORCL\ARCHIVELOG\2013_01_16\O1_MF_1_819_
  
  % U_. ARC
  ORA-00280: change 8433746 thread 1 is in sequence #819
  
  now, I don't have the log archiving with 819 sequence, I recover from 818. Please tell me how to do?

  Hello

  1. select * from v$log and see which log file is current. Query v$logfile to check physical file location belonging to current log group.
  2. Take bacup of your curent control file using copy/paste of your OS
  3. Issue following command in mount state
  recover database until cancel using backup controlfile
  4. When it finishes applying available archived logs, still it will ask for the location of archived logs which have not been applied, here provide path of current redo log file you got in first step. Here your recovery will finish after applying current redo log
  5.alter database open resetlogs.
  

  Salman

• With RMAN for backup, but not with the archive logs

  We run a 10.2.0.4 database and the rest 11.2.0.3. All databases are on RHEL 5.7.
  
  Our backups are via RMAN, with the data files, controlfiles and spfile saved to disk, then each day, it is copied off site to a backup server.
  
  My question is around logs archiving and RMAN.
  Our current situation is:
  -We do not save the logs to archive via RMAN. for example: backup of the list of the archivelog all; gives "specification does not match backups in the repository.
  -We set the archive_lag_target so archiving logs is produced every 30 minutes.
  -a cron job running on a remote server runs periodically to synchronize data (rsync server) the directory of archives with a remote control.
  -daily archive logs on the server host are bzip. Purge of these newspapers is scheduled for more than 3 days rman 'window of recovery '.
  
  I'm interested in feedback as to if our strategy around archiving logs is correct or not.
  
  Should we be backup logs archiving via RMAN? Are there potential problems with our approach?
  We just kept our backups in this way the DBA in the past want to see newspapers archived as opposed to it while a backupset.
  
  Curious to know what others are doing.

  Hello

  Welcome to OTN!

  Archivelogs with RMAN backup is a better option. When the archives are supported by RMAN, RMAN would be aware of the backup items which are required at the time of the recovery archives. You don't have to do it manually.

  On the disk space, you can delete the archives once they were saved by RMAN.

  RMAN > delete any backup archivelog entry;

  This supports the archivelogs and then remove the archives from the disk.

  If you have a dataguard configured, you can set the deletion policy 'applied on Eve', which removes the archives as and when they are applied to the database ensures there by the management of disk space again.

  RMAN > configure archivelog political of deletion to applied pending;

• difference between online redolog files and archived log files

  What is the fundamental difference between archived log files and online redo log files? .. .plz keep things simple as m a newbie

  Online redo log:

  Redo online Oracle log files are filled with records of restoration by progression. A record of remake, also called entrance to roll forward, is composed of a group of agents of change, each of which is a description of a change to a single block in the database. Each instance of an Oracle database has an associated online redo log to protect data in case of failure of the instance.

  See here,
  http://download.Oracle.com/docs/CD/B10500_01/server.920/a96521/onlineredo.htm

  Archived redo log:

  Oracle Database allows you to save files to one or more destinations offline newspapers filled with repeat groups, known collectively as the archived redo log. An archived redo log file is a copy of one of the members of a group of redo log filled.

  See here,
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14231/archredo.htm

  Thank you

• Recovery of database of old backup and archive log file complete

  Hi expert Oracle!
  I encountered the problem where my oracle database restore.
  
  In my case:
  -My version of the database: 10.2.0.2
  -J' have a full database backup (01 - Nov)
  -J' have all the archived since (01 - Nov-> 05 - Nov) log file
  -My database down to 05 - Nov with disk error (no data file, not again...).
  -I have no backup RMAN (01 - Nov-> 05 - Nov)
  
  How to restore my database to 05 - Nov?
  
  Thank you

  After you RESTORE the DATABASE,

  Use the VALUE UNTIL to set the Point of recovery to 05 - Nov, and then RECOVER the DATABASE
  OR
  Use the SQL command "RECOVER database with the HELP of BACKUP CONTROLFILE until CANCEL" that will keep asking 'future' ArchiveLogs backup.

  Hemant K Collette

• How the level 0 and level 1 backups are related?

  Version: 11 g
  
  I was going through the scripts in the post, two issues related to the RETENTION STRATEGY
  
  
  When you have a differential incremental backup strategy and when you run scripts to backup of level 1 and level 0 via cronjobs different from Sunday to Saturday, during recovery, how RMAN will identify all these level 1 backups and backup of level 0 parent as a single unit? In level 0, and its backup scripts later level 1, I do not see a clause that links the level 0 backup and its subsequent backups level 1?

  Hi Steve_74,

  How RMAN will identify all these level 1 backups and backup of level 0 parent as a single unit?

  Information used during a restore comes the controlfile.

  Example of
  Select backup, INCREMENTAL_LEVEL
  v $ backup_set
  /
  Will determine the backup set level 0 necessary depending on your clause of restore

  Select INCREMENTAL_LEVEL, INCREMENTAL_CHANGE #, CHECKPOINT_CHANGE #.
  v $ BACKUP_DATAFILE
  When file # = 1
  /
  Will determine what (s) to apply to the datafile 1 according to your restoration clause.

  Kind regards

  Tycho

  Edited by: tychos on November 1st, 2009 01:51

• Block Media Recovery and RMAN backup incremental level 1

  Hello
  
  I read somewhere that block Media Recovery will not work if a database is backed up with 1 incremental rman. Is this true and if so is there a work around?
  I can't find it in the documentation of oralce.
  
  Concerning
  Me

  Hello

  Yes you are right, for the recovery block media, you must have full rman backup. Incremental backups are not used by block
  media recovery. Only full backups and archived logs are used.

  See this doc on part III

  http://download-UK.Oracle.com/docs/CD/B19306_01/backup.102/b14191/TOC.htm

  concerning

  Jafar

  Published by: jerome on October 22, 2008 19:51

• 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

• Archive log backup Question

  Hi all - I am trying to reach a log backup strategy archive. So far, I did the following to mux the archiver process in two different places to allow potential disaster scenarios:
  
  
  1. set log_archive_dest_1 as the location of the FRA:
  
  ALTER SYSTEM SET LOG_ARCHIVE_DEST_1 = 'LOCATION = USE_DB_RECOVERY_FILE_DEST';
  
  2. change the log_archive_dest_2 to be an external location:
  
  ALTER SYSTEM SET LOG_ARCHIVE_DEST_1 = ' LOCATION = ' G:\Backup\ArchiveLogs;
  
  3. ensure to that the LOG_ARCHIVE_DEST_STATE_n for the two sites above is set to enable. It is the default property, and must already be defined.
  
  4. to take effect, a log switch must take place. This can be implemented by using the RMAN backup command:
  
  BACKUP DATABASE MORE ARCHIVELOG;
  
  
  Now that I have the archiver written in two different places, I want to back up the files also in two different places for the same reasons. I assume that I can do it in EM and schedule being new to Oracle but custom task I'm not sure how to go on this subject, and the wizard does not allow me to backup to a location.
  
  Can help or advise if what I'm doing is perhaps not common practice?
  
  Thank you very much

  Kwisatz78 wrote:
  Sorru Orawiss I'm still a bit thick here but how I'm doing backup in two places. For example if I use your script.

  RUN {}
  ALLOCATE CHANNEL d1 DEVICE TYPE DISK FORMAT ' / u01/backups/%U';
  ALLOCATE CHANNEL d2 DEVICE TYPE DISK FORMAT ' / u02/backups/%U';
  BACKUP DATABASE MORE ARCHIVELOG;
  OUTPUT CHANNEL;
  }

  I change the /u01/backups/%you to some thing like + DBFLASH_SOA and keep the auto manage the appearance of the FRA?

  Thank you

  See below; Only Autobackup spfile + controlfile is considered to be accompanied in the FRA. Because I choose CONFIGURE CONTROLFILE AUTOBACKUP.

  If you choose to specify the locations of your RMAN scripts, the FRA's automatic space management will not be enabled for these backups.

  So in my example, the format of the backup command clause sends the backup the physical location "/ home/oracle/backups/fra" (not the FRA) and ' / home/oracle/backup. There is no way to specify the FRA as the destination in a format clause, so if you format in your backup, by definition statement, you do not send something of the FRA.

  SQL> show parameter db_recovery
  
  NAME                         TYPE      VALUE
  ------------------------------------ ----------- ------------------------------
  db_recovery_file_dest               string      /home/oracle/backups/fra
  db_recovery_file_dest_size          big integer 4G
  SQL> 
  
  SQL> select  SUM(NUMBER_OF_FILES) from v$flash_recovery_area_usage;
  
   SUM(NUMBER_OF_FILES)
  --------------------
         33
  
  SQL> 
  
  RMAN> show all;
  
  using target database control file instead of recovery catalog
  RMAN configuration parameters for database with db_unique_name ORAWISS are:
  CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
  CONFIGURE BACKUP OPTIMIZATION OFF; # default
  CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
  CONFIGURE CONTROLFILE AUTOBACKUP ON;
  CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
  CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET PARALLELISM 2;
  CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
  CONFIGURE MAXSETSIZE TO UNLIMITED; # default
  CONFIGURE ENCRYPTION FOR DATABASE ON;
  CONFIGURE ENCRYPTION ALGORITHM 'AES192';
  CONFIGURE COMPRESSION ALGORITHM 'medium' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
  CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/home/oracle/backups/scncf/sncf.ora';
  
  RMAN> 
  
  RMAN> run{
     sql 'alter system set encryption wallet open identified by "wissem"';
     ALLOCATE CHANNEL d1 DEVICE TYPE DISK FORMAT '/home/oracle/backups/%U';
     ALLOCATE CHANNEL d2 DEVICE TYPE DISK FORMAT '/home/oracle/backups/fra/%U';
     BACKUP DATABASE PLUS ARCHIVELOG;
     RELEASE CHANNEL d1;
     RELEASE CHANNEL d2;
   }2> 3> 4> 5> 6> 7> 8> 
  
  sql statement: alter system set encryption wallet open identified by "wissem"
  
  allocated channel: d1
  channel d1: SID=410 device type=DISK
  
  allocated channel: d2
  channel d2: SID=28 device type=DISK
  
  Starting backup at 01-JUN-11
  current log archived
  channel d1: starting compressed archived log backup set
  channel d1: specifying archived log(s) in backup set
  input archived log thread=1 sequence=169 RECID=271 STAMP=752254789
  input archived log thread=1 sequence=170 RECID=272 STAMP=752525448
  input archived log thread=1 sequence=171 RECID=275 STAMP=752531841
  channel d1: starting piece 1 at 01-JUN-11
  channel d2: starting compressed archived log backup set
  channel d2: specifying archived log(s) in backup set
  input archived log thread=1 sequence=172 RECID=277 STAMP=752684381
  input archived log thread=1 sequence=173 RECID=278 STAMP=752684468
  channel d2: starting piece 1 at 01-JUN-11
  channel d2: finished piece 1 at 01-JUN-11
  piece handle=/home/oracle/backups/fra/2qmdq3dk_1_1 tag=TAG20110601T150108 comment=NONE
  channel d2: backup set complete, elapsed time: 00:00:03
  channel d1: finished piece 1 at 01-JUN-11
  piece handle=/home/oracle/backups/2pmdq3dk_1_1 tag=TAG20110601T150108 comment=NONE
  channel d1: backup set complete, elapsed time: 00:00:07
  Finished backup at 01-JUN-11
  
  Starting backup at 01-JUN-11
  channel d1: starting compressed full datafile backup set
  channel d1: specifying datafile(s) in backup set
  input datafile file number=00003 name=/home/oracle/app/oracle/oradata/ORAWISS/undotbs01.dbf
  input datafile file number=00002 name=/home/oracle/app/oracle/oradata/ORAWISS/sysaux01.dbf
  input datafile file number=00004 name=/home/oracle/app/oracle/oradata/ORAWISS/users01.dbf
  input datafile file number=00008 name=/home/oracle/app/oracle/oradata/ORAWISS/mgmt_ad4j.dbf
  channel d1: starting piece 1 at 01-JUN-11
  channel d2: starting compressed full datafile backup set
  channel d2: specifying datafile(s) in backup set
  input datafile file number=00001 name=/home/oracle/app/oracle/oradata/ORAWISS/system01.dbf
  input datafile file number=00007 name=/home/oracle/app/oracle/oradata/ORAWISS/mgmt.dbf
  input datafile file number=00005 name=/home/oracle/app/oracle/oradata/ORAWISS/example01.dbf
  input datafile file number=00006 name=/home/oracle/app/oracle/oradata/ORAWISS/mgmt_ecm_depot1.dbf
  input datafile file number=00009 name=/home/oracle/app/oracle/oradata/ORAWISS/fb_data_archive.dbf
  channel d2: starting piece 1 at 01-JUN-11
  
  channel d1: finished piece 1 at 01-JUN-11
  piece handle=/home/oracle/backups/2rmdq3ds_1_1 tag=TAG20110601T150116 comment=NONE
  channel d1: backup set complete, elapsed time: 00:00:45
  channel d2: finished piece 1 at 01-JUN-11
  piece handle=/home/oracle/backups/fra/2smdq3ds_1_1 tag=TAG20110601T150116 comment=NONE
  channel d2: backup set complete, elapsed time: 00:01:15
  Finished backup at 01-JUN-11
  
  Starting backup at 01-JUN-11
  current log archived
  channel d1: starting compressed archived log backup set
  channel d1: specifying archived log(s) in backup set
  input archived log thread=1 sequence=174 RECID=280 STAMP=752684552
  channel d1: starting piece 1 at 01-JUN-11
  channel d1: finished piece 1 at 01-JUN-11
  piece handle=/home/oracle/backups/2tmdq3g8_1_1 tag=TAG20110601T150232 comment=NONE
  channel d1: backup set complete, elapsed time: 00:00:01
  Finished backup at 01-JUN-11
  
  Starting Control File and SPFILE Autobackup at 01-JUN-11
  piece handle=/home/oracle/backups/fra/ORAWISS/autobackup/2011_06_01/o1_mf_s_752684554_6ydg3bww_.bkp comment=NONE
  Finished Control File and SPFILE Autobackup at 01-JUN-11
  
  released channel: d1
  
  released channel: d2
  
  RMAN> 
  
  [oracle@wissem ~]$ rlsqlplus 
  
  SQL*Plus: Release 11.2.0.1.0 Production on Wed Jun 1 15:03:02 2011
  
  Copyright (c) 1982, 2009, Oracle.  All rights reserved.
  
  Enter user-name: sys as sysdba
  Enter password: 
  
  Connected to:
  Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
  With the Partitioning, OLAP, Data Mining and Real Application Testing options
  
  SQL> select  SUM(NUMBER_OF_FILES) from v$flash_recovery_area_usage;
  
  SUM(NUMBER_OF_FILES)
   --------------------
              34
  
  [oracle@wissem ~]$ ls -rtl /home/oracle/backups/
  total 113424
  drwxr-xr-x 2 oracle oinstall      4096 Jan 15 00:07 arch
  drwxr-xr-x 2 oracle oinstall      4096 Jan 15 00:07 scncf
  -rw-r----- 1 oracle oinstall  11566080 Jun  1 15:01 2pmdq3dk_1_1
  drwxr-xr-x 3 oracle oinstall      4096 Jun  1 15:01 fra
  -rw-r----- 1 oracle oinstall 104546304 Jun  1 15:01 2rmdq3ds_1_1
  -rw-r----- 1 oracle oinstall     15872 Jun  1 15:02 2tmdq3g8_1_1
  [oracle@wissem ~]$ ls -rtl /home/oracle/backups/fra
  total 242424
  drwxr-x--- 5 oracle oinstall      4096 Jan 21 11:04 ORAWISS
  -rw-r----- 1 oracle oinstall   9469952 Jun  1 15:01 2qmdq3dk_1_1
  -rw-r----- 1 oracle oinstall 238764032 Jun  1 15:02 2smdq3ds_1_1
  [oracle@wissem ~]$ 
  

• RMAN-03009 and ORA-01858 everything by backing up archiving logs

  Hello!
  
  Since today, I get the above errors to backup the fra tape archiving logs. I tried the following: error ORA-01858 in RMAN during backup backupset format ' / test/rman/%U'
  If I manually do the backup for a client, it works!
  
  environment:
  Server: windows 2008 standard server
  Oracle: 10.2.0.4.0
  
  configuration of RMAN:
  CONFIGURE RETENTION POLICY TO THE 5 DAY RECOVERY 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; # 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 THE NONE ARCHIVELOG DELETION POLICY; # by default
  CONFIGURE SNAPSHOT CONTROLFILE NAME TO ' D:\ORACLE\PRODUCT\10.2.0\DB_1\DATABASE\SNCFAPEX. ORA'; # by default
  
  Error log:
  Recovery Manager: Release 10.2.0.4.0 - Production on Thu Oct 1 04:30 2009
  
  Copyright (c) 1982, 2007, Oracle. All rights reserved.
  
  connected to target database: APEX (DBID = 1331326226)
  connected to the recovery catalog database
  
  RMAN > sql 'alter system archive log current;
  2 > run {}
  3 > #-> drive backup
  4 > backup archivelog all;
  5 > # FRA-> band
  6 > allocate channel ch1 type 'sbt_tape '.
  7 > PARMS = "BLKSIZE = 262144, ENV = (CvClientName = ora5neu, CvInstanceName = Instance001)"; "
  8 > save the recovery area.
  {9 >}
  10 >
  SQL statement: alter system archive log current
  
  From backup 1st October 09
  Current archived log
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid = devtype 81 = DISK
  skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_09_10\O1_MF_1_2720_5BKO9BOL_. ARC; already saved 1 time
  ...
  skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_10_01\O1_MF_1_2981_5D7PZDXX_. ARC; already saved 1 time
  channel ORA_DISK_1: from archive newspaper backupset
  channel ORA_DISK_1: specification of archive log backup set
  archive log entry thread = 1 sequence = 2733 recid = 2733 stamp = 697286083
  archive log entry thread = 1 sequence = 2734 recid = 2734 stamp = 697293002
  archive log entry thread = 1 sequence = 2735 recid = 2735 stamp = 697293004
  archive log entry thread = 1 sequence = 2856 recid = 2856 stamp = 698142602
  archive log entry thread = 1 sequence = 2857 recid = 2857 stamp = 698142603
  archive log entry thread = 1 sequence = 2982 recid = 2982 stamp = 699078603
  archive log entry thread = 1 sequence = 2983 recid = 2983 stamp = 699078605
  channel ORA_DISK_1: starting piece 1 to October 1 09
  channel ORA_DISK_1: finished piece 1 to October 1 09
  piece handle = D:\FRA\APEX\BACKUPSET\2009_10_01\O1_MF_ANNNN_TAG20091001T043006_5D8520K4_. Tag BKP = comment TAG20091001T043006 = NONE
  channel ORA_DISK_1: complete set of backups, time: 00:00:03
  Backup finished on 1st October 09
  
  From control file and SPFILE Autobackup 1st October 09
  piece handle = D:\FRA\APEX\AUTOBACKUP\2009_10_01\O1_MF_S_699078626_5D8522W8_. Comment BKP = NONE
  File control finished and SPFILE Autobackup to on 1 October 09
  
  output channel: ORA_DISK_1
  allocated channel: ch1
  channel ch1: sid = 81 = SBT_TAPE devtype
  channel ch1: CommVault Systems for Oracle: Version 7.0.0 (BUILD76)
  
  From backup 1st October 09
  specification does not match any data file copy in the repository
  skip the log file archive D:\FRA\APEX\ARCHIVELOG\2009_09_10\O1_MF_1_2720_5BKO9BOL_. ARC; already saved 4 times
  ...
  jump key 5203 backupset; already saved 1 time
  channel ch1: from archive newspaper backupset
  channel ch1: specification of archive log backup set
  archive log entry thread = 1 sequence = 2982 recid = 2982 stamp = 699078603
  archive log entry thread = 1 sequence = 2983 recid = 2983 stamp = 699078605
  channel ch1: starting piece 1 to October 1 09
  channel ch1: finished piece 1 to October 1 09
  piece handle = i2kqm5vv_1_1 tag = comment TAG20091001T043031 = API 2.0, MMS Version 7.0.0.76 Version
  channel ch1: complete set of backups, time: 00:00:16
  entry count = 4670 stamp = 699064230 = creation_time backupset 1st October 09
  channel ch1: starting piece 1 to October 1 09
  RMAN-03009: failure of the backup command on channel ch1 at 2009-10-01 04:31:19
  ORA-01858: a non-digit character was found here where was waiting for a digital
  continue other job steps, not a not working will not re-run
  entry count = 4672 stamp = 699078622 = creation_time backupset 1st October 09
  channel ch1: starting piece 1 to October 1 09
  channel ch1: backup D:\FRA\APEX\BACKUPSET\2009_10_01\O1_MF_ANNNN_TAG20091001T043006_5D8520K4_ piece. BKP
  piece handle = i0kqm5uu_1_2 comment = API Version 2.0, Version MMS 7.0.0.76
  channel ch1: finished piece 1 to October 1 09
  channel ch1: complete set of backups, time: 00:00:07
  entry count = 4673 stamp = 699078626 = creation_time backupset 1st October 09
  channel ch1: starting piece 1 to October 1 09
  output channel: ch1
  RMAN-00571: ===========================================================
  RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =.
  RMAN-00571: ===========================================================
  RMAN-03009: failure of the backup command on channel ch1 at 01/10/2009 04:31:35
  ORA-01858: a non-digit character was found here where was waiting for a digital
  
  Complete recovery manager.
  
  Thanks for your help!
  
  Ciao,.
  Christian

  See my note of the Support of Oracle:

  Subject: RMAN backup fails with RMAN-03009 ORA-01858 ORA-01861
  DOC - ID: 744047.1 Type: PROBLEM
  Modification date: 20 March 2009 status: MODERATE

  This could be a NLS_DATE_FORMAT / NLS_LANG questioned.

• "BACKUP RECOVERY AREA DESTINATION" and several channels

  Hello

  I'm on 11 GR 2.

  I use the feature OF "< specific directory >" DESTINATION of the order of CONSERVATION RECOVERY AREA

  staging the backup, my CRF, a few hours earlier. I wish

  1 / to be able to compress this backup in my <>directory (my regular backup to the FRA is * not *)

  Tablet!) ;

  2 / and to parallelize this staging.

  Here http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsubcl018.htm#CIHBDIGE

  at some point, they say that "this paragraph, when it is used with the BACKUP RECOVERY AREA , allows.

  allowing you to designate a drive as the location channel': How do you understand this? Do you want that he woud allow you

  to specify things like

  Run {}

  ALLOCATE CHANNEL c1 DEVICE TYPE disk FORMAT ' / usr/oracle/FRAstaging ' MAXPIECESIZE 100 G;

  TYPE of DEVICE of c2 ALLOCATE CHANNEL FORMAT drive "/ usr/oracle/FRAstaging ' MAXPIECESIZE 100 G;

  recovery zone backup destination c1;

  recovery zone backup destination c2;

  }

  or should I rather do something like:

  Run {}

  TYPE of DEVICE of c1 ALLOCATE CHANNEL MAXPIECESIZE 100 G drive.

  TYPE of DEVICE of c2 ALLOCATE CHANNEL MAXPIECESIZE 100 G drive.

  recovery zone backup destination "/ usr/oracle/FRAstaging";

  }

  or simply? :

  Run {}

  TYPE of DEVICE of c1 ALLOCATE CHANNEL MAXPIECESIZE 100 G drive.

  TYPE of DEVICE of c2 ALLOCATE CHANNEL MAXPIECESIZE 100 G drive.

  backup recovery area;

  }

  Has anyone tried to stage his FRA on some directory of operating system or backup tape?

  Which of the above syntax is correct? Any idea?

  Thank you very much!

  Kind regards

  SEB

  Hello

  The correct syntax is the second. Take a look:

  RMAN> run {
  2>  ALLOCATE CHANNEL c1 DEVICE TYPE disk MAXPIECESIZE 1G;
  3>  ALLOCATE CHANNEL c2 DEVICE TYPE disk MAXPIECESIZE 1G;
  4>  backup recovery area to destination '/u04/temp';
  5>}
  
  allocated channel: c1
  channel c1: SID=453 device type=DISK
  
  allocated channel: c2
  channel c2: SID=36 device type=DISK
  
  Starting backup at 09-OCT-14
  specification does not match any datafile copy in the repository
  channel c1: starting compressed archived log backup set
  channel c1: specifying archived log(s) in backup set
  ......
  

  The first syntax is bad because you can't say "to destination c1. The destination must be a path.

  The third argument is false because ' RMAN-06603: DESTINATION option must be specified with the AREA of RECOVERY, RECOVERY of FILES or DB_RECOVERY_FILE_DEST on the disk device.

  Kind regards

  RJ

• Redo and Archives association Journal

  Hello
  I am curious about the redo file and archive log file association, is one to one or one to many? In other words, is a log of arc file does hold data to a single file or several files to redo?
  Or is the Group of redo of file association arc rather than redo the file to arc file?
  
  The size of the bow on my machine logs, sometimes exceeds much the size of a single file to roll forward and will sometimes well below the size.
  
  Thank you.

  natet wrote:
  Hello
  I am curious about the redo file and archive log file association, is one to one or one to many? In other words, is a log of arc file does hold data to a single file or several files to redo?
  Or is the Group of redo of file association arc rather than redo the file to arc file?

  The size of the bow on my machine logs, sometimes exceeds much the size of a single file to roll forward and will sometimes well below the size.

  Thank you.

  Files redo archive log means (as it may seem his name) again save file which has been archived. It's the same thing as a redo log file. Sometimes your databsae can have checkpoint and log change before redo log fills then you can get different sizes of archived redo log file. But this isn't more combination of a redo log file, it's just a copy of a redo log file

• Data Guard - RMAN removing archive log

  Hello

  I ' v DataGuard with physical standby.

  I do a backup only on the primaries. Both sites have ther separate backup systems.

  I ' v FRA and configured archivelog deletion with RMAN configuration:

  on primary: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

  standby: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

  It works fine but I think what if scenarios and I'v qestion on best practices for backup after the transition of role management. Let's say that for some reason, as i'v in switch mode sleep for a few days and the backup will be posible to watch (now primary) database. What would be the steps/reconfiguration appropriate to do?

  1 should I reconfigure RMAN?

  change of new primary to: CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;

  change back to sleep again: CONFIGURE ARCHIVELOG DELETION POLICY to APPLY ON STANDBY;

  2. make full backup

  Hello

  1. you can refer to the oracle documentation: http://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmconfb.htm#CHDCFHBG

  section: "all archived Redo Log deletion policy."

  Document provides the best algorithm to analysis of work

  You can use the CONFIGURE ARCHIVELOG DELETION POLICY BACKED UP integer TIMES TO DEVICE TYPE command to allow a policy of removal of archived newspaper. This configuration specifies that archived newspapers are eligible for deletion only when the specified number of archived log backups exist on the specified device type.

  
  

  If the deletion policy is configured with the BACKED UP integer TIMES clause, then a BACKUP ARCHIVELOG , the command copy newspapers, unless integer already exist on the specified device type backups. If integer are backups of logs, then the BACKUP ARCHIVELOG command ignores the newspapers. In this way, the deletion of archived newspaper policy works as a default NOT BACKED UP integer TIMES clause on the BACKUP ARCHIVELOG command. Note that you can override the deletion policy by specifying the FORCE option on the BACKUP command.

  The deletion of archived newspaper policy has also options specific to an environment Data Guard. , then RMAN can delete logs after they have been applied to all destinations remote mandatory. If you specify SHIPPED TO STANDBY , for example, then RMAN can remove log files when they were transferred to all destinations of mandatory relief.

  2. the paper provides good information, just to check and decide easily based on the functionality of the database role you can configure.

  It will be useful.

  -Thank you

  Pavan Kumar N

• Multiplex Archived Logs

  With the help of 11.2.0.4.0

  I am trying to mux the newspapers archived (duplicate); However, do not know if I'm doing things.

  I followed this http://docs.oracle.com/cd/B28359_01/server.111/b28310/archredo004.htm and made the following

  LOG_ARCHIVE_DEST_1 = 'LOCATION=Z:\FlashRecoveryArea\archlogs\'

  LOG_ARCHIVE_DEST_2 = 'LOCATION=\\backupserver\archlogs_location'

  I thought I was doing the right thing with handwritten copies in both places when I run

  "alter newspaper archive of the current system. However, to take a closer look, looks like maybe it's different.

  Z:\FlashRecoveryArea\archlogs has the logs archived LOG_1_68_xxxx. ARC and LOG_1_71_xxxx. ARC

  \\backupserver\archlogs_location archived LOG_1_69_xxxx newspapers. ARC, LOG_1_70_xxxx. ARC and LOG_1_71_xxxx. ARC

  I misunderstood the document? This is not duplication of archived newspapers?

  Thank you

  I think your problem is the backup archivelog and remove that happens at the same time as the journal was cheating (i.e. newspaper is too slow).

  Just do this - see crossouts and "BOLD" text 'everything '...

  RUN

  {

  SQL "alter session set nls_date_format = 'MON-DD-YYYY HH24:MI:SS' ';"

  overlap archivelog all;

  cross-checking of backup;

  SQL 'alter system archive log current';

  SQL 'alter system archive log current';

  backup

  (database FORMAT '\backupserver\full\FULLBKUP_%d.DBID%I.%T.%s.%p.rman')

  more all archivelog delete all input FORMAT '\\backupserver\full\ARCHLOGBKUP_%d.%e.DBID%I.%T.%s.%p.rman' TAG = "FULLBKUP_PLUS_ARCHLOG";

  window recovery obsolete report of 5 days;

  delete noprompt obsolete recovery window of 5 days;

  SPFile FORMAT '\\backupserver\full\SPFILE_BKUP_%d.DBID%I.%T.%s.%p.rman' label backup = "BKUP_SPFILE";

  SQL 'alter controlfile backup database path as "\\backupserver\full\ctlfilePROD.txt" RE-USE";

  SQL "' create pfile =" \\backupserver\full\pfile_PROD.ora "of spfile"; "

  SQL 'alter system archive log current';

  SQL 'alter system archive log current';

  backup FORMAT '\\backupserver\full\ARCHLOGBKUP_%d.%e.DBID%I.%T.%s.%p.rman' archivelog delete all all the entries TAG = "BKUP_ARCHLOG";

  backup current controlfile FORMAT '\\backupserver\full\CTLFILE_BKUP_%d.DBID%I.%T.%s.%p.rman' TAG = "BKUP_CTLFILE";

  }