|
Problem IT17797
|
Status: Closed |
PROXYBTCLEAN THREADS CAN BE MISTAKENLY STARTED ON A STANDALONE SERVER
|
| product: |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 |
| Problem description: |
When a standalone server is started with logrecovery
proxyBTClean are mistakenly started
when index operations are replayed in fast recovery.
IBM Informix Dynamic Server Version 12.10.FC7W1 -- On-Line -- Up
15 days
18:38:28 -- 644004 Kbytes
Threads:
tid tcb rstcb prty status
vp-class name
11 c00000003203f510 c000000030814030 3 yield time 1cpu
main_loop()
12 c0000000320d4030 0 1 running 17soc*
soctcppoll
13 c00000003212a710 0 1 running 18soc*
soctcppoll
14 c000000032178cc0 0 2 yield forever
1cpu* soctcplst
22 c0000000325439d0 c0000000308174e0 1 yield time 9cpu
btscanner_0
23 c00000003258dd30 c000000030817da8 3 cond wait
ReadAhead 9cpu readahead_0
24 c0000000325e1240 c000000030818670 3 yield time 10cpu
auto_tune
41 c000000032dfc190 c000000030821bb8 1 yield time 9cpu
proxyBTClean_1
42 c000000032dfc9f0 c000000030822480 1 yield time 9cpu
proxyBTClean_2
43 c000000032e992f0 c000000030822d48 1 yield time 1cpu
proxyBTClean_3
44 c000000032eec660 c000000030823610 1 yield time 1cpu
proxyBTClean_4
45 c000000032f58030 c000000030823ed8 1 yield time 11cpu
proxyBTClean_5 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Possible occurrance of problem during start up after *
* deletion from indexed table was interrupted (or immediately *
* followed) by non-clean termination of Informix server. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Update to IBM Informix Server 12.10.xC9 or newer. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.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) |
