Displays information about transactions waiting on any lockable Objectivity/DB object, which can be a federated database, a database, or a container.
Lists the status of all waiting transactions started on the specified host, subject to filtering based on other options. This option defaults to all nodes.
Lists the status of all waiting transactions started by the specified user, subject to filtering based on other options. This option defaults to all users.
Suppresses the copyright notice and program title banner. Useful when invoking the tool from another tool or product.
Path to a boot file specifying the lock server to be queried. You can omit this argument if you set the OO_FD_BOOT environment variable to the correct path.
This tool queries the specified lock server to check for waiting transactions started by a specified user or host. You can also use this tool to find out whether a specified transaction is waiting for a lockable object, and if so, which transactions currently hold the lock on that object. The displayed transactions may be waiting for resources in any of the federated databases or autonomous partitions serviced by the specified lock server.
The following table summarizes how to use the various options to view different types of transaction information.
Locks reported for objects of type M are internally used locks of short duration that manage access to page maps in containers. They are sometimes called latches.
Tuesday, October 30, 2012