Database utilities

@filename can be reused for several utilities Command parameter files can now be selectively parsed for the utility using the parameter file. The parsing is based on simple conditional directives placed in the parameter file. See Conditional parsing in configuration files.

Data Source utility (dbdsn) enhancements The following options have been added to the dbdsn utility:

-dr includes the DRIVER= parameter when you list the command that was used to create a data source. This allows you to recreate data sources so that they use a different version of the ODBC driver than the one included with the current version of the software.
-f displays the name of the system information file (typically .odbc.ini) being used.
-ns tells dbdsn not to search for the system information file (typically .odbc.ini), but to use the existing environment variables to determine where the file should be. This is useful when the file specified by one or more of the environment variables does not exist, and a ODBC data source is being created.
-pe encrypts the password field in the data source.

See Data Source utility (dbdsn).

Histogram utility (dbhist) enhancements Sheets within the Excel output file created by dbhist are now named to reflect the column name they apply to, instead of Sheet1, Sheet2, and so on. See Histogram utility (dbhist).

Information utility (dbinfo) enhancements The -u option now includes information about materialized views. See Information utility (dbinfo).

Initialization utility (dbinit) enhancements The Initialization utility (dbinit) now supports the following new options:

-a uses accent sensitivity for UCA string comparisons
-af uses French accent sensitivity rules for UCA string comparisons.
-dba changes the user ID and/or password of the default DBA database user in a new database.
-dbs specifies the initial size of the database file.
-ze specifies the character set encoding for the CHAR data type.
-zn specifies the collation sequence for the NCHAR data type.

See Initialization utility (dbinit).

Log Transfer Manager (LTM) enhancements The Log Transfer Manager (LTM) utility, also known as the Replication Agent, now supports identifiers up to 128 bytes for table, column, procedure, function, and parameter names when using the Replication Agent with Replication Server 15.0 and Open Server/Open Client 15.0. In earlier versions of the software, identifiers were limited to 30 bytes.

Timestamps in informational, warning, and error messages generated by dbltm now use the non-ambiguous ISO 8601 datetime format: {I|W|E} yyyy-mm-dd hh:mm:ss message.

Note

The Log Transfer Manager is unsupported as of SQL Anywhere version 12.

Ping utility (dbping) enhancements You can use the Ping utility (dbping) to obtain information about the performance of embedded SQL connections and your network's performance by specifying the -s or -st options. These options report statistics about the performance between the computer running dbping and the computer running the database server. See Testing embedded SQL and network connection performance (dbping).

The -pd option now lets you specify the name of the database you want to obtain the property value from. See Ping utility (dbping).

Server Enumeration utility (dblocate) enhancements The Server Enumeration utility (dblocate) now supports several new options to search for databases:

-d displays the server name and address, and a comma-separated list of all databases running on each server.
-dn displays the server name and address only if the server is running a database with the specified name.
-dv displays the server name and address, and lists all databases running on each server on a separate line.
-p displays servers using the specified TCP/IP port number.
-s displays servers with the specified name.
-ss displays server names that contain the specified substring.

See Server Enumeration utility (dblocate).

Service utility (dbsvc) enhancements The Service utility (dbsvc) supports the DBLTM service type, which allows you to manage services for the Log Transfer Manager, and the dblsn service type, which lets you manage services for the MobiLink Listener utility.

The Service utility also supports the -o option, which allows you to log output from the utility to a file. See Service utility (dbsvc) for Windows and Service utility (dbsvc) for Linux.

New SQL Anywhere Broadcast Repeater utility (dbns10) The SQL Anywhere Broadcast Repeater utility allows SQL Anywhere clients to find SQL Anywhere database servers on other subnets and through firewalls, where UDP broadcasts do not normally reach, without using the HOST parameter or LDAP. See Broadcast Repeater utility (dbns12).

New report submission utility (dbsupport) The new Support utility (dbsupport) provides the ability to submit error reports and statistics, the ability to query for updates (availability of EBFs), and the ability to check if previously submitted problems have been fixed. See Support utility (dbsupport).

Unload utility (dbunload) enhancements The following dbunload enhancements have been made:

unprocessed statements are logged when dbunload encounters a failure. See Failed unloads.
support for binary data in unloaded tables.
many internal enhancements have been made to improve performance for unloading databases.

The following new options have been added:

-dc recalculates the values for all computed columns in the database.
-g initializes materialized views during reload.
-k creates an auxiliary table for tracing support. Specifying this option populates the sa_diagnostic_auxiliary_catalog table. This option is useful when creating a tracing database.
-nl creates a reload.sql file that includes LOAD TABLE and INPUT statements for each table, but no data.

See Unload utility (dbunload).

Validation utility (dbvalid) A new database validation option, -d, has been added. This option performs a database validation that includes checksum validation, checks for orphaned table pages and BLOBs, as well as structural checks. Data is not checked. See Validation utility (dbvalid).