Prev
Next
Forums S3 Systems Administration

OBJID Table Lock

Sort:
You are not authorized to post a reply.
Author
Messages
mark.cook
Veteran Member
Posts: 444
Veteran Member
6/1/2011 3:48 PM
    We experienced a situation where the OBJID table locked. This caused anyone in AP/PO including RSS to see their session timeout or lock the screen.

    We were notified by our DBA after 20 minutes which is also about the time the calls started flowing into us that an issue was happening.

    Has anyone seen this type of error or have suggestions on how to troubleshoot? We seem to be moving very slowly with Lawson on troubleshooting this issue. It has happened 2-3 times in the last 6-9 months. It becomes an stability issue in the eyes of the users for us.

    John Henley
    Senior Member
    Posts: 3348
    Senior Member
    6/1/2011 4:08 PM
      I ran into this last year and had Lawson create a CTP for it. Let me see if I can find it. =
      Thanks for using the LawsonGuru.com forums!
      John
      mark.cook
      Veteran Member
      Posts: 444
      Veteran Member
      6/1/2011 4:49 PM
        Thanks John, any help is greatly appreciated.
        John Henley
        Senior Member
        Posts: 3348
        Senior Member
        6/1/2011 5:49 PM
          Mark, I went back and looked this up.

          It was actually an issue in a client's custom version of AR560 when interfacing AR invoices as GLTRANS and ACTRANS commitment records, which implicitly requires allocation of an OBJ-ID. This is done by calling a common library routine, which locks the OBJID record associated with the OBJ-ID being requested (e.g. OBJ-TYPE = “ACTRN” or ”GLTRN”) for the duration of the database transaction. This then blocks other (unrelated) users from obtaining OBJ-IDs until the transaction is committed.

          In testing, appears to be locking issue on OBJID when acquiring a new object id during requisition release; was taking sometimes 13-15 minutes to find & lock one OBJID record. Looking into the code in RQIF, the code is acquiring an object id when using GL/AC commitments. Turned off those flags on GL01, and releasing was fine. Turned the flags back on, and the releasing was slow again.

          In looking further, AP26 and AP126 releases were also slowed.

          In the end, I changed the custom AR560 to acquire OBJIDs in blocks of 1000 at a time (big client), rather than one at a time.
          Thanks for using the LawsonGuru.com forums!
          John
          mark.cook
          Veteran Member
          Posts: 444
          Veteran Member
          6/2/2011 1:58 PM
            That may help point us in the right direction as we have a custom routine running to update pricing for our office supply vendor and releasing the PO's. This rountine was running just before we saw the lock up issue.

            We will dig into that more. Thanks for the insight.
            You are not authorized to post a reply.