My Oracle Support Banner

Excessive Trace Generation in Foreground and/or Background Trace Files (Doc ID 2334195.1)

Last updated on JUNE 09, 2022

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

Database (RAC or Single Instance) is generating excessive trace file sizes for Foreground and/or Background trace files.  Many of these files will grow rapidly in size (particularly Shared Server and Foreground traces).  Review of the generated trace files show SQL_TRACE types of events in the trace. Keywords indicating SQL_TRACE or 10046 (event for SQL_TRACE) is enabled include:

PARSING IN CURSOR
PARSE
BINDS
EXEC
FETCH
WAIT
CLOSE

Here is an example of a foreground trace:

 <MOS Document 436036.1> (How To List All The Named Events Set For A Database) was reviewed and verified that NO EVENTS were set/enabled.

Changes

 

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.