This is a discussion on IDS 10.0FCnWm, replication and reversion within the Informix forums, part of the Database Server Software category; --> My customer is running IDS 10.0FC3 on a production system. It's crashed twice in the past week due to ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| My customer is running IDS 10.0FC3 on a production system. It's crashed twice in the past week due to what turned out to a known bug (Bug: 173090 SERVER CRASH WITH "ASSERT FAILED: YIELD_PROCESSOR: CONDITIONAL LATCH COUNT NON-ZERO IN THREAD 7" AT 2ND NODE IN A 2-NODE REPLICATION SCENARIO). Anyway, we've been provided with a version, 10.0FC3W2, which apparently addresses this problem whilst we wait for the pukka 10.0FC4 release due in January. Thinking about testing and resilience, do you think it's safe to assume that a) I can apply this to the secondary in an HDR pair: ie replicate from 10.0FC3 to 10FC3W2? b) If we find something unappetising about 10.0FC3W2 we can revert simply by bouncing the engine and bringing it back up as 10.0FC3 again? I've asked the IBM technician but expect to get back the "official" answer, which I'd expect to be "No, at least for a). Thanks Neil |