Informix - Problem description
Problem IT35515 | Status: Closed |
INSUFFICIENT SYNCHRONIZATION OF (MIRROR CHUNK) RESERVED PAGES EXTENSIONS AMONG CLUSTER NODES | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem description: | |
Primary server and secondaries can disagree on existence (or location) of mirror chunk extended reserved pages, also leading to extent overlaps in rootdbs and potentially worse consequences. This can occur when MIRROR onconfig parameter gets modified, from 1 to 0, on primary and, while the actual corruption occurs on the secondaries, it would only lead to real trouble once such secondary assumes primary (or standard) role, even if only temporarily. An indication for this problem is 'oncheck -ce|-pe rootdbs' reporting extent overlap between reserved pages and other extents, on a secondary server or one that once was a secondary server. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 14.10.FC7. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server prior to 14.10.FC7. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 14.10.FC7. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server prior to 14.10.FC7. * **************************************************************** | |
Comment | |
Fixed in Informix Server 14.10.FC7. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.01.2021 02.11.2021 02.11.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |