home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC10 FixList
12.10.xC16.X5 FixList
11.70.xC9.XB FixList
11.50.xC9.X2 FixList
11.10.xC3.W5 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

Informix - Problem description

Problem IT45318 Status: Closed

POTENTIAL FOR DATA LOSS OR INDEX PROBLEMS IN TABLES LOCATED IN ROOT
DBSPACE WHEN EXTENDED RESERVED PAGES ARE IN USE

product:
INFORMIX SERVER / 5725A3900 / E10 - 
Problem description:
An instance using a sufficiently large number of logical logs,
dbspaces, or chunks may be at risk of data loss or index errors
for tables located in the root dbspace. There are a number of
required conditions:

1. Informix server version 12.10.xC16, 14.10.xC9, 14.10.xC10 or
14.10.xC10W1, or a special build containing the fix for IT40986.
2. For OS platforms where a 4 kB base page size is used, any of
the following: at least 3727 logical logs, 429 dbspaces, or 429
chunks.  For all other OS platforms, using a 2 kB base page
size, any of the following: at least 1846 logical logs, 198
dbspaces, or 198 chunks.

3. Tables, including system catalogs, located in the root
dbspace with an extent that follows within 1 - 31 pages of a
reserved pages extent.
4. A recent update to a data or index page of an in-scope table
that has not been written to the chunk at the time of a
checkpoint.

If all of the above conditions are met then an affected page may
be cleared within the buffer pool before the page is flushed to
the chunk meaning that the update is lost. This could result in
a missing data update or inconsistencies in index pages that may
later give rise to an Assertion Failure such as "bfcheck: bad
page."

Secondary servers may also encounter rollforward errors when
updating tables that are located within the root dbspace.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server 12.10.xC16, 14.10.xC9, 14.10.xC10   *
* amd 14.10.xC10W1.                                            *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC16W1 (or higher) or       *
* 14.10.xC10W2 (or higher).                                    *
****************************************************************
See the following knowledge article for more details:
https://supportcontent.ibm.com/support/pages/notification-and-ad
ditional-details-pertaining-apar-it45318
Local Fix:
Databases with frequent update activity that are by default
located within the root dbspace, such as sysadmin or syscdr, may
be moved to a different dbspace.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server 12.10.xC16, 14.10.xC9, 14.10.xC10   *
* amd 14.10.xC10W1.                                            *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC16W1 (or higher) or       *
* 14.10.xC10W2 (or higher).                                    *
****************************************************************
See the following knowledge article for more details:
https://supportcontent.ibm.com/support/pages/notification-and-ad
ditional-details-pertaining-apar-it45318
Comment
Fixed in Informix Server 12.10.xC16W1 and 14.10.xC1W2.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
23.01.2024
05.03.2024
05.03.2024
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)