Path: text.usenetserver.com!out02b.usenetserver.com!news.usenetserver.com!in02.usenetserver.com!news.usenetserver.com!postnews.google.com!l1g2000hsa.googlegroups.com!not-for-mail
From: meysam.khayatan@gmail.com
Newsgroups: comp.databases.oracle.server
Subject: finding solution 4 this Special DeadLock
Date: Sun, 10 Feb 2008 02:04:02 -0800 (PST)
Organization: http://groups.google.com
Lines: 48
Message-ID: <767a5292-ee6e-4ea3-b4b3-144eaf52b997@l1g2000hsa.googlegroups.com>
NNTP-Posting-Host: 195.146.50.75
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Trace: posting.google.com 1202637843 23566 127.0.0.1 (10 Feb 2008 10:04:03 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Sun, 10 Feb 2008 10:04:03 +0000 (UTC)
Complaints-To: groups-abuse@google.com
Injection-Info: l1g2000hsa.googlegroups.com; posting-host=195.146.50.75; 
 posting-account=56bI_AoAAAD6Sn6Z7_XEk8sSZzuosGJc
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 
 SV1),gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.1 www.esfahansteel.com:3128 (squid/2.5.STABLE14)
Xref: usenetserver.com comp.databases.oracle.server:441346
X-Received-Date: Sun, 10 Feb 2008 05:04:03 EST (text.usenetserver.com)

Dear friends
i have a problem in DeadLock
in udump alert log file  i have a deadlock that in trace file
described as below:
===============================================================
*** 2008-02-06 09:00:06.223
*** SESSION ID:(32.18099) 2008-02-06 09:00:06.219
DEADLOCK DETECTED
Current SQL statement for this session:
LOCK TABLE PER_ANALYSIS_CRITERIA IN EXCLUSIVE MODE
The following deadlock is not an ORACLE error. It is a
deadlock due to user error in the design of an application
or from issuing incorrect ad-hoc SQL. The following
information may aid in determining the deadlock:
Deadlock graph:
                                         ---------
Blocker(s)--------            ---------Waiter(s)---------
Resource Name              process session holds waits  process
session holds waits
TM-0000aa04-00000000       104      32                 X
496          195              SS
TM-0000aa04-00000000       496     195       SS
104          32                 X
session 32: DID 0001-0068-00000006	session 195: DID 0001-01F0-00000006
session 195: DID 0001-01F0-00000006	session 32: DID 0001-0068-00000006
Rows waited on:
Session 195: no row
Session 32: no row
Information on the OTHER waiting sessions:
Session 195:
  pid=496 serial=47814 audsid=21880507 user: 183/APPS
  O/S info: user: applprod, term: , ospid: 17365, machine: ESCOERP1
            program:
  client info: 86
0
  application name: ESCO_TRAIN_ATT_ABS, hash value=1926534256
  action name: Online-ESCO_TRAINING_RESP, hash value=2617383380
  Current SQL Statement:
  lock table PER_ANALYSIS_CRITERIA in row share mode
End of information on OTHER waiting sessions.
===============================================================
its all description in my trace file !!!!
i can't find reason this deadlock
i'm beginner in oracle dba
how can i analyse this trace file???
please tell me reason of this DeadLock and how can i solve it?
thx
Best Regards
