|
Problem IT31293
|
Status: Closed |
ASSERT FAILURE AND CRASH MAY OCCUR WHEN HANDLING INVALID CHARACTERS IN MULTI-BYTE LOCALES
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
In database environments that are defined with a multi-byte
character locale, for example zh_hk.utf8, there are numerous
byte sequences that are not valid as they do not represent a
defined character. These invalid characters are normally
prevented from being stored as data in tables. If the database
server should encounter such an invalid character then some
operations may fail to correctly handle such a situation
resulting in an Aseert Failure (AF) and crash. The nature of the
AF may be such that a recursive exception occurs causing the
database server to terminate without creating a valid AF file or
shared memory dump.
An example of a server operation that may lead to this type of
problem is the SQL REPLACE function. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC14 and 14.10.xC4. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to Informix Server 12.10.xC14 or 14.10.xC4 (when *
* available). *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix Server prior to 12.10.xC14 and 14.10.xC4. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to Informix Server 12.10.xC14 or 14.10.xC4 (when *
* available). *
**************************************************************** |
| Comment |
Fixed in Informix Server 12.10.xC14 and 14.10.xC4.
NOTE: the majority of the fix is included in 12.10.xC14,
although a second smaller addition to the fix was added after
the release cutoff and will be present in the next release of
12.10. However, 14.10.xC4 contains the complete fix. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.12.2019
04.03.2020
04.03.2020 |
| Problem solved at the following versions (IBM BugInfos) |
12.10.0,
12.10.xC14,
14.10.xC4
|
| Problem solved according to the fixlist(s) of the following version(s) |
