The DBBL Does Not Restart When A MIB Call Is Made After the DBBL Goes Down (Doc ID 776630.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo - Version: 8.0 to 9.0
Information in this document applies to any platform.
Information in this document applies to any platform

Goal

Issue can be reproduce by the following step by step:

tmboot -A
kill -9 DBBL
ud32 -C tpsysadm <
SRVCNM<tab>.TMIB
TA_CLASS<tab>T_MSG
TA_OPERATION<tab>GET

tmadmin

tmshutdown


All these operations will hang and then the error message are dropped in the ULOG file:


HHMISS.BOXNAME!BBL.22127.1.0: LIBTUX_CAT:541: WARN: Server DBBL/0 terminated
HHMISS.BOXNAME!BBL.22127.1.0: LIBTUX_CAT:1276: WARN: Forcing deletion of table entries for server DBBL/0.



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