Informix

Informix

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only
  • 1.  Assert failed,Is it a new defect on 11.50FC9W3? Error in rsidxinfo

    Posted 10 hours ago
      |   view attached

    Hi, experts:

        The instance crashed, below are the messages in online.log, I checked the defect list and defect description in version11.50, and compare the stack trace, it likes a new defect.Do anyone meet those errors? 

    ===================================

    04:00:11  Stack for thread: 26021 sqlexec

     base: 0x070000035c5b7000
      len:   69632
       pc: 0x000000010005bc48
      tos: 0x070000035c5c3360
    state: running
       vp: 8

    0x000000010005be90 (oninit)afstack 
    0x000000010005e190 (oninit)afhandler
    0x00000001001321f0 (oninit)bffail  
    0x000000010013b250 (oninit)rsidxinfo
    0x0000000100613780 (oninit)fmidxinfo
    0x00000001006684b8 (oninit)usindex 
    0x00000001006670d4 (oninit)ustable 
    0x0000000100666900 (oninit)aud_ustable
    0x0000000100672bf0 (oninit)ustatistics
    0x0000000100539bd8 (oninit)excommand
    0x000000010042893c (oninit)sq_execute
    0x000000010026becc (oninit)sqmain  
    0x00000001002d51a4 (oninit)listen_verify
    0x00000001002d33b8 (oninit)spawn_thread
    0x0000000100e0b59c (oninit)startup 

    =========================

    online.log:


    04:00:11  Assert Failed: Page Check Error in rsidxinfo:bad btree node3
    04:00:11  IBM Informix Dynamic Server Version 11.50.FC9W3
    04:00:11   Who: Session(20964, informix@jsgqsptdb1, 59703658, 700000307ae0a68)
            Thread(26021, sqlexec, 700000307b3af60, 8)
            File: rsdebug.c Line: 1105
    04:00:11   Results: Possible inconsistencies in an index of 'gapsdb:"gaps".beps_replacebuy_s'
    04:00:11   Action: Run 'oncheck -cI gapsdb:"gaps".beps_replacebuy_s'
    04:00:11  stack trace for pid 64946524 written to /informix/tmp/af.698db24b
    04:00:11   See Also: /informix/tmp/af.698db24b
    04:00:15  Page Check Error in rsidxinfo:bad btree node3
    04:00:15  invoke_alarm(): /bin/sh -c '/usr/openv/scripts/informix_logical_log_backup 5 6 "Internal Subsystem failure: 'MT'" "Page Check Error in rsidxinfo:bad btree node3" ""'
    04:00:15  invoke_alarm(): mt_exec failed, status 256, errno 0
    04:00:15  Process exited with return code 1: /bin/sh /bin/sh -c /usr/openv/scripts/informix_logical_log_backup 4 2 "Index failure: 'gapsdb:"gaps".beps_replacebuy_s'." "Page Check Error in rsidxinfo:bad btree node3" "/informix/tmp/af.698db24b"
    04:00:23  Checkpoint Completed:  duration was 0 seconds.
    04:00:23  Tue Jun 24 - loguniq 251310, logpos 0xb98c018, timestamp: 0xc9945ab5 Interval: 1163100

    04:00:23  Maximum server connections 5261 
    04:00:23  Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 7239, Llog used 18669

    04:05:23  Checkpoint Completed:  duration was 0 seconds.
    04:05:23  Tue Jun 24 - loguniq 251310, logpos 0xec5e018, timestamp: 0xc997d92e Interval: 1163101

    04:05:23  Maximum server connections 5261 
    04:05:23  Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 13317, Llog used 13024

    04:05:55  Assert Failed: Page Check Error in rsidxinfo:bad btree node3
    04:05:55  IBM Informix Dynamic Server Version 11.50.FC9W3
    04:05:55   Who: Session(21312, informix@jsgqsptdb1, 60031274, 7000002feacdf08)
            Thread(26373, sqlexec, 7000002feb2d338, 8)
            File: rsdebug.c Line: 1105
    04:05:55   Results: Possible inconsistencies in an index of 'gapsdb:"gaps".ncs_transstatusqu'
    04:05:55   Action: Run 'oncheck -cI gapsdb:"gaps".ncs_transstatusqu'
    04:05:55  stack trace for pid 64946524 written to /informix/tmp/af.6aedb3a3
    04:05:55  ERROR: Exception recursion in afhandler (thread 26373).
    04:05:55  invoke_alarm(): /bin/sh -c '/usr/openv/scripts/informix_logical_log_backup 5 6 "Internal Subsystem failure: 'MT'" "ERROR: Exception recursion in afhandler (thread 26373)." ""'
    04:05:55  invoke_alarm(): mt_exec failed, status 256, errno 0
    04:05:55  Fatal error in ADM VP at mt.c:14069
    04:05:55  Unexpected virtual processor termination, pid = 64946524, exit = 0x100

    04:05:56  invoke_alarm(): /bin/sh -c '/usr/openv/scripts/informix_logical_log_backup 5 6 "Internal Subsystem failure: 'MT'" "Unexpected virtual processor termination, pid = 64946524, exit = 0x100
    " ""'
    04:05:56  invoke_alarm(): mt_exec failed, status 256, errno 0
    04:05:56  PANIC: Attempting to bring system down
    04:41:17  IBM Informix Dynamic Server Started.
    04:41:18  VP pid=62063052 priority fixed at 60

    Tue Jun 24 04:41:19 2025

    04:41:19  Event alarms enabled.  ALARMPROG = '/usr/openv/scripts/informix_logical_log_backup'
    04:41:19  Booting Language <c> from module <>

    and I attached the af file, any suggestion are welcome. 



    ------------------------------
    chuan lu
    ------------------------------

    Attachment(s)

    rar
    20250624informixCrashLog.rar   7.16 MB 1 version


  • 2.  RE: Assert failed,Is it a new defect on 11.50FC9W3? Error in rsidxinfo

    Posted 10 hours ago
    Hi, might be a defect. But you will not get a fix for this old version of IDS.
    It is highly recommended to upgrade to a more recent and supported version. 
    Anyway:
    Did you execute the oncheck commands which ae in the message file? These should try to repair the bad pages. 
    In case this would fail, try to drop and recreate the indexes mentioned.

    Best, Marcus 

    Gesendet von Outlook für Android





  • 3.  RE: Assert failed,Is it a new defect on 11.50FC9W3? Error in rsidxinfo

    Posted 9 hours ago

    yes,customer run onckeck and recreate index,I afraid it crashed again.



    ------------------------------
    chuan lu
    ------------------------------



  • 4.  RE: Assert failed,Is it a new defect on 11.50FC9W3? Error in rsidxinfo

    Posted 8 hours ago
    Hi,

    Could be a bug, as I said. Eventually a rare situation, since it came up like possibly after > 10 years of the instance lifetime.
    Or are there traces of the same/comparable error situation before ?
    The odd thing is that it seems to be related to two indexes at the same time.
    If no device failures have occurred (check the system logs), a bug might be the reason. 
    Might occur only occasional, but you cannot know.
    You should thoroughly check the instance with oncheck for other possible page errors with oncheck -cI / oncheck -cD.
    As long as there are only indexes affected, these are quite easy to repair, just in case. 

    Best,


    MARCUS HAARMANN






  • 5.  RE: Assert failed,Is it a new defect on 11.50FC9W3? Error in rsidxinfo

    Posted 40 minutes ago

    Lu:

    I'm guessing that the customer did not oncheck all indexes but only the one or two mentioned in the log messages you posted here and that if you look at the messages around the first crash and the later crash different indexes were mentioned. I would: a) run a full "oncheck -cDI" to check all tables and indexes, and b) that the REAL problem is that they disks are also over a decade old and are in the process of failing! Disk drives last about 4 to 5 years before they start to experience partial media failure. Over time more and more of the media fails and while the firmware will move data that is at risk of irreparable damage to reserved replacement sectors, which it does silently, eventually the drive runs out of replacement sectors and starts to return garbage. My guess is that this is what is happening to them. 

    They need to replace those drives and they need to upgrade to a supported, relicensed version of Informix, namely v14.10 or v15.0. If you are not an IBM or HCL partner, there are several of us here who are partners with IBM or HCL who can help them with the new licenses, including myself.

    Art



    ------------------------------
    Art S. Kagel, President and Principal Consultant
    ASK Database Management Corp.
    www.askdbmgt.com
    ------------------------------



  • 6.  RE: Assert failed,Is it a new defect on 11.50FC9W3? Error in rsidxinfo

    Posted 10 hours ago
    This is an antique, even if a defect it will not be fixed.  The probably don't have the source code and/or environment to build it anymore anyway :-) 

    Cheers
    Paul

    On 6/30/2025 8:23 PM, chuan lu via IBM TechXchange Community wrote:
    01000197c394ebb1-3e730f02-0903-4a30-a90e-e3e3f73ebeee-000000@email.amazonses.com">
    Hi, experts: The instance crashed, below are the messages in online.log, I checked the defect list and defect description in version11.50,... -posted to the "Informix" group