Why is the value for lock table entries different between the database start-up script, database log file and the promon? - Progress Community

Loading

Skip to Main Content

Why is the value for lock table entries different between the database start-up script, database log file and the promon?

Why is there a difference between -L value for lock table entries between the database start-up script, database log file and the promon?

Dec 5, 2012
Knowledge

Title

Why is the value for lock table entries different between the database start-up script, database log file and the promon?

URL Name

000036684

Article Number

000159393

Environment

Product: Progress Version: 9.x Product: OpenEdge Version: 10.x, 11.x OS: All Supported Operating Systems

Question/Problem Description

Why is there a difference between -L value for Lock Table entries between the database start-up script, database log file and PROMON
Difference in -L value between OE Console vs PROMON
Difference in -L value in the OE database log file vs PROMON

Steps to Reproduce

Clarifying Information

Error Message

Defect Number

Enhancement Number

Cause

Resolution

The reason for differences in the -L value are explained below:

1. Progress rounds the size of -L up to the nearest multiple of 32 .

Example:

If -L is set to 10000 when starting the database, it will round off to 10016 in the database log file which is a multiple of 32. The database log file will the following message:

(4241) Current Size of Lock Table (-L): 10016.

2. Each time there is a Lock Table overflow, Progress may need to add one additional Lock Table entry (-L). The memory for the extra entry comes from whatever free shared memory happens to be available (-Mxs). So the lock table size gradually grows until there is no more free shared memory left.

Example:

Assume the database has 10016 lock table entries.
When all 10016 entries are used up and another is needed for transaction backout, the database log file shows a lock table overflow error, "Lock table overflow, increase -L on server (915)".
If the database engine is in the middle of an UNDO, the Lock Table size and the overflow limit are both increased by one and it gets the additional lock.
Now the Lock Table size is 10017 and so is the overflow limit. The database will now give a Lock Table overflow again after 10017 entries have been consumed. then 10018, 10019, 10020, and so on until there is no more shared memory available. The PROMON Lock Table entry value after the Lock Table Overflow error will therefore be different from the value recorded in the database log file when it was originally started.

The above examples demonstrate why there is a difference between the Lock Table Entries value used in a database start-up script or configured in the DLC/properties/conmgr.properties file reported in the database log file when the database is started multi-user, to the value reported in PROMON.

Workaround

Notes

Keyword Phrase

Last Modified Date

5/25/2016 11:51 AM

OpenEdge DeploymentOpenEdge ArchitectureOpenEdge DevelopmentOpenEdge General DiscussionsOpenEdge Pro2OpenEdge RDBMS

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

Why is the value for lock table entries different between the database start-up script, database log file and the promon? - Progress Community