This command undoes DB2 Net Search Extender changes to a database.
You must run this command as a database administrator to disable the database. This requires you having DBADM authority.
>>-DISABLE-DATABASE-FOR-TEXT--+-------+-------------------------> '-FORCE-' >--+----------------------+------------------------------------>< '-|connection-options|-' connection-options: |--+--------------------------------------------------------------+--| '-CONNECT-TO--database-name--+-------------------------------+-' '-USER--userid--USING--password-'
This command resets the connected database, so that it can no longer be used by other DB2 Net Search Extender commands. If full-text indexes exist in the database, this command fails unless the FORCE option is used.
This command does not remove DBADM authority from the DB2 instance owner.
Disabling a database will fail if there are any text indexes defined in the database. It is recommended to remove these indexes one by one and then check if any problems occurr. If you use the disable database for text force command, it only guarantees that Net Search Extender catalog tables in the database are removed.
However, if some of the indexes can not be completely dropped, there may still be resources that need to be manually cleaned up. These include:
In the following example, the instance is DB2 and the database is SAMPLE.
DELETE FROM <ccSchema>.IBMSNAP_SIGNAL WHERE SIGNAL_INPUT_IN IN (SELECT MAP_ID FROM <ccSchema>.IBMSNAP_PRUNCNTL WHERE APPLY_QUAL= 'NSEDB2' AND TARGET_SERVER= 'SAMPLE'); DELETE FROM <ccSchema>.IBMSNAP_PRUNCNTL WHERE APPLY_QUAL= 'NSEDB2' AND TARGET_SERVER= 'SAMPLE'; DELETE FROM <ccschema>.IBMSNAP_PRUNE_SET WHERE APPLY_QUAL= 'NSEDB2' AND TARGET_SERVER= 'SAMPLE';
If you use the FORCE option, the cache is deleted for any activated cache of indexes. See DROP INDEX for further information.