Skip to Main Content

Breadcrumb

Question and Answer

Connor McDonald

Thanks for the question, Achim.

Asked: September 01, 2017 - 5:34 pm UTC

Last updated: September 02, 2017 - 7:19 am UTC

Version: XE 11.2.0.2.0, Express Edition

Viewed 1000+ times

You Asked

Hi Gentlemen,

if i have heavy DML operations, got this in alert_XE.log:
  Current log# 1 seq# 2063 mem# 0: /u01/app/oracle/fast_recovery_area/XE/onlinelog/o1_mf_1_d2fs5dqt_.log
Fri Sep 01 18:42:25 2017
Archived Log entry 2059 added for thread 1 sequence 2062 ID 0xa76b1c7a dest 1:
Fri Sep 01 18:43:28 2017
Thread 1 cannot allocate new log, sequence 2064
Checkpoint not complete
  Current log# 1 seq# 2063 mem# 0: /u01/app/oracle/fast_recovery_area/XE/onlinelog/o1_mf_1_d2fs5dqt_.log
Thread 1 advanced to log sequence 2064 (LGWR switch)
  Current log# 2 seq# 2064 mem# 0: /u01/app/oracle/fast_recovery_area/XE/onlinelog/o1_mf_2_d2fs5flp_.log
Fri Sep 01 18:43:31 2017
Archived Log entry 2060 added for thread 1 sequence 2063 ID 0xa76b1c7a dest 1:


logs are written every 3 minutes or every 3 seconds.
What can i do to avoid this?

Best regards

and Connor said...

"logs are written every 3 minutes or every 3 seconds."

Make your logs bigger for a start. This is not a guarantee - because ultimately it depends on the speed of your I/O subsystem to write redo, and write buffers from memory to the datafiles.

Details and examples on resizing here

https://uhesse.com/2010/01/20/how-to-change-the-size-of-online-redologs/





Is this answer out of date? If it is, please let us know via a Comment

More to Explore

Administration

Need more information on Administration? Check out the Administrators guide for the Oracle Database