You will have to turn on timed-statistics for the entire database using
'alter system set timed_statistics=true'.
Igor Neyman, OCP DBA
Perceptron, Inc.
(734)414-4627
[EMAIL PROTECTED]
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Wednesday,
I used the following syntax/package to run a trace on a user's already
running
session.
EXECUTE dbms_system.set_sql_trace_in_session(8,12,TRUE);
I then ran tkprof on the resulting trace file. It all worked fairly well
but
I didn't get any times on any of the statements that executed.
Is
There is another way.
I'm managing user's environment with a procedure
called by a db_startup on logon trigger.
In that procedure, I'm changing the environment with
dynamic sql depending on the user.
This is how I'm setting up sort_area_size,
hash_area_size,... specifically per user.
HTH
Which version of Oracle.
From 8.1.6 onwards, dbms_system contains
a call similar to set_sql_trace_in_session
which is name something like:
set_boll_param_in_session. Describe
dbms_system to check the proper
nmame and parms.
Jonathan Lewis
Seminars on getting the best out of Oracle
Last few
Jonathan,
Version is 8.0.4. I looked at the parameters for dbms_system in the 8.0.4
documentation
and saw nothing pertaining to timed_statistics.
I did an alter system over lunch and set timed statistics for the entire
database without
bouncing the database. That did the trick.
Thanks for
Stephane,
This sounds very clever. However, it's too much work for me today as I
have so
irons in the fire.
I'll keep it in mind for the future, though.
Thanks for taking time to reply.
Cherie
Igor,
Thanks for your reply. I decided to just turn it on for the whole database
for a few minutes
over lunch.
Cherie
Igor Neyman
Do you know what does procedure WAIT_FOR_EVENT in this package is doing?
Alex Hillman
-Original Message-
Sent: Wednesday, August 08, 2001 1:56 PM
To: Multiple recipients of list ORACLE-L
Which version of Oracle.
From 8.1.6 onwards, dbms_system contains
a call similar to
This should do it; (works for me - I'm on 8.1.6.3)
as system/manager...
select sid,serial# from v$session where ...(to get process you want to
enable trace for);
exec dbms_system.set_sql_trace_in_session(sid,serial#,true);
exec
It's pure 8.1.6+
something like:
dbms_system.set_bool_param(sid, serial,'parameter',true/false);
I don't think there is ANYTHING sneaky
you can do prior to 8.1.6;
alter system is the only option for avoiding
the bounce.
Jonathan Lewis
Seminars on getting the best out of Oracle
Last few
10 matches
Mail list logo
