Re: Distributed Transaction Timeout

From: Billy Verreynne <vslabs_at_onwe.co.za>
Date: 1998/04/05
Message-ID: <6g9rjr$s9j$1@hermes.is.co.za>#1/1

news.ns.net wrote in message <6g19tl$84i$1_at_aurora.ns.net>... <snipped>
>I realize that you can specify a lock timeout for distributed transactions
>in the init.ora file, but this is a different case -- the remote site is
>entirely unreachable before the transaction begins.

This is not a function of Oracle, but of the IP protocol stack I think. The socket connect() call does not support a timeout parameter, which means that the protocol stack will attempt a connection and wait for however long it has been configured to wait.

When the remote site is not available, try the ping command and see how long it takes. If it takes a few seconds to timeout (which I doubt), it means that Oracle itself is either waiting longer than it should, or retrying the connection. If it takes roughly the same time to timeout as the Oracle distributed connection, then you are hitting the actual timeout setting of the IP protocol stack.

regards,
Billy Received on Sun Apr 05 1998 - 00:00:00 CST