What Is The Course Of Action When Missing DB Client Library Symbol Caused Tuxedo Server Failed To Start (Doc ID 2292194.1)

Last updated on JULY 31, 2017

Applies to:

Oracle Tuxedo - Version 8.0 and later
Information in this document applies to any platform.

Goal

User migrated their Oracle DB 9.2.0.6 to 9.2.0.8 + CPUJUL2010 critical patch update.

OS is HP-UX B.11.11 U 9000/800.
Tuxedo version is 8.

After the migration procedure, user failed to start some of their application servers.


Log extract of the errors found:
  $ grep "xxxxx_3/100" ULOG.042817
  211013.ppppp!BBL.11518.1.0: LIBTUX_CAT:541: WARN: Server xxxxx_3/100 terminated
  211013.ppppp!BBL.11518.1.0: LIBTUX_CAT:557: INFO: Server xxxxx_3/100 being restarted
  211014.ppppp!restartsrv.11836.1.-2: server CUSTOMER_3/100: CMDTUX_CAT:1423: ERROR: Pipe error, assume failed.
  211213.ppppp!BBL.11518.1.0: LIBTUX_CAT:541: WARN: Server xxxxx_3/100 terminated
  211213.ppppp!BBL.11518.1.0: LIBTUX_CAT:557: INFO: Server xxxxx_3/100 being restarted
  211214.ppppp!restartsrv.12061.1.-2: server CUSTOMER_3/100: CMDTUX_CAT:1423: ERROR: Pipe error, assume failed.
  211414.ppppp!BBL.11518.1.0: LIBTUX_CAT:541: WARN: Server xxxxx_3/100 terminated
  ...

It seems that there's a common error affecting those processes, it is related to the external symbol 'slmxnoop' dependency not satisfied.

What course of action should user take in this case?

 

Solution

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