I agree with HTH. However, I would talk a look at the SQL the user is
executing when the poor performance is being experienced (what kind of query
or how many rows). You can get the SQL from the SGA (using some
dba/development tools) or the hard way and find it yourself.
Once you find it you can look at the Plan the optimizer generates for it.
You may just need some indexes on the right columns.
Tim
Connor McDonald wrote in message <380C5834.2567_at_yahoo.com>...
>R. Nettleton wrote:
>>
>> Hi,
>>
>> What is the first thing you do when a user complains of slow response
time
>> (every now and then, not all the time)? Every now and then I'll have a
>> complaint like this and no one else is complaining. Just curious.
>>
>> Thanks,
>>
>> Ron
>
>Could be a million things obviously...network, their PC etc...but if you
>want a quick look at their Oracle session
>
>select *
>from v$session
>
>Look for their username, what PC they're on, the program they're running
>etc. Once you locate them note down their STATUS, SID, and SQL_ADDRESS
>
>If STATUS is active then they're running a command at present, you can
>use SQL_ADDRESS to link to v$sql to find the text of that SQL and decide
>whether its a piece of junk SQL that's causing their problem.
>
>Once you have their SID, you can also query v$sesstat to see various
>performance indicators about that session...
>
>HTH
>--
>===========================================
>Connor McDonald
>"These views mine, no-one elses etc etc"
>connor_mcdonald_at_yahoo.com
>
>"Some days you're the pigeon, and some days you're the statue."
Received on Wed Oct 20 1999 - 00:35:03 CDT
