Please be aware that the content in SAP SQL Anywhere Forum will be migrated to the SAP Community in June and this forum will be retired.

I've been using SA since the Watcom days and never looked back. But once in a while I'll upgrade to a new EBF (for a reason), run some tests, so far so good, will then push the upgrade to the production server only to find out that without any apparent reason the database server crashes silently on one halfway complex query or stored procedure that's been working without a glitch for the past couple of years or longer...

This is actually a question, not gratuitous lamentations.

I'd like to know what the recommended practice is for troubleshooting what's causing the crash. There are times when rolling back the EBF is not really an option.

Here's what I've done:

  • confirmed the crash with EBF 2558 on various Windows platforms, both 32 and 64bit.
  • confirmed that the proc works with 11.0.1 until EBF 2550
  • rebuilt the database using dbunload
  • ran dbsupport -lc and dbsupport -sa to let Sybase Engineering know
  • restarted the server with request logging on: -zr all -zo "filename"

Now, unless I'm not reading it correctly, the log file does not provide any information on why the server crashes. All I can see is a trace of various blocks in a stored procedure being executed, then nothing more when the proc should be doing a SELECT. I guess the database server crashes first and stops logging.

Short of trying to make sense of the dump file which Sybase Engineering are getting, is there anything else I can do to try and isolate what causes the crash?

I understand this is situation I could report to Sybase directly, if I had a support plan that is ( not an option for budgetary reasons ). I'm reporting the matter using Case Express.

Is there anything else I can do to:

  • isolate the cause of the crash on my own
  • help Sybase correct what must be a SA bug


To follow up on Thomas' comment below, here's a copy of the proc:

asked 05 Mar '11, 16:43

Vincent%20Buck's gravatar image

Vincent Buck
accept rate: 15%

edited 05 Mar '11, 19:55


Cross-posted from Danke Volker für den Hinweis.

(05 Mar '11, 16:57) Vincent Buck

If you can show some source code perhaps it is possible to rewrite the select. Is it possible to get the plan of the Query before and after the EBF ?

(05 Mar '11, 17:03) Thomas Dueme...

We'll try to diagnose the crash as quickly as we can with the dbsupport submission. If you can provide the dbsupport submission numbers here (dbsupport -ls), we might be able to look into the issue a bit further for you.

If you wanted to track the issue through engineering, you should open a technical support case with us, so you that can be notified regarding the resolution and request an EBF with this fix:

For now, downgrading to would be your only real option. Were you just testing with 2558 or were you looking for a specific fix?

(11 Mar '11, 13:45) Jeff Albion
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 05 Mar '11, 16:43

question was seen: 2,903 times

last updated: 11 Mar '11, 13:45