Return-Path: Delivered-To: 2-oracle-l@orafaq.com Received: (qmail 32236 invoked from network); 21 Dec 2007 10:22:29 -0600 Received: from freelists-180.iquest.net (HELO turing.freelists.org) (206.53.239.180) by static-ip-69-64-49-119.inaddr.intergenia.de with SMTP; 21 Dec 2007 10:22:29 -0600 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 44A7E7DD5A1; Fri, 21 Dec 2007 11:22:29 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27349-03; Fri, 21 Dec 2007 11:22:29 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id B1D5D7DC7B5; Fri, 21 Dec 2007 11:22:28 -0500 (EST) Received: with ECARTIS (v1.0.0; list oracle-l); Fri, 21 Dec 2007 10:35:03 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 5E9F87DDFBA for ; Fri, 21 Dec 2007 10:35:03 -0500 (EST) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 19992-09 for ; Fri, 21 Dec 2007 10:35:03 -0500 (EST) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 3435D7DDF61 for ; Fri, 21 Dec 2007 10:35:02 -0500 (EST) Received: by an-out-0708.google.com with SMTP id b36so158974ana.101 for ; Fri, 21 Dec 2007 07:35:02 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:references:in-reply-to:subject:date:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language:message-id; bh=BWY40I8zDYUu2dNmoWliGJfGnu+N8cmXu8Y1XPIyayM=; b=wC/mGRfxKm53JfKcSWSfONdGgEJzDMFJG9DC3QAIeG4jF5LxyzwqanM3/RK65JCpBm7DnPvSc/tUzd6xIw3YPfFB2gD8AAdAiSE9eWf9x7nywu/MrPBlim5VJ00HrjMJ+kjE/J9l96WkGJedOT+Zew+hecL3FBYLN2v7dM5MBog= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:mime-version:content-type:content-transfer-encoding:x-mailer:thread-index:content-language:message-id; b=sYpi5gebWJ1E5Wn0jZ57DC9W4uYNO+C1aZynD7FuQQ2F69GOSg8xJDFt/ZnYCLQ9/OYPWMYB3OK7GHXKyi3b2RyAo8dL0CdU/QbrSefWETti23t+DMisYobOx8+u0qG7rAqVyxC0gF9BcEdxRILxkLWVl1u3Nk776H2vVCy0tyw= Received: by 10.100.247.14 with SMTP id u14mr2808774anh.85.1198251302785; Fri, 21 Dec 2007 07:35:02 -0800 (PST) Received: from UKJA ( [210.122.227.246]) by mx.google.com with ESMTPS id p33sm1881558elf.2.2007.12.21.07.34.59 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 21 Dec 2007 07:35:01 -0800 (PST) From: "Ukja.dion" To: "'Kurt Franke'" , "'oracle-l'" References: <853377594@web.de> In-Reply-To: <853377594@web.de> Subject: RE: Do selects block truncates? Date: Sat, 22 Dec 2007 00:34:49 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Language: ko Message-ID: <476bdd25.21c07e0a.3710.ffffce4f@mx.google.com> X-archive-position: 4087 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-to: oracle-l-bounce@freelists.org X-original-sender: ukja.dion@gmail.com Precedence: normal Reply-to: ukja.dion@gmail.com List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: oracle-l X-List-ID: oracle-l List-subscribe: List-owner: List-post: List-archive: X-list: oracle-l X-Virus-Scanned: Debian amavisd-new at localhost.localdomain >this is never a bug but is the consequence of enforcing statement-level read consistency >which is always guranteed by oracle. Can you explain in more detail? Which relationship does read consistency mechanism have with the blocking of truncate by select operation? I don't know no concept of "select" blocking any kind of operation in Oracle. (except some internal lightweight locks like latch or buffer lock, library cache lock/pin, blah blah blah) -----Original Message----- From: Kurt Franke [mailto:Kurt-Franke@web.de] Sent: Friday, December 21, 2007 10:35 PM To: 'oracle-l'; ukja.dion@gmail.com Subject: RE: Do selects block truncates? Hi, ... > > If select really blocks truncate, it's a amazing bug. :) > this is never a bug but is the consequence of enforcing statement-level read consistency which is always guranteed by oracle. the only exception from this mechanism is the complete refresh of a materialized view with "atomic_refresh => FALSE" which then does the truncate wether or not any select is runnig on the materialized view. active select on the materialized view will break then with ORA-08103 regards kf -- http://www.freelists.org/webpage/oracle-l