RME 4.2: Row-Locked Error message in Inventory Report

lo.mueller · ‎12-02-2008

Hello,

I got following error message in invreports.log when performing EoX-Reports:

Sybase -210; User "DBA" has the row in 'EOS_EOL_CARD' locked.

With older versions of Sybase-DB (9.x) in know that this lock can be restored with dbsrv9 -f <rme-db.db>.

But with LMS 3.1 and Sybase 10 this doesn't seem to work anymore as performing this command the lock couldn't be unlocked.

Parsing through the Sybase docs it was stated that with Sysbase 10 something was changed with the transaction locking.

Any help for unlocking lock rows?

Best Regards

Lothar

Joe Clarke · ‎12-04-2008

Restarting Daemon Manager should cause all pending transactions to either commit or rollback. If that is not happening, the same procedure can be applied (i.e. force the database closed) using, on Windows:

If the rmeng.log still exists, and is not corrupt:

NMSROOT\objects\db\win32\dbsrv10 -as NMSROOT\databases\rmeng\rmeng.db

If the rmeng.log no longer exists:

NMSROOT\objects\db\win32\dbsrv10 -f NMSROOT\databases\rmeng\rmeng.db

If the rmeng.log exists, but is corrupt, then delete it, and run:

NMSROOT\objects\db\win32\dbsrv10 -f NMSROOT\databases\rmeng\rmeng.db

Joan Pelser · ‎10-19-2009

Hi Joe,

what is the solaris version of this command please

Joe Clarke · ‎10-19-2009

Start a new thread for your issue.