DBBL Takes 10 Minutes To Stop When Migration On Windows
(Doc ID 1535433.1)
Last updated on FEBRUARY 09, 2023
Applies to:
Oracle Tuxedo - Version 11.1.1.2.0 and laterMicrosoft Windows (32-bit)
Symptoms
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.
Cause
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
Symptoms |
Cause |
Solution |
References |