Here are the trace level (upto 12.2 version).
Trace Levels
1 = use dbms_output.put_line instead of writing into trace file
2 = enable dbms_stat trace only at session level
4 = trace table stats
8 = trace index stats
16 = trace column stats
32 = trace auto stats – logs to sys.stats_target$_log
64 = trace scaling
128 = dump backtrace on error
256 = dubious stats detection
512 = auto stats job
1024 = parallel execution tracing
2048 = print query before execution
4096 = partition prune tracing
8192 = trace stat differences
-- 11.1 onwards
16384 = trace extended column stats gathering
-- 11.2.0.2 onwards
32768 = trace approximate NDV (number distinct values) gathering
-- 12.1 onwards
65536 = Online trace
131072 = Automatic DOP trace
262144 = System statistics trace
-- 12.2 onwards
524288 = Advisor trace
Regards,
Vishal Gupta
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Martin Berger
Sent: 15 December 2017 22:24
To: Franck Pachot
Cc: Lothar Flatz; oracle-l@xxxxxxxxxxxxx
Subject: Re: dbms_stats.gen_selmap
Lothar,
Did you try to trace the dbms_stats activities?
Jared Still has documented some trace levels here:
https://blog.pythian.com/options-for-tracing-oracle-dbms_stats/ ;
hth
Martin
2017-12-15 15:14 GMT+01:00 Franck Pachot <franck@xxxxxxxxxx>:
Hi Lothar,
It seems related to online statistics gathering, which makes sense during an
insert append.
Regards,
Franck.
On Fri, Dec 15, 2017 at 1:40 PM Lothar Flatz <l.flatz@xxxxxxxxxx> wrote:
We could trace it back to an insert /*+ append */. I did a little
experiment. The call is actually related to dynamic statistics generation.
Am 15.12.2017 um 09:41 schrieb Lothar Flatz:
Hi,
this is a long running procedure on one of our DB's. According to
Morgans Library it is an undocumented subprogram. Does anybody know
what it does and when it is called?
Regards
Lothar
