Use Lock Table Entries (-L) to change the limits of the record locking table.
Note: Starting in Release 10.1C, the OpenEdge RDBMS expands the range of internal validations used to ensure database consistency in both index and data blocks during forward processing. Validations using PROUTIL can be run online as part of routine health checks. For more information, see OpenEdge Data Management: Database Administration.
The number of entries in the record locking table. If you specify a value that is not a multiple of 32, OpenEdge rounds the value you specify to the next highest multiple of 32.
Each record that is accessed by any user takes one entry. This is true whether the record is accessed with SHARE-LOCK or EXCLUSIVE-LOCK.
Increase the size of the lock table if the following message appears:
SYSTEM ERROR: Record lock table too small. Increase -L parameter.
This message also might indicate that a particular procedure should be restructured into smaller transactions or should be run in single-user rather than multi-user mode. When lock table limits are exceeded, check to make sure transactions are not too large before increasing the lock table size.
If a user process tries to acquire a lock and the lock table overflows, the user's program is aborted, but the server continues to operate. Any partial transactions are undone.
Note: The two record locks are acquired when records are accessed with the BREAK BY option (in DO, FOR EACH, or REPEAT statements). Each lock table entry takes 18 bytes on typical systems.
