If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Does anyone find the same problem before? How can this be solved? The possible solution I've found is to increase the value of the parameter 'DISTRIBUTED_LOCK_TIMEOUT' (default is 60 sec).

However, the Oracle Server I'm using is Oracle 8.1.6 and the parameter is already obsolete. Could this parameter still be set? If yes, is it needed to restart my database for the parameter to be effective?

My database is production 24x7 database with heavy trasaction traffic, any suggestion on solving the problem without restarting the database?

Re:ORA-02049: timeout: distributed transaction waiting for lock

Both of the databases are 8.1.6.

Actually, I face the problem when calling the stored procedure in Database A to process data in local table and then insert data to a table in Database B by making use of public synonym that points to the remote table via database link.

As the error message suggests, you have to treat it as a deadlock.
Find out which are the other transactions holding locks on the table. Kill the other transaction or convert lock type using dbms_lock package.