IBM Support

LI73875: "FAILURE LOCKING SEGMENT IS IN MEMORY" IN THE DB2DIAG.LOG FILE WHEN WE ACTIVATE DATABASE.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • You may find the following error message in the db2diag.log file
    due to a program logic error when DB2 is trying to allocated a
    single large shared memory segment.
    
    PID     : 28863                TID  : 47046239621632PROC :
    db2pmd
    INSTANCE: db2inst1                  NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloRunPMD, probe:100
    MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
    memory addr"
              DIA8561C A invalid memory block was encountered.
    CALLED  : OS, -, shmctl                           OSERR: EINVAL
    (22)
    DATA #1 : String, 34 bytes
    Failure locking segment in memory.
    
    2008-10-30-12.50.02.869673-240 I8652E609          LEVEL: Error
    (OS)
    PID     : 29529                TID  : 46923152600336PROC :
    db2agent (Sample)
    INSTANCE: db2inst1                  NODE : 000         DB   :
    Sample
    APPHDL  : 0-12                 APPID:
    *LOCAL.db2inst1.081030165002
    FUNCTION: DB2 UDB, SQO Memory Management, sqloRequestMemPinSet,
    probe:130
    MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
    memory addr"
              DIA8561C A invalid memory block was encountered.
    CALLED  : OS, -, shmctl                           OSERR: EINVAL
    (22)
    DATA #1 : String, 34 bytes
    Failure locking segment in memory.
    
    2008-10-30-12.50.04.143486-240 I9262E501          LEVEL: Error
    (OS)
    PID     : 28863                TID  : 47046239621632PROC :
    db2pmd
    INSTANCE: db2inst1                  NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloRunPMD, probe:100
    MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
    memory addr"
              DIA8561C A invalid memory block was encountered.
    CALLED  : OS, -, shmctl                           OSERR: EINVAL
    (22)
    DATA #1 : String, 34 bytes
    Failure locking segment in memory.
    
    2008-10-30-12.50.04.143690-240 I9764E609          LEVEL: Error
    (OS)
    PID     : 29529                TID  : 46923152600336PROC :
    db2agent (Sample)
    INSTANCE: db2inst1                  NODE : 000         DB   :
    Sample
    APPHDL  : 0-13                 APPID:
    *LOCAL.db2inst1.081030165004
    FUNCTION: DB2 UDB, SQO Memory Management, sqloRequestMemPinSet,
    probe:130
    MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
    memory addr"
              DIA8561C A invalid memory block was encountered.
    CALLED  : OS, -, shmctl                           OSERR: EINVAL
    (22)
    DATA #1 : String, 34 bytes
    Failure locking segment in memory.
    
    The error only can be seen under above DB2 V8.2 fp15 on the HPUX
    and linux Platform and DB2_PINNED_BP=YES.
    

Local fix

  • NO
    

Problem summary

  • You may find the following error message in the db2diag.log file
    due to a program logic error when DB2 is trying to allocated a
    single large shared memory segment.
    
    PID     : 28863                TID  : 47046239621632PROC :
    db2pmd
    INSTANCE: db2inst1                  NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloRunPMD, probe:100
    MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
    memory addr"
              DIA8561C A invalid memory block was encountered.
    CALLED  : OS, -, shmctl                           OSERR: EINVAL
    (22)
    DATA #1 : String, 34 bytes
    Failure locking segment in memory.
    
    2008-10-30-12.50.02.869673-240 I8652E609          LEVEL: Error
    (OS)
    PID     : 29529                TID  : 46923152600336PROC :
    db2agent (Sample)
    INSTANCE: db2inst1                  NODE : 000         DB   :
    Sample
    APPHDL  : 0-12                 APPID:
    *LOCAL.db2inst1.081030165002
    FUNCTION: DB2 UDB, SQO Memory Management, sqloRequestMemPinSet,
    probe:130
    MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
    memory addr"
              DIA8561C A invalid memory block was encountered.
    CALLED  : OS, -, shmctl                           OSERR: EINVAL
    (22)
    DATA #1 : String, 34 bytes
    Failure locking segment in memory.
    
    2008-10-30-12.50.04.143486-240 I9262E501          LEVEL: Error
    (OS)
    PID     : 28863                TID  : 47046239621632PROC :
    db2pmd
    INSTANCE: db2inst1                  NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqloRunPMD, probe:100
    MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
    memory addr"
              DIA8561C A invalid memory block was encountered.
    CALLED  : OS, -, shmctl                           OSERR: EINVAL
    (22)
    DATA #1 : String, 34 bytes
    Failure locking segment in memory.
    
    2008-10-30-12.50.04.143690-240 I9764E609          LEVEL: Error
    (OS)
    PID     : 29529                TID  : 46923152600336PROC :
    db2agent (Sample)
    INSTANCE: db2inst1                  NODE : 000         DB   :
    Sample
    APPHDL  : 0-13                 APPID:
    *LOCAL.db2inst1.081030165004
    FUNCTION: DB2 UDB, SQO Memory Management, sqloRequestMemPinSet,
    probe:130
    MESSAGE : ZRC=0x820F0002=-2112946174=SQLO_INV_MEM "Invalid
    memory addr"
              DIA8561C A invalid memory block was encountered.
    CALLED  : OS, -, shmctl                           OSERR: EINVAL
    (22)
    DATA #1 : String, 34 bytes
    Failure locking segment in memory.
    
    The error only can be seen under above DB2 V8.2 fp15 on the HPUX
    and linux Platform and DB2_PINNED_BP=YES.
    

Problem conclusion

  • First fixed in DB2 UDB Version 8.2, FixPak 18
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI73875

  • Reported component name

    DB2 UDB WSUE LI

  • Reported component ID

    5765F4304

  • Reported release

    820

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-11-06

  • Closed date

    2009-09-15

  • Last modified date

    2009-09-15

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 UDB WSUE LI

  • Fixed component ID

    5765F4304

Applicable component levels

  • R820 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"820","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 September 2009