|
-
 Originally Posted by marist89
You will never understand what's truly going on until you dump the GUI.
Trace the process that is hanging. It most likely has nothing to do with SGA size or open_cursors.
hmmm...i wud have loved tracing but how am i to know which session will block others until it really blocks others..N if i start tracing after it blocks others, I am not likely to get the statement that really caused locking...Isn't it?
Originally Posted by LKBrwn_DBA
And, you will also get a better picture if you take a look at the trace (dump) files created by the deadlock(s).
It is only blocking other sessions and the problem corrects after 10-15 minutes....So how comes deadlock..
lucky
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|
Reply With Quote