Assertion failure
Posted in 2004
Topics: Installation, Setup & Upgrades, SQL Development & Query Writing, Error Codes & Troubleshooting, Platform-Specific Issues, Versions, Editions & End-of-Life
Hi all,
My IDS was encountered assertion failure and it had
been occured 3 times for the past 2 months. Every
assertion failure that happen were pointing to "bad
page". The last SQL that being captured in the AF file
was different for every occurence, but they are are
doing the pure SELECT statement. I can't re-produce
the assertion failure from the same SQL statement. If
it's cause by the known bug, do I have a workaround
solution instead of upgrade the engine?
Here's some useful info that may help you guys to help
me.
OS: Solaris 2.7
IDS 7.31.UC2
online.log
-----------
18:33:41 Assert Failed: read_record: bad page
18:33:41 Informix Dynamic Server Version 7.31.UC2X6
18:33:41 Who: Session(77960, informix@kfacdc, 26407,1556088228)
Thread(94722, sqlexec, 5bd5e9e0, 4)
File: rsread.c Line: 2436
18:33:41 Results: Record not read
18:33:41 Action: Please notify Informix Technical
Support.
onstat -g sql
-------------
/usr/informix/bin/onstat -g sql 77960:
Informix Dynamic Server Version 7.31.UC2 -- On-Line
(Prim) -- Up 17 days 04:19:29 -- 316208 Kbytes
Sess SQL Current Iso Lock
SQL ISAM F.E.
Id Stmt type Database Lvl Mode
ERR ERR Vers
77960 SELECT ificsdc DR Not Wait
0 0 7.20
Current statement name : i00073a8b_045c3b53
Current SQL statement :
SELECT max(orgdate) FROM o_failure, outer
(r_prodrollup, r_prodassc )
WHERE orgdate < ? AND opid = ? AND (item = ?
OR fmly_nm = ?) AND
defitem = ? AND defdesc = ? AND
r_prodrollup.sales_item =
r_prodassc.sales_item AND r_prodassc.mrp_item =
item
Last parsed SQL statement :
select mrp_item from r_prodassc a , r_prodrollup p
where a . sales_item =
p . sales_item and p . fmly_nm = ?
onstat -g stk
-------------Stack for thread: 94722 sqlexec
base: 0x5e050228
len: 66048
pc: 0x083400a1
tos: 0x5e05f648state: running
vp: 4
0x083565cd (oninit)afhandler(0x5e05f9f0, 0x5abad6cc,
0x5e917f20)
0x08356017 (oninit)affail_interface(0x2, 0x5abad6cc,
0x5e917f20)
0x082094c2 (oninit)read_record(0x5abad6cc, 0x5e917f20,
0x5de5bfcc)
0x08208730 (oninit)gather_records(0x5bd5eba4,
0x5c6fa974, 0x0)
0x082077e0 (oninit)rsread (0x5e05fdd8, 0x0,
0x5b8ff6e8)
0x083a0f79 (oninit)fmread (0x5, 0x5c6fa974, 0x102)
0x080e4a73 (oninit)sqisread(0x4, 0x5c6fa974, 0x102)
0x080eb4b4 (oninit)readidx (0x4, 0x5c6fa974, 0x102)
0x080ea486 (oninit)gettupl (0x5c6fa814, 0x100,
0x5e0601aa)
0x080e8e16 (oninit)scan_next(0x5c6fa814, 0x5b8ff12c,
0x5be0cc8c)
0x081ca9dc (oninit)join_next(0x5c6fa814, 0x5b8ff114,
0x5be0c9a8)
0x081ca9dc (oninit)join_next(0x5c6fa6b8, 0x6,
0x5c6fa440)
0x081cc38b (oninit)next_row(0x5c6fa650, 0x6,
0x5c6fa440)
0x081cc4ed (oninit)process_non_groupby(0x5c6fa440,
0x5c6fa440, 0x5e060304)
0x081cb45f (oninit)group_open(0x5c6fa440, 0x6,
0x5baa602c)
0x080ee0b9 (oninit)prepselect(0x5c6fa440, 0x6,
0x5baa602c)
0x08167e31 (oninit)open_cursor(0x5baa602c, 0x6, 0x5)
0x081679fd (oninit)sq_open (0x5e060414, 0x8174a8f,
0x0)
0x08174a8f (oninit)sqmain (0x0, 0x0, 0x0)
0x083417b8 (oninit)startup (0x0, 0x0, 0x0)
0x00000000 (***nosymtab***)0x0
Thanks & regards,
Miyaki
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
sending to informix-list
miyaki wrote:
> My IDS was encountered assertion failure and it had
> been occured 3 times for the past 2 months. Every
> assertion failure that happen were pointing to "bad
> page". The last SQL that being captured in the AF file
> was different for every occurence, but they are are
> doing the pure SELECT statement. I can't re-produce
> the assertion failure from the same SQL statement. If
> it's cause by the known bug, do I have a workaround
> solution instead of upgrade the engine?
Don't execute the query? I don't know that it is (or is not) a known
bug. You'd probably get good answers from Tech Support.
> Here's some useful info that may help you guys to help
> me.
>
> OS: Solaris 2.7
> IDS 7.31.UC2
7.31.UC2 is long in the tooth, rather like the operating system.
Both are overdue for an upgrade.
> online.log
> -----------
> 18:33:41 Assert Failed: read_record: bad page
> 18:33:41 Informix Dynamic Server Version 7.31.UC2X6
> 18:33:41 Who: Session(77960, informix@kfacdc, 26407,> 1556088228)
> Thread(94722, sqlexec, 5bd5e9e0, 4)
> File: rsread.c Line: 2436
> 18:33:41 Results: Record not read
> 18:33:41 Action: Please notify Informix Technical
> Support.
Have you chatted with IBM/Informix Technical Support about this?
Why not?
Have you run 'oncheck' diligently, at least on the tables mentioned in
the SQL?
> onstat -g sql
> -------------
> /usr/informix/bin/onstat -g sql 77960:>
> Informix Dynamic Server Version 7.31.UC2 -- On-Line
> (Prim) -- Up 17 days 04:19:29 -- 316208 Kbytes
> Sess SQL Current Iso Lock
> SQL ISAM F.E.
> Id Stmt type Database Lvl Mode
> ERR ERR Vers
> 77960 SELECT ificsdc DR Not Wait
> 0 0 7.20
Oh - you've got HDR running too? Shouldn't be a factor, but worth
mentioning in passing.
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/
Related threads
- Posting from the Informix-list
- Migrating from IDS 9.40.UC6 to 11.50.UC3
- Ip for a network session
- questions onstat -g