|
Hello everyone. I am a hardware tech not a Sybase admin or programmer and am troubleshooting a customer's network Their main practice management app is running on Sybase 12 on a Server 2008r2 server with 20gb RAM. Occassionally the Sybase closes with this event logged: "The SQL Anywhere - dv service terminated unexpectedly. It has done this 4 times." We have to open Sybase Central and restart the service and it is ok for a time period. It was about every 2 weeks but it has terminated 4 times in 48 hours. I checked the crash log and it reads: VERSION=12.0.1.3152 FILENAME=C:\ProgramData\SQL Anywhere 12\diagnostics\SA12_20190301_103539_4016.crash_log OS=Windows 2008R2 Build 7601 Service Pack 1 PROCESSOR=X86_64 EXEC_ARCH=X86_64 EXEC_PATH=C:\Program Files\SQL Anywhere 12\Bin64\dbsrv12.exe MODULE_PATH=C:\Program Files\SQL Anywhere 12\Bin64\dbserv12.dll EXCEPTION_PTR=000000001DFDF500 EXCEPTION_CODE=3221225477 EXCEPTION_FLAGS=0 EXCEPTION_RECORD=0000000000000000 EXCEPTION_ADDRESS=0000000020168F64 EXCEPTION_NumParameters=2 EXCEPTION_Param0=0000000000000000 EXCEPTION_Param1=0000000000000248 TRYING_TO_SAVE_MINI_DUMP C:\ProgramData\SQL Anywhere 12\diagnostics\SA12_20190301_103539_4016.dmp DUMPLEVEL 0 SAVING_MINI_DUMP_COMPLETED CRASH_LOG_COMPLETE ATTEMPTING_TO_SUBMIT_MINIDUMP... The db file is 2.8gb, is that an OK size? I cannot find any other logs. The Software support reps say it is an environmental issue. the staff say they do nothing unusual and nothing they have always done. I am looking for tips and suggestions to find out what is going on or relay to the software support. Thanks in advance |
|
There's nothing here that would suggest an environmental issue. It could be a bug or it could possibly be some file corruption. There could be some information in the console log if you are saving that with the -o switch. However, version 12 is long out of support. Version 16 is also out of support (there were no versions 13-15). Latest release is 17.0.9 -- you could try using that. John S, I would gladly use the -o switch, not sure where or how. Please remember I am a hardware tech trying to help a customer. Also updating to ver 17 is a cost to the customer that I have not addressed with the customer. It that is the answer, meaning that will fix the issue, then I will get right on it. Thank you
(01 Mar '19, 11:23)
chapindoug
C:\Program Files\SQL Anywhere 12\Bin64\dbsrv12.exe -hvSQLANYs_dv
(01 Mar '19, 11:53)
chapindoug
Replies hidden
I'll assume that you found that command line in the registry, right? Since you are already in the registry, you can change the command line parameters there. For services, the command line parameters are stored in a different key called 'Parameters'. I think this would be HKEY_LOCAL_MACHINE\CurrentControlSet\Services\<servicename>\Parameters. You can add "-o filename" to the parameters and specify a full path to a local file. You will need to restart the service for the changes to take effect. With no knowledge of what problem v12 is encountering, I cannot tell you if the problem is fixed in v17. I also don't know if you have the most recent v12 for that matter. In the end, though, there are no more fixes coming for v12.
(01 Mar '19, 13:11)
John Smirnios
Well, 12.0.1.3152 was an early 12.0.1 build, so way before the latest EBF (12.0.1.4436 or the like)?
(01 Mar '19, 13:58)
Volker Barth
I told the Software support rep we need a database check and he ran a validation and the db would not pass. He found data issues in many tables and he recovered and rebuilt. He said, "Now we have to wait and see." So we are waiting and seeing. If it still occurs we will move the db to a different server. I sure hope it works now. The one thing I don't understand is that with the help of John S I knew to tell them to check for data corruption. Wonder why I had to tell them that?
(01 Mar '19, 14:46)
chapindoug
|
