IDS 7.31 Crash
Kurt reported an IDS 7.31.TC6 instance on Windows NT4 panicking once or twice a day, always while an application executed a simple single-row INSERT stored procedure (Insert_T_Buf721); it had run fine on Solaris 8. The online log showed an MT_EX_OS memory exception (c0000005) with "No Exception Handler" and a PANIC. Replies mainly noted the version/OS were out of support and suggested checking parameter/column types and isolating the failing data. No fix was recorded; the poster suspected a known bug in freeing the stored procedure cache.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hello,
We have an IDS 7.31 TC6 instance on Windows NT4 that crashes 1 or 2 times a
day.
In the af-file that is generated, it's always the call of 1 particular stored
procedure that seeems to be the reason for the crash.
...
Current SQL statement :
EXECUTE PROCEDURE Insert_T_Buf721(? , ? , ? , ? , ? , ? , ? , ? , ? , ? ,
? , ? , ? , ? , ? , ? , ? , ? , ?)
...
But the server doesn't always crash on the procedure, sometimes it passes!
The IDS server was recently migrated from a Solaris 8 server were we never had
this problem.
This is the source of the procedure:
CREATE PROCEDURE insert_t_buf721(In_File_In_Ref CHAR(14)
,In_MsgHosp_ref CHAR(14)
,In_MsgHosp_stat CHAR(2)
,In_Dossier_nr INT
,In_Registration_nr CHAR(12)
,In_Hosp_nr CHAR(12)
,In_Rec_Invdat DATETIME YEAR TO SECOND
,In_Rijks_nr CHAR(11)
,In_Verzek_gd CHAR(03)
,In_Verzekerdenr CHAR(13)
,In_Hosp_Ref CHAR(25)
,In_Hosp_begdat CHAR(10)
,In_Dienst_uur INT
,In_Dienst_nr CHAR(03)
,In_Protect_Code CHAR(01)
,In_Field CHAR(02)
,In_Accident_Code CHAR(01)
,In_Msg_Type CHAR(01)
,In_Stock_motive CHAR(3))
INSERT INTO T_Buf721 (File_In_Ref, MsgHosp_ref, MsgHosp_stat, Dossier_nr,
Registration_nr, Hosp_nr, Rec_Invdat, Rijks_nr, Verzek_gd, Verzekerdenr,
Hosp_Ref, Hosp_begdat
,Dienst_uur, Dienst_nr, Protect_Code, Field, Accident_Code, Msg_type,
Stock_motive)
VALUES (In_File_In_Ref, In_MsgHosp_ref, In_MsgHosp_stat, In_Dossier_nr,
In_Registration_nr, In_Hosp_nr, In_Rec_Invdat, In_Rijks_nr, In_Verzek_gd,
In_Verzekerdenr
,In_Hosp_Ref, In_Hosp_begdat,In_Dienst_uur, In_Dienst_nr,
In_Protect_Code,In_Field, In_Accident_Code,In_Msg_Type, In_Stock_motive);
END PROCEDURE;
Has anyone an idea?
KURT VAN GOMPEL wrote: > Hello, > > We have an IDS 7.31 TC6 instance on Windows NT4 that crashes 1 or 2 times a > day. Wow. That is bloody ancient. I'd recommend that you upgrade to a later release, but of course, IDS 7.31 went end of support two days ago. Perhaps it's time to upgrade? ;o) -- Cheers, Obnoxio The Clown http://obotheclown.blogspot.com -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean.
2009/10/2 KURT VAN GOMPEL <kvangompel@caami-hziv.fgov.be>:
> Hello,
>
> We have an IDS 7.31 TC6 instance on Windows NT4 that crashes 1 or 2 times a
> day.
> In the af-file that is generated, it's always the call of 1 particular stored
> procedure that seeems to be the reason for the crash.
> ....
> Current SQL statement :
> EXECUTE PROCEDURE Insert_T_Buf721(? , ? , ? , ? , ? , ? , ? , ? , ? , ? ,>
> ? , ? , ? , ? , ? , ? , ? , ? , ?)
> ....
>
> But the server doesn't always crash on the procedure, sometimes it passes!
>
> The IDS server was recently migrated from a Solaris 8 server were we never
had
> this problem.
>
> This is the source of the procedure:
> CREATE PROCEDURE insert_t_buf721(In_File_In_Ref CHAR(14)
> ,In_MsgHosp_ref CHAR(14)
> ,In_MsgHosp_stat CHAR(2)
> ,In_Dossier_nr INT
> ,In_Registration_nr CHAR(12)
> ,In_Hosp_nr CHAR(12)
> ,In_Rec_Invdat DATETIME YEAR TO SECOND
> ,In_Rijks_nr CHAR(11)
> ,In_Verzek_gd CHAR(03)
> ,In_Verzekerdenr CHAR(13)
> ,In_Hosp_Ref CHAR(25)
> ,In_Hosp_begdat CHAR(10)
> ,In_Dienst_uur INT
> ,In_Dienst_nr CHAR(03)
> ,In_Protect_Code CHAR(01)
> ,In_Field CHAR(02)
> ,In_Accident_Code CHAR(01)
> ,In_Msg_Type CHAR(01)
> ,In_Stock_motive CHAR(3))>
> INSERT INTO T_Buf721 (File_In_Ref, MsgHosp_ref, MsgHosp_stat, Dossier_nr,
> Registration_nr, Hosp_nr, Rec_Invdat, Rijks_nr, Verzek_gd, Verzekerdenr,
> Hosp_Ref, Hosp_begdat>
> ,Dienst_uur, Dienst_nr, Protect_Code, Field, Accident_Code, Msg_type,
> Stock_motive)
>
> VALUES (In_File_In_Ref, In_MsgHosp_ref, In_MsgHosp_stat, In_Dossier_nr,
> In_Registration_nr, In_Hosp_nr, In_Rec_Invdat, In_Rijks_nr, In_Verzek_gd,
> In_Verzekerdenr
>
> ,In_Hosp_Ref, In_Hosp_begdat,In_Dienst_uur, In_Dienst_nr,
> In_Protect_Code,In_Field, In_Accident_Code,In_Msg_Type, In_Stock_motive);
>
> END PROCEDURE;
>
> Has anyone an idea?
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
That'll teach you to forsake sensibility and go to the dark side !! :-))
IDS 7.31 is quite old and out of support, NT4 is very old and very out
of support !!
What error messages are you seeing in the on-line log? Does the table
into which you are inserting match the structure of the procedure call
and do the parameters being passed in match the procedure types??
Keith
I know it is an old version and we are looking to upgrade, but that doesn't help me very much now!!
Hy Keith, Thanks for your response. This is what is mentionned in the logfile: ... 13:10:04 Assert Failed: No Exception Handler 13:10:04 Informix Dynamic Server Version 7.31.TC6 13:10:04 Who: Session(196, pdeclerk@600srv03.caami-hziv.int, 626, 0) Thread(224, sqlexec, 0, 1) Exception at Addr: 0x68e48e, TOS: 0x29af7250, FP:0x29af7268, Exc: c0000005 13:10:04 Results: Exception Caught. Type: MT_EX_OS, Context: mem 13:10:04 Action: Please notify Informix Technical Support. 13:10:42 See Also: af.4c8df8b, shmem.4c8df8b.0 13:10:47 , line -1, thread 224, proc id 306, No Exception Handler. 13:10:47 PANIC: Attempting to bring system down ... Yes, the columns in the table an the procedures do match.
Did this start happening recently, or has this been happening for a while? Another question, have you ever tried loading this data on a test instance when it fails to see if it fails in your test instance? If you have done that, have you thought of breaking the load file up into smaller chunks to see if you can narrow it down to maybe a certain row that might contain a value that does not fit in one of its fields? Larry > To: ids@iiug.org > From: kvangompel@caami-hziv.fgov.be > Subject: Re: IDS 7.31 Crash [17295] > Date: Fri, 2 Oct 2009 09:26:46 -0400 > > Hy Keith, > > Thanks for your response. > This is what is mentionned in the logfile: > .... > 13:10:04 Assert Failed: No Exception Handler > 13:10:04 Informix Dynamic Server Version 7.31.TC6 > 13:10:04 Who: Session(196, pdeclerk@600srv03.caami-hziv.int, 626, 0) > > Thread(224, sqlexec, 0, 1) > > Exception at Addr: 0x68e48e, TOS: 0x29af7250, FP:0x29af7268, Exc: c0000005 > 13:10:04 Results: Exception Caught. Type: MT_EX_OS, Context: mem > 13:10:04 Action: Please notify Informix Technical Support. > 13:10:42 See Also: af.4c8df8b, shmem.4c8df8b.0 > 13:10:47 , line -1, thread 224, proc id 306, No Exception Handler. > 13:10:47 PANIC: Attempting to bring system down > .... > > Yes, the columns in the table an the procedures do match. > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. >
Hello Larry, It's not a bulk load we are doing, it's just an application that calls that specific procedure from time to time to insert a single record. Sometimes it runs without any problem and the record in inserted, sometimes it makes go the server down with a PANIC. I found some information on the IBM site where they talk about a bug in freeing the stored procedure cache, I think it's something like that we are running into. Thanks for your answer anyway!!