11-26-2013 02:14 AM - edited 03-16-2019 08:35 PM
I've just upgraded my test cluster from 8.6.2 to 9.1.2. After over an hour, the publisher DB Replication state is still stuck at state 0. My test cluster is tiny, so upgrades usually go quite quickly.
As this is my test cluster, I can easilly roll back and try again, but I'd be interested to know if anyone else has come across this?
Thanks,
GTG
11-26-2013 02:38 AM
Hi Gordon.
Can you find something strange on ccm logs?
file view activelog cm/log/informix/ccm.log
I've seen something similar in this bug
https://tools.cisco.com/bugsearch/bug/CSCua09290
HTH
Regards
Carlo
Please rate all helpful posts
"The more you help the more you learn"
11-26-2013 02:53 AM
Doh! Should have checked the logs first
The logs are showing lots of "connection rejected" messages..
10:39:02 (8175) connection rejected - no calls allowed for cdraccept
10:39:57 Checkpoint Completed: duration was 0 seconds.
10:39:57 Tue Nov 26 - loguniq 13, logpos 0x4316018, timestamp: 0x2d0666 Interval: 140
10:39:57 Maximum server connections 75
10:39:57 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 22, Llog used 20
10:44:03 (8762) connection rejected - no calls allowed for cdraccept
10:44:58 Checkpoint Completed: duration was 0 seconds.
GTG
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide