Symptom
- The database server does not restart because of Assertion failed 200505 Checksum failure on page xxxxx
- An example of what can be seen in the database server console is below:
SQL Anywhere Personal Server Version 17.0.9.4857
Advanced Edition
Copyright © 2018 SAP SE or an SAP affiliate company.
All rights reserved.
Use of this software is governed by the SAP Software Use Rights Agreement.
Refer to http://www.sap.com/about/agreements.html.
Connection limit (Personal Server): 10
Processors detected: 4 logical processor(s) on 2 core(s) on 1 physical processor(s)
Processor license restriction (Personal Server): all logical processors on at most 4 core(s) on at most 1 physical processor(s)
This server is licensed to use: all logical processors on at most 4 core(s) on at most 1 physical processor(s)
Processors in use by server: 4 logical processor(s) on 2 core(s) on 1 physical processor(s)
This server is licensed to:
SAP
SAP
Running Windows 10 Build 16299 on X86_64
Server built for X86_64 processor architecture
476452K of memory used for caching
Minimum cache size: 69536K, maximum cache size: 14815320K
Using a maximum page size of 4096 bytes
Multiprogramming level: 20
Starting database "Business" (C:\db\myDB.db) at Fri Oct 12 2018 09:36
*** ERROR *** Assertion failed: 200505 (17.0.9.4857)
Checksum failure on page 87707
3. Executing dblocate utility returns No servers found
Read more...
Environment
SAP SQL anywhere 17
Product
Keywords
crash, corruption, corrupt, recovery, salvage , KBA , BC-SYB-SQA-SRV , SQL Anywhere - Server , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.