Oracle Database 11g The Complete Reference (Osborne ORACLE ...

642 Part V: Object-Relational Databases
Because there are three LOB columns, the create table command should be modified to
include the storage specifications for the out-of-line LOB data (if you plan to store the LOB data
out of line). Two of the LOB columns—Proposal_Text and Budget—will store data within the
database. The revised version of the create table command, with the LOB storage clause specified,
is shown in the following listing:
create table PROPOSAL
(Proposal_ID NUMBER(10),
Recipient_Name VARCHAR2(25),
Proposal_Name VARCHAR2(25),
Short_Description VARCHAR2(1000),
Proposal_Text CLOB,
Budget BLOB,
Cover_Letter BFILE,
constraint PROPOSAL_PK primary key (Proposal_ID))
tablespace PROPOSALS
lob (Proposal_Text, Budget) store as
(tablespace Proposal_Lobs
storage (initial 100K next 100K pctincrease 0)
chunk 16K pctversion 10 nocache logging);
The last four lines of the create table command tell Oracle how to store the out-of-line LOB
data. The instructions are as follows:
lob (Proposal_Text, Budget) store as
(tablespace Proposal_Lobs
storage (initial 100K next 100K pctincrease 0)
chunk 16K pctversion 10 nocache logging);
The lob clause tells Oracle that the next set of commands deals with the out-of-line storage
specifications for the table’s LOB columns. The two LOB columns (Proposal_Text and Budget) are
explicitly listed. When the two columns’ values are stored out of line, they are stored in a segment
as specified via the lob clause:
lob (Proposal_Text, Budget) store as
NOTE
If there were only one LOB column, you could specify a name for the
LOB segment. You would name the segment immediately after the
store as clause in the preceding command.
The next two lines specify the tablespace and storage parameters for the out-of-line LOB
storage. The tablespace clause assigns the out-of-line data to the PROPOSAL_LOBS tablespace,
and an optional storage clause can be used to specify the initial, next, and pctincrease values the
out-of-line data storage will use. See the entry for the storage clause in the Alphabetical Reference
for an explanation of the available storage parameters for segments.
(tablespace Proposal_Lobs
Because the segments are for storing LOB data, several additional parameters are available,
and they are specified within the lob clause: