Archive Files Log Backup in DB2

Hi,
I have archived files moved to /db2/TXT/log_archive from /db2/TXT/log_dir.
I have very less space configured for /db2/TXT/log_archive file system.
I don't have tape drive connected to production server to take backup of Archive log file to TAPE using DB13.
Currently I am taking Database backup to DISK not to TAPE and would like to take the archive log files (Offline transaction logs) backup also to DISK.
Please let me know the way out for this situation
Thanks

Hello,
I think brtools for this (brarchive) is not usable for db2 because this is typical for oracle and not supported for db2. For more information about the log management see note 913481.
Which DB2 version you´re using? If it is 9.5 the standard is an online backup includes logs so you´ve your archived log file in the online backup. If you´re using a DB2 version smaller then 9.5 you can include the parameter "include logs" in your backup command.
Regards
Olaf

Similar Messages

Archiving file log in application server

Hi all,
where to set archiving log folder path in application server .
Rgs,
siva

Hi Siva
have a look at these links.
I found it very helpfull.
[https://forums.sdn.sap.com/click.jspa?searchID=20703185&messageID=6294517]
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/607e9392-8167-2b10-b9a8-e0aa297e88c6]
PLS DONT FORGET TO CLOSE THE THREADS
Regards
Hareesh

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

Automatic log backup to pipe

Hi SAPers
I have problem with maxdb (content server). Is it possible to activate automatic log backup to pipe? We are backuping through Tivoli on tapes. Backup media are created and manual backups are working fine but i am not able to activate automatic log backups! Always when I am activating this the file instead of pipe is created in /sapdb/RDB/backup directory and backup is not performed.
In the Note 869267 - FAQ: MaxDB LOG area I found out that it is not possible to activate automatic log backups to pipe is it true?
Thanks in advance
JM

Hello JM,
What database version are you running?
You already found the note 869267, which gave you answer on the question "24. Can the log area be saved to a pipe? ". The SAP note 869267 also give you the answer on the question "26. How do I archive the log backup files generated?
"Is it possible to activate automatic log backup to pipe?"
*No.
And it's true, that "Automatic log backups to a pipe CANNOT be supported at present" , as it was explained in the SAP note 869267.
But you could run the interactive log backups to a pipe.
In general you could find the information/documents at https://www.sdn.sap.com/irj/sdn/maxdb
-> The Complete SAP MaxDB Documentation Set -> Open the SAP MaxDB 7.7 Library
-> Database Administration-> Backing Up the Database
< -> Backing Up Log Entries >
Thank you and best regards, Natalia Khlopina
Edited by: Natalia Khlopina on Apr 28, 2008 1:26 PM
Edited by: Natalia Khlopina on Apr 28, 2008 1:26 PM

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.

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

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

Hoping for a quick response : EXP and Archived REDO log files

I apologize in advance if this question has been asked and answered 100 times. I admit I didn't search, I don't have time. I'm leaving on vacation tomorrow, and I need to know if I'm correct about something to do with backup / restore.
we have 10g R2 running a single instance on a single server. The application vendor has "embedded" oracle with their application. The vendor's backup is a batch file using EXP - thus:
exp system/xpwdxx@db full=y file=D:\Orant\admin\db\EXP\db_full.dmp log=D:\Orant\admin\db\EXP\db_full.txt direct=y compress=y
This command is executed nightly at midnight. The files are then backed up by our nightly backup to offsite storage media.
Te database is running in autoarchive mode. The problem is, the archived redo files filled the drive they were being stored on, and it is the drive the database is on. I used OS commands to move 136G of archived redo logs onto other storage media to free the drive.
My question: Since the EXP runs at midnight, when there is likely NO activity, do I need to run in AutoArchive Mode? From what I have read, you cannot even apply archived redo log files to this type of backup strategy (IMP) Is that true? We are ok losing changes since our last EXP. I have read a lot of stuff about restoring consistent vs. inconsistent, and just need to know: If my disk fails, and I have to start with a clean install of Oracle and nothing else, can I IMP this EXP and get back up and running as of the last EXP? Or do I need the autoarchived redo log files back to July 2009 (136G of them).
Hoping for a quick response
Best Regards, and thanks in advance
Bruce Davis

Bruce Davis wrote:
Amardeep Sidhu
Thank you for your quick reply. I am reading in the other responses that since I am using EXP without consistent=y, I might not even have a backup. The application vendor said that with this dmp file they can restore us to the most recent backup. I don't really care for this strategy as it is untested. I asked them to verify that they could restore us and they said they tested the dmp file and it was OK.
Thank you for taking the time to reply.
Best Regards
BruceThe dump file is probably ok in the sense it is not corrupted and can be used in an imp operation. That doesn't mean the data in it is transactionally consistent. And to use it at all, you have to have a database up and running. If the database is physically corrupted, you'll have to rebuild a new database from scratch before you can even think about using your dmp file.
Vendors never understand databases. I once had a vendor tell me that Oracle's performance would be intolerable if there were more than 5 concurrent connections. Well, maybe in HIS product ..... Discussions terminated quickly after he made that statement.

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

Is it possible to use Archive Redo log file

Hi friends,
My database is runing in archive log mode.I had taken cold backup on Sunday but i am taking archive log file daily evening.
Wednesday my database crash that means i lost all control file,redo log file,datafile etc.
I have archived log file backup till Tuesday Night and other files like control file,datafile etc of Sunday .
1)Is it possible to recover database till tuesday if yes HOW to use archive log file.
(See SCN no of control file and datafiles is same ,if we use RECOVER DATABASE command oracle shows that media recovery is not requide.)
we don't have current control file we had lost in media crash.
null

Dear friend
In this scenario
you lost the contorl file
1>If you have old copy of Contorl file,
which has the current structure of the
database and all the archive files then
you can recover the database with
Ponint in time recovery (Using Backup Controlfile)
suresh

Clone from standby ended in ARC: Cannot archive online log based on backup

Hi
I m into scenario where my prod db is in one data center and standby is in other data center.
Both are geographically separated. I have to get a copy of prod on to standby data center side.
Sending data over the network is taking long time either with duplicate db from active db or take backup and copy over standby side and restore it.
so i thought of duplicate db from standby db which is in same data center, using 11g RMAN duplicate from active standby command.
I have simulated scenario which is as below
oracle version 11.2.0.1
os version REHL 5.4
My procedure & parameter are as below.
on standby side from where i m copying (TARGET)
1) on standby
alter database recover managed standby db cancel;
2)alter database convert to snapshot standby;
which gave me
/u01/data/DGSTD/archive/1_152_750425930.dbf
/u01/data/DGSTD/archive/1_153_750425930.dbf
*/u01/data/DGSTD/archive/1_1_752604441.dbf*
*/u01/data/DGSTD/archive/1_2_752604441.dbf*
3) alter database open;
4) alter system switch logfile;
now from rman
RMAN> connect target sys/system@DGSTD
connect auxiliary sys/system@GGR
connected to target database: DGPRM (DBID=578436102)
RMAN>
connected to auxiliary database: NOTREAL (not mounted)
RMAN>
run{
allocate channel prmy1 type disk;
allocate channel prmy2 type disk;
allocate channel prmy3 type disk;
allocate channel prmy4 type disk;
allocate channel prmy5 type disk;
allocate auxiliary channel stby1 type disk;
duplicate target database to ggr from active database
spfile
parameter_value_convert='DGSTD','GGR','/u01/data/DGSTD/','/u01/data/ggr/'
set db_file_name_convert='/u01/oradata/DGSTD/','/u01/data/ggr/'
set log_file_name_convert='/u01/oradata/DGSTD/','/u01/data/ggr/'
set 'db_unique_name'='ggr'
set 'audit_file_dest'='/u00/app/oracle/admin/ggr/adump'
set 'sga_max_size'='140m'
set 'pga_aggregate_target'='28940697'
nofilenamecheck;
and when output of rman reaches up below
Starting backup at 31-MAY-11
channel prmy1: starting datafile copy
input datafile file number=00001 name=/u01/data/DGSTD/datafile/system01.dbf
channel prmy2: starting datafile copy
input datafile file number=00002 name=/u01/data/DGSTD/datafile/sysaux01.dbf
in alert log of clone db it gives massive error saying
ARC3: Cannot archive online log based on backup controlfile
ARC2: Cannot archive online log based on backup controlfile
ARC3: Cannot archive online log based on backup controlfile
ARC2: Cannot archive online log based on backup controlfile
and it fill up whole fs. and finally duplicate command throws error.
not sure what i m missing of inside duplicate command or is it valid to duplicate database from snapshot standby.
can somebody light on it please
Edited by: user12281508 on Jun 1, 2011 10:26 AM
Edited by: user12281508 on Jun 1, 2011 10:28 AM

duplicate target database to ggr from active database
spfile
parameter_value_convert='DGSTD','GGR','/u01/data/DGSTD/','/u01/data/ggr/'
set db_file_name_convert='/u01/oradata/DGSTD/','/u01/data/ggr/'
set log_file_name_convert='/u01/oradata/DGSTD/','/u01/data/ggr/'
set 'db_unique_name'='ggr'
set 'audit_file_dest'='/u00/app/oracle/admin/ggr/adump'
set 'sga_max_size'='140m'
set 'pga_aggregate_target'='28940697'
nofilenamecheck;
}I think you should use standby cluase as
DUPLICATE TARGET DATABASE TO dup1 FOR STANDBY FROM ACTIVE DATABASE;

Unable to do a Full backup due to missing archived Files

I had setup everything to do a full backup and when the job started, it failed. It seems not able to find the archived file.
I had deleted the archived File earlier due to low storage space. Can anybody advised me ? Thanks in advance.
------From Job --------
switch logfile executed
Recovery Manager: Release 8.1.7.0.0 - Production
RMAN-06005: connected to target database: DB (DBID=97457188)
RMAN-06008: connected to recovery catalog database
RMAN> run {
2> allocate channel DB_Channel type disk format 'Z:\b_%u_%s_%p';
3> backup incremental level 1 ( database include current controlfile );
4> backup ( archivelog all
5> delete input );
6>
7> }
8>
RMAN-03022: compiling command: allocate
RMAN-03023: executing command: allocate
RMAN-08030: allocated channel: DB_Channel
RMAN-08500: channel DB_Channel: sid=15 devtype=DISK
RMAN-03022: compiling command: backup
RMAN-03025: performing implicit partial resync of recovery catalog
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-06052: no parent backup or copy of datafile 22 found
RMAN-03023: executing command: backup
RMAN-08008: channel DB_Channel: starting incremental level 1 datafile backupset
RMAN-08502: set_count=24 set_stamp=454219212 creation_time=FEB 19 2002 04:00:12
RMAN-08010: channel DB_Channel: specifying datafile(s) in backupset
RMAN-08522: input datafile fno=00002 name=E:\ORACLE\ORADATA\DB\RBS01.DBF
RMAN-08522: input datafile fno=00001 name=D:\ORACLE\ORADATA\DB\SYSTEM01.DBF
RMAN-08011: including current controlfile in backupset
RMAN-08522: input datafile fno=00009 name=H:\ORACLE\ORADATA\DB\CALL_H1.ORA
RMAN-08522: input datafile fno=00013 name=H:\ORACLE\ORADATA\DB\OPT1.ORA
RMAN-08522: input datafile fno=00015 name=H:\ORACLE\ORADATA\DB\CALL_H2.ORA
RMAN-08522: input datafile fno=00017 name=H:\ORACLE\ORADATA\DB\OPT2.ORA
RMAN-08522: input datafile fno=00022 name=H:\ORACLE\ORADATA\DB\CALL_H3.ORA
RMAN-08522: input datafile fno=00003 name=D:\ORACLE\ORADATA\DB\USERS01.DBF
RMAN-08522: input datafile fno=00004 name=E:\ORACLE\ORADATA\DB\TEMP01.DBF
RMAN-08522: input datafile fno=00006 name=E:\ORACLE\ORADATA\DB\INDX01.DBF
RMAN-08522: input datafile fno=00008 name=H:\ORACLE\ORADATA\DB\CALL_L1.ORA
RMAN-08522: input datafile fno=00010 name=H:\ORACLE\ORADATA\DB\TIC1.ORA
RMAN-08522: input datafile fno=00011 name=H:\ORACLE\ORADATA\DB\OTH1.ORA
RMAN-08522: input datafile fno=00012 name=H:\ORACLE\ORADATA\DB\SS1.ORA
RMAN-08522: input datafile fno=00014 name=H:\ORACLE\ORADATA\DB\REP1.ORA
RMAN-08522: input datafile fno=00016 name=H:\ORACLE\ORADATA\DB\CALL_L2.ORA
RMAN-08522: input datafile fno=00018 name=H:\ORACLE\ORADATA\DB\OTH2.ORA
RMAN-08522: input datafile fno=00019 name=H:\ORACLE\ORADATA\DB\REP2.ORA
RMAN-08522: input datafile fno=00020 name=H:\ORACLE\ORADATA\DB\SS2.ORA
RMAN-08522: input datafile fno=00021 name=H:\ORACLE\ORADATA\DB\TIC2.ORA
RMAN-08522: input datafile fno=00007 name=D:\ORACLE\ORADATA\DB\OEM_REPOSITORY.ORA
RMAN-08522: input datafile fno=00023 name=H:\ORACLE\ORADATA\DB\RCVCAT01.ORA
RMAN-08522: input datafile fno=00005 name=D:\ORACLE\ORADATA\DB\TOOLS01.DBF
RMAN-08013: channel DB_Channel: piece 1 created
RMAN-08503: piece handle=Z:\B_0ODH5LEC_24_1 comment=NONE
RMAN-08525: backup set complete, elapsed time: 00:02:48
RMAN-03023: executing command: partial resync
RMAN-08003: starting partial resync of recovery catalog
RMAN-08005: partial resync complete
RMAN-03022: compiling command: backup
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: DB_Channel
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: backup
RMAN-06089: archived log G:\ORACLE\ORADATA\DB\ARCHIVE\DBT001S03368.ARC not found or out of sync with catalog
Recovery Manager complete.
child process exited abnormally

The RMAN Crosscheck command only validates that what RMAN thinks is backed up really is.
The Change archivelog all validate is what you need to run when you delete archivelogs before they have been backed up by RMAN.
If you have to restore a backup that was made before you deleted the archive logs, you will not be able to perform a full recovery.
You may want to consider running just archivelog backups more often and have RMAN delete them after they have been successfully backed up. In Oracle9i Release 2, there is an option to delete the archive logs after they have been backed up X number of times in case you want the logs duplex archivelog backups.

Archive files and rman backup

Hi Experts,
For testing, I creates a testing DB. after that, I delete some archive file from physical side.
testing DB works well.
However, I tyr to back up thsi testing DB. I got below error message
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'D:\Oraclebackup\CLS\exports\RMAN\%U
new RMAN configuration parameters are successfully stored
released channel: ORA_DISK_1
Starting backup at 15-JAN-09
current log archived
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=142 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup plus archivelog command at 01/15/2009 15:18:13
RMAN-06059: expected archived log not found, lost of archived log compromises re
coverability
ORA-19625: error identifying file D:\test\ARC00001_0675529905.001
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
So How to fix this issue?
That means we can not delete any archive log files that we do not need it.
Otherwise there are a problemwhen we try to backup later
JIm

Hi Jim,
change archivelog all crosscheck ;
will do the trick.
You can purge archive files but do it within rman.
Add a line in your rman backup script which makes backup your database and archive files like this.
delete noprompt copy of archivelog all completed before 'SYSDATE-3';
Regards,
Tycho

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.

How to restore backup archived files

hi folks
i have backup the archived files ,now just for educational purpose i want to back up/restore database from these archived files what steps i will take,i read that control files should also be back up is it true if it is then why control files should be backed up..
if i have archive files and control files then what i will take step to restore the database after failure please tell me some steps.
umaisi
tks & regards

Now I'm eager to know also,if I have my weekly cold
backup,which is the datafiles,controlfiles and
redologs, and I do export bckup for my data
daily.and if the db crashes, what r the steps for me
to restore my data.will I be able to restore it upto
the date I took the last export? we dnt have archive
on and the RMAN is not working for past 10 months.You can use the colde backup to restore your database,
then truncate or drop user tables,
then use your daily export data to get the newest data.
HTH

Archive Files Log Backup in DB2

Similar Messages

Maybe you are looking for