We have a job that copies data in a table on a remote database to a local database through a database link. Here are the steps in the job:
1. truncate the table of t1 on the local database 2. insert into t1 select * from [EMAIL PROTECTED] 3. commit
There are only 847 records in the table. The job completes in 1 sec normally. However, last Sunday we got ORA-02049: timeout: distributed transaction waiting for lock during commit process. As my understanding, the error comes from a DML statement that requires locks on a remote database can be blocked if another transaction own locks on the requested data. I'm pretty sure that there were no any activities on the remote database since the application was not open. Also I can see from the log file (see below) that 847 records were inserted into the t1 table on the local database. The error was generated during the commit process. Does any one have any comments? Thanks for any input.
Here is the job log file: 847 rows created.
commit * ERROR at line 1: ORA-02049: timeout: distributed transaction waiting for lock
We are in Oracle 8.1.7.4 and SunOS 5.8. We take the default value for DISTRIBUTED_LOCK_TIMEOUT .
Dave
_________________________________________________________________
Get a FREE computer virus scan online from McAfee. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
-- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: David Boyd INET: [EMAIL PROTECTED]
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
