|
|
|
It is sometimes necessary to identify users who hold a record lock. For example, when profiling performance issues, record locks held longer than necessary are frequently identified as the culprit. It is useful to identify the owner of the record lock to determine the nature of these locks.
To provide additional diagnostic information to the application server administrator, a FairCom DB function was added to retrieve a list of users that own, and are waiting for, a data record lock at a specified byte offset of a data file.
