When IQ server suddenly faces 'Assertion failed: 200509', there are a few causing factors.
1) By IQ internal problem
: A certain operation in IQ or SA side, it can cause assertion failed. Recently in IQ16, there are two reference cases CR-786120, 800969.
This can cause recovery failure in transaction log at start-up. Those known issues are going to be resolved or already fixed.
2) By non-IQ problem : For example unexpected overwritten, file-system malfunction....etc
3) ...etc ( unknown if there is )
This note is a case study of above '2)' case.
In this case, while server was running, suddenly a customer DB sent 'Assertion failed' error and crash.
I. TDS 6: result row: 2016/09/12 3:52:37.127 PM
I. TDS 6: request complete
I. Starting checkpoint of "NLSDEV" (NLSDEV.db) at Mon Sep 12 2016 15:53
E. *** ERROR *** Assertion failed: 200509 (220.127.116.114)
Checksum of critical sectors for page 0 failed
After the 'Assertion failed', recovery failed at start-up due to invalid transaction log.
I. Database recovery in progress
I. Last checkpoint at Mon Sep 12 2016 15:46
I. Checkpoint log...
I. Transaction log: /usr/sap/NLSDEV/sapdata/log/NLSDEV_log.log...
E. Error: Cannot open transaction log file -- /usr/sap/NLSDEV/sapdata/log/NLSDEV_log.log is an invalid transaction log
E. Cannot open transaction log file -- /usr/sap/NLSDEV/sapdata/log/NLSDEV_log.log is an invalid transaction log
"Assertion failed: 200509" ; "invalid transaction log" ; "Checksum of critical sectors for page" ; , KBA , BC-SYB-IQ , Sybase IQ , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.