onspaces -a: Add a chunk to an sbspace

>>-onspaces -a--sbspace-- -p--pathname-- -o--offset------------->

>-- -s--size--+----------------------+--+--------------+-------->
              '- -m--pathname offset-'  '- -Ms--mdsize-'   

>--+----------------+--+-----+---------------------------------><
   '- -Mo--mdoffset-'  '- -U-'

Use onspaces -a to add a chunk to an sbspace.


Element	Purpose	Key considerations
-a	Indicates that a chunk is to be added	You can have up to 32766 chunks in an instance. You can put all those chunks in one storage space, or spread them among multiple storage spaces.
-m pathname offset	Specifies an optional path name and offset to the chunk that mirrors the new chunk Also see the entries for *pathname* and *offset* in this table.	For background information, see adding a chunk to 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 should be stored	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. For background 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	Value can be an integer between 0 and the chunk size. For background information, see sizing sbspace metadata, in the chapter on managing disk space in the HCL OneDB Administrator's Guide.
-o offset	After the -a option, offset indicates, in kilobytes, the offset into the disk partition or into the unbuffered device to reach the initial chunk of the new blobspace or dbspace.	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 offset is 2 or 4 terabytes, depending on the platform. 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 that you are creating The chunk must be an existing unbuffered device or buffered file.	The chunk path name can be up to 256 bytes. When you specify a path name, you can use either a full path name or a relative path name. However, if you use a relative path name, it must be relative to the directory that was the current directory when you initialized the database server. For path name syntax, see your operating-system documentation.
-U	Specifies that the entire chunk should be used to store user data	The -M and -U options are mutually exclusive. For background information, see adding a chunk to an sbspace, in the chapter on managing disk space in the HCL OneDB Administrator's Guide.
-s size	Indicates, in kilobytes, the size of the new sbspace chunk	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 offset is 4 terabytes
*sbspace*	Names the sbspace to which you are adding a chunk	See adding a chunk to an sbspace in the chapter on managing disk space in the HCL OneDB Administrator's Guide. Syntax must conform to the Identifier segment; see the HCL OneDB Guide to SQL: Syntax.

This command has an equivalent SQL administration API function.