drop chunk argument: Drop a chunk (SQL administration API)
Use the drop chunk argument with the admin() or task() function to drop the specified chunk from a dbspace, blobspace, or sbspace.
Syntax
| Element | Description | Key Considerations |
|---|---|---|
| offset | The offset, in kilobytes, into the disk partition or into the unbuffered device to reach the initial chunk of the dbspace, blobspace, or sbspace that you are dropping. | The starting offset, an unsigned integer, must be equal to or greater than 0. The starting offset plus the chunk size cannot exceed the maximum chunk size, which is 8 EB. |
| path_name | 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. |
| space_name | The name of the dbspace, sbspace, or blobspace from which to drop a chunk. | You can drop a chunk from a dbspace, temporary
dbspace, or sbspace when the database server is online or quiescent. You can drop a chunk from a blobspace only when the database server is in quiescent mode. |
Usage
This function is equivalent to the onspaces -d command.
Example
The following example drops a chunk at an offset of 5200 kilobytes from a dbspace named dbspc3:EXECUTE FUNCTION task("drop chunk", "dbspc3","\\.\e:","5200");