Failure getting record lock on a record from table DBADMIN.B

Posted by Fernando.Ferreira on 28-Dec-2017 17:57

We are frequently receiving the error below.

Failure getting record lock on a record from table DBADMIN.BIZEVENT

Because of this error, we believe it is impacting BPM performance.

Do you know how to correct this mistake?

Best Regards,


All Replies

Posted by Karthikeyan Bhaskaran on 29-Dec-2017 00:47

Hello Fernando,

You should be able to avoid these errors by increasing the Lock Wait Timeout value, governed by startup parameter -SQLLockwaitTimeout. Default value is 5 seconds, which could be too small in a production-like environment.

The optimal value will depend upon your environment.

To override this value, use -SQLLockwaitTimeout and a value (>5)  [by adding it to the under $DLCWORK/oebpsdb (if you use the startdb.bat/sh), or append to your proserve command.]

Documentation reference:

Please let us know if this change helps also to improve the performance as well (the errors should become less frequent /  not occur with a large enough value).

Posted by Fernando.Ferreira on 29-Dec-2017 07:24

Hello, thank you for your answer.

Our Database is starded by service ( admin service )

The SQL lock wait timeout:  is with: 302

Whats is the best way to calculete this number ?



This thread is closed