LOB Storage

From: Todd Carlson <tcarlson_at_tripos.com>
Date: Thu, 12 Jun 2003 07:52:32 -0700
Message-ID: <F001.005B0258.20030612071456@fatcity.com>

Hey Guys,

8.1.7.4, HP-UX 11, 16k block size, avg CLOB size is 4k to 32k (most are less than 16k).

We have to load 3.5 million CLOBs into a table with 3 columns, two IDs and the CLOB. I am new to using CLOBs and am unsure about what storage parameters would be the best choice for this case.

If the LOB is stored in-line and it goes over 3964 bytes, it is automatically store out of line in the same tablespace as the table. My questions are these:
1) With LMTs and a CLOB stored out of line, does one CLOB equal one extent in the out of line tablespace? If that is the case, we will chew through space because the smallest extent in a LMT will be 4x the block size, in this case 64k. That is terribly inefficient. 2) Should I just not specific an out of line tablespace and deal with the row chaining? Would this be a better approach with a 16k block size for conversing space and the cost of speed?

Thanks in advance for the help on this!

Todd

--

Please see the official ORACLE-L FAQ: http://www.orafaq.net
--

Author: Todd Carlson
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). Received on Thu Jun 12 2003 - 09:52:32 CDT