Hourly Archive Log Backup

Hi All,
Is it reasonable to backup archive logs every hour rather than just nightly using the below commands?
backup archivelog all;
delete noprompt obsolete;
delete noprompt archivelog all backed up 2 times to disk;
This is instead of simply compressing the archive logs and purging them after n number of days.
NB: Of course a nightly backup of the database still takes place.
Thanks..

1. Your last backup ran from midnight to 1am.
2. The database is active today.
3. The SAN storage crashes and your database AND your Archivelogs
(on the same SAN) are all destroyed/corrupted/lost at 10pm.
You can only restore and recover as of upto 1am because you did not backup
archivelogs generated after 1am.
You decide to multiplex your archivelogs -- ensure that you multiplex to different
locations (ie that is what Standby databases are -- at a seperate DataCenter,
seperate SAN).
If can afford to restore and recover upto 1am and lose your transactions after that, you do not need to backup archivelogs more than daily.
OK, say you have a DR site and, therefore, your archivelogs are mirrored to your
DR site because you have SAN mirroring.
Then, the only risk is an SA or DBA deleting archivelogs 'by mistake' ! (a deleted
file get's delete on the DR site as well !)

Similar Messages

Error while taking archive log backup

Dear all,
We are getting the below mentioned error while taking the archive log backup
============================================================================
BR0208I Volume with name RRPA02 required in device /dev/rmt0.1
BR0210I Please mount BRARCHIVE volume, if you have not already done so
BR0280I BRARCHIVE time stamp: 2010-05-27 16.43.41
BR0256I Enter 'c[ont]' to continue, 's[top]' to cancel BRARCHIVE:
c
BR0280I BRARCHIVE time stamp: 2010-05-27 16.43.46
BR0257I Your reply: 'c'
BR0259I Program execution will be continued...
BR0280I BRARCHIVE time stamp: 2010-05-27 16.43.46
BR0226I Rewinding tape volume in device /dev/rmt0 ...
BR0351I Restoring /oracle/RRP/sapreorg/.tape.hdr0
BR0355I from /dev/rmt0.1 ...
BR0278W Command output of 'LANG=C cd /oracle/RRP/sapreorg && LANG=C cpio -iuvB .tape.hdr0 < /dev/rmt0.1':
Can't read input
===========================================================================
We are able to take offline, online backups but we are facing the above mentioned problem while taking archive log backup
We are on ECC 6 / Oracle / AIX
The kernel is latest
The drive is working fine and there is no problem with the tapes as we have tried using diffrent tapes
can this be a permissions issue?
I ran saproot.sh but somehow it is setting owner as sidadm and group as sapsys to some of the br* files
I tried by changing the permissions to oraSID : dba but still the error is the same
Any suggestions?

Means you have not initialized the medias but trying to take backups.
First check how many medias you have entered in your tape count parameter for archive log backups (just go to initSID.sap and check)
Then increase/reduce them to according to your archive backup plan >> Initialize all the tapes according to their name (same as you have initialized in initSID.sap) >> stick physical label to all the medias according to name >> Schedule archive backups
It will not ask you for initialization as already you have initialized in second step.
Suggestion: Use 7 medias per week (one tape per day)
Regards,
Nick Loy

RMAN never deletes archive log backups

Hi all,
I have same problem as some of you have already faced.
I have some instances 10.2.0.4 running un archive log mode.
I take full hot backup daily.
I setup a rman script to backup and delete obsolete backups according to the following policy:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
and then:
run {
ALLOCATE CHANNEL RMAN_BACK_CH01 TYPE DISK;
BACKUP AS COMPRESSED BACKUPSET DATABASE FORMAT '/mnt/rman_202/pnetpres/db_pres_%U';
CROSSCHECK ARCHIVELOG ALL;
BACKUP AS COMPRESSED BACKUPSET ARCHIVELOG ALL FORMAT '/mnt/rman_202/pnetpres/al_pres_%U';
CROSSCHECK BACKUP;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT EXPIRED BACKUP;
RELEASE CHANNEL RMAN_BACK_CH01;
crosscheck archivelog all;
delete noprompt archivelog all completed before 'sysdate -2';
DB full backups are being deleted, however archive logs backups are not deleted.
There are no tablespaces in backup or offline mode.
How can I know the reason why some archive log backups are kept ?
Even I clear the policy and perform a crosscheck and delete, those are not marked as obsolete neither deleted from disk.
Thanks in advance.

Hi Fernando,
This are the ouputpus of the commands:
RMAN> REPORT OBSOLETE;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
no obsolete backups found
RMAN> LIST BACKUP OF ARCHIVELOG ALL;
List of Backup Sets
===================
BS Key Size Device Type Elapsed Time Completion Time
1090 69.65M DISK 00:00:16 23-FEB-11
BP Key: 1093 Status: AVAILABLE Compressed: YES Tag: TAG20110223T061511
Piece Name: /mnt/rman_202/pnetproy/al_pres_0jm5c6bf_1_1
List of Archived Logs in backup set 1090
Thrd Seq Low SCN Low Time Next SCN Next Time
1 13 2173025156 21-FEB-11 2173028010 21-FEB-11
1 14 2173028010 21-FEB-11 2173041730 21-FEB-11
1 15 2173041730 21-FEB-11 2173041813 21-FEB-11
1 16 2173041813 21-FEB-11 2173106066 22-FEB-11
1 17 2173106066 22-FEB-11 2173108831 22-FEB-11
1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1411 125.43M DISK 00:00:28 24-FEB-11
BP Key: 1414 Status: AVAILABLE Compressed: YES Tag: TAG20110224T061643
Piece Name: /mnt/rman_202/pnetproy/al_pres_0mm5eqqb_1_1
List of Archived Logs in backup set 1411
Thrd Seq Low SCN Low Time Next SCN Next Time
1 18 2173108831 22-FEB-11 2173116745 22-FEB-11
1 19 2173116745 22-FEB-11 2173117735 22-FEB-11
1 20 2173117735 22-FEB-11 2173117739 22-FEB-11
1 21 2173117739 22-FEB-11 2173117753 22-FEB-11
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1600 164.40M DISK 00:00:37 25-FEB-11
BP Key: 1603 Status: AVAILABLE Compressed: YES Tag: TAG20110225T061643
Piece Name: /mnt/rman_202/pnetproy/al_pres_0pm5hf6b_1_1
List of Archived Logs in backup set 1600
Thrd Seq Low SCN Low Time Next SCN Next Time
1 22 2173117753 22-FEB-11 2173165783 23-FEB-11
1 23 2173165783 23-FEB-11 2173168857 23-FEB-11
1 24 2173168857 23-FEB-11 2173221907 23-FEB-11
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
1829 132.24M DISK 00:00:30 26-FEB-11
BP Key: 1832 Status: AVAILABLE Compressed: YES Tag: TAG20110226T061627
Piece Name: /mnt/rman_202/pnetproy/al_pres_0sm5k3hr_1_1
List of Archived Logs in backup set 1829
Thrd Seq Low SCN Low Time Next SCN Next Time
1 25 2173221907 23-FEB-11 2173246002 24-FEB-11
1 26 2173246002 24-FEB-11 2173249177 24-FEB-11
1 27 2173249177 24-FEB-11 2173313111 25-FEB-11
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2058 218.03M DISK 00:00:48 27-FEB-11
BP Key: 2061 Status: AVAILABLE Compressed: YES Tag: TAG20110227T061628
Piece Name: /mnt/rman_202/pnetproy/al_pres_0vm5mnts_1_1
List of Archived Logs in backup set 2058
Thrd Seq Low SCN Low Time Next SCN Next Time
1 28 2173313111 25-FEB-11 2173316259 25-FEB-11
1 29 2173316259 25-FEB-11 2173380316 26-FEB-11
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2298 205.39M DISK 00:00:45 28-FEB-11
BP Key: 2301 Status: AVAILABLE Compressed: YES Tag: TAG20110228T061620
Piece Name: /mnt/rman_202/pnetproy/al_pres_12m5pc9l_1_1
List of Archived Logs in backup set 2298
Thrd Seq Low SCN Low Time Next SCN Next Time
1 30 2173380316 26-FEB-11 2173388686 26-FEB-11
1 31 2173388686 26-FEB-11 2173465280 27-FEB-11
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
BS Key Size Device Type Elapsed Time Completion Time
2546 180.29M DISK 00:00:39 01-MAR-11
BP Key: 2549 Status: AVAILABLE Compressed: YES Tag: TAG20110301T061533
Piece Name: /mnt/rman_202/pnetproy/al_pres_15m63to5_1_1
List of Archived Logs in backup set 2546
Thrd Seq Low SCN Low Time Next SCN Next Time
1 32 2173465280 27-FEB-11 2173499757 27-FEB-11
1 33 2173499757 27-FEB-11 2173527280 27-FEB-11
1 34 2173527280 27-FEB-11 2173530545 27-FEB-11
1 35 2173530545 27-FEB-11 2173589000 28-FEB-11
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
2801 85.40M DISK 00:00:19 02-MAR-11
BP Key: 2804 Status: AVAILABLE Compressed: YES Tag: TAG20110302T061613
Piece Name: /mnt/rman_202/pnetproy/al_pres_18m66i5d_1_1
List of Archived Logs in backup set 2801
Thrd Seq Low SCN Low Time Next SCN Next Time
1 36 2173589000 28-FEB-11 2173592018 28-FEB-11
1 37 2173592018 28-FEB-11 2173671730 01-MAR-11
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3058 137.93M DISK 00:00:30 03-MAR-11
BP Key: 3061 Status: AVAILABLE Compressed: YES Tag: TAG20110303T061548
Piece Name: /mnt/rman_202/pnetproy/al_pres_1bm696gk_1_1
List of Archived Logs in backup set 3058
Thrd Seq Low SCN Low Time Next SCN Next Time
1 38 2173671730 01-MAR-11 2173674751 01-MAR-11
1 39 2173674751 01-MAR-11 2173736248 02-MAR-11
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3324 138.96M DISK 00:00:31 04-MAR-11
BP Key: 3327 Status: AVAILABLE Compressed: YES Tag: TAG20110304T061559
Piece Name: /mnt/rman_202/pnetproy/al_pres_1em6bqsv_1_1
List of Archived Logs in backup set 3324
Thrd Seq Low SCN Low Time Next SCN Next Time
1 40 2173736248 02-MAR-11 2173739307 02-MAR-11
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3597 178.07M DISK 00:00:39 05-MAR-11
BP Key: 3600 Status: AVAILABLE Compressed: YES Tag: TAG20110305T061543
Piece Name: /mnt/rman_202/pnetproy/al_pres_1hm6ef8f_1_1
List of Archived Logs in backup set 3597
Thrd Seq Low SCN Low Time Next SCN Next Time
1 41 2173739307 02-MAR-11 2173784198 02-MAR-11
1 42 2173784198 02-MAR-11 2173816111 03-MAR-11
1 43 2173816111 03-MAR-11 2173819171 03-MAR-11
1 44 2173819171 03-MAR-11 2173882472 04-MAR-11
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
3835 198.44M DISK 00:00:43 06-MAR-11
BP Key: 3838 Status: AVAILABLE Compressed: YES Tag: TAG20110306T061548
Piece Name: /mnt/rman_202/pnetproy/al_pres_1km6h3kk_1_1
List of Archived Logs in backup set 3835
Thrd Seq Low SCN Low Time Next SCN Next Time
1 45 2173882472 04-MAR-11 2173885557 04-MAR-11
1 46 2173885557 04-MAR-11 2173947612 05-MAR-11
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4131 185.94M DISK 00:00:40 07-MAR-11
BP Key: 4134 Status: AVAILABLE Compressed: YES Tag: TAG20110307T061546
Piece Name: /mnt/rman_202/pnetproy/al_pres_1nm6jo0i_1_1
List of Archived Logs in backup set 4131
Thrd Seq Low SCN Low Time Next SCN Next Time
1 47 2173947612 05-MAR-11 2173951657 05-MAR-11
1 48 2173951657 05-MAR-11 2174026607 06-MAR-11
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4435 161.37M DISK 00:00:35 08-MAR-11
BP Key: 4438 Status: AVAILABLE Compressed: YES Tag: TAG20110308T061540
Piece Name: /mnt/rman_202/pnetproy/al_pres_1qm6mccc_1_1
List of Archived Logs in backup set 4435
Thrd Seq Low SCN Low Time Next SCN Next Time
1 49 2174026607 06-MAR-11 2174062014 06-MAR-11
1 50 2174062014 06-MAR-11 2174087203 06-MAR-11
1 51 2174087203 06-MAR-11 2174090299 06-MAR-11
1 52 2174090299 06-MAR-11 2174147018 07-MAR-11
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
4745 79.24M DISK 00:00:18 09-MAR-11
BP Key: 4748 Status: AVAILABLE Compressed: YES Tag: TAG20110309T061555
Piece Name: /mnt/rman_202/pnetproy/al_pres_1tm6p0os_1_1
List of Archived Logs in backup set 4745
Thrd Seq Low SCN Low Time Next SCN Next Time
1 53 2174147018 07-MAR-11 2174149955 07-MAR-11
1 54 2174149955 07-MAR-11 2174239915 08-MAR-11
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
BS Key Size Device Type Elapsed Time Completion Time
5270 135.13M DISK 00:00:31 10-MAR-11
BP Key: 5273 Status: AVAILABLE Compressed: YES Tag: TAG20110310T061603
Piece Name: /mnt/rman_202/pnetproy/al_proy_20m6rl53_1_1
List of Archived Logs in backup set 5270
Thrd Seq Low SCN Low Time Next SCN Next Time
1 55 2174239915 08-MAR-11 2174242816 08-MAR-11
1 56 2174242816 08-MAR-11 2174304682 09-MAR-11
1 57 2174304682 09-MAR-11 2174307679 09-MAR-11
1 58 2174307679 09-MAR-11 2174353241 09-MAR-11
1 59 2174353241 09-MAR-11 2174384330 10-MAR-11
1 60 2174384330 10-MAR-11 2174387259 10-MAR-11
RMAN>
For example the backups of archivelog from Feb 21st will never be deleted unless I force the delete.
I'd like to understand why it happens :-)
Thanks a lot,
Regards,
Diego.

Archive log backup issue

Hi,
I am facing the issue with archive log backup with external autoloader tape drive ( HP data protector software).
The archivelog backup is not successfull.
Kindly provide me a suggestion o solve this issue. Please find the log below
BR0002I BRARCHIVE 7.00 (32)
BR0262I Enter database user name[/password]:
BR0169I Value 'util_file_online' of parameter/option 'backup_dev_type/-d' ignored for 'brarchive' - 'util_file' assumed
BR0006I Start of offline redo log processing: adzulphz.sve 2009-01-28 12.12.11
BR0252E Function fopen() failed for '/oracle/SFD/saparch/adzulphz.sve' at location main-6
BR0253E errno 13: Permission denied
BR0121E Processing of log file /oracle/SFD/saparch/adzulphz.sve failed
BR0007I End of offline redo log processing: adzulphz.sve 2009-01-28 12.12.11
BR0280I BRARCHIVE time stamp: 2009-01-28 12.12.11
BR0005I BRARCHIVE terminated with errors
[Major]
From: OB2BAR_OMNISAP@sfwdqs "OMNISAP" Time: 01/28/09 12:12:11
BRARCHIVE /usr/sap/SFD/SYS/exe/run/brarchive -a -c -u system/******** returned 3
[Normal]
From: BSM@sfwsol "Archive" Time: 1/28/2009 12:19:09 PM
OB2BAR application on "sfwdqs" disconnected.
[Normal]
From: BMA@sfwsol "HP:Ultrium 3-SCSI_1_sfwsol" Time: 1/28/2009 12:19:38 PM
Tape0:0:5:0C
Medium header verification completed, 0 errors found
[Normal]
From: BMA@sfwsol "HP:Ultrium 3-SCSI_1_sfwsol" Time: 1/28/2009 12:19:58 PM
By: UMA@sfwsol@Changer0:0:5:1
Unloading medium to slot 4 from device Tape0:0:5:0C
[Normal]
From: BMA@sfwsol "HP:Ultrium 3-SCSI_1_sfwsol" Time: 1/28/2009 12:20:21 PM
ABORTED Media Agent "HP:Ultrium 3-SCSI_1_sfwsol"
[Normal]
From: BSM@sfwsol "Archive" Time: 1/28/2009 12:20:21 PM
Regards,
Kumar

Hi ,
Please check the directory permissions for "/oracle/SFD/saparch".
Please check permissions for <sid>adm and ora<sid> for the above directory.
"Note 17163 - BRARCHIVE/BRBACKUP messages and codes" and also related notes may help you for addtional information.
Regards
Upender Reddy

Can archive log backup influence database performance?

Hi,
can archive log backup generally influence the database performance? I mean: users can view their query to go slowly during backup of archived redolog?

Are you asking about backing up the archived redo logs via rman or directly to tape or the actual archive process where Oracle backs the online redo to disk?
-- comments on archive process
Normally the redo log archiving process should have no noticable effect on database performance. About the only way for the process to have a noticable performance impact while it is running is if you store all your online redo logs on the same physical disk. You would also want the backup to be on a different physical disk.
Check your alert log to make sure you do not have error messages related to being unable to switch redo logs and checkpoint incomplete messages. These would be an indication that your online redo logs are defined too small and you are trying to cycle around before Oracle has finished archiving the older logs.
-- comments on archived redo log backup
Archived reodo logs should not be on the same disk as the database so using rman or an OS task to back these files up should not impact Oracle unless you server is itself near capacity and any additional task effects the server.
HTH -- Mark D Powell --

DB2 archive log backup

Dear Sir
i am using SAP EHP5 with DB2 9.7 FP4 on windows 2008r2
1) i have turn on archive log and log is generating following following directory
:\db2\PSD\log_archive\DB2PSD\PSD\NODE0000\C0000000
2) we want to take archive log backup, as per SAP DB13 tcode there is option "Archive log file to tape", we are not using tape drive, is there any option to take archive log backup to disk?
regards

Yes you can restore the backup as follows :
1 . Restore the database :
      db2 restore db <SID> from <backup_dir> LOGTARGET <directory_to_which_log_files_will_be copied>
    Rollforward the database:
    db2 "rollforward db <SID> to end of logs overflow log path ('<directory_to_which_log_files_will_be copied>')"
2. The simplest way is to use the following command .
     db2 RECOVER DB <SID>
    This will use the latest backup image and rollforward to the end of logs using all default values.
Also an online backup as of DB2 9.7 includes the transaction logs by default , you do not need to exclusively specify.

Hourly archive log generation

Hi,
I am working in Oracle 10g RAC database on Hp-UX... in the standby environment..
Instance name :
R1
R2
R3
for the above three instance... i need to find the hourly archive log generation in standby site.....
Hours 1 2 3
R1
R2
R3
Total
Share the query...

set parameter archive_lag_target to required value. its a dynamic parameter and specified in secs.

How can i see the Archive log backup contens from th tapes

hello
I am taking Archive log Backup regularly
i want ot chk my backup contents from tape through the db2 command
From DB13 it is showing successfully Completed
but for the comfirmation where and how i can see the contents of tape
Point in advance from me
Jayesh

Hello Jayesh ,
using db2tapemgr you can display the tape header DB2TAPEMGR.HEADER using
db2tapemgr SHOW TAPE HEADER <tape device>
in "contents:" field you can see , which logfiles are on tape at which position .
see
[db2tapemgr - Manage log files on tape command|http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/index.jsp?topic=/com.ibm.db2.luw.admin.cmd.doc/doc/r0011704.html]
[IBM DB2 Universal Database for UNIX and Windows:New Log File Management|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50c7d3ef-5a59-2a10-a3ab-fb3b0887f479]
Best regards
dirk

Archive Log Backups Retention Policy

How can I define Retention Policy for archive log backups?

The question asked and answer you have marked as "Correct answer" is misleading.
For archived log deletion policy, look below.
Configuring the RMAN Environment
For the actual question posted "How can I define Retention Policy for archive log backups?", look below link.
http://docs.oracle.com/cd/E11882_01/backup.112/e10642/rcmconfb.htm#i1019318
Also, did you start the thread to clear your doubt or test the other forum users?
Thank you!!

RMAN archive logs backup and restore in RAC environment.

Hello All,
I have a 8 node RAC using ASM production database and a single node standby database using ASM. I have archive log gap on the standby database and the archive logs on the primary database is backed up and removed.
I need to resync the standby database using RMAN backup/restore.
Could you please help me on how to backup the specific archive logs file (all threads) from production and restore/recover the standby database. Any specific RMAN script or Metalink ID will help alot.
Details:
Source: 8 node RAC, ASM, Linux,
target: Non-RAC, ASM, Linux.
Regards,

You can try LIKE clause of BACKUP ARCHIVELOG such as:
RMAN> backup archivelog like '%XE%2010%20%';
Starting backup at 20-AUG-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=58 recid=19 stamp=727519553
input archive log thread=1 sequence=59 recid=20 stamp=727544121
input archive log thread=1 sequence=60 recid=21 stamp=727544127
channel ORA_DISK_1: starting piece 1 at 20-AUG-10
channel ORA_DISK_1: finished piece 1 at 20-AUG-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_08_20\
O1_MF_ANNNN_TAG20100820T154401_66X1O353_.BKP tag=TAG20100820T154401 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 20-AUG-10or you can try SEQUENCE clause:
RMAN> backup archivelog sequence between 58 and 60 thread 1;
Starting backup at 20-AUG-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=58 recid=19 stamp=727519553
input archive log thread=1 sequence=59 recid=20 stamp=727544121
input archive log thread=1 sequence=60 recid=21 stamp=727544127
channel ORA_DISK_1: starting piece 1 at 20-AUG-10
channel ORA_DISK_1: finished piece 1 at 20-AUG-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_08_20\
O1_MF_ANNNN_TAG20100820T154911_66X1YRJL_.BKP tag=TAG20100820T154911 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 20-AUG-10or
RMAN> backup archivelog sequence between 58 and 60;
Starting backup at 20-AUG-10
using channel ORA_DISK_1
channel ORA_DISK_1: starting archive log backupset
channel ORA_DISK_1: specifying archive log(s) in backup set
input archive log thread=1 sequence=58 recid=19 stamp=727519553
input archive log thread=1 sequence=59 recid=20 stamp=727544121
input archive log thread=1 sequence=60 recid=21 stamp=727544127
channel ORA_DISK_1: starting piece 1 at 20-AUG-10
channel ORA_DISK_1: finished piece 1 at 20-AUG-10
piece handle=C:\ORACLEXE\APP\ORACLE\FLASH_RECOVERY_AREA\XE\BACKUPSET\2010_08_20\
O1_MF_ANNNN_TAG20100820T154748_66X1W5Z0_.BKP tag=TAG20100820T154748 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:04
Finished backup at 20-AUG-10See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta008.htm#i78730

Archival Log Backup

Hi,
I'm taking hot backup with archival logs...once the back up done
will the archive log file system get flushed out automatically or else i need to flush
Thanks in Advance
Gobi

If it's a user managed backup the user (i.e. you) manages it.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/osbackup.htm#BRADV016
If using rman, it would depend on the configuration and commands used.
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup003.htm#sthref371

Archive Log Backup

Hi,
Can anyone tell me why cant we take hot backup of DB in no archive mode
Also,pls tell me that why do we take the backup of redolog files only in DB in noarchive mode and not when DB is in archive mode.
I mean lets say DB crashed and latest commited data was only in redo log file and not been archived.In that case ,i think bkp of redo log files shud also be taken.
Pls clear my doubts.
thanks

During a hot backup the database is alive and changes are occurring. These changes must be saved to the redologs (datafiles themselves are temporarily blocked) and you cannot rely on the online redologs alone, because it's very likely their entries will be overwritten , while the backup is running. So a hot backup needs archivelog mode.
Yourself give the answer, why online redologs are not backed up. Yes, the latest commited data could be in one of the online redologs, but in the CURRENT one, not in those you backed up yesterday or whenever else. You will get trouble, when replacing the actual redologs by older ones.
To avoid loss of data one should care about these crucial log files, so it's recommended to mirror or multiplex these files.

Archive log backup fails in brtools

Hi, I have latest BRTOOLS PATCH, and I use BRTOOLS STUDIO.
I NEED TO DO A ARCHIVELOG BACKUP IN MY SOLUTION MANAGER SYSTEM.
I log on on brtools studio with sapsr3 user, with same privileges as these sap notes.
Note 134592 - Importing the SAPDBA role (sapdba_role.sql)
Note 834917 - Oracle Database 10g: New database role SAPCONN
Note 1028220 - ORA-01031: Insufficient privileges despite SAPCONN role
1. click in avaibility
2. click in Archivelog
3. click in execute
4. in function = save or save_deleted(at the end, the same mistake)
5. in device= disk
6. in number i left blank
7- click in next
8. compresion = yes or no(at the end, the same mistake)
9. verify = no
10.fill mode = no
11.In modify and delay, I choose the 3 option(at the end, the same mistake)
12.Confirm
13.Back up.
here the job begin and some minutes or seconds later the job finish.. the only log that i can see is this:
ERROR 2009/11/21 01:13:38 [Tools] Instance QAS_SAPSR3_USER reports failure while running job Archivelog Backup:
BR0002I BRARCHIVE 7.00 (44)
BR0156E Illegal value 'delay' found for option '-modify'
BR0007I End of offline redo log processing: aebypmny.log 2009-11-21 01.13.38
BR0280I BRARCHIVE time stamp: 2009-11-21 01.13.38
BR0005I BRARCHIVE terminated with errors
if i search for aebypmny.log, i found nothing.
below if i choose modify no then it says:
Illegal value 'no' found for option'-modify' or if i choose yes it says:
Illegal value 'yes' found for option '-modify'
Then my question. how can i perform this archilog backup in brtools studio???

Hi, thanks for your answer
Only posted log before.
ERROR 2009/11/21 01:13:38 Tools Instance QAS_SAPSR3_USER reports failure while running job Archivelog Backup:
BR0002I BRARCHIVE 7.00 (44)
BR0156E Illegal value 'delay' found for option '-modify'
BR0007I End of offline redo log processing: aebypmny.log 2009-11-21 01.13.38
BR0280I BRARCHIVE time stamp: 2009-11-21 01.13.38
BR0005I BRARCHIVE terminated with errors
if i search for aebypmny.log, i found nothing.
are this issue related to this problem?
why in avaibility option i can´t select this options | Restore | Recovery | Disaster Recovery???, I only can select Copy | Backup
I do a offline and online backup. but options for revorey are unavailable..

RMAN backup archive logs on tape that has not been backuped yet...

We are using RMAN with catalog on Legato. Oracle 10gR2.
Our archive log backup is taking every 2 hours with scriipt:
run {
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
send 'NSR_ENV=(NSR_SERVER=hitbackup.hit.hypohr,NSR_CLIENT=a22ff020.hit.hypobck)';
# 0.0840278 = 121 minutes!
backup archivelog FROM TIME = 'sysdate-0.0840278' filesperset 50 format '/arch1_%d_%u/';
release channel t1;
release channel t2;
}In the night we take everyday full backup where we delete all 9 days old archive log which has been backuped on tape at least once. The script is following:
run {
allocate channel t1 type 'SBT_TAPE';
allocate channel t2 type 'SBT_TAPE';
send 'NSR_ENV=(NSR_SERVER=hitbackup.hit.hypohr,NSR_CLIENT=a22ff020.hit.hypobck)';
backup full database filesperset 2 format '/full_%d_%U/';
release channel t1;
release channel t2;
allocate channel d2 type disk;
delete archivelog until time 'trunc(sysdate)-9'
backed up 1 times to device type SBT_TAPE;
release channel d2;
}Problem is that sometimes archive log backup is not performed (Legato head is busy with other backups or some restore that happened in the time when backup is scheduled and later 2hours frame is missing those logs) and then we backup them with some manual script.
We'd like to know how to backup to tape all archive logs in last 5 days that has not been backuped once to tape. I.E:
backup archivelog FROM TIME = 'sysdate-7' filesperset 50 format '/arch1_%d_%u/'
backed up 0 times to device type SBT_TAPE;This part will be included in daily job...which should recollect all missing archive logs from last seven days.
THX

You could try to use the NOT BACKED UP x TIMES clause from BACKUP command.

Error when I backup with rman plus archive log

Hi All,
I tried below command
run {
SQL 'ALTER SYSTEM ARCHIVE LOG CURRENT';
BACKUP DATABASE INCLUDE CURRENT CONTROLFILE PLUS ARCHIVELOG DELETE ALL INPUT;
and that show below error
archived log file name=+DATA/pimprd/archivelog/pimarch_2_95_698703544.arc RECID=128 STAMP=706186164
archived log file name=+DATA/pimprd/archivelog/pimarch_2_96_698703544.arc RECID=130 STAMP=706186173
Finished backup at 21-DEC-09
ORACLE error from target database:
ORA-03114: not connected to ORACLE
Starting backup at 21-DEC-09
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=259 instance=pimdb1 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=153 RECID=113 STAMP=705896703
input archived log thread=1 sequence=154 RECID=116 STAMP=705983105
input archived log thread=1 sequence=155 RECID=119 STAMP=706069504
archived log file name=+DATA/pimprd/archivelog/pimarch_2_95_698703544.arc RECID=128 STAMP=706186164
archived log file name=+DATA/pimprd/archivelog/pimarch_2_96_698703544.arc RECID=130 STAMP=706186173
Finished backup at 21-DEC-09
ORACLE error from target database:
ORA-03114: not connected to ORACLE
Starting backup at 21-DEC-09
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-03114: not connected to ORACLE
RMAN-03002: failure of backup plus archivelog command at 12/21/2009 11:00:18
ORA-03114: not connected to ORACLE
There are RAC 11.1.0.6.0 on AIX 5.3 with ASM.
Please advise,
Thank you,
Hiko

็Hi All,
I tried backup archivelog again and show same error,
Line: -----
rman target /
Recovery Manager: Release 11.1.0.6.0 - Production on Mon Dec 21 14:48:29 2009
Copyright (c) 1982, 2007, Oracle. All rights reserved.
connected to target database: PIMDB (DBID=3834713912)
RMAN> run
2> {
3> backup archivelog all;
4> }
Starting backup at 21-DEC-09
current log archived
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=275 instance=pimdb1 device type=DISK
channel ORA_DISK_1: starting archived log backup set
channel ORA_DISK_1: specifying archived log(s) in backup set
input archived log thread=1 sequence=161 RECID=131 STAMP=706190624
input archived log thread=1 sequence=162 RECID=133 STAMP=706200525
input archived log thread=2 sequence=97 RECID=132 STAMP=706190625
input archived log thread=2 sequence=98 RECID=134 STAMP=706200526
channel ORA_DISK_1: starting piece 1 at 21-DEC-09
channel ORA_DISK_1: finished piece 1 at 21-DEC-09
piece handle=/oradata/backup/pimdb/rman/pimdb_Fulldata_20091221_97_1.bck tag=TAG20091221T144854 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:01
Finished backup at 21-DEC-09
Starting Control File and SPFILE Autobackup at 21-DEC-09
piece handle=/oradata/backup/pimdb/rman/pimdb_Controlfile_c-3834713912-20091221-02 comment=NONE
Finished Control File and SPFILE Autobackup at 21-DEC-09
ORACLE error from target database:
ORA-03114: not connected to ORACLE
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-03114: not connected to ORACLE
RMAN-03009: failure of REFAF command on default channel at 12/21/2009 14:59:33
ORA-03114: not connected to ORACLE
RMAN> exit
Recovery Manager complete.
Line: -----
And I check in alert log file that show below error
Line: -----
Mon Dec 21 14:48:44 2009
Thread 1 advanced to log sequence 163
Current log# 1 seq# 163 mem# 0: +DATA/pimdb/onlinelog/group_1.282.698703549
Mon Dec 21 14:49:17 2009
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3E00000000] [PC:0x10180AA48, kxfpg1srv()+04e8]
Errors in file /oracle/diag/rdbms/pimdb/pimdb1/trace/pimdb1_ora_5095646.trc (incident=64044):
ORA-07445: exception encountered: core dump [kxfpg1srv()+04e8] [SIGSEGV] [ADDR:0x3E00000000] [PC:0x10180AA48] [Address not mapped to object] []
Incident details in: /oracle/diag/rdbms/pimdb/pimdb1/incident/incdir_64044/pimdb1_ora_5095646_i64044.trc
Mon Dec 21 14:49:31 2009
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x3E00000000] [PC:0x10180AA48, kxfpg1srv()+04e8]
Errors in file /oracle/diag/rdbms/pimdb/pimdb1/trace/pimdb1_m000_1831050.trc (incident=64163):
ORA-07445: exception encountered: core dump [kxfpg1srv()+04e8] [SIGSEGV] [ADDR:0x3E00000000] [PC:0x10180AA48] [Address not mapped to object] []
Incident details in: /oracle/diag/rdbms/pimdb/pimdb1/incident/incdir_64163/pimdb1_m000_1831050_i64163.trc
Mon Dec 21 14:49:33 2009
Trace dumping is performing id=[cdmp_20091221144933]
Mon Dec 21 14:49:34 2009
Sweep Incident[64163]: completed
Mon Dec 21 14:59:33 2009
Process 0x70000020477df88 appears to be hung while dumping
Current time = 1584185732, process death time = 1584124482 interval = 60000
Attempting to kill process 0x70000020477df88 with OS pid = 5095646
OSD kill succeeded for process 70000020477df88
Line: -----
Please advice,
Thank you
Hiko

Hourly Archive Log Backup

Similar Messages

Maybe you are looking for