Results 1 to 2 of 2
  1. #1
    Join Date
    Oct 2013
    Posts
    8

    Unanswered: DB2 UDB, Client-side (app) latches, sqloxlatchterm_app, probe:10

    Hi all,
    The following error triggering in db2diag.log,could anyone please unblock me.

    2014-12-24-10.00.29.842942-300 E114066576E424 LEVEL: Error (OS)
    PID : 1420 TID : 139635703904000PROC : db2fmp (
    INSTANCE: db2inst2 NODE : 000 DB : PRDINFAD
    APPID : *LOCAL.db2inst2.141223092038
    FUNCTION: DB2 UDB, Client-side (app) latches, sqloxlatchterm_app, probe:10
    MESSAGE : ZRC=0x83000010=-2097151984
    CALLED : OS, -, unspecified_system_function OSERR: EBUSY (16)

    2014-12-24-10.05.30.160948-300 E114067001E424 LEVEL: Error (OS)
    PID : 1420 TID : 139635703904000PROC : db2fmp (
    INSTANCE: db2inst2 NODE : 000 DB : PRDINFMR
    APPID : *LOCAL.db2inst2.141223091040
    FUNCTION: DB2 UDB, Client-side (app) latches, sqloxlatchterm_app, probe:10
    MESSAGE : ZRC=0x83000010=-2097151984
    CALLED : OS, -, unspecified_system_function OSERR: EBUSY (16)

    2014-12-24-10.05.30.183036-300 E114067426E424 LEVEL: Error (OS)
    PID : 1420 TID : 139635696576256PROC : db2fmp (
    INSTANCE: db2inst2 NODE : 000 DB : PRDINFRP
    APPID : *LOCAL.db2inst2.141223103102
    FUNCTION: DB2 UDB, Client-side (app) latches, sqloxlatchterm_app, probe:10
    MESSAGE : ZRC=0x83000010=-2097151984
    CALLED : OS, -, unspecified_system_function OSERR: EBUSY (16)

    2014-12-24-10.10.29.847132-300 E114067851E424 LEVEL: Error (OS)
    PID : 1420 TID : 139635705218816PROC : db2fmp (
    INSTANCE: db2inst2 NODE : 000 DB : PRDINFRP
    APPID : *LOCAL.db2inst2.141223091543
    FUNCTION: DB2 UDB, Client-side (app) latches, sqloxlatchterm_app, probe:10
    MESSAGE : ZRC=0x83000010=-2097151984
    CALLED : OS, -, unspecified_system_function OSERR: EBUSY (16)

  2. #2
    Join Date
    Apr 2012
    Posts
    1,034
    Provided Answers: 18
    Post your db2-server version and fixpack, and operating-system details.
    Set the DB2DIAG temporarily to 4 to see if it gives information about which file (or directory) is reporting EBUSY.
    Check your system error log for messages with the same timestamps as the EBUSY messages in db2diag.log.

Posting Permissions

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