Vivek, The hybrid system is an interesting option - presumably you mean part OLTP part DSS It's possible that you could use multiple block sizes for damage limitation purposes - if you have two databases in one. Stick the DSS tables into one size, and the OLTP into another, and you could protect the "OLTPbuffer" from any DSS queries that go insane and start reading huge volumes of data - and you also
have the option to switch memory from OLTP to DSS at different times of day. Of course, if this is going to work, you also needto take the James Morle "Same San" approach and separate the OLTP and DSS data files onto
different disks (and channels and ...) so that an insane DSS query doesn't kill the OLTP disks. Rather than having multiple block sizes, you mightget the same effect by allocating the Recycle pool for the DSS and the Default cache for the OLTP (perhaps with some reference tables in the default).
Regards Jonathan Lewis http://jonathanlewis.wordpress.com Author: Cost Based Oracle: Fundamentals http://www.jlcomp.demon.co.uk/cbo_book/ind_book.html The Co-operative Oracle Users' FAQ http://www.jlcomp.demon.co.uk/faq/ind_faq.html
Subject: Use of Multiple BLOCK Sizes ? Date: Tue, 19 Dec 2006 16:10:41 +0530 From: "VIVEK_SHARMA" <VIVEK_SHARMA@xxxxxxxxxxx> Folks Does use of Multiple BLOCK sizes (for different Tablespaces) help in Performance of a Hybrid Application? Any best practices, Links, Docs?