You can view a lock snapshot by using one of the following commands:
db2text CONTROL LIST ALL LOCKS FOR DATABASE mydatabase INDEX myindex
db2text CONTROL LIST ALL LOCKS FOR DATABASE mydatabaseNote that only indexes that are actually locked are in the list.
The first time a text index is locked, memory is reserved for the database and the text index in the locking services. If further text indexes are locked, memory is also allocated for these indexes in the locking services. This memory is only freed again when the text index is dropped or the database disabled, or whenever the Net Search Extender services are restarted. This means that a text index or database consumes memory in the locking services, even if there are no locks currently set.
The command "db2text CONTROL CLEAR ALL LOCKS" forces the release of all the locks on a database or index. See CONTROL for details on how to use this command. Note that this command does not free any memory allocated for the database or indexes. To free memory, you must either drop the index or disable the database, or restart the Net Search Extender services.