FORCE_DROP option

Causes Sybase IQ to leak, rather than reclaim, database disk space during a DROP command.

ON, OFF

OFF

Requires DBA permissions to set this option. Can be set temporary, for an individual connection, or for the PUBLIC group. Takes effect immediately.

You must drop a corrupt index, join index, column or table and set the FORCE_DROP option to ON. This prevents the free list from being incorrectly updated from incorrect or suspect file space allocation information in the object being dropped. After dropping corrupt objects, you can reclaim the file space using the -iqfrec and -iqdroplks server switches.

When force dropping objects, you must ensure that only the DBA is connected to the database. The server must be restarted immediately after a force drop.

If FORCE_DROP is set to ON, you cannot drop a join index on a multiplex write server. If you need to force drop a join index on a multiplex write server, you must first start the server in single-node mode. If FORCE_DROP = ON on the write server and an object is dropped, the FORCE_DROP option settings, on query servers are unaffected. After the drop restart only the write server.

Do not attempt to force drop objects unless Sybase Technical Support has instructed you to do so.