K
Karthikeyan Bhaskaran
Guest
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 oebps.pf under $DLCWORK/oebpsdb (if you use the startdb.bat/sh), or append to your proserve command.] Documentation reference: documentation.progress.com/.../lock-wait-timeout-(-sqllockwaittimeout).html 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).
Continue reading...
Continue reading...