Informix - Problem description
Problem IT40129 | Status: Closed |
CONVERSION FAILED ON RSS SERVER WHEN ANY LOGICAL LOG IS NOT MARKED AS BACKED UP ON RSS | |
product: | |
INFORMIX SERVER / 5725A3900 / E10 - | |
Problem description: | |
When RSS stop before logical log marked as backed up, it will failed in conversion and backup of logs not possible on RSS prior to 14.10.FC6. Below message in online.log on RSS 10:55:30 Conversion halted because logs are not backed up. To continue conversion it is necessary to restart prior server and backup logical logs. 10:55:30 Conversion failed. 10:55:30 FAILED 10:55:30 Restart conversion after fixing the problem. 10:55:30 oninit: Fatal error in shared memory initialization 10:55:30 IBM Informix Dynamic Server Stopped. Make sure all Logical logs marked as backed up on RSS before start upgrade.Need to rebuild RSS from level 0 backup if Primary already upgraded to newer version. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 14.10.xC9. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 14.10.xC9. * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 14.10.xC9. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 14.10.xC9. * **************************************************************** | |
Comment | |
Fixed in Informix Server 14.10.xC9. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.03.2022 06.10.2022 06.10.2022 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |