Too easy ;)
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
Coming soon one-day tutorials:
Cost Based Optimisation
Trouble-shooting and Tuning
Indexing Strategies
(see http://www.jlcomp.demon.co.uk/tutorial.html )
UK___March 19th
USA_(FL)_May 2nd
Next Seminar dates:
(see ht
Title: RE: How to dump UGA ??
KG,
That's what I am looking for ... which sessions have trace enabled ...?
Developers *forget* to disable tracing in their code when they move it to production ... so I have to investigate ..
Jonathan:
How about calling the DBMS_SYSTEM.READ_EV procedure?
I think this is simpler than going to the UGA dumps..
THe restriction with DBMS_SYSTEM is, you can not get
the event settings of the other sessions. But Dumps
can.
Best Regards,
K Gopalakrishnan
-Original Message-
Lew
Title: RE: How to dump UGA ??
Jonathan,
Thank you very much ...
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESP
If you want to see if tracing is on:
alter session set events 'immediate trace name events level 1';
(level 2 for process level events, level 4 for system).
You can obviously use the oradebug equivalent, or
the dbms_support package to fire this at another
session.
However - if you can read the
Title: RE: How to dump UGA ??
Thanks Jonathan,
I was trying to find where (and how) does it show that sql trace (or event 10046) is enabled in the session. Any pointers??
TIA
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra
If you use oradebug you can do:
oradebug dump heapdump 4
or
oradebug dump heapdump 4100
These options dump the UGA heap. The first
is structure only, the second includes content
and could get quite large.
Regards
Jonathan Lewis
http://www.jlcomp.demon.co.uk
Coming soon a new one-day
Title: How to dump UGA ??
Does anyone know the command to dump UGA?
TIA
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of