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 d
bsupport -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
Edit:
To follow up on Thomas' comment below, here's a copy of the proc:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.