Received: (qmail 14274 invoked from network); 2 Feb 2009 14:08:26 -0600 Received: from freelists-180.iquest.net (HELO turing.freelists.org) (206.53.239.180) by static-ip-85-25-126-90.inaddr.intergenia.de with SMTP; 2 Feb 2009 14:07:55 -0600 Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 283ADB902D4; Mon, 2 Feb 2009 15:06:56 -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 07252-04; Mon, 2 Feb 2009 15:06:56 -0500 (EST) Received: from turing.freelists.org (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 96FD3B902D1; Mon, 2 Feb 2009 15:06:55 -0500 (EST) Received: with ECARTIS (v1.0.0; list oracle-l); Mon, 02 Feb 2009 15:04:48 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 2853DB90212 for ; Mon, 2 Feb 2009 15:04:48 -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 06926-09 for ; Mon, 2 Feb 2009 15:04:48 -0500 (EST) Received: from SG2EHSOBE001.bigfish.com (outbound-sin.frontbridge.com [207.46.51.80]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 37196B90160 for ; Mon, 2 Feb 2009 15:04:30 -0500 (EST) Received: from mail38-sin-R.bigfish.com (10.3.40.3) by SG2EHSOBE001.bigfish.com (10.3.40.21) with Microsoft SMTP Server id 8.1.291.1; Mon, 2 Feb 2009 20:04:24 +0000 Received: from mail38-sin (localhost.localdomain [127.0.0.1]) by mail38-sin-R.bigfish.com (Postfix) with ESMTP id F1C811BC80AF; Mon, 2 Feb 2009 20:04:23 +0000 (UTC) X-BigFish: VPS-22(zz9370Pf01M936fM9371Pzzzz5a6ciz2ei6bh43j61h) X-Spam-TCS-SCL: 0:0 Received: by mail38-sin (MessageSwitch) id 1233605061334594_23717; Mon, 2 Feb 2009 20:04:21 +0000 (UCT) Received: from AAPQHTCAS04.proque.st (unknown [165.215.94.2]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail38-sin.bigfish.com (Postfix) with ESMTP id 8ADE7C08060; Mon, 2 Feb 2009 20:04:18 +0000 (UTC) Received: from AAPQMAILBX02V.proque.st ([fe80::a5a3:d005:a27c:9314]) by AAPQHTCAS04.proque.st ([fe80::6883:b760:3780:b2db%10]) with mapi; Mon, 2 Feb 2009 15:04:16 -0500 From: "Bobak, Mark" To: "stmontgo@gmail.com" , "oracle-l@freelists.org" Date: Mon, 2 Feb 2009 15:04:12 -0500 Subject: RE: Large block sizes for OLAP database Thread-Topic: Large block sizes for OLAP database Message-ID: <6AFC12B9BFCDEA45B7274C534738067F0B5C1778@AAPQMAILBX02V.proque.st> References: <0016367ed4e1da4edd0461f4ac6a@google.com> In-Reply-To: <0016367ed4e1da4edd0461f4ac6a@google.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_6AFC12B9BFCDEA45B7274C534738067F0B5C1778AAPQMAILBX02Vpr_" MIME-Version: 1.0 X-archive-position: 14392 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-to: oracle-l-bounce@freelists.org X-original-sender: Mark.Bobak@proquest.com Precedence: normal Reply-to: Mark.Bobak@proquest.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 --_000_6AFC12B9BFCDEA45B7274C534738067F0B5C1778AAPQMAILBX02Vpr_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable With OLAP, there may be an argument for larger block sizes, however, whatev= er size you choose, that should be the only size in your database. Oracle = only introduced multiple block sizes to support transportable tablespaces b= etween databases w/ differing blocksizes. I won't go into a lot of detail, as this has been done to death many, many = times on Oracle-L and in the Oracle forums, and probably many other venues = as well. Try googling, I imagine you'll get *lots* of hits. Hope that helps, -Mark -- Mark J. Bobak Senior Database Administrator, System & Product Technologies ProQuest 789 E. Eisenhower, Parkway, P.O. Box 1346 Ann Arbor MI 48106-1346 +1.734.997.4059 or +1.800.521.0600 x 4059 mark.bobak@proquest.com www.proquest.com www.csa.com ProQuest...Start here. From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] = On Behalf Of stmontgo@gmail.com Sent: Monday, February 02, 2009 2:37 PM To: oracle-l@freelists.org Subject: Large block sizes for OLAP database Good day, We're jumping into the wonderfull world of Oracle Business Intelligence wit= h HR Analytics. It looks like we'll be creating an OLAP type of database where Oracle recom= mends large block sizes. The database will also contain some metadata for the Inf= ormatica Configuration and HR Analytics portion. If I'm looking at larger block sizes and am wondering if I should be creati= ng the database with a large block size or should I be looking at creating tablespaces with larg= er block sizes and leaving the db with a standard 8k size. Does anyone have an opion either way? Thanks Steve Our config will look like this OEL 64 bit Oracle 10.2.0.4 OBIEE 10.1.3.4 OBI (Hr Analytics) 7.9.5.1 --_000_6AFC12B9BFCDEA45B7274C534738067F0B5C1778AAPQMAILBX02Vpr_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

With OLAP, there may be an argument for larger block sizes, however, whatever size you choose, that should be the only size in your database.  Oracle only introduced multiple block sizes to support transportable tablespaces between databases w/ differing blocksizes.

 

I won’t go into a lot of detail, as this has been done= to death many, many times on Oracle-L and in the Oracle forums, and probably m= any other venues as well.  Try googling, I imagine you’ll get *lo= ts* of hits.

 

Hope that helps,

 

-Mark

 

--
Mark J. Bobak
Senior Database Administrator, System & Product Technolo= gies
ProQuest
789 E. Eisenhower, Parkway, P.O. Box 1346
Ann Arbor MI 48106-1346
+1.734.997.4059  or +1.800.521.0600 x 4059
mark.bobak@proquest.com=
www.proquest.com
www.csa.com

ProQuest...Start here.

 

From: oracle-l-bounce@freelists.org [mailto:oracle-l-bounce@freelists.org] On Behalf Of stmontgo@gmail.com
Sent: Monday, February 02, 2009 2:37 PM
To: oracle-l@freelists.org
Subject: Large block sizes for OLAP database

 

Good day,
We're jumping into the wonderfull world of Oracle Business Intelligence wit= h HR Analytics.

It looks like we'll be creating an OLAP type of database where Oracle recommends
large block sizes. The database will also contain some metadata for the Informatica Configuration
and HR Analytics portion.

If I'm looking at larger block sizes and am wondering if I should be creati= ng the database with
a large block size or should I be looking at creating tablespaces with larg= er block sizes
and leaving the db with a standard 8k size.

Does anyone have an opion either way?

Thanks

Steve

Our config will look like this
OEL 64 bit
Oracle 10.2.0.4
OBIEE 10.1.3.4
OBI (Hr Analytics) 7.9.5.1

--_000_6AFC12B9BFCDEA45B7274C534738067F0B5C1778AAPQMAILBX02Vpr_-- -- http://www.freelists.org/webpage/oracle-l