Informix 11.50.FC9W3 assert failed question

Hi, I use Informix 11.50.FC9W3 , it's the newest version on 11.50 . today the RSS SERVER is abnormal terminated. blow are some information from online.log and af file. 1) online.log 00:06:51 Maximum server connections 65 00:06:51 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 7517, Llog used 0 00:10:01 stack trace for pid 7274794 written to /informix/tmp/af.d4a71c59 00:10:01 Assert Failed: No Exception Handler 00:10:01 IBM Informix Dynamic Server Version 11.50.FC9W3 00:10:01 Who: Session(512128, query@::ffff:155.11.1.138, -1, 7000002d1e21bc8) Thread(512191, sqlexec, 7000002d1df51a8, 11) File: mtex.c Line: 491 00:10:01 Results: Exception Caught. Type: MT_EX_OS, Context: mem 00:10:01 Action: Please notify IBM Informix Technical Support. 00:10:01 See Also: /informix/tmp/af.d4a71c59 00:10:06 mtex.c, line 491, thread 512191, proc id 7274794, No Exception Handler. 00:10:06 invoke_alarm(): /bin/sh -c '/usr/openv/scripts/informix_logical_log_backup 5 6 "Internal Subsystem failure: 'MT'" "mtex.c, line 491, thread 512191, proc id 7274794, No Exception Handler." ""' 00:10:06 invoke_alarm(): mt_exec failed, status 32512, errno 0 00:10:06 Fatal error in ADM VP at mt.c:14069 00:10:06 Unexpected virtual processor termination, pid = 7274794, exit = 0x100 00:10:06 invoke_alarm(): /bin/sh -c '/usr/openv/scripts/informix_logical_log_backup 5 6 "Internal Subsystem failure: 'MT'" "Unexpected virtual processor termination, pid = 7274794, exit = 0x100" ""' 00:10:06 invoke_alarm(): mt_exec failed, status 32512, errno 0 00:10:06 PANIC: Attempting to bring system down 02:17:47 IBM Informix Dynamic Server Started. 02:17:48 VP pid=11141796 priority fixed at 60Mon Apr 21 02:17:49 2025 02:17:49 Event alarms enabled. ALARMPROG = '/usr/openv/scripts/informix_logical_log_backup'2) stack trace 00:10:01 Stack for thread: 512191 sqlexecbase: 0x0700000335b48000 len: 69632 pc: 0x000000010005bc48 tos: 0x0700000335b56000 state: running vp: 11 0x000000010005be90 (oninit)afstack 0x000000010063491c (oninit)mt_ex_throw_sig 0x0000000100032594 (oninit)afsig_handler 0x000000010015483c (oninit)buffget 0x0000000100154804 (oninit)buffget 0x00000001005fcf2c (oninit)btcurrent 0x00000001001c5090 (oninit)rsreadidx 0x00000001005ceb5c (oninit)fmread 0x000000010067a0f8 (oninit)readidx_old 0x000000010067ed58 (oninit)gettupl 0x0000000100682500 (oninit)scan_next 0x00000001005afdd8 (oninit)getrow 0x00000001005b3f64 (oninit)fetchrow 0x0000000100538b18 (oninit)exfetch 0x0000000100424488 (oninit)sql_nfetch 0x0000000100424a64 (oninit)sq_nfetch 0x000000010026becc (oninit)sqmain 0x00000001002d51a4 (oninit)listen_verify 0x00000001002d33b8 (oninit)spawn_thread 0x0000000100e0b59c (oninit)startup 3) and before the rss instance down, it's running the log apply program and below select statement: ===========------------- - - - - - - /informix/bin/onstat -g ses 512128: IBM Informix Dynamic Server Version 11.50.FC9W3 -- Read-Only (RSS) -- Up 301 days 21:41:24 -- 13493808 Kbytessession effective #RSAM total used dynamic id user user tty pid hostname threads memory memory explain 512128 query - - -1 ::ffff:1 1 196608 167696 off Program : - tid name rstcb flags curstk status 512191 sqlexec 7000002d1df51a8 ---PRR- 12944 running- Memory pools count 2 name class addr totalsize freesize #allocfrag #freefrag 512128 V 700000334800040 192512 28104 171 14 512128*O0 V 700000323ab1040 4096 808 1 1 name free used name free used overhead 0 6576 scb 0 144 opentable 0 3576 filetable 0 832 log 0 16536 temprec 0 20640 keys 0 256 ralloc 0 79288 gentcb 0 1584 ostcb 0 3400 sqscb 0 21656 sql 0 72 hashfiletab 0 552 osenv 0 2600 sqtcb 0 8448 fragman 0 1536 sqscb info scb sqscb optofc pdqpriority optcompind directives 7000002d1b31fc8 70000032e30b028 0 0 2 1 Sess SQL Current Iso Lock SQL ISAM F.E. Id Stmt type Database Lvl Mode ERR ERR Vers Explain 512128 SELECT gapsdb DR Not Wait 0 0 9.20 Off Current statement name : _ifxc0000000000000 Current SQL statement (3) : SELECT businum, sendbkid, msgid, batchseqno, txcid, wkdt, payseqno, payername, paycstmrid, payeraccno, payersttlmacctnm, payersttlmacct, paybkid, rcvbkid, rcvername, rcveraccno, paysttlmbkid, rcvsttlmbkid, paybknm, payeraddr, ctrctnb, chckid, ccy, amt, rmkinf, trstatus, txsts, sndsts, txprccd, txrjctcd, txrjctinf, ansmsgtp, ansmsgid, txrespsts, anstxrjctcd, anstxrjctinf, respps, txnetgdt, txnetgrnd, sttlmdt, provno, orgno, accprovno, accorgno, handprovno, handorgno, turnprovno, turnorgno, autooper, checkoper, corebksts, pltdate, pltnum, chksts, txtpcd, txctgypurpcd, cityflag, trrespcode, trrespmsg, printnum, unisoccd, pyeinnmegnm, pyeinnmegaccno, socorgflownb, chrgsflg, sysdt, systm, mkinfo1, mkinfo2, mkinfo3, mkinfo4, mkinfo5, mkinfo6, createts, updatets FROM BEPS_BATREPLACEBUY_S_HIS AS BEPS_BATREPLACEBUY_S_HIS WHERE ( 1=1 ) AND ( businum >= '2025030?1?4?2?93?1?7?1?6?2?2耷' ) AND ( businum < '20250311524288' )Last parsed SQL statement : SELECT businum, sendbkid, msgid, batchseqno, txcid, wkdt, payseqno, payername, paycstmrid, payeraccno, payersttlmacctnm, payersttlmacct, paybkid, rcvbkid, rcvername, rcveraccno, paysttlmbkid, rcvsttlmbkid, paybknm, payeraddr, ctrctnb, chckid, ccy, amt, rmkinf, trstatus, txsts, sndsts, txprccd, txrjctcd, txrjctinf, ansmsgtp, ansmsgid, txrespsts, anstxrjctcd, anstxrjctinf, respps, txnetgdt, txnetgrnd, sttlmdt, provno, orgno, accprovno, accorgno, handprovno, handorgno, turnprovno, turnorgno, autooper, checkoper, corebksts, pltdate, pltnum, chksts, txtpcd, txctgypurpcd, cityflag, trrespcode, trrespmsg, printnum, unisoccd, pyeinnmegnm, pyeinnmegaccno, socorgflownb, chrgsflg, sysdt, systm, mkinfo1, mkinfo2, mkinfo3, mkinfo4, mkinfo5, mkinfo6, createts, updatets FROM BEPS_BATREPLACEBUY_S_HIS AS BEPS_BATREPLACEBUY_S_HIS WHERE ( 1=1 ) AND ( businum >= '2025030?1?4?2?93?1?7?1?6?2?2耷' ) AND ( businum < '20250311524288' ) and I attached all the document also . it include the online.log in the primary and rss instance, and whole assert file also .It most like a defect in this version. Do anyone know which version fix the problem? any suggestion are welcome. ------------------------------ chuan lu ------------------------------

Hi Chuan, Did you try to `oninit` the RSS? ------------------------------ Sincerely, Dennis ------------------------------

Chuan: This looks like an old bug long ago fixed. For now just restart the RSS and hope it remains online. Long term you should upgrade to a supported version which would be v14.10 or v15.0 (v12.10 is still under support but will go out-of-support within the year). ------------------------------ Art S. Kagel, President and Principal Consultant ASK Database Management Corp. www.askdbmgt.com ------------------------------

Dennis: Yes, I restart the RSS instance successful, and it catch up the primary log also, it work fine. ------------------------------ chuan lu ------------------------------

Ok, I make sense and will suggest the customer to do the upgrade. ------------------------------ chuan lu ------------------------------

HI,Kagel: which website has this defect description? thanks. ------------------------------ chuan lu ------------------------------

Chuan: Likely none. The bug I am thinking of was fixed over a decade ago. Art ------------------------------ Art S. Kagel, President and Principal Consultant ASK Database Management Corp. www.askdbmgt.com ------------------------------