SQL error (-959) Assert Failed during add column

Hello we migrated to Informix version 12.10 FC11 last week and since then we can no longer create a column in tables We have a assert failed when we run "alter table ma_table add (mon_champ varchar (8));" 15:52:20 Assert Failed: No Exception Handler 15:52:20 IBM Informix Dynamic Server Version 12.10.FC11 15:52:20 Who: Session(586, stat3@mcougnaud-lb.siege.cer85.com, -1, 0x55f5b218) Thread(671, sqlexec, 55f2eee8, 1) File: mtex.c Line: 508 15:52:20 Results: Exception Caught. Type: MT_EX_OS, Context: mem 15:52:20 Action: Please notify IBM Informix Technical Support. 15:52:20 See Also: /opt/IBM/informix/tmp/af.6879f24 15:52:22 Thread ID 671 will now be suspended. 15:52:22 Process exited with return code 126: /bin/sh /bin/sh -c /opt/IBM/informix/etc/alarmprogram.sh 4 6 "Internal Subsystem failure: 'MT'" "Thread ID 671 will now be suspended." "" 6501 15:53:26 Checkpoint Completed: duration was 0 seconds. 15:53:26 Fri Nov 9 - loguniq 28534, logpos 0xea2b018, timestamp: 0x7c13d850 Interval: 752477 it seems incredible ! What is the problem ? thanks for your help.

The message log output is showing an SQL level error code of -126 which indicates that there is a bad row in that table. So, first thing would be to run oncheck -cDI on that table to see if there is a problem and if oncheck can correct it. If that does not fix the problem, the next step would be to call IBM and open a PMR.

thanks a lot for your help I just run an oncheck -cDI cer85:ma_table : no error I'm calling IBM support

I don't think there is a '-126' SQL error code; the '126' is a shell return code from 'alarmprogram.sh'. For the 126 error you should refer to this: http://www-01.ibm.com/support/docview.wss?uid=swg21635728 To get any further help from the group you'd need to post the AF file but really it's one for Informix support. I did a quick test of adding a similar column in 12.10.FC11 and it works for me and I am sure we've done several of these in production so you must have hit something unusual. Ben.

we have just migrated to version 12.10 FC12, the error has been corrected, we have no problem creating new fields in our tables. IBM told us it was a bug Thanks for your help