CLOB storage uses more than it need
From: Ed Wong <ewong_at_mail.com>
Date: 30 Jan 2002 18:24:30 -0800
Message-ID: <a5ae1554.0201301824.70d59ce5_at_posting.google.com>
[Quoted] I have a 5M records table with a big clob column. I allocate this particular clob column to a single tablespace(nothing else uses it). I checked the total size of the clob column it's 60GB. However, it uses 100GB in the tablespace. Why is it? Is it because I set the chunk to 32k?
TABLESPACE prod_data
storage ...
LOB (result) STORE AS lob_result
(
Date: 30 Jan 2002 18:24:30 -0800
Message-ID: <a5ae1554.0201301824.70d59ce5_at_posting.google.com>
[Quoted] I have a 5M records table with a big clob column. I allocate this particular clob column to a single tablespace(nothing else uses it). I checked the total size of the clob column it's 60GB. However, it uses 100GB in the tablespace. Why is it? Is it because I set the chunk to 32k?
Table definition:
CREATE TABLE Result
(
id NUMBER(10), len NUMBER(10), result CLOB, CONSTRAINT pk_Result PRIMARY KEY (id) storage ...)
TABLESPACE prod_data
storage ...
LOB (result) STORE AS lob_result
(
TABLESPACE prod_result
STORAGE (INITIAL 200M NEXT 200M MINEXTENTS 1
MAXEXTENTS UNLIMITED PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1)
CHUNK 32K PCTVERSION 20 CACHE DISABLE STORAGE IN ROW
INDEX lobi_result_output
);
Received on Thu Jan 31 2002 - 03:24:30 CET