application is slow? what to check immediately [message #543763] |
Thu, 16 February 2012 13:42 |
janakors
Messages: 232 Registered: September 2009
|
Senior Member |
|
|
hi,
well i am asking a very basic question and novice in performance tuning of oracle databases so pardon me please.
one fine morning clients come up with a complaint that application is dead slow and application tier checked it and found nothing and i have been asked to see your DB, what straight away action i will take to see that to see if there any issue with my DB ? on EM and on sql
kindly advice
regards
janakors
|
|
|
|
|
Re: application is slow? what to check immediately [message #543768 is a reply to message #543765] |
Thu, 16 February 2012 14:31 |
ThomasG
Messages: 3212 Registered: April 2005 Location: Heilbronn, Germany
|
Senior Member |
|
|
Thats a query I use in my database every time someone complains "it is slow...."
select DISTINCT s.sid,s. SERIAL#, event, p1text, p1, p2text, p2,
p3text, p3,
wait_time, seconds_in_wait, state,
osuser, program,client_info, s.MODULE,
sql_text
from v$session s
join v$sql q ON q.hash_value = s.sql_hash_value
where event not in ('SQL*Net message from client',
'SQL*Net message to client',
'jobq slave wait')
AND event not like 'PX Deq Credit%';
It basically gives me a quick "which user is waiting for what database events, with which running sql".
95% of the time someone user is complaining about slowness that catches the problematic part for me.
(If the cause is really the database)
|
|
|
Re: application is slow? what to check immediately [message #543984 is a reply to message #543768] |
Sat, 18 February 2012 16:04 |
|
LNossov
Messages: 318 Registered: July 2011 Location: Germany
|
Senior Member |
|
|
1. your query should be problematic on very busy systems (unsorted long output, which is difficult for analysis),
2. a complete list of idle events is much longer,
3. some of 'PX Deq Credit%' events aren't idle.
So you have to improve your query.
|
|
|