Archived logs quickly filling up

DBA from the client site where one of our product is running is complaining that one of the processes from our application is generating too much redo and are filling up the archive redo log files quickly. How can i find the SQL which is creating the most redo?

Hi,
Enable STATSPACK/AWR on the database and monitor whats happening at the peak time.
If you would like to see which process/statement generated more redo then you need to mine the archive logs.
To monitor which process is currently generating redo then use the below query:
select b.name stat_name, sum(a.value)
from v$sesstat a, v$statname b
where a.statistic# = b.statistic#
and b.name like '%redo%'
group by b.name ;

Similar Messages

To generate email alert when archive logs fill

Hi. I was away yesterday and the archive logs were filling up and were at 92% when I got in this morning.
I need to have an email generated once the /archlogs directory fills past 90%.
The total size of that directory is 8064M. So once it hits around 7257M I would like an email fired to me and my boss.
Oracle 9.2.0.5.0
UNIX AIX 5.2

In addition to Sybrand's reply, you might want to consider some other factors.
First, when setting up email notifications, you need to adjust your expectations to account for the possible latency in email delivery. I have seen 'critical' emails take several hours to get through the system. This is not a function of Oracle, but of the email servers.
Second, if archivelog destination filling up is an ongoing problem, I'd be looking at how my archivelogs are backed up and deleted - how I do my housekeeping on that destination. You should have more important things to do than constant monitoring and responding to 'destination full' conditions.

Archive log filling up a gig per minute

Hi there,
No one is on the database amd every day now the archive log is filling up over a gig per minute so when I get in work in the morning the backup didn't run and the archive directory is full and the database is not available.
This has been happening for the last 6 days and I can't figure it out. I have to keep clearing out archive files to get the directory percentage down so a few users can run some reports.
This database is not growing at all. There is no data being added to it, its a histrical database for report running only.
Here is the file system, as you can see, big drive so I am at a loss.
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
3.1G 829M 2.2G 28% /
/dev/mapper/VolGroup00-LogVol_USR
4.0G 3.0G 813M 79% /usr
/dev/mapper/VolGroup00-LogVol_d01
160G 116G 36G 77% /d01
/dev/mapper/VolGroupBackup-LogVol_Backup
213G 195G 7.6G 97% /backup
/dev/sda1 99M 11M 84M 11% /boot
none 1.5G 0 1.5G 0% /dev/shm

user13286861 wrote:
Hi there,
No one is on the database amd every day now the archive log is filling up over a gig per minute so when I get in work in the morning the backup didn't run and the archive directory is full and the database is not available.
This has been happening for the last 6 days and I can't figure it out. I have to keep clearing out archive files to get the directory percentage down so a few users can run some reports.
This database is not growing at all. There is no data being added to it, its a histrical database for report running only.
Here is the file system, as you can see, big drive so I am at a loss.
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
3.1G 829M 2.2G 28% /
/dev/mapper/VolGroup00-LogVol_USR
4.0G 3.0G 813M 79% /usr
/dev/mapper/VolGroup00-LogVol_d01
160G 116G 36G 77% /d01
/dev/mapper/VolGroupBackup-LogVol_Backup
213G 195G 7.6G 97% /backup
/dev/sda1 99M 11M 84M 11% /boot
none 1.5G 0 1.5G 0% /dev/shmRun off a statspack report and post the "Instance Activity", "Top 5" and "Load Profile" sections here. Don't forget to use the "cost" tags to get the output in fixed font (see end of post).
Question 1 - what did you do 6 days ago ?
Question 2 - what method are you using for backups.
Guess 1 - you have a load of tablespaces in backup mode, and you're doing a lot of delayed block cleanout.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
To post code, statspack/AWR report, execution plans or trace files, start and end the section with the tag {noformat}{noformat} (lowercase, curly brackets, no spaces) so that the text appears in fixed format.
There is a +"Preview"+ tab at the top of the text entry panel. Use this to check what your message will look like before you post the message. If it looks a complete mess you're unlikely to get a response. (Click on the +"Plain text"+ tab if you want to edit the text to tidy it up.)

Managing ARCHIVE Logs in Oracle 10.2.0.3

I am working with a customer who seems to think there is a way of controling the database other than a custom JOB, script or RMAN in how it creates, manages and deletes its archive logs while running in archivelog mode. He wants the database to automatically delete obsolete archive logs. He also wants to control the duration in time between each time an archive log is written in order to stop the growth of archive logs and filling up disk space.
I am saying this is not possible. You either configure RMAN to delete the obsolete or expired archive logs based on your retention policy or do it manually in the Enterprise Manager or Grid Control Console by deletenig obsolete or expired logs.
Am I correct or am I off base here?

4.1.3 Sizing Redo Log Files
The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance. Undersized log files increase checkpoint activity and reduce performance.
Although the size of the redo log files does not affect LGWR performance, it can affect DBWR and checkpoint behavior. Checkpoint frequency is affected by several factors, including log file size and the setting of the FAST_START_MTTR_TARGET initialization parameter. If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control.
It may not always be possible to provide a specific size recommendation for redo log files, but redo log files in the range of a hundred megabytes to a few gigabytes are considered reasonable. Size your online redo log files according to the amount of redo your system generates. A rough guide is to switch logs at most once every twenty minutes.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14211/build_db.htm#sthref237
If you are talking about data guard then:
4.1.3 Sizing Redo Log Files
The size of the redo log files can influence performance, because the behavior of the database writer and archiver processes depend on the redo log sizes. Generally, larger redo log files provide better performance. Undersized log files increase checkpoint activity and reduce performance.
Although the size of the redo log files does not affect LGWR performance, it can affect DBWR and checkpoint behavior. Checkpoint frequency is affected by several factors, including log file size and the setting of the FAST_START_MTTR_TARGET initialization parameter. If the FAST_START_MTTR_TARGET parameter is set to limit the instance recovery time, Oracle automatically tries to checkpoint as frequently as necessary. Under this condition, the size of the log files should be large enough to avoid additional checkpointing due to under sized log files. The optimal size can be obtained by querying the OPTIMAL_LOGFILE_SIZE column from the V$INSTANCE_RECOVERY view. You can also obtain sizing advice on the Redo Log Groups page of Oracle Enterprise Manager Database Control.
It may not always be possible to provide a specific size recommendation for redo log files, but redo log files in the range of a hundred megabytes to a few gigabytes are considered reasonable. Size your online redo log files according to the amount of redo your system generates. A rough guide is to switch logs at most once every twenty minutes.
Automatic Deletion of Applied Archive Logs
Archived logs, once they are applied on the logical standby database, will be automatically deleted by SQL Apply.
This feature reduces storage consumption on the logical standby database and improves Data Guard manageability.
See also:
Oracle Data Guard Concepts and Administration for details
http://download.oracle.com/docs/cd/B19306_01/server.102/b14214/chapter1.htm#sthref269

Archive log directory full

Hello all,
I had a problem where my archive log dir filled up last night and corrupted a datafile.
I haave tried to do an incomplete recovery until just before the directory filled.
When running this recovery I get errors:
RMAN-03022: compiling command: IRESTORE
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: restore
RMAN-03002: failure during compilation of command
RMAN-03013: command type: IRESTORE
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 19 found to restore
RMAN-06023: no backup or copy of datafile 6 found to restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
I have Identified these datafiles as tmp, and rollback segment datafiles which I have not been backingup, because I didn't see the need to.
can anybody give advice on how to solve this issue.
Thanks,
Lenny

I ended up attempting a restore of the corrupt corrupt, and it worked. The database is up and running properly. Since I have done a full backup before releasing access to the company.
Thanks,
Lenny

Logical standby | archive log deleted | how to remove gap ???

hi gurus...
i have problem on logical standby
by mistake standby log coming to logical standby has been deleted , now how to fill up the gap ???
ON STANDBY
SEQUENCE# FIRST_CHANGE# NEXT_CHANGE# APPLIED
228 674847 674872 YES
229 674872 674973 CURRENT
230 674973 674997 NO
231 674997 675023 NO
232 675023 675048 NO
233 675048 675109 NO
234 675109 675135 NO
235 675135 675160 NO
236 675160 675183 NO
237 675183 675208 NO
238 675208 675232 NO
239 675232 675257 NO
240 675257 675282 NO
241 675282 675382 NO
242 675382 675383 NO
243 675383 675650 NO
244 675650 675652 NO
245 675652 675670 NO
246 675670 675688 NO
247 675688 675791 NO
248 675791 678524 NO
archive log are shipping to standby location also and getting registered
ALERT LOG OF STANDBY
Fri May 7 12:25:36 2010
Primary database is in MAXIMUM PERFORMANCE mode
RFS[21]: Successfully opened standby log 5: '/u01/app/oracle/oradata/BEST/redo05.log'
Fri May 7 12:25:37 2010
RFS LogMiner: Registered logfile [u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_248_1_715617824.dbf] to LogMiner session id [1]
but i dont have standby log after 229 sequence ...
ON PRIMARY
SYS@TEST AS SYSDBA> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /u01/app/oracle/flash_recovery_area/TEST/standlogOldest online log sequence 247
Next log sequence to archive 249
Current log sequence 249
what to do next to apply sequences and bring both in sync.
please help me ,,,,
Edited by: user12281508 on May 7, 2010 9:45 AM

thanks for response.
no its pure logical standby
i have tried to ftp the archive logs of primary to standby and applied manually
SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf';
alter database register logfile '/u01/app/oracle/flash_recovery_area/BEST/archivelog/archBEST_230_1_715617824.dbf'
ERROR at line 1:
ORA-01289: cannot add duplicate logfile
SYS@BEST AS SYSDBA> alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf';
alter database register logfile '/u01/app/home/archTEST_230_1_715617824.dbf'
ERROR at line 1:
ORA-01289: cannot add duplicate logfile
any other way ????

Archive log files are not being created

I am doing some testing of the backup and recovery of our databases.
I have a database which is in archive log mode.
I have added some records to a table and I am expecting to see some archive files
being written to but nothing is being produced.
We are running Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
The current archive information is as follows :
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 1
Next log sequence to archive 3
Current log sequence 3
SQL> show parameter db_recovery_file_dest;
NAME TYPE VALUE
db_recovery_file_dest string /export/flash_recovery_area
When I look in the directory as indicated above I see no files :
cd /export/flash_recovery_area/MRESTORE/archivelog/2013_04_16
(no files)
I'm wondering if I am missing something obvious here.
Thank you in advance.

user6502667 wrote:
I am doing some testing of the backup and recovery of our databases.
I have a database which is in archive log mode.
I have added some records to a table and I am expecting to see some archive files
being written to but nothing is being produced.
We are running Oracle Database 11g Release 11.2.0.2.0 - 64bit Production
The current archive information is as follows :
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 1
Next log sequence to archive 3
Current log sequence 3
SQL> show parameter db_recovery_file_dest;
NAME TYPE VALUE
db_recovery_file_dest string /export/flash_recovery_area
When I look in the directory as indicated above I see no files :
cd /export/flash_recovery_area/MRESTORE/archivelog/2013_04_16
(no files)
I'm wondering if I am missing something obvious here.
Thank you in advance.There can be several, but I'd say the most likely is that you simply didn't yet generate enough redo information to fill a redolog and thus trigger the writing of an archivelog.

Logs are filling up disk space

Dear all
i am facing a problem in my database
the database is in archive log mode and continuous archiving of log is filling up the disk space
please let me know what should i do so that at the end of activity there should be no complaints of logs filling up
i wil ensure the big disk space
please let me know what kind of administration i have to do with this issue ...

hello Sagar
when you use RMAN for backup you can set RETENTION POLICY for window of day or redundancy for example
RMAN> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS;
or
RMAN> CONFIGURE RETENTION POLICY TO REDUNDANCY 3;
and when you backup use "BACKUP ... PLUS ARCHIVELOG" for example
BACKUP DEVICE TYPE sbt
DATABASE PLUS ARCHIVELOG;
it cause that RMAN when backup your database , backup your archived logs too ;
and about that two first CONFIGURE command
first command cause backupfiles and archived log files that backuped up before than 3 days signed obsolete in V$BACKUP_FILES view
(you can query the V$BACKUP_FILES view and check the OBSOLETE column)
second command cause backupfiles and archived log files that backuped up 3 times signed obsolete in V$BACKUP_FILES view
and if you use "DELETE OBSOLETE ..." command in RMAN it delete obsolete files
and your archived logs that backued up and are obsolete will be delete
AND you can use DBMS_SCHEDULER for synchronize this routine
Message was edited by: khosravi
khosravi

Removing archived log files

Hello all,
Using Oracle 10g R2 ( 10.2.4.0) under UNIX Sun Solaris 10 , I have two rman backup types
1-L0 backup
2-L1 Backup ( Incremental cummulative)
Facts:
-Due to space pressure on archived log destination I'm trying to get less archived files possible under the archived log fs thus at any given time the archived log files destination contains archived log files aged no more than 22hours.
* The backup runs each day at 4PM and there is custom script that remove and compressed archived log files ( out of backup jobs windows) from midnight until 3:45PM
* From the above removal schedule task L0 or L1 backup will always have 24 hours worth of archived log files available during the backup.
-The Backup files Windows retention period is 22 hours meaning that each backup type L0 or L1 removes previous backup files aged more than 22hours.
-Tracking file is enabled
Target:
Knowing that our backup retention windows is 22hours.
Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup.
Would this affect L1 backup? and how?
Thank in advance for your response
Alex

user8979607 wrote:
Hello all,
Using Oracle 10g R2 ( 10.2.4.0) under UNIX Sun Solaris 10 , I have two rman backup types
1-L0 backup
2-L1 Backup ( Incremental cummulative)
Facts:
-Due to space pressure on archived log destination I'm trying to get less archived files possible under the archived log fs thus at any given time the archived log files destination contains archived log files aged no more than 22hours.
* The backup runs each day at 4PM and there is custom script that remove and compressed archived log files ( out of backup jobs windows) from midnight until 3:45PM
* From the above removal schedule task L0 or L1 backup will always have 24 hours worth of archived log files available during the backup.
-The Backup files Windows retention period is 22 hours meaning that each backup type L0 or L1 removes previous backup files aged more than 22hours.
-Tracking file is enabled
Target:
Knowing that our backup retention windows is 22hours.
Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup.
Would this affect L1 backup? and how?
Thank in advance for your response
AlexI'm not sure what you are talking about with Backup files Windows retention period ... 22 hours".
I don't know what you mean by "Our next goal is to get less than 2 hours from 24 hours of archived log files available when L0 or L1 backup."
If you are not taking your database backups with rman you are on shaky ground. The principles are simple. To recover your database from a failure, you will need to start with an L0 backup. The rman RESTORE command will then restore individual blocks from any applicable and available L1 backups. You would follow that with a RECOVER command, that would attempt to apply all necessary redo from available archivelogs. If the necessary archivelogs have been deleted, rman will attempt to restore them from a backup. You can use rman to backup AND DELETE archivelog files to keep the archivelog destination cleaned out.
I take an L0 backup once a week, an L1 the other 6 days, and archivelogs twice a day. The only time I've had a problem with the archivelog dest filling up is when some buggy code that has a loop goes into production and starts flooding redo.
Exactly how are you taking your database backups? If you are not using rman, then you are already on shaky ground.

Finding the order of archive logs in RAC to NON-RAC manual cloning

Hi,
I am in the process of automating a RAC to NON-RAC clone using traditional method [ not using RMAN ].
Here are the steps:
On Source:
Record the sequence number and thread of the instance
put the database in begin backup mode
copy the files
disable the backup mode
record the sequence number and thread of the instance
prepare the order of the archive logs which will be needed for recovery ==> Here is where I need help
On Target:
Restore the backup
Issue recovery using the order of archive logs identified ==> Failing as order is not correct.
I am finding the archive logs based on FIRST_TIME# and preparing the order which is not correct. I think i should be using SCN but not sure what should be the criteria.
Could you please let me know on what basis we can find the order of the archive logs which will be asked during the recovery ?
Your quick response is appreciated. Thanks in advance for your help.
Thanks
Suneel

Yes, When we execute recover database using backup controlfile until cancel, will prompt for the redo log sequences.
But as i mentioned before, I am trying script everything and cannot manually enter the sequence numbers required. I need to know the archives and thread it is going to ask [ in what order as well ] so that recovery command can be scripted in shell.
Please let me know if there is a away to find the order of archive logs which needs to be applied to recover [ if this is a NON-RAC, we can simply go with the sequence numbers but since it is a RAC, i should know the thread number as well ].
Thanks

Archive log mode

Hi
i m using oracle 10gR2 after installation i enable the archive log mode.
1) How can i determine the size of archive log?
2)When i enable the archive log mode after switch it genrate the second archive (01_MF_1_2_43.ARC) instead of first (01_MF_1_1_43.ARC) why?
Thanks

The size of archived logs will normally be the same as the size of online redo logs. However, if you switch the logs before the get filled with redo, the size of archived log will be smaller depending in the amount of redo.

DB backup and removal of archive log files?

I have an application that uses Oracle 10gR2 on Linux RedHat EL 4.5. The DB is fairly simple, so backing up daily or weekly by using expdp (Datapump) is fine for our needs. We have an install that uses Data Guard, which in archivelog mode is filling up the disks fast.
What is the best way to clean up archive log files in a Data Guard configuration? I have seen posts that indicate RMAN is tough to work with and has problems with recovery, so I would rather avoid it.
I would like script something on a daily or weekly basis.
Thanks,

RMAN not easy? Lets see how hard it is:
rman target /
RMAN> backup database;Surely that isn't too challenging.
Now if you want to do it properly you are talking about setting up a repository ... much more complex:
-- on the repository database server
CREATE USER repos
IDENTIFIED BY oracl1
DEFAULT TABLESPACE users
TEMPORARY TABLESPACE temp
QUOTA UNLIMITED on users;
GRANT create session, recovery_catalog_owner TO repos;
-- on the target server (your production db)
rman target / catalog repos/oracle1@<tnsnames_entry_for_your repository>
RMAN> create catalog;
RMAN> register database;
RMAN> backup database;If this is too much perhaps you should look into MS Access. <g>
All of this is documented at the top of the RMAN page in Morgan's Library at www.psoug.org so you can cut-and-paste your way through it if you want.
How is an export not a backup you ask?
The Oracle docs can be found at http://tahiti.oracle.com. You should consider reading them some time.
As I said before ... an export can NOT be used to recover ... ever. That says it all.
Your resistance to change. Your resistance to doing things properly. Your resistance to reading the docs. You'd better watch out. There are people who would like to have your job ... a lot of them.

OVM 3.0 Database Creating Lots of Archive Logs

Greetings - ever since we initially installed OVM 3.0 earlier this fall (~October), the OVM database has generated archive logs at a very rapid rate. It continually threatens to fill up our 16 GB filesystem dedicated to archive logs, even after daily backup and purging.
Our OVM database itself is about 4-6 GB large, and we would need to increase the archive log filesystem to about 20-25 GB in size, which we see as unreasonable for such a small database.
What is causing OVM to generate so many redo logs? Our best guess is that OVM is continuously gathering guest VM CPU usage on each physical server.
Is there a way to configure the OVM application in order to reduce the amount of redo/archive logs being created?
We are currently running 3.0.3, having upgraded each time a 3.0.* patch was released. OVMM running on OEL 6.1, database running on latest HP-UX.

majedian21 wrote:
Greetings - ever since we initially installed OVM 3.0 earlier this fall (~October), the OVM database has generated archive logs at a very rapid rate. It continually threatens to fill up our 16 GB filesystem dedicated to archive logs, even after daily backup and purging.I would log an SR with Oracle Support for this, so that Development can look at it. Sounds like your environment has lots of VMs running and yes, collecting usage stats for all of those environments. However, there may be some old data from the previous versions that's causing more stats to be collected than necessary.

Data Warehouse Archive logging questions

Hi all,
I'd like some opinions/advice on archive logging and OWB 10.2 with a 10.2 database.
Do you use archive logging on your non-production OWB instances? I have a development system that only has "on demand" backups done and the archive logs fill frequently. In this scenario, should I disable archive logging? I realize that this limits my recovery options to cold backups but on a development environment, this seems sufficient for me. Would I be messing up any OWB features by turning off archive logging?
For production instances, how large do you make your archive log (as a percentage of your total DW size perhaps)?
How do you manage them? With Flash recovery areas? Manually? RMAN or other tools?
Thanks in Advance,
Mike

Usualy, I don't set any DW tables to log. Since it's a data warehouse, I believe it's better to make cold backups. In some cases, ETL Mappings may work like backup procedures themselves.
In OWB, select the object you need (table or index) to create. Right-click it, select Configuration -> Performance Parameters -> Logging Mode -> NOLOGGING
Flash RecoveryDon't think it's going to help you, since most of your data manipulation is based on batch jobs.
RMANIf you want to make hot backups, this is something that can really help you manage backup procedures.
ManuallyMaybe... Why not?
I don't take hot backups from DW databases. I prefer to take cold backups. In a recovery scenario, you restore the cold backup and if it's 3 days late, I execute the ETL mappings for the last 3 days.
Regards,
Marcos

Delete old and backed up archive log,

Hi all,
Am trying to modify our RMAN backup script to delete old and backed up archive logs off the disk.
We run daily Incremental L0 or L1 backups, with 3 daily archive log backups. Currently we delete archive logs as they are backed up (backup archivelog all delete input). However, we are considering leaving x days worth of archive logs on disk, just in case, quick restore is needed (e.g. tablespace media recovery etc. etc.)
For example,
We can delete archive logs old tha n x (where x=no_days depending on database) by,
delete archivelog until time 'sysdate-15';
We can also delete archive logs that have been backed up to disk by,
delete archivelog all backed up 1 times to disk;
Questions,
1) Why does 'backed up 1 times to disk' require the 'all' in the statement ?
2) Is there any way to combine the 2 statements ? (backed up 1 times and older than x days ?). Just being a bit extra cautious to ensure that we have everything backed up. In real-world shouldn't be a problem, as we will be alerted to any backup failures, but trying to cater for the very worst situation.
Thanks for your help and insight.

Hi,
Scratch the questions. Found the answer in another thread. Seems when I tried to combine the statements initally, I had a typo.
It is now working as expected.
Thanks and regards,

Archived logs quickly filling up

Similar Messages

Maybe you are looking for