Dropping a Chunk from an Sbspace with onspaces

The following example drops a chunk from sbsp3 on UNIX. An offset of 300 kilobytes is specified. The database server must be in online single-user, or quiescent mode when you drop a chunk from an sbspace or temporary sbspace.

onspaces -d sbsp3 -p /dev/raw_dev1 -o 300 

You cannot drop the initial chunk of an sbspace with the syntax in the previous example. Instead, you must drop the sbspace. Use the fchunk column of onstat -d to determine which chunk is the initial chunk of an sbspace.

Using the -f (Force) Option

You can use the -f option of onspaces to drop an sbspace chunk without metadata allocated in it. If the chunk contains metadata for the sbspace, you must drop the entire sbspace. Use the Chunks section of onstat -d to determine which sbspace chunks contain metadata.

onspaces -d sbsp3 -f

Deleting Smart Large Objects Without any Pointers

Each smart large object has a reference count, the number of pointers to the smart large object. When the reference count is greater than 0, the database server assumes that the smart large object is in use and does not delete it.

Rarely, a smart large object with a reference count of 0 remains. You can use the onspaces -cl command to delete all smart large objects that have a reference count of 0, if it is not open by any application.

For information on using onspaces -cl, see information on the onspaces utility in the IBM Informix Administrator's Reference.