onspaces -d: Drop a chunk in a dbspace, blobspace, or sbspace

Use the onspaces -d option to drop a chunk in a dbspace, blobspace, or sbspace.

Read syntax diagramSkip visual syntax diagram
Syntax:

>>-onspaces -d--+-dbspace----------+-- -p--pathname------------->
                +-blobspace--------+                  
                '-+-----+--sbspace-'                  
                  '- -f-'                             

>-- -o--offset--+-----+----------------------------------------><
                '- -y-'   

This command has an equivalent SQL administration API function.

Element Purpose Key considerations
-d Drops a chunk You can drop a chunk from a dbspace, temporary dbspace, or sbspace when the database server is online or quiescent. For more information, see the chapter on managing disk space in the HCL Informix® Administrator's Guide.

You can drop a chunk from a blobspace only when the database server is in quiescent mode.

-f Drops an sbspace chunk that contains user data but no metadata If the chunk contains metadata for the sbspace, you must drop the entire sbspace. Use the -f option with sbspaces only. If you omit the -f option, you cannot drop an sbspace that contains data.

For more information, see dropping a chunk from an sbspace with onspaces, in the chapter on managing disk space in the HCL Informix Administrator's Guide.

-o offset Indicates, in kilobytes, the offset into the disk partition or into the unbuffered device to reach the initial chunk of the dbspace, blobspace, or sbspace that you are dropping 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 offset is 4 terabytes.

For more information, see allocating raw disk space on UNIX, in the chapter on managing disk space in the HCL Informix Administrator's Guide.

-p pathname Indicates the disk partition or unbuffered device of the initial chunk of the dbspace, blobspace, or sbspace that you are dropping 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.

For path name syntax, see your operating-system documentation.

-y Causes the database server to automatically respond yes to all prompts None.
blobspace Names the blobspace from which the chunk is dropped Syntax must conform to the Identifier segment; see the HCL Informix Guide to SQL: Syntax. For more information, see dropping a chunk from a blobspace, in the chapter on managing disk space in the HCL Informix Administrator's Guide.
dbspace Names the dbspace from which the chunk is dropped Syntax must conform to the Identifier segment; see the HCL Informix Guide to SQL: Syntax. For more information, see dropping a chunk from a dbspace with onspaces, in the chapter on managing disk space in the HCL Informix Administrator's Guide.
sbspace Names the sbspace from which the chunk is dropped Syntax must conform to the Identifier segment; see the HCL Informix Guide to SQL: Syntax. For background information, see dropping a chunk from a dbspace with onspaces, in the chapter on managing disk space in the HCL Informix Administrator's Guide.
Important: You must specify a path name to indicate to the database server that you are dropping a chunk.

Copyright© 2019 HCL Technologies Limited