on 2018 Oct 26 6:04 AM
[SQL Anywhere 17.0.8.4103]
We have a single engine (dbsrv17.exe) running multiple databases. Recently we had an assertion error, with the following text appearing in the log:
E. 10/25 19:33:13. ERROR Assertion failed: 200505 (17.0.8.4103) Checksum failure on page 10798
We are not using the '-ufd' switch so based on the help file I would expect the default 'abort' value to be in place i.e. 'The affected database is stopped. The status of the database server and other databases remains unchanged.' However, what actually happened is that the engine stopped (the dbsrv17.exe process ended). It was possible to restart the engine without an assertion but I suspect at some point it will happen again.
Some questions on this:
1) Have I misunderstood the nature of this assertion and it is actually related to the engine rather than a single database?
2) Or is the default value for -ufd not working as documented?
3) Is there any way of finding out from the engine what it thinks the current -ufd value is (some undocumented server or database property)?
4) Assuming that the assertion is related to a database rather than the engine, is there any easy way of finding out which database is the cause? ('easy' being some solution other than trying to divide the databases between multiple engines and see which one fails or running dbvalid across all databases)
I've subsequently found out that when the assertion occurs the engine crashes rather than shuts down gracefully so I'm guessing the actual behaviour of -ufd is not relevant here. I'll open a case with SAP to have a look at the crash dumps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
69 | |
9 | |
8 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.