Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 12.0.0 » SQL Anywhere Server - Database Administration » Maintaining your database » Troubleshooting SQL Anywhere database issues


Error reporting in SQL Anywhere

When a fatal error or crash occurs and is detected by any of the following applications, an error report is created about what was happening at the time of the problem:

The error report includes information such as the execution state of the threads at the time of the crash, so that iAnywhere Solutions is better able to diagnose the cause of the problem. By default, the error report is created in the diagnostic directory (specified by the SADIAGDIR environment variable), or if this location does not exist, it is created in the same directory as the database file.

Error report file names are composed as follows:

  • a prefix that identifies the application:

    Application identifier Application
    LSN Listener utility
    MLC MobiLink client
    MLS MobiLink server
    QAA QAnywhere agent
    SA Personal or network database server
    SR SQL Remote
  • a value indicating the software version

  • two fields linked with underscores that provide the timestamp for when the error report was created

  • the application identifier

  • the extension .mini_core

For example, SA12_20090620_133828_32116.mini_core is an error report from a SQL Anywhere version 12 database server from 2009/06/20, at 1:38:28 p.m., from process 32116.

During normal database server operation, diagnostic information is also recorded about the database server, such as how many CPUs are on the computer, whether hyperthreading is enabled, and what options were specified when the server was started. This information can also be submitted using dbsupport.

 How SQL Anywhere software submits error reports and diagnostic information
 See also