Symptom
Customer has encountered server crash by 'Assertion Failed : 101412(16.0.0.807)' three times so far.
Those assertion crash happened while daily batch was running on secondary server ( PADW2 ).
Same SQL scripts are running daily, therefore no deffierence.
But we don't have any clue or reproduction at all.
Following is lists of the assertion failed
2014-10-18 => E. 10/18 04:07:32. *** ERROR *** Assertion failed: 101412 (16.0.0.807)
Page number on page does not match page requested
2015-03-14 => E. 03/14 01:01:40. *** ERROR *** Assertion failed: 101412 (16.0.0.808)
Page number on page does not match page requested
2015-04-14 => E. 04/14 04:32:04. *** ERROR *** Assertion failed: 101412 (16.0.0.808)
Page number on page does not match page requested
2015-03-14
-----------------
Assertion happened at 01:01:40, then the error looks to affect to new connection and resulted in second 'Assertion' error.
I. 03/14 01:01:40. <,33936,COMMIT
E. 03/14 01:01:40. *** ERROR *** Assertion failed: 101412 (16.0.0.808)
Page number on page does not match page requested
I. 03/14 01:01:40. <,33942,CONNECT
I. 03/14 01:01:40. E,33942,-301,Internal database error *** ERROR *** Assertion failed: 101412 (16.0.0.808)
Page number on page does not match page requested -- transaction rolled back
What was running at that time,
- ev_begintxn was running at that time
- DML jobs were running ( Delete SQL, )
- In IQmsg, Signal 10 was logged
Read more...
Environment
SAP IQ 16.0
Product
Keywords
"Assertion failed: 101412" ; "Page number on page does not match page requested" ; , KBA , BC-SYB-IQ , Sybase IQ , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.