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

STRESSING SHMTOTAL WITH DISK_ENCRYPTION TURNED ON CAN CRASH SERVER DURING
PHYSICAL OR LOGICAL LOGGING

product:
INFORMIX SERVER / 5725A3900 / E10 - 
Problem description:
When the problem happens you typically see an assert warning
followed by an assert failed:

04/21/2022 12:19:12   Assert Warning: I/O write chunk 1, pagenum
43300, pagecnt 64
04/21/2022 12:19:12   IBM Informix Dynamic Server Version
14.10.FC8
04/21/2022 12:19:12    Who: Session(321, informix@hostname,
9525, 0x45fceda8)
                Thread(339, sqlexec, 59ac8c28, 1)
                File: rsbuff.c Line: 6001
04/21/2022 12:19:12    Action: Please notify IBM Informix
Technical Support.
04/21/2022 12:19:12   stack trace for pid 17563 written to
INFORMIXDIR/tmp/af.53b920f
04/21/2022 12:19:12    See Also:
INFORMIXDIR/tmp/af.53b920f
04/21/2022 12:19:12   I/O write chunk 1, pagenum 43300, pagecnt
64
04/21/2022 12:19:13   Assert Failed: Dynamic Server must abort
04/21/2022 12:19:13   IBM Informix Dynamic Server Version
14.10.FC8
04/21/2022 12:19:13    Who: Session(321, informix@hostname,
9525, 0x45fceda8)
                Thread(339, sqlexec, 59ac8c28, 1)
                File: rslog.c Line: 3552
04/21/2022 12:19:13    Results: Dynamic Server must abort

An example of a stack at the assert warn.  This shows a create
database was being execute,
however, the stack can be produced from anything that is logged.

12:19:12  Stack for thread: 339 sqlexec

0x00000000014cfead (oninit) afstack
0x00000000014cd869 (oninit) afhandler
0x00000000014ca642 (oninit) afwarn_interface
0x0000000000e7aa21 (oninit) physio
0x0000000000ead560 (oninit) logwrite
0x0000000000ffd88a (oninit) log_put
0x0000000000ff6b7c (oninit) logm_write
0x0000000000eb102f (oninit) logvimage_new
0x00000000010494d1 (oninit) wrt_home
0x0000000001048a4c (oninit) wrtrecord
0x0000000001048593 (oninit) rswrite
0x00000000015a79b1 (oninit) fmwrite
0x0000000000a7eaf6 (oninit) adddata
0x0000000000a7e3b7 (oninit) creatproc
0x000000000071ee75 (oninit) aud_creatproc
0x00000000006069d2 (oninit) excommand
0x0000000000a5f99a (oninit) exstmt_int
0x0000000000a602e8 (oninit) scread
0x0000000000a561ab (oninit) dbcreate
0x000000000071a9de (oninit) aud_dbcreate
0x00000000007c196e (oninit) sqcreatedb
0x0000000000606542 (oninit) excommand
0x0000000000aaf15c (oninit) sq_execute_workhorse
0x0000000000aaf995 (oninit) sq_execute
0x0000000000b93e2e (oninit) sqmain
0x0000000001603a79 (oninit) spawn_thread
0x00000000014bcfb3 (oninit) th_init_initgls
0x00000000015054cf (oninit) startup

Then the stack at the assert fail

12:19:13  Stack for thread: 339 sqlexec

0x00000000014cfead (oninit) afstack
0x00000000014cd869 (oninit) afhandler
0x00000000014ca6e2 (oninit) afcrash_interface
0x0000000000eb2c64 (oninit) logerr
0x0000000000ffc8a6 (oninit) log_put
0x0000000000ff6b7c (oninit) logm_write
0x0000000000eb102f (oninit) logvimage_new
0x00000000010494d1 (oninit) wrt_home
0x0000000001048a4c (oninit) wrtrecord
0x0000000001048593 (oninit) rswrite
0x00000000015a79b1 (oninit) fmwrite
0x0000000000a7eaf6 (oninit) adddata
0x0000000000a7e3b7 (oninit) creatproc
0x000000000071ee75 (oninit) aud_creatproc
0x00000000006069d2 (oninit) excommand
0x0000000000a5f99a (oninit) exstmt_int
0x0000000000a602e8 (oninit) scread
0x0000000000a561ab (oninit) dbcreate
0x000000000071a9de (oninit) aud_dbcreate
0x00000000007c196e (oninit) sqcreatedb
0x0000000000606542 (oninit) excommand
0x0000000000aaf15c (oninit) sq_execute_workhorse
0x0000000000aaf995 (oninit) sq_execute
0x0000000000b93e2e (oninit) sqmain
0x0000000001603a79 (oninit) spawn_thread
0x00000000014bcfb3 (oninit) th_init_initgls
0x00000000015054cf (oninit) startup


Below is an example of the customer failure which occurred
during physical logging
as is believed to be a result of the same underlying issue

22:15:00  Assert Warning: I/O write chunk 350, pagenum 13788650,
pagecnt 65 --> errno = 22
22:15:00   Who: Session(18341513, username, -1, 1c47f3018)
                Thread(1419340837, sqlexec, 22e8b0848, 28)
                File: rsbuff.c Line: 6004
22:15:00   Action: Please notify IBM Informix Technical Support.

22:15:01  IBM Informix Dynamic Server Version 14.10.FC4W1

22:15:01  Assert Failed: Dynamic Server must abort
22:15:01   Who: Session(18341513, username, -1, 1c47f3018)
                Thread(1419340837, sqlexec, 22e8b0848, 40)
                File: rsbuff.c Line: 4814
22:15:01   Action: Reinitialize shared memory
22:15:01  SHM Globals and Master Pool/Master Block Adresses:

0x101409964 oninit :: mt_system + 0x114
0x101431328 oninit :: afhandler + 0x1128
0x1014301d0 oninit :: afcrash_interface + 0xa0
0x100c6ac30 oninit :: bfphysflush + 0x620
0x100c6a03c oninit :: bfphyslogx + 0xc4c
0x100bf227c oninit :: dodrecord + 0x61c
0x100bea350 oninit :: logundo + 0x1b20
0x100e285e4 oninit :: rlogm_undo + 0x1d4
0x100be7b6c oninit :: rollback + 0x114c
0x100be5efc oninit :: rsrollback + 0x33c s
0x10066304c oninit :: sqisrollback + 0x7c
0x1006197cc oninit :: sqrollback + 0xa7c
0x100572dec oninit :: aud_sqrollback + 0xc
0x10092fd10 oninit :: sql_rollback + 0x2a0
0x10092fa44 oninit :: sq_rollback + 0x84
0x1009fbe68 oninit :: sqmain + 0xa48
0x101532220 oninit :: listen_verify + 0x650
0x101531860 oninit :: spawn_thread + 0x18a0
0x1013f0fe8 oninit :: th_init_initgls + 0x168
0x10141e4e4 oninit :: startup + 0x1c4
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 14.10.xC9.                 *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 14.10.xC9.                        *
****************************************************************
Local Fix:
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Users of Informix Server prior to 14.10.xC9.                 *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Informix Server 14.10.xC9.                        *
****************************************************************
Comment
Fixed in Informix Server 14.10.xC9.
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.04.2022
29.09.2022
05.10.2022
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)