Parse Calls Vs Executions - DB Configuration
445801Jun 16 2005 — edited Jun 16 2005i found it strange .. any help ?
regards
Sonal
--- In oracle_champions@yahoogroups.com, "ankit_inde" <JainAnkit@b...> wrote:
I issued the following statement on the Production DB.
select parse_calls, executions,
substr(sql_text, 1, 300)
from v$sqlarea
where command_type in (2, 3, 6, 7);
And find the following stats:
PARSE_CALLS EXECUTIONS SUBSTR(SQL_TEXT,1,300)
16 0 SELECT * FROM "V$LOG"
16 0 SELECT * FROM "V$SGA"
86 86 select 'x' from dual
4167 4167 SELECT USER FROM DUAL
17 0 SELECT * FROM "V$SESSION"
142 0 SELECT * FROM "V$SYSSTAT"
16 0 SELECT * FROM "V$VERSION"
15 32 SELECT USER FROM SYS.DUAL
8545 8545 delete com$ where obj#=:1
8604 8604 delete lob$ where obj#=:1
...
...
...
I understand that number of PARSE_CALLS shouldn't be close to that of
EXECUTIONS. But in here even simple statements like "SELECT USER FROM
DUAL"
have 4167 parse calls and executions.
What could be the reasons for this massive hard parsing of queries.
Could there be any DB parameter that governs this ?
Thanks and Regards,
Ankit
--- End forwarded message ---