My Oracle Support Banner

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

Last updated on MAY 19, 2020

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:


BBL.PID: LIBTUX_CAT:541: WARN: Server DBBL/0 terminated
BBL.PID: LIBTUX_CAT:1276: WARN: Forcing deletion of table entries for server DBBL/0.



Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.