onspaces -c -S: Create an sbspace

Use the onspaces -c -S option to create a sbspace or a temporary sbspace.

Figure 1: Syntax:


Element	Purpose	Key Considerations
-S`sbspace`	Names the sbspace to be created	The sbspace name must be unique and must not exceed 128 bytes. It must begin with a letter or underscore and must contain only letters, numbers, underscores, or the $ character. Syntax must conform to the Identifier segment; see the HCL OneDB™ Guide to SQL: Syntax.
-c	Creates an sbspace You can create up to 32767 storage spaces of any type.	None.
-Df `default list`	Lists default specifications for smart large objects stored in the sbspace	Restrictions: Tags are separated by commas. If a tag is not present, system defaults take precedence. The list must be enclosed in double quotation marks (“) on the command line. References: For a list of tags and their parameters, see -Df Default Specifications.
-m `pathname offset`	Specifies an optional pathname and offset to the chunk that mirrors the initial chunk of the new sbspace Also see the entries for -p `pathname` and -o `offset` in this table.	For more information, see sbspaces in the chapter on data storage, and creating an sbspace, in the chapter on managing disk space in the HCL OneDB Administrator's Guide.
-Mo `mdoffset`	Indicates, in kilobytes, the offset into the disk partition or into the device where metadata will be stored.	Restrictions: Value can be an integer between 0 and the chunk size. You cannot specify an offset that causes the end of the metadata space to be past the end of the chunk. References: For more information, see sizing sbspace metadata, in the chapter on managing disk space in the HCL OneDB Administrator's Guide.
-Ms `mdsize`	Specifies the size, in kilobytes, of the metadata area allocated in the initial chunk The remainder is user-data space.	Restrictions: Value can be an integer between 0 and the chunk size.
-o `offset`	Indicates, in kilobytes, the offset into the disk partition or into the device to reach the initial chunk of the sbspace	Restrictions: Unsigned integer. The starting offset must be equal to or greater than 0. The starting offset plus the chunk size cannot exceed the maximum chunk size. The maximum chunk size is 4 terabytes for systems with a two-kilobyte page size and 8 terabytes for systems with a four-kilobyte page size. References: For more information, see allocating raw disk space on UNIX™, in the chapter on managing disk space in the HCL OneDB Administrator's Guide.
-p `pathname`	Indicates the disk partition or unbuffered device of the initial chunk of the sbspace	The chunk must be an existing unbuffered device or buffered file. When you specify a pathname, you can use either a full pathname or a relative pathname. However, if you use a relative pathname, it must be relative to the directory that was the current directory when you initialized the database server. References: For pathname syntax, see your operating-system documentation.
-s `size`	Indicates, in kilobytes, the size of the initial chunk of the new sbspace	Restrictions: Unsigned integer. The size must be equal to or greater than 1000 kilobytes and a multiple of the page size. The starting offset plus the chunk size cannot exceed the maximum chunk size. The maximum chunk size is 2 or 4 terabytes, depending on the platform.
-t	Creates a temporary sbspace for storage of temporary smart large objects. You can specify the size and offset of the metadata area	Restrictions: You cannot mirror a temporary sbspace. You can specify any -Df option, except the LOGGING=ON option, which has no effect. References: For more information, see Creating a Temporary Sbspace with the -t Option.
-u	Specifies to create an unencrypted space	Use this option to create an unencrypted storage space when encryption is enabled by the DISK_ENCRYPTION configuration parameter.