Path: text.usenetserver.com!out03b.usenetserver.com!news.usenetserver.com!in02.usenetserver.com!news.usenetserver.com!postnews.google.com!r29g2000hsg.googlegroups.com!not-for-mail
From:  CrazyKarma <skalki@gmail.com>
Newsgroups: comp.databases.oracle.server
Subject: Deadlock encountered
Date: Thu, 06 Sep 2007 08:27:21 -0700
Organization: http://groups.google.com
Lines: 19
Message-ID: <1189092441.492168.286450@r29g2000hsg.googlegroups.com>
NNTP-Posting-Host: 168.215.166.78
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1189092441 10562 127.0.0.1 (6 Sep 2007 15:27:21 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Thu, 6 Sep 2007 15:27:21 +0000 (UTC)
Cc:  skalki@gmail.com
User-Agent: G2/1.0
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1),gzip(gfe),gzip(gfe)
Complaints-To: groups-abuse@google.com
Injection-Info: r29g2000hsg.googlegroups.com; posting-host=168.215.166.78;
   posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0
Xref: usenetserver.com comp.databases.oracle.server:434512
X-Received-Date: Thu, 06 Sep 2007 11:27:21 EDT (text.usenetserver.com)

Using Oracle 10gR1

Apparently, enabling constraints with or without no validate option
and accessing that table across a DBLINK creates deadlock.  Steps are
broken down below

           *  Over a database link execute a block of code that will
disable, exchange partition and enable constraints.
          * Over a dblink query this specific table where the above
actions are taking place

You will encounter a deadlock. Wierd thing is when you query the table
in question on the local schema then you won't encounter deadlock.

Combination of DBLINK and enabling constraints creates deadlocks. is
this an expected behaviour? any rational explantion would help

-CrazyKarma