Obtaining locks at the table level, rather than at the page or row level will reduce the shared memory requirements for a transaction, but may reduce concurrency. These programs are good candidates for tuning for lock optimization. This screen identifies all sessions connected to the DBEnvironment. The PIN is the operating system process identification number of the session. XID is a system-generated identifier for the transaction that is active for the session.
Smaller values indicate older transactions.
No additional tuning suggestions are available for this screen. This screen groups together all sessions running the same program. This information can help you determine if a performance problem is related to a particular program, as opposed to simply related to a particular session. No additional tuning suggestions are available for this screen.