Symptom
- When diagnosing certain crash issues with SQL Anywhere on Microsoft Windows, it may have been required to generate a full dump file from the database server (KBA 2097372)
- The dump file is extremely large in size and transferring this file to SAP for analysis may take a significant amount of time
- An identified problem may have already been diagnosed from a previous full dump file and you are looking to quickly confirm if this is the same problem. SAP Technical support agrees that this could be confirmed via a mini-dump file.
Read more...
Environment
- SAP SQL Anywhere 16
SAP SQL Anywhere 12
SAP SQL Anywhere 11
SAP SQL Anywhere 10
SAP SQL Anywhere 9 - Microsoft Windows (all versions)
Product
SAP SQL Anywhere 16.0 ; SAP Sybase SQL Anywhere 12.0 ; SQL Anywhere 9.0 ; Sybase SQL Anywhere 10.0 ; Sybase SQL Anywhere 11.0
Keywords
sybase, dump, mini-dump, debug, debugging, windbg, .dmp, SQL Anywhere, iAnywhere, database, RDBMS , KBA , BC-SYB-SQA , SQL Anywhere (on premise, on demand) , How To
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.
SAP Knowledge Base Article - Preview