We are faced with the following problem (SQL Anywhere Network Server Version 12.0.1.3537).
asked 23 Nov '16, 05:40 Ilia63 |
Then that does appear to be a 'stuck' dbsrv12 process. I do suspect it could be related to some feature(s) you are using. Maybe external environments, maybe proxy tables, maybe events, ... it would be hard to guess. My leading theory (for the range of builds you are using) would be that you are experiencing a problem related to Intra-Query Parallelism. You can test for this possibility in either of these 2 ways:
The original Intra-query parallelism implementation could cause a hang on shutdown in some cases and the builds mentioned (#2 above) were past all the relevant corrections to that feature. The first option (#) just disables intra-query parallelism and will allow you to factor that feature out from your testing and should be preventative if your issue is related to intra-query parallelism; but can be expected to have some impact upon your performance. answered 24 Nov '16, 11:55 Nick Elson S... Thanks. Most likely I will suggest to the client upgrade (to SQL Anywhere 12.01.4314).
(25 Nov '16, 03:46)
Ilia63
|
You could just be seeing a system failure to flush the last lines (SQL Anywhere - .... stopped) to the media. If this is what has occurred then I would not expect there to be any negative consequences due to it. Do you have any other evidence of a shutdown failure? Do you have extra (or have to kill) dbsrv12.exe processes or reboot the system to correct for this? There might be evidence of a crash or assertion if you run these cmdlines: dbsupport -ls dbsupport -lc {do report any submissions from the first and you will need to be in contact with Product Support for either} answered 23 Nov '16, 13:06 Nick Elson S... Symptoms: unable to connect to the DB on mornings. In order to get them up and running we need to end the process via Task Manager as it is unable to be stopped via SCJVIEW. Windows event log:
ASA12 message log:
(24 Nov '16, 03:32)
Ilia63
|