guys,

I see many trace files being generated in a user's UDUMP directory. There is no tracing turned on ( as far as I know). Its a 8.1.7.4 instance on Solaris.

SQL> show parameter trace

NAME TYPE VALUE
------------------------------------ ------- ------------------------------
log_archive_trace integer 0
oracle_trace_collection_name string
oracle_trace_collection_path string ?/otrace/admin/cdf
oracle_trace_collection_size integer 5242880
oracle_trace_enable boolean FALSE
oracle_trace_facility_name string oracled
oracle_trace_facility_path string ?/otrace/admin/fdf
sql_trace boolean FALSE
tracefile_identifier string

Output of one of the trace file:

Oracle8i Enterprise Edition Release 8.1.7.4.0 - Production
With the Partitioning option
JServer Release 8.1.7.4.0 - Production
ORACLE_HOME = /u02/app/oracle/product/8.1.7
System name: SunOS
Node name: Node1
Release: 5.9
Version: Generic_117171-02
Machine: sun4u
Instance name: PROD
Redo thread mounted by this instance: 1
Oracle process number: 13
Unix process pid: 26122, image: [Email Address Removed] (TNS V1-V3)

*** 2004-08-03 10:19:35.232
*** SESSION ID:(13.5555) 2004-08-03 10:19:35.231
NOTICE: COMMITTED THE TRANSACTION
*** 2004-08-03 10:20:01.690
NOTICE: COMMITTED THE TRANSACTION

What else can I look at to see why these files are being generated?

Regards,
Seema

Oracle LazyDBA home page