APAR status
Closed as program error.
Error description
With temp tables the rollback of index deletes (for table DELETEs or UPDATEs) can fail with page check error in bfput. The index will be set BAD after this. Sample assertion: 12:01:50 Assert Failed: Page Check Error in bfput 12:01:50 Who: Session(137, informix@mybox, 29819076, 70000002047b1c8) Thread(216, sqlexec, 70000002043c1a8, 1) File: rsdebug.c Line: 1145 12:01:50 Results: Possible inconsistencies in 'stores7:"informix".mytmp' 12:01:50 Action: Run 'oncheck -cDI stores7:"informix".mytmp' 12:01:50 See Also: tmp/af.4c05e0e, shmem.4c05e0e.0 12:01:53 Page Check Error in bfput 12:01:54 Assert Failed: Rollback error 105 12:01:54 Who: Session(137, informix@mybox, 29819076, 70000002047b1c8) Thread(216, sqlexec, 70000002043c1a8, 1) File: rsextlog.c Line: 1718 12:01:54 Results: Log record (OLDRSAM:DELITEM) in log 39, offset 0x3459c was not rolled back 12:01:54 Action: Use 'onlog' to view the transaction and repair manually. 12:01:54 stack trace for pid 20512964 written to /tmp/af.4c05e0e 12:01:54 See Also: /sqldists/12.10.FC1B2/tmp/af.4c05e0e 12:01:57 Rollback error 105 In the af file you'll find: 12:01:50 bfcheck: bad page: pg_frptr 2841 < sizeof(ifx_page_t) 24 or > slotbeg 2840 and a stack like this: 12:01:50 Stack for thread: 216 sqlexec base: 0x07000000218f4000 len: 69632 pc: 0x00000001000ab6bc tos: 0x07000000219014c0 state: running vp: 1 (oninit)afstack (oninit)afhandler (oninit)affail_interface (oninit)bffail (oninit)buffput (oninit)btadditem (oninit)doitem (oninit)logundo (oninit)rlogm_undo (oninit)rollback (oninit)rsrollback (oninit)isrollback (oninit)sqisrollback (oninit)sqrollback (oninit)aud_sqrollback (oninit)excommand (oninit)sq_execute (oninit)sqmain (oninit)listen_verify (oninit)spawn_thread (oninit)startup One of the conditions for this failure seems to be that rows are inserted into the temp table and then deleted again, then new rows (with new index values!) are inserted and deleted as well, before all gets rolled back.
Local fix
Workaround could be dropping and recreatᄀng the temp table instead of purging and reusing it, or at least to recreate the index on every iteration.
Problem summary
**************************************************************** * USERS AFFECTED: * * ALL DBUSERS using temp tables * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Update to IDS-11.70.xC8 * ****************************************************************
Problem conclusion
Problem Fixed In IDS-11.70.xC8
Temporary fix
Comments
APAR Information
APAR number
IC92919
Reported component name
INFORMIX SERVER
Reported component ID
5725A3900
Reported release
B70
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2013-06-07
Closed date
2014-02-26
Last modified date
2014-02-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
INFORMIX SERVER
Fixed component ID
5725A3900
Applicable component levels
RC10 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B70","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
26 February 2014