|
Problem IT18142
|
Status: Closed |
CREATION OF INDEX ON SDS PRIMARY CAN HANG IN IPL THREAD EVEN WHEN LOG_INDEX_BUILDS IS NOT ACTIVE
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
When you create an index on an SDS primary you may observe this
index creation to hang while an ipl (index page logging) thread
is waiting for an ipl_commit() to finish.
This can happen when there are transactions that started some
logs ago.
On a primary with at least one active SDS node this will happen
regardless of the setting of LOG_INDEX_BUILDS. Even when
LOG_INDEX_BUILDS is switched off, the primary will use the ipl
thread if at least one active SDS node is connected.
The stack of the ipl thread:
yield_processor_mvp
mt_yield
ipl_commit
ipl_scanner_thread
th_init_initgls
startup
The output of onstat -l
address number flags uniqid begin
size used %used
44c8cc90 1 U-B---- 79 1:25263
5000 14 0.28
44c8ccf8 2 U------ 80 1:30263
5000 11 0.22
44c8cd60 3 U------ 81 1:35263
5000 1 0.02
44c8cdc8 4 U------ 82 1:40263
5000 9 0.18
44c8ce30 5 U------ 83 1:45263
5000 5 0.10
44c8ce98 6 U---C-L 84 1:50263
5000 71 1.42
and onstat -x
44c78e30 A-B-- 44c3a6a8 3 80:0x9018
80:0x9050 COMMIT 00:00:00 0
To let the index creation continue you need to terminate the
oldest open transaction(s). |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Any customer using SDS will see this behavior. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to IBM Informix Server 12.10.xC9 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 28.11.2016
10.07.2017
10.07.2017 |
| Problem solved at the following versions (IBM BugInfos) |
12.10.xC9
|
| Problem solved according to the fixlist(s) of the following version(s) |
