SBSPACENAME configuration parameter

Use the SBSPACENAME configuration parameter specifies the name of the default sbspace.

onconfig.std value
Not set.
if not present
0
values
Up to 128 bytes.

SBSPACENAME must be unique, begin with a letter or underscore, and contain only letters, digits, underscores, or $ characters.

takes effect
After you edit your onconfig file and restart the database server.
When you reset the value dynamically in your onconfig file by running the onmode -wf command.
When you reset the value in memory by running the onmode -wm command.

Usage

If your database tables include smart-large-object columns that do not explicitly specify a storage space, that data is stored in the sbspace that SBSPACENAME specifies.

The default sbspace is also used by the built-in encryption and decryption functions to store BLOB or CLOB values. If DECRYPT_BINARY or an encryption function cannot find an sbspace in which to store a BLOB or CLOB argument or returned value, the function fails with the following error message: 
Fatal error in server row processing - SQL error -9810 ISAM error -12053
If you see this error message after you invoke an encryption or decryption function that has a CLOB or BLOB argument, configure a default sbspace using the SBSPACENAME configuration parameter, and then repeat the function call.
You must create the default sbspace with the onspaces -c -S utility before you can use it. The database server validates the name of the default sbspace when one of the following occurs:
  • You specify the default sbspace as the storage option for a CLOB or BLOB column in the PUT clause of the CREATE TABLE or ALTER TABLE statement.
  • The database server attempts to write a smart large object to the default sbspace when no sbspace was specified for the column.
  • You store multirepresentational data in the default sbspace.
JAVA Language Support:

If you are using J/Foundation, you must provide a smart large object where the database server can store the Java™ archive (JAR) files. These JAR files contain your Java user-defined routines (UDRs). It is suggested that when you use Java UDRs, you create separate sbspaces for storing smart large objects.

Warning: When you use Enterprise Replication, you must set the CDR_QDATA_SBSPACE parameter and create the sbspace before you define the replication server.

Automatic creation of the default sbspace

Under certain circumstances, a default sbspace is created even if the SBSPACENAME configuration parameter is not set:
  • If you create a bts index and do not explicitly specify an sbspace name
  • If you create a table with a spatial data type column and do not explicitly specify an sbspace name

A default sbspace is created even if the SBSPACENAME configuration parameter is not set if you create a bts index and do not explicitly specify an sbspace name.

The default sbspace is created in the root dbspace for the database server with a size of 10 000 KB. You must manually increase the size of the default sbspace when it fills.