In the database
server, a smart large object has two parts:
The data, which is stored in an sbspace
A large-object handle, known as an LO handle,
which identifies the location of the smart-large-object data in its sbspace
Suppose you store the picture of an employee as a smart large object.
The following figure shows how the LO handle contains information
about the location of the actual employee picture in the sbspace1_100 sbspace.Figure 1: Smart large object in
the database server
In the figure, the sbspace holds the actual employee image that
the LO handle identifies. For more information about the structure
of an sbspace, and the onspaces database utility
that creates and drops sbspaces, see the HCL OneDB™
Administrator's Guide.
Important: Smart large objects can only be stored in sbspaces.
You must create an sbspace before you attempt to insert smart large
objects into the database.
Because a smart large object is potentially very large, the database
server stores only its LO handle in a database table; it can then
use this handle to find the actual data of the smart large object
in the sbspace. This arrangement minimizes the table size.
Applications obtain the LO handle from the database and use it
to locate the smart-large-object data and to open the smart large
object for read and write operations.
