Locktables

[Former Member]

When we are using WorkStatus,our locking tables is getteing extremely large. Is there anyone else having the same problems, and how do you solve this?

[sorin_radulescu · Accepted solution]

It is depending about what tables you are speaking.

If you are speaking about LCK"Applicationname" tables then the number of records from these tables can be under control using Send Governor parameters:

THREAD_MAXNUM_SG - Maximum number of additional concurrent threads inserting into write back table

Default value is 3

INTERVAL_CHECK_SEND - Frequency the system sends batches of data from the stag-ing table to the write-back table. (milliseconds)Default value is 3000

MAXCELLS_THREAD_SG - The number of cells that will be processed by a thread.

Default value is 1000000

UNITPER_SP Maximum number of cells inserted into the write back table per send

Default value is 1000000

Any way the number of records from LCK tables has any impact into performances.

Even if that number is big the performances can be good if you increase INTERVAL_CHECK_SEND and use THREAD_MAXNUM_SG = 1

Regards

Sorin Radulescu