home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
14.10.xC11 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 IT06392 Status: Closed

CREATING A TABLE IN A DBSPACE WITH PAGE SIZE > 4K WILL CORRUPT THE FIRST
EXTENT SIZE

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
Creating a table in a dbspace with page size > 4k will corrupt 
the first extent size in the system tables if it was not 
specified at creation time. 
 
oncheck -cc reports a discrepancy between system tables and disk 
structures: 
 
    Validating systables for database db16 
ERROR: informix.test fextsize 8 != tblspace.fextsize 32 
    TBLspace name                  test 
    Owner                          informix 
    TBLspace number                200045 
    Tabid                          102 
    Row size                       4 
[...]
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL DBUsers using 8K/16K pagesize dbspaces                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IBM Informix Server 12.10                          * 
****************************************************************
Local Fix:
Solution
Problem Fixed In IBM Informix Server 12.10
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
09.01.2015
16.10.2015
16.10.2015
Problem solved at the following versions (IBM BugInfos)
12.10.0
Problem solved according to the fixlist(s) of the following version(s)
12.10.xC5 FixList
12.10.xC5.W1 FixList