Oracle Articles, Oracle Tools, Oracle Tips, Database Articles and DBA Tips  

The Largest Online Resource for Oracle Articles, Oracle Tips, Oracle Scripts & Oracle Tools!!


Enter your Email:
 
Navigate at FreeMegaZone Home      Articles      Tools      Jobs      Games      Support      Submit Content      Advertise
Advertise at http://www.articles.freemegazone.com

Advertise at FreeMegaZone

Give tremendous boost to your business by advertising at FreeMegaZone. Contact webmaster@freemegazone.com

 


Rating: *****                                             Rate this article:    

One of the many problems that the users that are using the databases are currently facing at the current stage is the problem related to “thread 1 is unable to allocate new log, sequence 124825, all online logs need archiving”.

ARCH: Connecting to console port…
Thread 1 cannot allocate new log, sequence 124825
All online logs needed archiving

While checking up the connection most users did report this error was coming up when they had the active connection checked up and their connection was refused from the web server. Upon verifying the logs most Application user connections were refused for 10 minutes or less. The information alert file did generate the following syntax upon verification. nd below information alert.

log_archive_max_processes value is 2 & redo log file size is 250 MB which is for 3 Groups only.

The problem is mainly due to the high rate of transactions or the frequent occurance of the DML process that pile up to generate the error related to the archiever which is than unable to achieve the online redo log files. The best way to solve this problem is to go over the steps that are described below to get the allocation process rectified.

  • Get the log_archive_max_processes increased from 2 till 5
  • Add up more new online redo log groups, if you have 3 groups than try getting them to be 5
  • Get the size of the online redo log file increased from 250MB to 500MB

Once done with the steps do ensure yourself by checking up the active user connection again and try retrieving the information log for it. If the problem still persist than try performing the steps again and do look for any possible errors that might have taken place while performing these 3 steps for it. The process is quite reliable and will get the problem solved once properly executed.

 More Oracle Articles, Database Articles and DBA Tips

  Database Security: Step by step guideline

  Oracle Multitable Inserts, Important Concerns!!

  Top-N Queries for Oracle - SQL, Some Concerns

  Oracle: A Guide to determine Best Execution Plan

  Reusing Databases - A good approach


 

 
HOME      ABOUT US      SUPPORT      SITE MAP      PRIVACY POLICY      TERMS OF USE      SUBMIT CONTENT      ADVERTISE
Copyright © 2007 - 2012 Oriole Intellect Inc. All rights reserved.

The name Oracle is a trademark of Oracle Corporation. Any other names used on this website may be trademarks of their respective owners