We have the synchronization of data of a table between a source
and a target server defined. The number of free pages in the
target server becomes 0 in a dbspace housing the index.
In this situation, if we are running UPDATE SQLs on source
server, then we might see an AF with following stack and server
will go down.
0x00000000014ce3ed (oninit) afstack
0x00000000014d11d9 (oninit) mt_ex_throw_sig
0x00000000014d2cd8 (oninit) afsig_handler
0x00007ff1033f8b10 (Linux)
0x000000000090d6dc (oninit) doupdate
0x000000000090b3de (oninit) chkrowcons
0x000000000091c41a (oninit) dodmlrow
0x00000000007fcfac (oninit) sqcdrdelupd
0x00000000007fc3d7 (oninit) sqcdrDbop
0x000000000121e163 (oninit) dsiResolverThread
0x0000000001148cb5 (oninit) cdrTrampolineThread
0x00000000014bb6b3 (oninit) th_init_initgls
0x000000000150337f (oninit) startup
12:46:38 Assert Failed: No Exception Handler
12:46:38 IBM Informix Dynamic Server Version 14.10.FC7
12:46:38 Who: Session(78, informix@testlab1, 0, 0x45c43be8)
Thread(96, CDRD_4, 45c0d3c0, 1)
File: mtex.c Line: 569
12:46:38 Results: Exception Caught. Type: MT_EX_OS, Context:
mem
12:46:38 Action: Please notify IBM Informix Technical Support.
12:46:38 See Also: /data/logs/af.4487b9e
12:46:39 Blocking whole system for max 600 secs
12:46:43 Thread ID 96 will NOT be suspended because
it is deemed too critical to the server.
12:46:43 See Also: /data/logs/af.4487b9e.
12:46:44 Starting crash time check of:
12:46:44 1. memory block headers
12:46:44 2. stacks
12:46:44 Crash time checking found no problems
12:46:44 mtex.c, line 569, thread 96, proc id 5570, No
Exception Handler.
12:46:44 Releasing server from system block
12:46:47 The Master Daemon Died
12:46:47 PANIC: Attempting to bring system down
The problem can be avoided by ensuring that the dbspaces has
enough space by either adding another chunk or enabling storage
provisioning. |
