What to do if you can't connect to a database

If you are unable to connect to a Sybase IQ database, check the items described below.

Check that you have entered your data source name correctly, or that you have selected the correct server name for a JDBC connection.

Check that your data source (DSN or FILEDSN) contains the correct server name, database, network parameters, and any other connection information you expect.

On Windows, select Settings > Control Panel > Data Sources (ODBC), then select the User DSN tab and select the source name for the server you want.
On UNIX, check your .odbc.ini file

Check that the database server you want is running.

On Windows: If the server is running on the local host, check the icon on the toolbar at the bottom of the screen. If the server is remote, select Settings > Control Panel > Data Sources (ODBC) to open the ODBC Administrator, then select the User DSN tab, highlight the source name for the server you want, and click Configure > Test Connection. If that server is running, and the data source is set correctly, you see a Connection Successful message.
On UNIX, enter the following at the system prompt, substituting the name of your database server for asiqdemo:
```
ps -eaf | grep asiqdemo
```

Check that any connection parameters you enter on the command line are correct.

The Interactive SQL utility behaves differently from Embedded SQL when a CONNECT statement is issued while already connected to a database. If no database or server is specified in the CONNECT statement, Interactive SQL connects to the current database, rather than to the default database. This behavior is required for database reloading operations.

If you specify a database without a server name, DBISQL attempts to connect to the specified database on the current server. (Note that you must specify the database name defined in the -n database switch, not the database file name.) If you specify a server name without a database name, DBISQL connects to the default database on the specified server.

If you are connecting to a database that is not running, check that the server was started with the -gd ALL switch. If not, then only the DBA can start databases on that server, by first connecting to the utility_db database and then issuing a START DATABASE command for the desired database.

Check that you have permission to use the database for the requested operation. The DBA or database owner must grant you CONNECT permission; see “Managing individual user IDs and permissions”.
If you are having problems establishing a connection across a network, you can use debugging options at both client and server to diagnose problems. On the server, you use the -z command-line option. The startup information appears on the server window: you can use the -o option to log the results to an output file.
Check that all of the files exist for the database you have requested. At a minimum, there must be an IQ Store (dbname.iq), a Catalog Store (dbname.db), an IQ Temporary Store (dbname.iqtmp), a transaction log (dbname.log This may be missing if the database is newly created and has not been modified.), and a message file (dbname.iqmsg). The names shown here in parentheses are the default format; yours may be different.
Check that any restores have completed successfully.