DBBL Takes 10 Minutes To Stop When Migration On Windows
Last updated on MARCH 08, 2013
Applies to:Oracle Tuxedo - Version 18.104.22.168.0 and later
Microsoft Windows (32-bit)
When using MP configuration, if doing master migration with aliving master node(not failover, usually planned migration for this case) DBBL on original master node remains 10minutes for stopping the process.
When exiting DBBL process , CMDTUX_CAT:655 outputs, it outputs 10 minutes later from master migration.
That DBBL has already detached from Tuxedo BB, so there is no effect , just remain the process.
It can be executed to back master node again even if old DBBL remains.
This problem happen on Windows platform only.
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