|
SQL Anywhere 12.0.1.3797 In the logfile of dbsrv12 I see "Starting checkpoint of...". and "Finished checkpoint of ...". This is normally very fast for 1 database. This engine manages 240 databases and it takes serveral minutes. The processor peeks to 100% and we can not log in anymore. Is there anything we can do to prevent starting checkpoint of all the databases at the same time? |
Follow this question
By Email:Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
- *italic* or _italic_
- **bold** or __bold__
- link:[text](http://url.com/ "title")
- image?
- 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: 04 Feb '21, 06:14
question was seen: 659 times
last updated: 08 Feb '21, 07:41
Does this happen every time a checkpoint is taken for one database, they are taken for all 240?
Or does it just happen when dbsrv12.exe is started and stopped? (which is expected)
No, this does not happen every time. I just noticed that dbsrv12 sometimes (1 or 2 times in a week) takes 100% processor time for a short period (few minutes). In the log file I see a lot of Starting and finished checkpoints. Just before these checkpoints I see a lot of
Disconnected TCPIP client's AppInfo: Connection terminated abnormally
When is a start checkpoint logged?
The server decides when to do checkpoint (among other conditions) based on the "idle time", so could it be the server has busily served many connections (and thereby needed to delay checkpoining) and now, those connections somehow unexectedly were disconnected (so rollbacks must be applied), and after that, it is now "idle" enough to do those checkpoints?
Do you know why so many connections where abnormally terminated - because that woulds conern me more...?
What do you mean by that? By default, the start is logged in the message log, so I don't quite understand your question.
Correlation is not causation... it is very unlikely that the checkpoints are the cause of any performance problem; they may be a symptom of some other problem, but not the cause.
FWIW Foxhound works with Version 12 target databases, and it may provide more information about what is going on. (Note that Foxhound itself runs on its own instance of the 32-bit or 64-bit SQL Anywhere 17 network server build 4882 or later; see the Requirements.)