Monitoring Locking with SQLMON [ ALLBASE/SQL Reference Manual ] MPE/iX 5.5 Documentation
ALLBASE/SQL Reference Manual
Monitoring Locking with SQLMON
SQLMON is an online diagnostic tool that monitors the activity of your
DBEnvironment. In addition to providing information on file capacity,
I/O, logging, tables, and indexes, SQLMON displays information on the
locks currently held in your DBEnvironment. SQLMON is fully documented
in the ALLBASE/SQL Performance and Monitoring Guidelines.
[REV BEG]
MONITOR Authority
Users with DBA authority or who are granted MONITOR authority can run
SQLMON. Use the GRANT MONITOR command to allow users to run SQLMON. Use
the REVOKE MONITOR command to revoke the authority. SYSTEM.SPECAUTH and
CATALOG.SPECAUTH identify users with MONITOR authority.[REV END]
Monitoring Tasks
Table 5-5 summarizes the monitoring tasks related to locking you can
perform with SQLMON:
Table 5-5. SQLMON Monitoring Tasks
-----------------------------------------------------------------------------------------------
- Task - Screens - Fields -
-----------------------------------------------------------------------------------------------
| Determining Size of | Overview | RUNTIME CB % |
| Runtime Control Block | | Used Pages |
| | | Max Pages |
-----------------------------------------------------------------------------------------------
| Monitoring DBEnvironment Lock | Load | LOCK REQTS |
| Activity | | LOCK WAITS |
| | | LOCK WAIT % |
-----------------------------------------------------------------------------------------------
| Comparing Number of Locks by | Lock TabSummary | OWNER.TABLE |
| Table | | G |
| | | TOTAL LOCKS |
-----------------------------------------------------------------------------------------------
| Comparing Number of Locks by | Lock Memory | TABLE |
| Session | | PAGE |
| | | ROW |
| | | TOTAL |
| | | MAXTOTAL |
-----------------------------------------------------------------------------------------------
| Identifying Locks on a Table or | Lock | OWNER.TABLE[/CONSTRAINT] |
| Referential Constraint (PCR) | | G |
| | | PAGE/ROW ID |
| | | LOCK QUEUE |
-----------------------------------------------------------------------------------------------
| Determining Number of Sessions thatLock | LOCK QUEUE |
| are Accessing a Particular Lock | | |
-----------------------------------------------------------------------------------------------
| Determining Number of Transactions Overview | IMPEDE XACT |
| that are Waiting for Locks | Load | |
-----------------------------------------------------------------------------------------------
| Identifying Locks for which Sessionsock | all fields |
| are Waiting | | |
-----------------------------------------------------------------------------------------------
| Identifying Sessions that have | Lock Object | GWC |
| Obtained a Particular Lock | | MOD |
| | | PIN |
-----------------------------------------------------------------------------------------------
| Identifying Sessions that are | Lock Object | GWC |
| Waiting to Obtain (or to Convert)| | MOD |
| a Particular Lock | | NEW |
| | | PIN |
-----------------------------------------------------------------------------------------------
| Identifying Lock Activity for | Lock Session | all fields |
| a Particular Session | | |
-----------------------------------------------------------------------------------------------
| Identifying Locks Obtained by a | Lock Impede | all fields |
| Particular Session that are | | |
| Causing Other Sessions to Wait | | |
-----------------------------------------------------------------------------------------------
| Detecting Deadlocks | Load | DEADLOCKS |
| | Load Session | |
| | Load Program | |
-----------------------------------------------------------------------------------------------
| Resolving Deadlocks | Lock | all fields |
| | Lock Object | |
| | Lock Impede | |
-----------------------------------------------------------------------------------------------
MPE/iX 5.5 Documentation