Salesforce

Running UPDATE STATISTICS on all tables columns indexes overflows lock table

« Go Back

Information

 
TitleRunning UPDATE STATISTICS on all tables columns indexes overflows lock table
URL NameP113776
Article Number000154453
EnvironmentProduct: Progress
Version: 9.1D, 9.1E
Product: OpenEdge
Version: All Supported Versions
OS: All supported platforms
Other: UPDATE STATISTICS, 915
Question/Problem Description
Running UPDATE STATISTICS on all tables columns indexes simultaneously fails with error 915
UPDATE TABLE STATISTICS AND INDEX STATISTICS AND ALL COLUMN STATISTICS;
Steps to Reproduce
Clarifying Information
Error MessageLock table overflow, increase -L on server (915)
Defect Number
Enhancement Number
Cause
The Lock table -L is not set high enough when running UPDATE STATISTICS on all tables columns and indexes simultaneously.
Resolution
When the STATISTICS commands are run separately, less locks will be used than running all three of these updates at once:
UPDATE TABLE STATISTICS AND INDEX STATISTICS AND ALL COLUMN STATISTICS

Run the UPDATE STATISTICS statements in this exact order:

update table statistics;
commit;
update index statistics;
commit;
update all column statistics;
commit;


The first table and index statistics, will only lock the system statistics tables we write to in this process and do not use many locks.

This formula gives an idea of the number of locks needed and -L can be adjusted accordingly if necessary from the current value of -L:

UPDATE COLUMN STATISTICS uses 11 locks:
  • For the 11 records of information we write to the system statistics tables
  • 10 values and 1 timestamp for each column of indexed data. 
  • Example, if a table has 25 columns, and 12 are indexed, this means 12*11=132 locks.
Workaround
Notes
Keyword Phrase
Last Modified Date3/17/2020 6:50 PM

Powered by