The purpose of this feature, I believe, is to accomodate "transportable
tablespace" restores, so that it is possible to say,transport a tablespace
from a 2K block size database, to a 4k block database.

Raj




                                                                                       
                             
                    Michael                                                            
                             
                    Fontana              To:     Multiple recipients of list ORACLE-L 
<[EMAIL PROTECTED]>        
                    <mfontana@ver        cc:                                           
                             
                    io.net>              Subject:     Re: 2k and  8k block size        
                             
                    Sent by:                                                           
                             
                    root@fatcity.                                                      
                             
                    com                                                                
                             
                                                                                       
                             
                                                                                       
                             
                    February 10,                                                       
                             
                    2003 04:59 PM                                                      
                             
                    Please                                                             
                             
                    respond to                                                         
                             
                    ORACLE-L                                                           
                             
                                                                                       
                             
                                                                                       
                             




Reading my oracle 9i new features , there is now something called:
Multiple Database Block Size Support.  In other words, it is no longer
necessary
to commit to a single block size for your database.  I'd suggest looking
into this, as
it may now be possible to test using different blocksizes for different
tablespaces.


At 01:04 PM 2/10/2003 -0800, [EMAIL PROTECTED] wrote:
     An 8.0.6 ops database being migrated to 9i RAC database on Solaris 8.
     The
     8.0 database had an block size of 2k.  Multiblock read count is 8.
     This is
     an OLTP database, all transactions almost always work on a single row.
     None
     of the row sizes exceed the block size. Hardly any chained or migrated
     rows. Now, during this migration, it was recommended to change the
     block
     size to 8k. And my concerns are:

     1. Would this not increase pinging across the instances? With 9i and
     interconnect and cache fusion, this should be reduced considerably,
     so, is
     it a mute point?
     2. This could alter the execution plans of some statements. Would
     some,
     maybe a very few of the statements not prefer a full table scan?

     Any other positive or negative effects of this increase in block size?

     Thanks
     One Paranoid DBA



-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: 
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to