cancel
Showing results for 
Search instead for 
Did you mean: 

LOCKSTATISTICS table is empty

Former Member
0 Kudos

Hi,

i tried to issue the SELECT * FROM LOCKSTATISTICS and get no results, exists something wrong with database? i wish to know the better value for REQUEST_TIMEOUT parameter.

Version is: 7.6.03.15

regards

Clóvis

Accepted Solutions (1)

Accepted Solutions (1)

lbreddemann
Active Contributor
0 Kudos

...and yes. about that parameter...

Why do you want to actually change it?

Do you often encounter situations where sessions hang enlessly while they wait for a lock?

regards,

Lars

Former Member
0 Kudos

Hi Lars

today REQUEST_TIMEOUT have the default value 5000, and yes, i still having that Vwait things that blocks my application, now i will work with isolation level 0, and i'm try to reduce the REQUEST_TIMEOUT to a number near of my reality.

regards

Clóvis

lbreddemann
Active Contributor
0 Kudos

Hi Clovis,

ok, so if I get you right you want to limit the time any session waits for a lock.

This can be done via the db parameter REQUEST_TIMEOUT/RequestTimeout.

The SessionTimeout parameter is used to kick out inactive sessions.

It's mainly usefull to prevent situation where new sessions cannot be created because of "zombie" sessions that hang on.

Be aware that although you can set the value to any value within the allowed range, the timeout task will check for it only every 5 seconds.

So don't count on the timing here

regards,

Lars

Answers (1)

Answers (1)

lbreddemann
Active Contributor
0 Kudos

> i tried to issue the SELECT * FROM LOCKSTATISTICS and get no results, exists something wrong with database? i wish to know the better value for REQUEST_TIMEOUT parameter.

Everything should be fine.

LOCKSTATISTICS only contains rows when there are locks being held.

LOCKLISTSTATISTICS however might be the table you want to check.

regards,

Lars