ISH Unreleased Lock On LIBTUX_CAT:5005: WARN: USEM[0] Lock Appears Stuck
Last updated on APRIL 10, 2018
Applies to:
Oracle Tuxedo - Version 12.1.1 and laterInformation in this document applies to any platform.
Symptoms
With SPINCOUNT=0, a lock problem of the ISH may occur with error messages in the log file (ULOG) such as:
145231.YourHostName!BBL.19064.1804359392.0: WARN: USEM[0] sticker 9593 is killed --> ISH process was locking the BB and has been killed
145231.YourHostName!BBL.19064.1804359392.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=9593
145231.YourHostName!TMSYSEVT.19715.2645915360.0: LIBTUX_CAT:6916: WARN: .SysBBDeadLocked: USEM[0] lock appears stuck: held by pid=9593 on host GCTX
145231.YourHostName!ISL.19757.2150065888.0: ISNAT_CAT:1067: ERROR: IIOP Handler died, cleaning up
145345 - ISH.29151 restarted
145231.YourHostName!BBL.19064.1804359392.0: LIBTUX_CAT:5005: WARN: USEM[0] lock appears stuck: held by pid=9593
145231.YourHostName!TMSYSEVT.19715.2645915360.0: LIBTUX_CAT:6916: WARN: .SysBBDeadLocked: USEM[0] lock appears stuck: held by pid=9593 on host GCTX
145231.YourHostName!ISL.19757.2150065888.0: ISNAT_CAT:1067: ERROR: IIOP Handler died, cleaning up
145345 - ISH.29151 restarted
Cause
Sign In with your My Oracle Support account |
|
Don't have a My Oracle Support account? Click to get started |
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms