General guide for troubleshooting issue of redo log files that fill up the ArchiveLogs directory

Document ID : KB000029770
Last Modified Date : 14/02/2018
Show Technical Document Details

Troubleshooting issue of redo log files that fills up the ArchiveLogs directory

Normally the REDO log switches take place every 10-15 minutes. That means about 4 to 6 redo log files will be created in one hour. Sometimes it can create 1 tor more redo log files within one minute due to heavy database activity or a large database transaction. This rapid creation of redo log files can fill up the ArchiveLogs directory in less than one hour, and thus cause the eHealth to run out of disk space. This is because most eHealth intsallations only allocate 10 to 50 Gb for the ArchiveLogs directory. The immediate workaround is to stop eHealth server and Oracle, remove all of the redo log files under the ArchiveLogs directory, then start  Oracle and the eHealth server again. Then check the following to figure out why this occurred.

  1. Check to see if the deleteArchivelog job has run successfully within the last hour.
  2. Check to see if the weekly Db Maintenance job has run successfully.

  3. Check to see how old and how frequently the redo log files are generated. Also check the size of the redo logs, and send the output of ls –l.

  4. If a binary incremental save is scheduled, the archive logs will not be deleted until a full save is run. This may cause a major buildup of log files.
  5. Check error messages in the system log and oracle alert log during the time range when the redo log files accumulate. Any errors may provide clues regarding what database transaction, or what sql action, triggered the redo log file accumulation.

 Below are the possible solutions to fully resolve the problem,depending on the specific situation.

  1. Stop the eHealth server and database, delete the redo logs in ArchiveLogs directory, then restart the database and eHealth.

  2. Fix  the scheduled deleteArchiveLog job

  3. Find what heavy database transaction that may cause redo log file accumulation, and take action

  4. Resize the redo log files to make them larger to reduce the number of log switches

  5. Destroy, create and reload a recent database save that was saved prior to redo log accumulation.