Informix - Problem description
Problem IT35939 | Status: Closed |
A TYPO IN ONCONFIG PREVENTS INFORMIX TO START AND GET INMEDIATE SEGMENTATION VIOLATION | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
A typo in onconfig prevents Informix to start and get inmediate segmentation violation ie. (please note the k before the comments) k############################################################### ### # Licensed Material - Property of IBM Corporation # # "Restricted Materials of IBM Corporation" # # IBM Informix Dynamic Server # Copyright IBM Corporation 1994, 2018. All rights reserved. # # Title: onconfig.std Same onconfig with typo works ok on 12.10.xC12 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 12.10.xC15 and 14.10.xC6. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC15 (when available) or * * 14.10.xC6 (when available). * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 12.10.xC15 and 14.10.xC6. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC15 (when available) or * * 14.10.xC6 (when available). * **************************************************************** | |
Comment | |
Fixed in Informix Server 12.10.xC15 and 14.10.xC6. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.02.2021 18.05.2021 18.05.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |