The utility described is not available for as-a-service customers.
The Lock Display utility, lokdisp, provides information about all real-time database locks.
Database Engine 20 uses locks for concurrency control, ensuring data involved in a particular transaction remains consistent for the duration of that transaction, while the database remains available to multiple concurrent users and queries. For more information on Database Engine 20 locks, see SQL Request and Transaction Processing, B035-1142.
Locks are applied automatically as appropriate by Database Engine 20. Optionally, you can specify the lock to be applied to a database object using the SQL LOCKING request modifier. For more information, see SQL Data Manipulation Language, B035-1146. Locks are applied to different levels of database objects as required by the particular operation requiring the lock. Locks can be applied with the following granularities:
- Database
- Table
- Partition (row-partition)
- Range of rows
- Row (locks rows having a particular rowhash value, which may be more than a single row)
Lock Display can obtain lock information from the following:
- A specific AMP
- A group of AMPs
- All AMPs
- Perm AMPs
For a Database Engine 20 system with many AMPs and a heavy load, be careful when selecting the number of AMPs from which to obtain information. The fewer the AMPs selected, the lower the volume of lock information generated, and the more manageable the output. Teradata recommends obtaining information from all AMPs only when the lock information for a specific transaction is needed.
Lock information can also be monitored and displayed using the Lock Viewer portlet in Teradata Viewpoint. For more information, see Teradata® Viewpoint User Guide, B035-2206.