onspaces -c -b: Create a blobspace
- 1 Windows™ Only
Use onspaces -c -b to create a blobspace.
| Element | Purpose | Key considerations |
|---|---|---|
| -b blobspace | Names the blobspace to be created | The blobspace name must be unique and cannot exceed 128 bytes. It must begin with
a letter or underscore and must contain only letters, numbers, underscores, or the $
character. For more information, see creating a blobspace, in the chapter on managing disk space in the HCL OneDB™ Administrator's Guide. The syntax must conform to the Identifier segment. For more information, see the HCL OneDB Guide to SQL: Syntax. |
| -c | Creates a dbspace, blobspace, sbspace, or extspace You can create up to 2047 storage spaces of any type. |
After you create a storage space, you must back
up both this storage space and the root dbspace. If you create a storage
space with the same name as a deleted storage space, perform another
level-0 backup to ensure that future restores do not confuse the new
storage space with the old one. For more information, see creating a dbspace, blobspace, or extspace, in the chapter on managing disk space in the HCL OneDB Administrator's Guide. |
| drive | Specifies the Windows drive to allocate
as unbuffered disk space The format can be either \\.\<drive>, where drive is the drive letter assigned to a disk partition, or \\.\PhysicalDrive<number>, where PhysicalDrive is a constant value and number is the physical drive number. |
For information on allocating unbuffered disk space,
see allocating unbuffered disk space on Windows in the chapter on managing disk space
in the HCL
OneDB
Administrator's Guide.
Examples:For path name syntax, see your operating-system documentation. |
| -g pageunit | Specifies the blobspace blobpage size in terms of page_unit, the number of the base page size of the instance (either 2K or 4K) | Unsigned integer. Value must be greater than 0. The maximum number of pages that a blobspace can contain is 2147483647. Therefore, the size of the blobspace is limited to the blobpage size x 2147483647. This includes blobpages in all chunks that make up the blobspace. For more information, see blobpage size considerations, in the chapter on I/O Activity in the HCL OneDB Performance Guide. |
| -m pathname offset | Specifies an optional path name and offset to the chunk that mirrors the initial
chunk of the new blobspace or dbspace Also see the entries for -p pathname and -o offset in this table. |
For more information, see creating a dbspace or a blobspace in the chapter on managing disk space in the HCL OneDB Administrator's Guide. |
| -o offset | Indicates, in kilobytes, the offset into the disk partition or into the device to reach the initial chunk of the new blobspace, dbspace, or sbspace | 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, in the chapter on managing disk space in the HCL OneDB Administrator's Guide. |
| -p pathname | Indicates the disk partition or device of the initial chunk of the blobspace or dbspace that you are creating | The chunk must be an existing unbuffered device
or buffered file. 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. UNIX™ example (unbuffered device): /dev/rdsk/c0t3d0s4 UNIX example (buffered device): /ix/ids9.2/db1chunk Windows example:c:\Ifmxdata\ol_icecream\mychunk1.dat For path name syntax, see your operating-system documentation. |
| -s size | Indicates, in kilobytes, the size of the initial chunk of the new blobspace or dbspace | 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. |
| -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. |
This command has an equivalent SQL administration API function.