This command lets you list and delete full-text index locks managed by the Net Search Extender Instance Services. If the locking and update services are running, you can view their status as well as information on the activated cache.
In a distributed DB2 environment this only affects the current partition. The user is responsible for invoking the DB2 command, db2_all for the desired partitions.
You must run this command as a DB2 instance owner on the server.
>>-CONTROL--+-CLEAR--|set-of-locks|------------------------+--->< +-LIST--|set-of-locks|-------------------------+ +-SHOW-CACHE-STATUS-FOR--|index-specification|-+ '-STATUS---------------------------------------' set-of-locks: |--ALL-LOCKS-FOR--+-|database-specification|-+------------------| '-|index-specification|----' index-specification: |--|database-specification|--INDEX------------------------------> >--+------------------+--index-name-----------------------------| '-index-schema-"."-' Database-specification: |--DATABASE--database-name--------------------------------------|
You can also use LIST to view the number of documents updated during the update process. Note this is only for the time the lock is holding the index.
When using a replication capture table, there are no update operations. Instead, insert operations can be either from an insert or an update operation on the source table the index was created on.
When an administration command error message indicates that there is a locking problem, ensure that no conflicting task is running. For example, attempting an ALTER command while an UPDATE command is running. Then free all the locks for the index.
Use SHOW CACHE STATUS for an incremental index update to check that the specified memory size is still large enough to hold all the update information during the next update, or to check if an activation has been done.