AdabasD - Lock Request Timeout

[MichiFr]

Hi,

as the subject already tells, this question is aimed to a former MaxDB database version: AdabasD. I could not find any answers to my issue in Internet so I'm trying to post it here, perhaps someone is able to answer it nevertheless. As MaxDB is the successor of AdabasD there may be little chance.

We are still using AdabasD 10.x in an third-party application (not SAP) and I noticed a lock record using SQL statement

show statistics lock

the result reads

u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500  A D A B A S  u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500
LOCK INFO
u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500u2500
TABLE_AKTIVI  key(10): ' I10003D2O'
   LAST REQUEST TIMEOUT AT 2010-03-19 09:37:47
   REQ  ROW share (000s)  00.00544114.001340 USER10           0009

Basically I can read from this information that there is still an existing shared lock request on table TABLE_AKTIVI which occurred on 2010-03-19, is this correct?

This row lock, if any, still persists since March, this year. The database has not been restarted for months now.

How can I remove this kind of row lock? I've already tried to use an UNLOCK statement, to no avail. I guess shutting down the database into offline or into cold mode will remove this lock, however, are there any better ways to do this. The user USER10 is not logged in into the database, btw.

Thanks,

Michael

[Former Member]

Hi,

I think you misunderstand the output you mentioned.

there it is written, that on 19.3. there had been the last LOCK REQUEST TIMEOUT.

It is NOT said, that currently any lock / lock-request exist.

Therefore you will (and have to) fail to unlock this non-existing something.

The meaning of this output is: at that time, one request could not be handled and the user got an error Request timeout (error-number 500 or so).

Then the lock request did not succeed, was not written in lock-list.

This info is useful only in cases where AFTER having had that error-number or in case of deadlocks, users or support want to know what happened, which lock-collision caused the request-timeout/the deadlock.

Therefore: if you will not have another lock request timeout, this info will remain and remain and remain..... and should not worry in any case.

For current lock-info you should check LOCKS (or the like), but not STATISTICS LOCK.

BTW: Why do you stay with ADABASD and do not change to MaxDB?

Elke

[MichiFr]

Hi Elke,

thanks for your reply! I was not really sure if this is still an existing lock or just some kind of information, however, you explained it very well, thanks again.

Why did I post this question? I'm facing a lock problem from time to time, in a third-party application, not SAP R/3 or similar, as mentioned before. The application,however, was built by a company which was bought up by SAP some years ago: Kiefer & Veittinger. So my question is somehow SAP releated ;-).

We are still using this application. AdabasD cannot be replaced as we do not own the source of this application nor can we change the database access layer. As a result we cannot switch to MaxDB or any alternate RDBMS.