Home

	Expand Search

ASA Reference Manual

Chapter 2: The Database Server

The client compatibility executable

The client compatibility executable

Syntax

dbcli6 [switches] server-name

Windows 3.x syntax

dbcli6w [switches] server-name

See also

The database server .

Description

Compatibility only

The database client executable is provided for compatibility with SQL Anywhere Version 5 installations only. If you do not have an existing SQL Anywhere 5.0 installation that you wish to upgrade to Adaptive Server Anywhere, you do not need to use dbcli6.exe.

In SQL Anywhere Version 5, the database client executable handled connections from client applications to a network database server. In Adaptive Server Anywhere, no separate executable is required: all connections are handled by a client library. The database client executable for Adaptive Server Anywhere simply creates an ODBC data source (for use by the client library) and then terminates.

Switches

-e

Encrypt all packets that this client transmits over the network. By default, packets are not encrypted. If you are concerned about the security of network packets, use the

-e

Using the

-e

-e

-ga

Automatically shut down the server after the last connection to a server is closed.

-o filename

Output all error messages and debugging messages (see

-Z

-p packet-size

Set the maximum size of communication packets. The default is 1000 bytes. The minimum value is 200 bytes. If the specified packet size is larger than that of the database server, the server's packet size is used.

-r

Opens a database in read-only mode, allowing the server to access databases on CD-ROM devices without first creating a write file. No changes to the database are allowed. The database file and transaction log files will not be modified by the server. A database which requires recovery cannot be started in read-only mode. Database files created using an on-line backup cannot be started in read-only mode if there were any open transactions when the backup was started, since these transactions would require recovery when the database was started.

-s size

Set the memory allowed for buffers, in K. The value must be at least 10 and at most 1000. The default is 100.

-tl seconds

(Lower case TL.) A liveness packet is sent periodically across a client/server TCP/IP or IPX communications protocol to confirm that a connection is intact. If the client runs for a liveness timeout period (default 120 seconds) without detecting a liveness packet, the communication is severed. The client forgets about the address of the server and looks it up the next time a connection is made. Win 3.x clients, UNIX non-threaded clients, and TDS connections do not do liveness checking.

If no

-tl

Liveness packets are sent at an interval of the (liveness timeout)/4.

-x list

Use only the listed communications links (IPX, TCPIP, NetBIOS). The default is to try all communication links supported by the version of dbcli6.

Named Pipes and Windows links are for local communications only.

By default, the Client tries to use IPX, TCP/IP, and then NetBIOS when locating a server. The Client starts slightly faster if unnecessary network drivers are not started.

Additional parameters may be provided, in the format

-x tcpip{PARM1=value1;PARM2=value2;...}
-x "tcpip{PARM1=value1;PARM2=value2;...}"

The quotation marks are required for the UNIX client and server only, and only if more than one parameter is supplied.

For a description of available parameters, see Network communications parameters .

-z

Provides diagnostic information on communications links on startup. This is useful if

-o