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 IT41349 Status: Closed

With DRINTERVAL 30 or more we get -242/-154 error in online.log when Auto
Update Statistics Evaluation task is run.

product:
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10
Problem description:
With HDR secondary paired to primary and DRINTERVAL is set to 30
or more, on primary server we get
-242/-154 error in online.log when ever Auto Update Statistics
Evaluation task is run.

06/24/22 09:01:27  SCHAPI:  last statement CREATE INDEX
aus_work_info_idx2 ON aus_work_info(aus_info_partnum)
06/24/22 09:01:27  SCHAPI: [Auto Update Statistics Evaluation
47-4] Error -242 Could not open database
table(informix.aus_work_info).

06/24/22 09:01:27  SCHAPI: [Auto Update Statistics Evaluation
47-4] Error -154 ISAM error: Lock timeout Expired

Auto Update Statistics Evaluation task drops and re-creates some
tables in sysadmin database, when this task re-creates the
index, primary server will ship the newly created indexes. In
this process we get -242 error while AUS Evaluation task
creating the index aus_work_info_idx2 on aus_work_info.

If we set DRINTERVAL to 0, then HDR_TXN_SCOPE takes precedence
and we no longer see this error.
We don't see -242 error when we set the DRINTERVAL to smaller
value compared to default value.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 12.10.xC16 and 14.10.xC9.  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC16 or 14.10.xC9.          *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 12.10.xC16 and 14.10.xC9.  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 12.10.xC16 or 14.10.xC9.          *
****************************************************************
Comment
Fixed in Informix Server 12.10.xC16 and 14.10.xC9.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
28.06.2022
15.05.2023
15.05.2023
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)