We are using SDM in our production environment.
Earlier we did not enecounter any problem in starting the active & back up broker. But nowadays though the acive broker starts alright, the backup broker never starts.The container log - the container housing the back up broker - says "Dual active detected, local saved state STANDALONE & peer saved state STANDALONE".
Without running a clean installation script, is there any way to solve this problem?
Pl. help.
Regards,
Subhendu
hello Subhendu,
You can find your answer in the knowledge Base. hope this help
Be very carefull because you may lost some messages when you will reinitialize broker's storage.
you can also read
ID: P137832 |
Title: "The Sonic tools do not allow easy recovery from a dual active scenario." |
Regards
Chan Jeremy
ID: S267 Title: ""Dual active detected, local saved state STANDALONE and peer saved state STANDALONE." error in container log file" | |
Created: 02/02/2007 | Last Modified: 05/24/2010 |
Status: Verified | |
Symptoms:
| |
Facts:
| |
Cause:
| |
Fixes: The broker disparity can only be resolved by stopping both brokers and initializing one of the databases. Please refer S1213,"How to create or reinitialize a broker's storage" on how to initialize the broker's database. The note from the SonicMQ Deploym |