Administration Tools - oolockmon

Printer-friendly version
Lists all processes and locks currently managed by a lock server.
oolockmon
-host hostName | [bootFilePath]
[-detail]
[-notitle]
[-help]
Options
-host hostName
Host on which the desired lock server is running. If you specify this option, you must omit the bootFilePath argument. Specifying the -host option is convenient when a boot file is not available or its location is not known.
bootFilePath
Path to the boot file of the federated database or autonomous partition whose lock server is to be queried. You can omit this argument if you specify the -host option or if you set the OO_FD_BOOT environment variable to the correct path.
-detail
Displays intention locks. An intention lock is a special kind of lock placed on a database or federated database when you request access to it. An intention lock simply indicates that the transaction may also hold a read, update, or exclusive lock lower in the storage hierarchy.
-notitle
Suppresses the copyright notice and program title banner. Useful when invoking the tool from another tool or product.
-help
Prints the tool syntax and definition to the screen.
Discussion
This tool reports the state of the specified lock server. The lock server may be either a standard lock server (which runs as a separate process) or an in-process lock server (which runs as part of an IPLS application process). The oolockmon tool displays the requested information in a table that includes:
n
The transaction identifier of the transaction that obtained the lock
n
The lock mode—read or update
n
The type of locked object—federated database, database, or container
n
The federated database, autonomous partition, database, and container identifiers (if relevant) of the locked object
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.

Date: 
Tuesday, October 30, 2012
Product: 
Objectivity/DB
Version: 
10.2.1
10.2
10.1.4
10.1.2
9.4.1