Hi.
Execute in sqltrace is for that particular session only whereas in statspack, it's system wide.
A lot of sessions might have executed the same query.
Best regards
| "VIVEK_SHARMA" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 11/17/2003 02:19 PM
|
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]> cc: (bcc: Rhojel Echano/Manila/PH/SGS) Subject: Trace versus Statspack data |
We are doing Interest processing on a SET of 10,000 Bank A/cs
Following SQL Query Shows DIFFERING values for :-
"Execute" from SQL_TRACE = 2584
"Executions" from Statspack report = 10,000
Qs. What is the reason for this?
SQL_TRACE :-
call count cpu elapsed disk query current rows
------- ------ -------- ---------- ---------- ---------- ---------- ----------
Parse 1 0.00 0.00 0 0 0 0
Execute 2584 0.55 0.55 0 10475 2783 0
Fetch 2584 0.50 0.51 0 0 0 2584
------- ------ -------- ---------- ---------- ---------- ---------- ----------
total 5169 1.05 1.06 0 10475 2783 2584
Statspack :-
CPU Elapsd
Buffer Gets Executions Gets per Exec %Total Time (s) Time (s) Hash Value
--------------- ------------ -------------- ------ -------- --------- ----------
51,271 10,000 5.1 23.0 4.31 3.95 1862033429
Module: [EMAIL PROTECTED] (TNS V1-V3)
select TO_CHAR(accrued_upto_date_cr,'DD-MM-YYYY HH24:MI:SS') ,TO
_CHAR(accrued_upto_date_dr,'DD-MM-YYYY HH24:MI:SS') ,TO_CHAR(las
t_accrual_run_date_cr,'DD-MM-YYYY HH24:MI:SS') ,TO_CHAR(last_acc
rual_run_date_dr,'DD-MM-YYYY HH24:MI:SS') ,TO_CHAR(booked_upto_d
ate_cr,'DD-MM-YYYY HH24:MI:SS') ,TO_CHAR(booked_upto_date_dr,'DD
Thanks
