Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

CRM On Demand - Administration (MOSC)

How to stop creating trace file that is created by FND_TRACE.START_TRACE

Jan 5, 2024 2:23AM in CRM On Demand - Administration (MOSC) 2 commentsAnswered

EBS 12.2.8

Database 12.1.0.2.0

Hello, experts.

There are many trace files that named

InstanceName_ora_UnixPid_ANONY_date_time

or

InstanceName_ora_UnixPid_APPS_date_time

created in Diag Trace directory.

They content

begin FND_TRACE.START_TRACE; end;

Reffers to doc id 556756.1

select * from dba_enabled_traces;

returned no rows selected.

Is there any idea to stop creating these trace files?

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month