000021015 - Error: 'Lock table overflow  increase -L on Server (315)' (SQL Message)

Document created by RSA Customer Support Employee on Jun 16, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000021015
Applies ToMicrosoft Windows NT Server 4.0 SP6
Microsoft Windows 2000
UNIX (AIX, HP-UX, Solaris, Linux)
IssueError: "Lock table overflow, increase -L on Server (315)" (SQL Message)
Database is large, likely more than 64,000 users or tokens
Trying to run a live database dump using sddumpsrv -m or sddump -s -m
CauseWhen dumping the database in multi-user mode (the ACE/Server is running), each record that is accessed by any user or process takes one entry in the lock table. The default table size is 64,000, so if any database table exceeds that limit, the live dump will fail with the above error. NOTE: This doesn't affect the dump when the server is not running.
Resolution

To correct this issue, edit the following files:

  • /ace/rdbms/startup.pf
  • /ace/prog/sdserv.pf
  • /ace/prog/sdlog.pf

In each of these files, modify the line "-L n", where n is the number of records in the largest table of the database. For instance, when you do a database dump with the server down, the output provides you with the number of records in each table. Provide some extra values and use these. Before doing so, consider the following:

1. Record locks are done as part of the ACE/Server's normal operation. The number of these locks at any particular time changes according to activity, so this number may not be sufficient at busy times.

2. Each lock will use 18 bytes of shared memory. Although the dump process is relatively quick, you will likely see a noticeable performance hit during its execution. Because of these reasons (mostly dependant on database size), doing a live dump may not be right for you. If you decide to do so, you should consider running it during off peak hours.

Legacy Article IDa20094

Attachments

    Outcomes