Tests connections to database servers and optionally to databases.
dbping [ options ]
Reads in options from the specified environment variable or configuration file. See Configuration files.
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).
|-c "keyword=value; ..."||
Specifies the connection parameters used to connect to the server and optionally the database. By default, dbping connects to a running server; specify the -d option to connect to the database. See Troubleshooting: How to test connection strings (dbping).
Tests connecting to the database. If necessary, dbping can automatically start the server and database. With -d, dbping behaves like a regular client-application establishing a connection.
If you supply the -d option, then dbping reports success if it connects to the server and to the database. If you do not supply the -d option, then dbping reports success if it finds the server.
For example, if you have a database server named blair running the sample database, the following succeeds since dbping can connect to the server blair:
The following command fails, with the message
|-en||Specifies that you want dbping to exit with a failed return code when NULL is returned for any of the properties specified. By default, dbping prints NULL when the value for a property specified by -pc, -pd, or -ps is unknown, and exits with a success return code. This option can only be used with -pc, -pd, and -ps.|
Specifies the ODBC library to use (without its file extension). This option avoids the use of the ODBC driver manager, and so is useful on Unix operating systems.
For example, the following command loads the ODBC driver directly:
On Unix, to use a threaded connection library, you must use the threaded version of the Ping utility, dbping_r.
|-m||Establishes a connection using ODBC. By default, the utility connects using the embedded SQL interface.|
|-o filename||Writes output messages to the named file.|
Displays the specified connection properties. Supply the properties in a comma-separated list. You must specify enough connection information to establish a database connection if you use this option. See List of connection properties.
For example, the following command displays the fire_triggers option setting, which is available as a connection property.
Displays the specified database properties. Supply the properties in a comma-separated list. See List of database properties.
For example, the following command displays the page size in use by the database:
Optionally, you can specify the name of a database running on the database server you want to obtain the value from. For each property listed, if the database name is not specified by appending @db-name to the property, then the database name used for the previous property is used.
The following command displays the page size and collation of the database mydb:
Displays the specified database server properties. Supply the properties in a comma-separated list. You must specify enough connection information to establish a database connection if you use this option. See List of database server properties.
For example, the following command displays the number of licensed seats or processors for the database server:
|-q||Runs in quiet mode—messages are not displayed.|
|-s||Returns information about the performance of the network between the computer running dbping and the computer running the database server. Approximate connection speed, latency, and throughput are displayed. The -c option is usually required to specify the connection parameters to connect to a database on the server. You can only use dbping -s for embedded SQL connections. This option is ignored if -m or -l is also specified. By default, dbping -s loops through the requests for at least one second for each statistic it measures. A maximum of 200 connect and disconnect iterations are performed, regardless of the time they take, to avoid consuming too many resources. On slower networks, it can take several seconds to perform the minimum number of iterations for each statistic. The performance statistics are approximate, and are more accurate when both the client and server computers are fairly idle. See Troubleshooting: How to test embedded SQL and network connection performance (dbping).|
|-st time||Returns the same information as the -s option, except that the -st option specifies the length of time, in seconds, that dbping loops through the requests for each statistic it measures. This option allows more accurate timing information to be obtained that -s. See Troubleshooting: How to test embedded SQL and network connection performance (dbping).|
|-z||Displays the network communication protocols used to attempt connection, and other diagnostic messages. This option is available only when an embedded SQL connection is being attempted. That is, it cannot be combined with -m or -l.|
The dbping utility is a tool to help debug connection problems. It takes a full or partial connection string and returns a message indicating whether the attempt to locate a server or connect to a database was successful.
The utility can be used for embedded SQL or ODBC connections. It cannot be used for jConnect (TDS) connections.
Exit codes are 0 (success) or non-zero (failure).
Discuss this page in DocCommentXchange.
|Copyright © 2014, SAP AG or an SAP affiliate company. - SAP Sybase SQL Anywhere 16.0|