Results 1 to 2 of 2
  1. #1
    Join Date
    Sep 2015
    Posts
    17

    Unanswered: Locklist Change in DB2 diag log

    Hello All,

    I see the below 2 messages in the diag log. First message says a very low availability while the second message just after 7 seconds shows a very high available number. There is no lock escalation message. Can you please help let me know the reason the reason around this?

    2015-09-17-09.55.19.922724+330 E259394A605 LEVEL: Warning
    PID : 11993140 TID : 53202 PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000 DB : NOWPROD
    APPHDL : 0-17443 APPID: XXXXXXXXXXXXXX
    AUTHID : DB2INST1 HOSTNAME: nowdbprod
    EDUID : 53202 EDUNAME: db2agent (NOWPROD) 0
    FUNCTION: DB2 UDB, lock manager, sqlpUpdateMemStatus, probe:611
    DATA #1 : <preformatted>
    Locking memory management: LLM-memory low.
    Escalation threshold activated.
    LLM-lock list size = 420184
    LLM-lock list available = 221

    2015-09-17-09.55.26.589188+330 E260000A609 LEVEL: Warning
    PID : 11993140 TID : 33670 PROC : db2sysc 0
    INSTANCE: db2inst1 NODE : 000 DB : NOWPROD
    APPHDL : 0-21508 APPID: YYYYYYYYYYYYYY
    AUTHID : DB2INST1 HOSTNAME: nowdbprod
    EDUID : 33670 EDUNAME: db2agent (NOWPROD) 0
    FUNCTION: DB2 UDB, lock manager, sqlpUpdateMemStatus, probe:611
    DATA #1 : <preformatted>
    Locking memory management: LLM-status normal, all LLM-thresholds resolved.
    LLM-lock list size = 424148
    LLM-lock list available = 332505

    Thanks & Regards,
    Dhiraj

  2. #2
    Join Date
    Oct 2007
    Posts
    246
    Is it causing any issue ?, could be your STMM is ON .

    Regds
    Paul

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •