From oracle-l-bounce@freelists.org Wed May 4 16:06:08 2005 Return-Path: Received: from air891.startdedicated.com (root@localhost) by orafaq.com (8.12.10/8.12.10) with ESMTP id j44L67u4029901 for ; Wed, 4 May 2005 16:06:07 -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 j44L674Z029896 for ; Wed, 4 May 2005 16:06:07 -0500 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id D014019091D; Wed, 4 May 2005 15:03:32 -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 27706-01; Wed, 4 May 2005 15:03:32 -0500 (EST) Received: from turing (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 45D09190623; Wed, 4 May 2005 15:03:32 -0500 (EST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type; b=lAEbHpg8HU9W8OEjVb0nad9qi47O0hWqKqa+K8mPXw+CYO7YxBD8b1VRRtEIYFQ3ReHwFBlO4CANa7nwhGJyDogY4m7MbdDUVT5Fytrk08ik0eSe0L0GC4zfHl8PIevft2av2rBU/EWCmq+uxv/ALoOoH4JzVubMcPKiLCv3Xp0= Message-ID: Date: Wed, 4 May 2005 16:01:43 -0400 From: Robyn To: Oracle-L Freelists Subject: SAP and 9.2.0.6; histograms can now be a very bad thing? Mime-Version: 1.0 Content-type: text/plain Content-Transfer-Encoding: 8bit X-archive-position: 19346 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-To: oracle-l-bounce@freelists.org X-original-sender: robyn.sands@gmail.com Precedence: normal Reply-To: robyn.sands@gmail.com X-list: oracle-l X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on air891.startdedicated.com X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,NORMAL_HTTP_TO_IP autolearn=no version=2.63 Hello everybody, According to SAP, Oracle had 'a bug that meant that even if bind varibales where used, accesses via columns with only one distinct value could be better analyzed by a factor of 100 if histrams were created for these columns.' Again, according to SAP, this bug was fixed in 9.2.0.6, which has resulted in performance issues for SAP databases on 9.2.0.6 . The fix is to remove histograms by reanalyzing the tables without the "for all columns" clause. Was this really a "bug" for Oracle or is SAP just trying to pass the buck on this one? I thought bind variable peeking was plus, and our non-SAP systems using bind variables and the "for all columns" clause have not experienced performance problems after an upgrade to 9.2.0.6 . Has anyone else exerienced problems with upgrading an SAP system to 9.2.0.6? We're on HP-UX. tia ... Robyn -- http://www.freelists.org/webpage/oracle-l