Re: CPU intensive fetch

run the query from sqlplus. before you run it, run this first:

alter session set events '10046 trace name context forever, level 12';

then run the query and exit sqlplus. Go to your user dump dest directory and find the most recent trace file. Open it up and look for the "alter session" text near the top, to confirm that you have the right trace file. Zip it up and post it here. I will tell you exactly what is going on with your query.

• ricky

u783416748_at_spawnkill.ip-mobilphone.net wrote:

> Could someone perhaps help to explain the following.
> The query is VERY long so I haven't included it, but
> no table (7 of them) has more than 20 rows.
> The CPU time is genuine, it takes over the machine for 2 minutes,
> which seems excessive give the disk, query, and current values.
>
> call count cpu elapsed disk query current rows
> ------- ------ -------- ---------- ---------- ---------- ---------- ----------
> Parse 1 0.02 0.02 0 0 0 0
> Execute 1 18.65 18.68 0 0 0 0
> Fetch 2 118.81 120.05 1 19 28 1
> ------- ------ -------- ---------- ---------- ---------- ---------- ----------
> total 4 137.48 138.75 1 19 28 1
>
> TIA
>
> Eric
>
>
> --
> Sent by eric from deptj in field demon element from co within field uk
> This is a spam protected message. Please answer with reference header.
> Posted via http://www.usenet-replayer.com/cgi/content/new
  Received on Mon Apr 02 2001 - 17:27:22 CDT