RE: Large block sizes for OLAP database
Date: Mon, 2 Feb 2009 15:04:12 -0500
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 many other venues as well. Try googling, I imagine you'll get *lots* of hits.
Hope that helps,
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_at_proquest.com<mailto:mark.bobak_at_il.proquest.com> www.proquest.com<http://www.proquest.com> www.csa.com<http://www.csa.com>
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of stmontgo_at_gmail.com
Sent: Monday, February 02, 2009 2:37 PM
Subject: Large block sizes for OLAP database
We're jumping into the wonderfull world of Oracle Business Intelligence with 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 creating the database with a large block size or should I be looking at creating tablespaces with larger block sizes and leaving the db with a standard 8k size.
Does anyone have an opion either way?
Our config will look like this
OEL 64 bit
OBI (Hr Analytics) 126.96.36.199
http://www.freelists.org/webpage/oracle-l Received on Mon Feb 02 2009 - 14:04:12 CST