Re: Did anyone had problems with trace files in database 12c patch 13
- From: Martin Berger <martin.a.berger@xxxxxxxxx>
- To: jcdrpllist@xxxxxxxxx
- Date: Tue, 4 Nov 2014 14:27:02 +0100
can you share the trace and the (missing) query (sql_id should be enough)?
Without a proper system at hand I'd guess tkprof claims the query as a
recursive one - but that's pure guesswork right now.
On Tue, Oct 28, 2014 at 8:41 PM, Juan Carlos Reyes Pacheco <
jcdrpllist@xxxxxxxxx> wrote:
> Hello please.
> I always had used tkprof, hundreds of times, and never had problems.
>
> Recently I made a trace I got from jasper reports on 12c patch 13 (3
> times).
> And tkprof simple didn't showed me the queries, opening the trace, the
> queries was there.
>
> I used tkprof from 11g and the same problem.
>
> I run on it on
> http://www.ubtools.com/web/public/products/itrprof/itrprof_run
>
> And I got some error lines (I suppose some features not covered in 11g)
> But it showed me all the queries, and everthing ok.
>
> Thank you :)
>
> note.- I use this trigger to enable trace
>
> CREATE OR REPLACE TRIGGER TGR_ENABLE_TRACE
> AFTER
> LOGON
> ON DATABASE
> DECLARE
> cUSR_LHABILITA_TRACE VARCHAR2(1);
> BEGIN
>
> SELECT USR_LHABILITA_TRACE
> INTO cUSR_LHABILITA_TRACE
> FROM DAZ.UTL_USUARIO_SIS_ME
> WHERE USR_NOMSIS=USER;
>
> IF cUSR_LHABILITA_TRACE='T' THEN
> EXECUTE IMMEDIATE 'alter session set TIMED_STATISTICS=TRUE';
> EXECUTE IMMEDIATE 'alter session set STATISTICS_LEVEL=ALL';
> EXECUTE IMMEDIATE 'alter session set max_dump_file_size=UNLIMITED';
> EXECUTE IMMEDIATE 'ALTER SESSION SET EVENTS ''10046 TRACE NAME CONTEXT
> FOREVER, LEVEL 12''';
> EXECUTE IMMEDIATE 'alter session set sql_trace=true';
> EXECUTE IMMEDIATE 'alter session set
> TRACEFILE_IDENTIFIER='''||USER||'''';
> END IF;
> END;
> /
>
--
Martin Berger martin.a.berger@xxxxxxxxx
Lederergasse 27/2/14 +43 660 660 83306
1080 Wien http://berxblog.blogspot.com
Other related posts:
