Re: Assert Failed.
Posted in 2003
Topics: Installation, Setup & Upgrades, Error Codes & Troubleshooting, Platform-Specific Issues, Versions, Editions & End-of-Life
Hi, Pls show me how to correct this problem whether
you experienced it. Platform : RedHat 7.3, IDS9.21.UC4-1with GLIBC_2.2.5-34,
Kernel_2.4.18-3When run ONINIT -iy utility at first time, the problem issued
belows $oninit -iy Oninit: relocation Error: /var/lib/libthread.so.0: symbol
__on_exit, version
GLIBC_2.0 not defined on file libc.so.0 with link time reference. However,
it's no problem when i install it on RedHat 7.2 ( Glibc_2.2.4.-13,
Kernel_2.4.7-10). Best regards, Bernard.
"ART KAGEL, BLOOMBERG/ 65E 55TH" <KAGEL@bloomberg.net> wrote:Looks like an
engine bug. Contact tech support and see if it is fixed in a
later version like a later 9.21 release or 9.3 or 9.4. BTW itis normally better
to post to CDI, the IDS Forum, or the Linux Forum as more users will see the
problem and likely recognize it. I'm doing this a long time but even I haven't
seen it all.
Art S. Kagel
----- Original Message -----
From: Kam Bernard
At: 4/14 0:37
>
> Hi Art Kagel,
>
> IDS 9.21.UC1, RedHat 7.3
>
> While i insert into BLOB column or do SELECT data from BLOB column, then the
> Transaction failed.
>
> The below is error mesgs in online.log file
>
> =============================
>
> Assert Failed: Exeption caught Type MT_EX_OS, context: mem>
> Who: session(69, infromix@business,4442,292975944)
>
> Thread(105,sqlexec, 1173b338,1)
>
> File: mtext.c line:356
>
> Action:p leasenotify information tech support
>
> Stack for thread :105 sqlexec>
> WARNING: 1 mem pools not freed.(destroy-session) user: informix, prog, ses
id:65
>
> Assert failed: pool not freed
>
> pool name:65*01, address: 12226020
>
> ========================================
>
> please help how to correct it.
>
>
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Tax Center - File online, calculators, forms, and more
> ATTACHMENT part 2 application/octet-stream name=85913991.htm
---------------------------------
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
I think it is a known problem where our customized libpthread.so does not
work correctly on RH 7.3 ... The reason for this error is that the _on_exit
funciton is declared as PRIVATE which causes our supplied pthread library
to fail ...The workaround is to use the system's libpthread ...so, you need
to do the following:
a) Remove the link /var/lib/libpthread.so.0
b) Run a ldd $INFORMIXDIR/bin/oninit to see which libpthread it picks up
now ... (I think it should be now /lib/libpthread.so.0) ..
HTH
Thanx much,
Rajib Sarkar
Advisory Support Engineer (Wells Fargo Bank)
IBM Data Management Group
Ph : (602)-217-2100
Fax: (602)-217-2100
As long as you derive inner help and comfort from anything, keep it --
Mahatma Gandhi
"Kam Bernard "
<bernard_kam2002@ To: ids@iiug.org
yahoo.com> cc:
Sent by: Subject: Re: Assert Failed. [934]
forum.subscriber@
iiug.org
04/15/2003 10:45
PM
Hi, Pls show me how to correct this problem whether you experienced it.
Platform : RedHat 7.3, IDS9.21.UC4-1with GLIBC_2.2.5-34,
Kernel_2.4.18-3When run ONINIT -iy utility at first time, the problem
issued belows $oninit -iy Oninit: relocation Error:
/var/lib/libthread.so.0: symbol __on_exit, version
GLIBC_2.0 not defined on file libc.so.0 with link time reference. However,
it's no problem when i install it on RedHat 7.2 ( Glibc_2.2.4.-13,
Kernel_2.4.7-10). Best regards, Bernard.
"ART KAGEL, BLOOMBERG/ 65E 55TH" <KAGEL@bloomberg.net> wrote:Looks like an
engine bug. Contact tech support and see if it is fixed in a
later version like a later 9.21 release or 9.3 or 9.4. BTW itis normally
better
to post to CDI, the IDS Forum, or the Linux Forum as more users will see
the
problem and likely recognize it. I'm doing this a long time but even I
haven't
seen it all.
Art S. Kagel
----- Original Message -----
From: Kam Bernard
At: 4/14 0:37
>
> Hi Art Kagel,
>
> IDS 9.21.UC1, RedHat 7.3
>
> While i insert into BLOB column or do SELECT data from BLOB column, then
the
> Transaction failed.
>
> The below is error mesgs in online.log file
>
> =============================
>
> Assert Failed: Exeption caught Type MT_EX_OS, context: mem>
> Who: session(69, infromix@business,4442,292975944)
>
> Thread(105,sqlexec, 1173b338,1)
>
> File: mtext.c line:356
>
> Action:p leasenotify information tech support
>
> Stack for thread :105 sqlexec>
> WARNING: 1 mem pools not freed.(destroy-session) user: informix, prog,
ses
id:65
>
> Assert failed: pool not freed
>
> pool name:65*01, address: 12226020
>
> ========================================
>
> please help how to correct it.
>
>
>
>
>
> ---------------------------------
> Do you Yahoo!?
> Yahoo! Tax Center - File online, calculators, forms, and more
> ATTACHMENT part 2 application/octet-stream name=85913991.htm
---------------------------------
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
Hi, I am using IDS Version9.21.UC4 running in Sun E450. Recently, the informix database ususally down with following messages in online.log: 18:47:57 Assert Failed: No Exception Handler 18:47:57 Who: Session(41327, informix@server_1a, 14926, 705960568) Thread(41358, sqlexec, 2a119658, 6) File: mtex.c Line: 405 18:47:57 Results: Exception Caught. Type: MT_EX_OS, Context: mem 18:47:57 Action: Please notify Informix Technical Support. 18:47:57 Stack for thread: 41358 sqlexec Is it the same case? Thank you.
That's funny, I've had the same problem - also on a Sun server 09:36:40 Assert Failed: No Exception Handler 09:36:40 Who: Session(4457, cshbet@sf-cqa-satdb01, 2401, 286690916) Thread(4629, sqlexec, 1114c818, 1) File: mtex.c Line: 420 09:36:40 Results: Exception Caught. Type: MT_EX_OS, Context: mem 09:36:40 Action: Please notify Informix Technical Support. 09:36:40 Stack for thread: 4629 sqlexec -----Original Message----- From: HON ALAN [mailto:alan1234@netvigator.com] Sent: Thursday, April 17, 2003 8:48 PM To: ids@iiug.org Subject: Re: Re: Assert Failed. [961] Hi, I am using IDS Version9.21.UC4 running in Sun E450. Recently, the informix database ususally down with following messages in online.log: 18:47:57 Assert Failed: No Exception Handler 18:47:57 Who: Session(41327, informix@server_1a, 14926, 705960568) Thread(41358, sqlexec, 2a119658, 6) File: mtex.c Line: 405 18:47:57 Results: Exception Caught. Type: MT_EX_OS, Context: mem 18:47:57 Action: Please notify Informix Technical Support. 18:47:57 Stack for thread: 41358 sqlexec Is it the same case? Thank you.
Hi, all,
Such asserts usually create 'af' files in /tmp directory.
This 'af' file should contain almost complete 'onstat -a'
output and also stack trace for user threads.
This file 'af' can give a real picture of what is happening.
Many different Informix errors can cause the same simple
'online.log' output
Formally, 'af' file can be sent to Informix technical support.
You can also try to analyze it youself
------------------------------------------
Alexey Sonkin
-----Original Message-----
From: Terrence Mu.... [mailto:terrence@wagerworks.com]
Sent: Friday, April 18, 2003 3:56 PM
To: ids@iiug.org
Subject: Re: Assert Failed. [965]
That's funny, I've had the same problem - also on a Sun server
09:36:40 Assert Failed: No Exception Handler
09:36:40 Who: Session(4457, cshbet@sf-cqa-satdb01, 2401, 286690916)
Thread(4629, sqlexec, 1114c818, 1)
File: mtex.c Line: 420
09:36:40 Results: Exception Caught. Type: MT_EX_OS, Context: mem
09:36:40 Action: Please notify Informix Technical Support.
09:36:40 Stack for thread: 4629 sqlexec
-----Original Message-----
From: HON ALAN [mailto:alan1234@netvigator.com]
Sent: Thursday, April 17, 2003 8:48 PM
To: ids@iiug.org
Subject: Re: Re: Assert Failed. [961]
Hi,
I am using IDS Version9.21.UC4 running in Sun E450. Recently, the informix
database ususally down with following messages in online.log:
18:47:57 Assert Failed: No Exception Handler
18:47:57 Who: Session(41327, informix@server_1a, 14926, 705960568)
Thread(41358, sqlexec, 2a119658, 6)
File: mtex.c Line: 405
18:47:57 Results: Exception Caught. Type: MT_EX_OS, Context: mem
18:47:57 Action: Please notify Informix Technical Support.
18:47:57 Stack for thread: 41358 sqlexec
Is it the same case? Thank you.