Juan, with all due respect, I believe this is *not* a good advice. I actually think it is a *bad* advice. you try to achieve something with the wrong technique, at a way too high price. let me first say that the only *intended* reason for multiple blocksizes is to make transportable tablespaces more flexible. any other reason might have its merits, but should be considered with caution. the biggest disadvantage of a segmented cache is that free space gets segmented too, obviously -- typically leading to much more memory wastage than with a single unsegmented buffer cache. kind regards, Lex. ------------------------------------------------------------------ Steve Adams Seminar http://www.naturaljoin.nl/events/seminars.html ------------------------------------------------------------------ -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Juan Carlos Reyes Pacheco Sent: Thursday, July 21, 2005 18:45 To: Oracle-L@xxxxxxxxxxxxx Subject: Re: Anyone using multi-block sizes for their databases Hi, This works really nice, this allows to create separate areas of memory for different things. For example big blobs documents, in a 32k normal tables 8k indexes 16k, etc. etc. You have to set the database memory cache in the init.ora for each different block size. -- //www.freelists.org/webpage/oracle-l
BEGIN:VCARD VERSION:2.1 N:de Haan;Lex FN:Lex de Haan ORG:Natural Join B.V. TEL;WORK;VOICE:+31.30.2515022 TEL;HOME;VOICE:+31.30.2518795 TEL;CELL;VOICE:+31.62.2955714 TEL;WORK;FAX:+31.30.2523366 ADR;WORK:;;Pieter Breughelstraat 10;Utrecht;;3583 SK;Netherlands LABEL;WORK;ENCODING=QUOTED-PRINTABLE:Pieter Breughelstraat 10=0D=0AUtrecht 3583 SK=0D=0ANetherlands URL;WORK:http://www.naturaljoin.nl EMAIL;PREF;INTERNET:lex.de.haan@xxxxxxxxxxxxxx REV:20040224T160439Z END:VCARD