Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!enews.sgi.com!news-hog.berkeley.edu!ucberkeley!newsfeed.stanford.edu!postnews1.google.com!not-for-mail
From: tashepkov@yandex.ru (Tim Ashepkov)
Newsgroups: comp.databases.oracle.server
Subject: ORA-30006 and distributed transaction
Date: 8 Aug 2003 12:08:43 -0700
Organization: http://groups.google.com/
Lines: 14
Message-ID: <673929a5.0308081108.28a03095@posting.google.com>
NNTP-Posting-Host: 205.172.241.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Trace: posting.google.com 1060369723 14923 127.0.0.1 (8 Aug 2003 19:08:43 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: 8 Aug 2003 19:08:43 GMT
Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:240119

In distributed transaction I can't set timeout to more than 60 seconds
using the following statement:

SELECT x FROM y@dblink FOR UPDATE WAIT n.

If rows in remote table are locked, and the value n <= 60, then this
select works as expected: it fails with ORA-30006 after timeout of n
seconds.

For any n > 60 the timeout does not exceed 60 seconds.

Is there any database or SQL*Net parameter that can cause this?

Thanks.