Informix - Problem description
Problem IT33823 | Status: Closed |
IFXCLONE FOR AN RSS MAY FAIL WITH "HDR: COULD NOT START HDR SUBSYSTEM." RESULTING IN ENGINE TERMINATING WITH NO DIAGNOSTICS | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem description: | |
At the final stage of attempting to clone an RSS server using ifxclone, the RSS server may terminate with the following: Finished processing open transactions on secondary during startup. HDR: Could not start HDR subsystem. Error 4294967252 Snapshot instantiation failed, killing myself. This APAR is to reflect the lack of any diagnostics being gathered. If this situation is encountered, then a restart of the PRIMARY followed by start of the RSS Secondary, should result in a functioning RSS Secondary; restarting the PRIMARY may not be viable due to PRODUCTION requirements. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 14.10.xC5. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to Informix Server 14.10.xC5. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 14.10.xC5. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to Informix Server 14.10.xC5. * **************************************************************** | |
Comment | |
Fixed in Informix Server 14.10.xC5. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 06.08.2020 07.12.2020 07.12.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |