Does anyone have any ideas on where to start looking when a database engine service simply disappears? No assertion, no error in the console log, nothing in the Windows event logs.
Server re-starts without complaint.
asked 20 Sep '12, 08:04
When the SQL Anywhere database server unexpectedly crashes, it will normally catch this event itself and automatically create a mini-dump file and supply this information to dbsupport. Depending upon your submission settings, dbsupport will either auto-submit this information automatically to SAP/Sybase or will hold on to the information until you submit it manually.
If your server is still crashing and no information is being passed to dbsupport, there are other ways to manually collect this diagnostic information from the server (via procdump and psexec, if required). If you need to go this route though, we would recommend that you also open a technical support case with us so that we can work with you on collecting this output and have it analyzed.
A reminder that SQL Anywhere 10.0.x has been end-of-life'd, so there could also be an outstanding technical issue with the product that will not be fixed by a software patch - we will attempt to provide "limited technical assistance" for the product via technical support instead (suggest workarounds, etc.).
"Crashes" can frequently be related to database corruption (although this will typically be reported as an "assertion" in the database console log - I noted that you've already checked this:
Update by Justin Willey - support found the problem in a query evaluation / optimizer routine. The routine was rewritten for v11 so shouldn't be present in v11 or higher versions. See comments below.