From oracle-l-bounce@freelists.org Tue Apr 12 09:15:34 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j3CEFXBK012774 for ; Tue, 12 Apr 2005 09:15:33 -0500 X-ClientAddr: 206.53.239.180 Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180]) by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j3CEFXem012770 for ; Tue, 12 Apr 2005 09:15:33 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 9685E93E20; Tue, 12 Apr 2005 08:13:23 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08167-10; Tue, 12 Apr 2005 08:13:23 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 1C27293F04; Tue, 12 Apr 2005 08:13:23 -0500 (EST) From: "John Dunn" To: Subject: SQL*Loader-908: Unable to lock table due to ORACLE error 54 Date: Tue, 12 Apr 2005 14:13:45 +0100 Message-ID: <009401c53f61$756f4050$3e04050a@johnman> MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-archive-position: 18349 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: jdunn@sefas.com Precedence: normal Reply-To: jdunn@sefas.com X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on air891.startdedicated.com X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=ham version=2.60 X-Spam-Level: We have a situation where batches of data are being loaded into a table using sqlldr all day long. sqlldr uses direct load for speed. At the same time we have a routine that deletes old records from the table. I believe that sqlldr needs to take an exclusive table lock...is that correct? Which would explain why I sometimes get Oracle 54 errors from sqlldr when the delete process is running? Is my analysis of this error correct? Any ideas on resolution? I presume conventional load does not take an exclusive table lock? Oracle version is 9.2 -- http://www.freelists.org/webpage/oracle-l