My Oracle Support Banner

Excessive Archive Log Generation with INTERNAL and COMMIT operations (Doc ID 1070861.1)

Last updated on DECEMBER 17, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 11.2.0.2.0 [Release 9.2 to 11.2]
Information in this document applies to any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and environment data used represents fictitious data from the Oracle sample or bulit-in schema(s), Public Documentation delivered with an Oracle database product or other training material.  Any similarity to actual environments, actual persons, living or dead, is purely coincidental and not intended in any manner.

We see high archive log generation and most of the operations are internal. Using LogMiner, we get a similar output with the one below from v$logmnr_contents:

COUNT(1) USERNAME SESSION# OPERATION SEG_OWNER SEG_NAME
1 UNKNOWN 89 DELETE SCOTT EMP
4 UNKNOWN 89 UPDATE SCOTT EMP
..
343 UNKNOWN 89 START
14517 UNKNOWN 89 INTERNAL
14737 UNKNOWN 89 COMMIT



The internal operations are ten times up to hundred times higher than the normal DML.
Also, it can be observed that the internal operation is generated together with DML on a certain table, or
several specific tables.

Changes

No important changes made in the database. This problem can occur of the sudden.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.