Deleting Archivelog files.

I'm trying to do some cleanup of my archivelog files that are over 30 days old that have been backed up using the command:
delete archivelog until time 'sysdate -30';
I get an ORA-15028 saying that a file is currently being accessed.
My question is how can I find out what is trying to access a file that is close to 40 days old?

Note the difference betweeen 'UNTIL TIME' and 'COMPLETED BEFORE'
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta008.htm#sthref121
Is your "latest" Level 0 backup more than 30 days old ? Or do you have Retention Policy exceeding 30 days ?

Similar Messages

How to delete archivelog file at standby database

Hi All,
I'm running Physical Standby Database on ASM. At standby database, I can see all logs using asmcmd:
ASMCMD> ls
thread_1_seq_14.330.625772527
thread_1_seq_15.346.625772527
thread_1_seq_16.329.625772527
thread_1_seq_17.327.625772559
thread_1_seq_18.324.625772599
thread_1_seq_19.341.625772367
thread_1_seq_2.325.625772329
But when I run RMAN to delete all these archivelogs, its give me error:
oradr:/u01/app/oracle$rman rcvcat rman/rman@rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thu Jun 28 13:50:41 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: AIXDB (DBID=2438430915, not open)
connected to recovery catalog database
RMAN> delete archivelog all;
Starting implicit crosscheck backup at 28-JUN-07:01:50:56
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 06/28/2007 13:50:56
RMAN-12010: automatic channel allocation initialization failed
RMAN-06004: ORACLE error from recovery catalog database: RMAN-20001: target database not found in recovery catalog
RMAN> register database;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of register command at 06/28/2007 13:51:06
RMAN-08040: full resync skipped, control file is not current or backup
Even it is not registering it. So how to delete archivelog file at standby database.
Thanks in Advance
Rakesh

This appears related to Bug 3298797 that was supposed to be fixed in 10.2.0.1. The workaround is to switch over to the standby, register the standby and then switch back.

RMAN in 10g database deletes archivelog files before standby receives them

Hi all,
We currently have problem with our Oracle 10gR1 database on Windows 2000 server in that the RMAN backups on the primary database delete archivelogs before the standby database can receive current and new archivelogs from primary database. What happens is that RMAN backs up the archivelogs and deletes them from disk before the archivelogs are sent to the standby. The standby then looks for these archivelogs on the primary but is unable to locate them. Whenever this happens, the production database (primary) hangs and we have to restart the instance on the primary. We have our Data Guard setup in maximum performance mode so this should not happen.
As a short term fix, we have changed the backups to have RMAN backup and delete the archive logs 15 minutes older than current time so that the standby can receive the logs and not have problems. Besides this fix is there a long term solution to the problem or is it a bug in Oracle 10g? The issue came up after we upgraded from 9i to 10g and never saw it before in 9i with RMAN and Data Guard physical standby databases.
Thanks
Ben Prusinski, Oracle DBA

thanks for answer...
did you managed to make it 'work'?
according to doc. if set on standby it should:
<>
Then, these files are eligible for deletion:
Archived redo log files in the flash recovery area that
were applied on the standby database.
<>
and this is to my understanding irespective to retention policy...unfortunately report obsolete does not report applied archived logs as eligable for deletion.
How this works in your case?
regards.
goran

Deleting archivelog files once applied to physical standby database

Hi,
Any procedure for automatically deleting the archivelog files after applied to physical standby database.

also pls see DataGuard: auto delete redo logs after applied to physical standby?

Using RMAN to delete unwanted archivelog files..??

Hi All,
How can i remove the unwanted archivelog files from the disk, to manage the disk space usage, using RMAN?
My 10g database is in ARCHIVELOG mode and the OS is RHEL ES Release 3
when i tried with 'delete expired archivelog all;', i got the result as follows:
RMAN> delete expired archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=363 devtype=DISK
specification does not match any archive log in the recovery catalog
Please update...
Many Thanks in advance.....!!!

with the delete all input, can i assume that the archivelog files has been got deleted...Don't you trust Oracle ? :-)
You should see two series of messages, like below
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=73 recid=1 stamp=599697994
input archive log thread=1 sequence=74 recid=2 stamp=599698064
input archive log thread=1 sequence=75 recid=3 stamp=599698103
input archive log thread=1 sequence=76 recid=4 stamp=599698138
input archive log thread=1 sequence=116 recid=44 stamp=600271740
input archive log thread=1 sequence=117 recid=45 stamp=600271859
input archive log thread=1 sequence=118 recid=46 stamp=600277637
channel ORA_DISK_1: starting piece 1 at 04-SEP-06
channel ORA_DISK_1: finished piece 1 at 04-SEP-06
piece handle=/home/ora102/flash_recovery_area/DB102/backupset/2006_09_04/o1_mf_annnn_TAG20060904T154722_2hrcmh13_.bkp tag=TAG20060904T154722 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:37
channel ORA_DISK_1: deleting archive log(s)
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_73_2h6ok83j_.arc recid=1 stamp=599697994
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_74_2h6omjb9_.arc recid=2 stamp=599698064
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_75_2h6onq39_.arc recid=3 stamp=599698103
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_08_28/o1_mf_1_76_2h6oosvn_.arc recid=4 stamp=599698138
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_09_04/o1_mf_1_116_2hr5tw8c_.arc recid=44 stamp=600271740
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_09_04/o1_mf_1_117_2hr5ym80_.arc recid=45 stamp=600271859
archive log filename=/home/ora102/flash_recovery_area/DB102/archivelog/2006_09_04/o1_mf_1_118_2hrcm58z_.arc recid=46 stamp=600277637
Finished backup at 04-SEP-06

Archivelog Mode Deleting archive files

Hey,
I have been reading about archivelog mode for a while and understand the concept and how it works. The one thing that is still alluding me is the removal/deleting of old archivelog files and how long I need to keep the files.
I hear people saying "backup your archive files", how long do I need to keep the backed up archive files?
What this sounds like to me is "you better keep every archive file ever created by your database in order to restore". This sounds silly to me but thats how I am interpreting this. Can someone please help me understand this a bit better?
Thank

Archive logs are normally backed up when a database backup is done. Some shops might backup archive logs more or less frequently. You need to keep the backuped archive logs for as long a necessary to meet the recovery policies set forth by the business.
For example, for some database that I manage the business decision is to retain backups for an entire year. Other database have a smaller time frame of 2 to 6 months and some are only a week. So you can see that I do not keep every archive log ever created, I just keep the ones necessary to fulfil the recovery policies set by the business.

Flash recovery area: archivelog file directory modification time

Using Oracle Database 10g Release 10.2.0.3.0 - 64bit (Standard Edition) on Solaris 10, SunOS 5.10 Generic_118833-33, archivelog files in the Flash Recovery Area are still present, after the time that they should have been made redundant and therefore deleted::
bvsmdb01-oracle10g $ date
Thu Jan 24 16:04:46 GMT 2008
bvsmdb01-oracle10g $ ls -lt archivelog
total 20
drwxr-x--- 2 oracle10g oinstall 1024 Jan 24 16:00 2008_01_24
drwxr-x--- 2 oracle10g oinstall 512 Jan 23 23:30 2008_01_19
drwxr-x--- 2 oracle10g oinstall 1536 Jan 23 23:04 2008_01_23
drwxr-x--- 2 oracle10g oinstall 1536 Jan 22 23:30 2008_01_18
drwxr-x--- 2 oracle10g oinstall 1536 Jan 22 22:53 2008_01_22
drwxr-x--- 2 oracle10g oinstall 1024 Jan 21 23:07 2008_01_21
drwxr-x--- 2 oracle10g oinstall 512 Jan 20 22:20 2008_01_20
bvsmdb01-oracle10g $
The archivelog directory for 2008_01_19 has a modification time of Jan 23 23:30 - this is almost 4 days after it was last written to.
The current redundancy setting in RMAN is shown in the output of show all:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
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 PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
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 OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/dbs/snapcf_kierli.f'; # default
So, the current retention policy is three days. It is 24/1 today - the archivelog directory from 19/1 should have been deleted by now, but it has not been.
The modification time for the archivelog directory 2008_01_19 has a modification time of Jan 23 23:30 2008.
Why is this? How can this be investigated? Does anyone have any suggestions?
Thanks
Jerry Mander

From 2 Day DBA:
Even after files in the flash recovery area are obsolete, they are generally not deleted from the flash recovery area until space is needed to store new files. As long as space permits, files recently moved to tape will remain on disk as well, so that they will not have to be retrieved from tape in the event of a recovery.
What is the current space used in the FRA and what is the FRA disk limit ?

Delete archivelogs using RMAN

Hi,
I usually delete archivelogs with RMAN with command as "DELETE ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE -1' if i have to clear the archivelogs to freeup space from the FRA.
My question is if i delete the archivelogs-does this deletes the records from the catalog also(I think so) if backed up to tape.In that case the catalog doesn't have info for these archives even if they are on tapes,correct?
So in case of recovery how can i restore them?
Thanks
Edited by: 822424 on May 15, 2011 7:28 PM

The RESYNC CATALOG that may be part of your backup script or implicitly executed by a Backup would synchronise from the control file to the catalog schema (repository).
I don't think that you can selectively decide what to not resync.
You can query RC_ARCHIVEDLOG (the STATUS column) in the repository and in V$ARCHIVED_LOG (which is against the controlfile)
i) before the DELETE executed by RMAN and
ii) again after the next BACKUP which does a RESYNC to see if changes are reflected.
Hemant K Chitale

Rman-08137 can't delete archivelog because the capture process need it

When I use the rman utility to delete the old archivelog on the server ,It shows :Rman-08137 can't delete archivelog because the capture process need it .how to resolve the problem?

It is likely that the "extract" process still requires those archive logs, as it is monitoring transactions that have not yet been "captured" and written out to a GoldenGate trail.
Consider the case of doing the following: ggsci> add extract foo, tranlog, begin now
After pressing "return" on that "add extract" command, any new transactions will be monitored by GoldenGate. Even if you never start extract foo, the GoldenGate + rman integration will keep those logs around. Note that this GG+rman integration is a relatively new feature, as of GG 11.1.1.1 => if "add extract foo" prints out "extract is registered", then you have this functionality.
Another common "problem" is deleting "extract foo", but forgetting to "unregister" it. For example, to properly "delete" a registered "extract", one has to run "dblogin" first:
ggsci> dblogin userid <userid> password <password>
ggsci> delete extract foo
However, if you just do the following, the extract is deleted, but not unregistered. Only a warning is printed.
ggsci> delete extract foo
<warning: to unregister, run the command "unregister...">
So then one just has to follow the instructions in the warning:
ggsci> dblogin ...
ggsci> unregister extract foo logretention
But what if you didn't know the name of the old extracts, or were not even aware if there were any existing registered extracts? You can run the following to find out if any exist:
sqlplus> select count(*) from dba_capture;
The actual extract name is not exactly available, but it can be inferred:
sqlplus> select capture_name, capture_user from dba_capture;
<blockquote>
CAPTURE_NAME CAPTURE_USER
================ ==================
OGG$_EORADF4026B1 GGS
</blockquote>
In the above case, my actual "capture" process was called "eora". All OGG processes will be prefixed by OGG in the "capture_name" field.
Btw, you can disable this "logretention" feature by adding in a tranlog option in the param file,
TRANLOGOPTIONS LOGRETENTION DISABLED
Or just manually "unregister" the extract. (Not doing a "dblogin" before "add extract" should also work in theory... but it doesn't. The extract is still registered after startup. Not sure if that's a bug or a feature.)
Cheers,
-Michael

Ye olde "delete archivelogs in standby" question

11.2.0.2.0
According to note
Configure RMAN to purge archivelogs after applied on standby [ID 728053.1]
oracle should remove archive logs if we have deletion policy set to "delete applied on standby" which I have set on primary and standby. Monitoring the alert log we see
"Deleted Oracle managed file /path/to/an/archive/log"
so we think cool, its removing them automatically. Question is, when does it delete them? Right now my standby is in sync, yet my alert log is only sporadically showing my logs being deleted which were applied hours ago which I can visibly verify.

Hemant K Chitale wrote:
Oracle automatically deletes archivelogs only when it needs to clear space in the FRA (db_recovery_file_dest).
Hemant K ChitaleI had thought this so tested.
SQL> SELECT
2 substr(name, 1, 30) name,
3 space_limit/(1073741824) AS Quota_GB,
4 space_used/(1073741824) AS Used_GB,
5 space_reclaimable/(1073741824) AS Reclaimable_GB,
6 number_of_files AS files
7 FROM
8 v$recovery_file_dest ;
NAME                             QUOTA_GB    USED_GB RECLAIMABLE_GB      FILES
/u00/oracle/flash_recovery_are        310 19.7361012     18.1420259         46
-- bring the db_recovery_dest_size to 20gb to so we know we're over 90%. according to that first note I posted, the FRA deems anything over 85% as space pressure
SQL> alter system set db_recovery_file_dest_size=20g scope=both;
System altered.
SQL> SELECT
2   substr(name, 1, 30) name,
3   space_limit/(1073741824) AS Quota_GB,
4   space_used/(1073741824) AS Used_GB,
5   space_reclaimable/(1073741824) AS Reclaimable_GB,
6   number_of_files AS files
7   FROM
8   v$recovery_file_dest ;
NAME                             QUOTA_GB    USED_GB RECLAIMABLE_GB      FILES
/u00/oracle/flash_recovery_are         20 19.7437358     18.1420259         47
SQL> So i waited a good ten minutes but still no extra logs cleared out.
So I switched the logs a couple of times in production as well to see would that help and we did get some deleted then to bring the space used down to 17.5.gb which is just below the 85% mark.
SQL> SELECT
2   substr(name, 1, 30) name,
3   space_limit/(1073741824) AS Quota_GB,
4   space_used/(1073741824) AS Used_GB,
5   space_reclaimable/(1073741824) AS Reclaimable_GB,
6   number_of_files AS files
7   FROM
8   v$recovery_file_dest ;
NAME                             QUOTA_GB    USED_GB RECLAIMABLE_GB      FILES
/u00/oracle/flash_recovery_are         20 17.5075302     15.6462598         47
SQL> quick experiment, dropped to 15gb which is below the 17gb currently used. And yes immediately, I can see the files being deleted.
so what I take from this is that if there is any space available in the 15% free then Oracle waits to be woken up by the receipt of a log from primary, sees that theres less than 15% free and deletes logs to below that limit. however, if the space free is less than the space used then oracle wakes up itself and deletes the logs. Cool.
Thanks hemant.
Edited to fix coding

Rman syntext for deleting archivelogs

I am looking for rman syntax to delete all archivelogs but leave last 30 minutes on the disk. I tried following but it did not work
delete archivelog until time ‘sysdate – 30/(24* 60)’
any help would be appreciated.
Thanks,
mkjoco

There was no error but RMAN was keep deleting extra logs that were created after the requested time. But good news is that it is working now with following command:
"delete copy of archivelog all completed before 'sysdate - 30/(24*60)';"
I found this on the net. It seems to me that RMAN was looking for first SCN time, in the log with "UNTIL TIME " but with "COPY OF" its look for file creation time.
Don't take my words this is my guess .... If someone can verify this would be nice
Thanks

Archivelog files and Rman backup

Hi all,
Please somebody guide me regarding the following concept.
We have the oracle server version 10.2.0.1.0, working with Windows OS,
I had set the parameter log_archive_dest_1 for locating archivelog files, then I had changed the archivelog files to the flash recovery area(located in another disk) by using the parameters db_recovery_file_dest_size and db_recovery_file_dest.
Now the archivelog files are being located at two different location. At this point, If I take backup for archivelog files with the aid of RMAN, then ,
How will the RMAN take backup from those two different locations?
Thanks&Regards,
Jai.

PROBLEM :
I have archivelogs duplexed - when running RMAN - rman backups up the archivelogs from both duplexed destinations - from the user manual - this should not be the case, any ideas?
Details:
I have archivelogs duplexed
I have the following set in rman :
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 2 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO DISK;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/backup/rman/WPPMD/control_%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 10 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/backup/rman/WPPMD/backup_%d_%T_%U' MAXPIECESIZE 10 G;
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'LOW' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE;
CONFIGURE ARCHIVELOG DELETION POLICY TO BACKED UP 1 TIMES TO DISK;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/app/oracle/product/11.2.0/dbhome_1/dbs/snapcf_WPPMD.f'; # default
When I run backups via a script :
backup incremental level=$RMAN_LEVEL database plus archivelog;
($RMAN_LEVEL changes between 0 and 1 depending on the day of the week)
It backs both duplex copies of the same archivelog
From the document :
Oracle10g / 11g - Getting Started with Recovery Manager (RMAN) [ID 360416.1]
It says :
Even if your redo logs are being archived to multiple destinations and you use RMAN to back up archived redo logs,
RMAN selects only one copy of the archived redo log file to include in the backup set. (Since logs with the same log sequence number are identical, there is no need to include more than one copy.)
But this is not the case ie
RMAN> list archivelog sequence 2445;
using target database control file instead of recovery catalog
List of Archived Log Copies for database with db_unique_name WPPMD
=====================================================================
Key Thrd Seq S Low Time
4640 1 2445 A 17-DEC-10
Name: /log/recovery_area/WPPMD/archivelog2/1_2445_735315419.dbf
4639 1 2445 A 17-DEC-10
Name: /log/recovery_area/WPPMD/archivelog/2010_12_17/o1_mf_1_2445_6jpx9n7c_.arc
So it still backing up both copies of the archive log.
Any ideas? is this a bug?
Thanks
Luca
Edited by: user4599449 on 17-Dec-2010 07:05
Edited by: user4599449 on 17-Dec-2010 07:06

Which archivelog files can be safely removed from OS

Hi,
I didn't used "delete input" option when backup the archivelog files. So all archivelog files still remain on the file system. How can I identily which archivelog files I can delete using the command
"RMAN>change archivelog '/u04/arch/arch_xxx.arc' delete; "
where xxx is the seq I need to make sure it's safe to be removed.
I need to make sure "restore archivelog all validate" command will still report successful afterward. The total size of archivelog files is over 20GB and I'm running out of space now. Thanks.

The only way to delete your archlog is do not do a cross check archivelog all. Bec that will invalidate your archlogs. We have a rentetion of 28 days and we dlete archlogs after everybackup using delete input. While doing cross check we use "cross check completed before 'xxx'" and then it still keeps active in repo.
Regards,
http://askyogesh.com

ReDoLog & ArchiveLog files

My ReDoLog & ArchiveLog files are growing too fast. they are eating a lot of computer spaces. Can I delete those old files? How?
I'm with 10g, and windowXP

My ReDoLog & ArchiveLog files are growing too fast. they are eating a lot of computer spaces. Can I delete those old files? How? Redo logs must be added by you with some purpose (I guess). You will be a better judge to decide that you need to drop it or not.
You can drop the redo log groups using following command once those are not in use:
ALTER DATABASE DROP LOGFILE GROUP <group number>;
Regards,
S.K.

Rman delete old file and recover

Hi Friends,
after full backup.
we use below syntax to delete old file.
delete noprompt archivelog until time '(SYSDATE - 10)';
However, we get a message that file is used and delete failure. ramn stop process.
my question:
does the old archivelog file is deleted ot not?
If the old archivelog file is delete, do we have any command like sql rollback to recover it?
any other commane to recover mis comman in ramn.
or we must recover it?
Thanks,
ji

user589812 wrote:
Hi Friends,
after full backup.
we use below syntax to delete old file.
delete noprompt archivelog until time '(SYSDATE - 10)';
However, we get a message that file is used and delete failure. ramn stop process.
Please paste the error here.
my question:
does the old archivelog file is deleted ot not?
If the old archivelog file is delete, do we have any command like sql rollback to recover it?
any other commane to recover mis comman in ramn.
or we must recover it?
Thanks,
jithere is no any command sort of rolback to recover archivelog,if you have backup of archivelog then you can restore
archivelog from this archivelog backupset.
RMAN>restore archivelog all
Khurram

Deleting Archivelog files.

Similar Messages

Maybe you are looking for