Sends information about errors and software usage to iAnywhere Solutions.
dbsupport [ options ] operation [ operation-specific-option ]
dbsupport configuration-options
Option | Description |
---|---|
@data |
Reads in options from the specified environment variable or configuration file. See Configuration files. If you want to protect passwords or other information in the configuration file, you can use the File Hiding utility to obfuscate the contents of the configuration file. See File Hiding utility (dbfhide). |
-o filename | Sends output to the specified file. |
-q | Displays only critical messages. |
Operation | Description | ||||
---|---|---|---|---|---|
-e configuration-option |
Displays the setting for the specified configuration option. For example, suppose you ran the following command to configure dbsupport to prompt when possible:
When you run the command
If the current value of the configuration option has never been explicitly set, nothing is echoed. |
||||
-is submission-ID [ -rr N ] |
Checks the status of a crash report that has been submitted to iAnywhere Solutions. For example, the following command returns the status of submission ID 66:
|
||||
-iu [ -r N ] |
Checks for updates to your build of SQL Anywhere. Updates include:
You can also check for updates using Interactive SQL and Sybase Central. See Software updates. |
||||
-lc | Generates a list of all crash reports that have not been submitted to iAnywhere Solutions. The report names listed can be used with the -sc option. | ||||
-ls |
Generates a list of submission IDs for all reports that have been submitted to iAnywhere Solutions. For example:
This returns information similar to the following:
|
||||
-pc filename | Displays crash report information. You can use this option to view information before it is submitted to iAnywhere Solutions. | ||||
-pd | Displays the diagnostic information that has been collected. You can use this option to view information before it is submitted to iAnywhere Solutions. | ||||
-ps submission-ID |
Displays information about a specific report that has been submitted to iAnywhere Solutions. For example:
This returns information about submission 4:
|
||||
-sa [ -r number-of-submission-retries ] | Submits all crash report and diagnostic information stored in the diagnostic directory to iAnywhere Solutions. | ||||
-sc reportname [ -r number-of-submission-retries ] [ -nr | -rr N ] |
Submits a crash report and diagnostic information to iAnywhere Solutions. For example:
Use the -lc option to see a list of reports that have not been submitted. |
||||
-sd [ -r number-of-submission-retries ] |
Submits only diagnostic information to iAnywhere Solutions. For more information about the diagnostic directory, see SADIAGDIR environment variable. |
Configuration option | Description | ||||
---|---|---|---|---|---|
-cc [ autosubmit | no | promptDefY | promptDefN ] |
Changes the prompting behavior of dbsupport. You can specify one of the following options:
If you specify this option, its value becomes the default used by the Support utility. The setting is stored in the dbsupport.ini file in the diagnostic directory. The following command configures the Support utility so that it does not submit reports and never prompts the user to submit reports:
|
||||
-cd retry-delay |
Specifies the retry delay, in seconds, for submitting a report if the previous attempt is unsuccessful. The default delay is 30 seconds. If you specify this option, its value becomes the default used by the Support utility. The setting is stored in the dbsupport.ini file in the diagnostic directory. The following dbsupport command specifies that failed submissions should be retried every 3 seconds, up to a maximum of 4 times before giving up:
|
||||
-ce email-address;email-server[:port ][;user-id:password ] |
Specifies the address where an email is sent after a crash occurs. The email is sent using the email-server SMTP server. Optionally, you can specify the port that should be used, and the user-id and password used to authenticate with the SMTP server. |
||||
-cet | Tests the email settings specified by the -ce option. | ||||
-ch crash-handler-program |
Specifies a program that is called when a crash occurs. If you specify this option, its value becomes the default used by the Support utility. The setting is stored in the dbsupport.ini file in the diagnostic directory. The database server supports three substitution parameters that set up information that is passed to the crash-handler-program:
You can use $F, $P, and $S as alternatives to %F, %P, and %S. Because different command shells interpret the characters % and $, both are provided. For example, on 4NT, %F is substituted with the value of the environment variable F; $F can be used to avoid this substitution. Suppose you have a crash handler program in c:\test.bat that contains the following commands:
On Windows, the following command tells dbsupport to launch c:\test.bat with two parameters when a crash occurs. If the report is being submitted, this program is called before the report is submitted.
The substituted path specified by %F is sent to c:\test.bat as the first parameter. The parameter parm2 is sent to c:\test.bat as the second parameter. Quotation marks must be used to specify a crash handler program that takes arguments. In the example above, additional quotes were used around the full path to the generated report file. To avoid problems accessing the report file that dbsupport is using, the crash handler program should make its own copy of the report file. |
||||
-ch- |
Removes the crash handler settings that are stored in the dbsupport.ini file. For example:
|
||||
-cid customer-id |
Specifies a string that identifies you in the submission report. If you specify this option, its value becomes the default used by the Support utility. The configuration is stored in the dbsupport.ini file in the diagnostic directory. The following examples specify a customer identification string for dbsupport:
|
||||
-cid- |
Removes the customer identification string from the dbsupport.ini file. For example:
|
||||
-cp { email-server [ :port ] | autodetect } |
Configures the HTTP proxy host and port used to submit error reports. On Windows, the syntax -cp autodetect is also supported. If you specify this option, then if a proxy server and port have been set using Internet Explorer, and they are currently enabled, dbsupport configures its proxy server and port using the system setting. You might need to set the proxy server and port in Internet Explorer. |
||||
-cp- |
Removes HTTP proxy host and port settings from the dbsupport.ini file. For example:
|
||||
-cr number-of-submission-retries |
Specifies the number of times a failed submission should be retried. If you specify this option, its value becomes the default used by the Support utility. The setting is stored in the dbsupport.ini file in the diagnostic directory. The following dbsupport command specifies that failed operations should be retried every 3 seconds, up to a maximum of 4 times before giving up:
|
Operation-specific option | Description | ||
---|---|---|---|
-ac | Adds a comment to the submission. | ||
-af | Attaches a file to the submission. You can specify the -af option more than once to attach multiple files to the submission. | ||
-nr |
Specifies that dbsupport does not check the server for the status of the submission. For example, the following command submits the report, but does not check for the status of the new submission:
By default, dbsupport checks whether there is already a fix for the problem being submitted. |
||
-r number-of-submission-retries | Specifies the maximum number of times dbsupport should try to send the submission. Specifying 0 means retry indefinitely. The default value is 10. Specifying -r overrides the -cr value stored in the dbsupport.ini file, if one exists. | ||
-rd retry-delay | Specifies the number of seconds dbsupport waits between attempts to resend the report. The default value is 30. Specifying -rd overrides the -cd value stored in the dbsupport.ini file, if one exists. | ||
-rr number-of-submission-response-retries | Specifies the maximum number of times dbsupport should try to obtain a submission response. Specifying 0 means retry indefinitely. The default value is 10. |
If a fatal error or crash occurs in any SQL Anywhere program, an error report is created which contains technical information about the program at the time of the error. When an error report is created, you are prompted to submit this report to the SQL Anywhere support team. You can also submit this report using the Support utility (dbsupport). Submitting error reports assists with diagnosing the cause of a fatal error or assertion. Once an error report is submitted, you receive a submission ID which you can quote to technical support. If you report the problem to the technical support department, sending them this error file can speed up the processing of your issue. It is recommended that you submit error reports, even if you choose not to contact technical support, to help improve the product.
The Support utility (dbsupport) can be used for any of the following tasks:
submitting diagnostic information and crash reports to iAnywhere Solutions over the Internet
submitting feature statistics
listing information about submitted and unsubmitted crash reports
printing information about submitted and unsubmitted crash reports
inquiring about the status of a submission
inquiring whether there are software updates available for your build of SQL Anywhere
configuring dbsupport behavior for when a fatal error (assertion/crash) is detected. For example, it can be configured to run a specified handler program each time the database server submits an error report. This feature is useful for adding your own custom actions to the error handling process.
configuring how many times to retry sending a report. For example, when submitting a report, it could be configured to retry the operation again in 30 seconds, up to a maximum of 10 times. This feature is useful for handling the case where the service may be temporarily unavailable.
Settings for the Support utility are stored in the dbsupport.ini file in the diagnostic directory.
The operation-specific options are useful for overriding default behavior, including those that have been saved in the dbsupport.ini file.
The graphical administration tools can be configured to remove the option to submit error reports. See Administration tools configuration.
If you choose not to submit an error report, it remains in the diagnostic directory on your hard disk. This directory is created automatically by SQL Anywhere programs and is used only for saving error reports and for storing settings for the Support utility (dbsupport).
Diagnostic directory location The location of the diagnostic directory varies depending upon the platform:
Windows (excluding Windows Mobile)
The directory specified by the SADIAGDIR environment variable, if it is set.
The default diagnostic directory location:
On Windows XP: %ALLUSERSPROFILE%\Application Data\SQL Anywhere 12\diagnostics.
On Vista and later: %ALLUSERSPROFILE%\SQL Anywhere 12\diagnostics.
The current directory.
The temporary directory. See SATMP environment variable and TMP, TMPDIR, and TEMP environment variables.
Windows Mobile
The directory of the executable file, or if that directory is not writable.
The current directory, or if that directory is not writable.
The temporary directory. See Registry settings on Windows Mobile.
Unix, Linux, OS X
The directory specified by the SADIAGDIR environment variable, if it is set.
The default diagnostic directory: $HOME/.sqlanywhere12/diagnostics.
The current directory.
The temporary directory. See SATMP environment variable and TMP, TMPDIR, and TEMP environment variables.
On Unix, writing crash reports to the user's home directory is not recommended when the database or MobiLink server is running as a daemon, or the user is root/nobody.
Error report file names Error report file names are composed as follows:
a prefix that identifies the application:
Application prefix | Application |
---|---|
DBCONSOLE | SQL Anywhere Console utility |
ISQL | Interactive SQL utility |
LSN | Listener utility |
MLC | MobiLink client |
MLS | MobiLink server |
ML_MON | MobiLink Monitor |
QAA | QAnywhere agent |
SA | Personal or network database server |
SCJ | Sybase Central |
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 .dmp
For example, SA12_20110620_133828_32116.dmp is an error report from a SQL Anywhere version 12 database server from 20011/06/20, at 1:38:28 p.m., from process 32116.
You can change the default behavior of dbsupport with the -cc option:
The following command configures dbsupport to submit error reports automatically without prompting the user:
dbsupport -cc autosubmit |
The following command turns off automatic error report submission:
dbsupport -cc no |
You can view the list of error reports with the -lc option:
The following command generates a list of all crash reports that have not been submitted to iAnywhere Solutions:
dbsupport -lc |
You can manually submit the error reports with the -sa, -sc, or -sd option:
The following command submits all crash report and diagnostic information stored in the diagnostic directory to iAnywhere Solutions:
dbsupport -sa |
You can also include comments and files with the error report by specifying the -ac and -af options, respectively.
dbsupport -sc SA12_20080901_113308_3360 -ac "The message.txt file provides more information about this error report." -af c:\scenario.txt -af c:\message.txt |
Discuss this page in DocCommentXchange.
|
Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1 |