DB Connection

Go Up to IBConsole - Main Menu

This diagnostic tool allows a user to check their database connection information after network connectivity has been confirmed. To confirm network connectivity, use the appropriate network protocol tester.

To run a Database Connectivity Test

1. Provide the Server Information required to communicate with the desired server. Choose the locale - Local or Remote - of the server. If connecting to a remote server, enter the Server Name and the Network Protocol (choose from the dropdown listbox). If you choose Local, no more information is needed.
2. Enter the name of a database into the Databasefield or press the browse button and use the Open File dialog box to locate the database file. The database file must be located on the server specified. The connection will be refused if the database file resides on a networked or mapped drive.
3. Enter a valid User Name and Password.
4. Click Test, and review the output in the Results window.

Notes:

• InterBase Server must be running on your machine before you can connect to a local database.
• Local connection mode is not available on UNIX servers.
• A database file must not reside on an NFS (networked filesystem) or a mapped drive. When the server finds such a case, it either denies the connection or passes the connection request on to the InterBase service running on the networked file server, if there is one. To correct this situation, move your database (gdb file) to a hard disk that is physically local to the database server.
• For a Windows NT or Windows 95/98 server, the database path must contain the appropriate drive letter designation. For example: D:\users\accting\fin\accrec.gdb
• For a Unix server, you must enter the complete and absolute directory path for the database. You must also provide the hostname; the SuperServer architecture necessarily disables the local database attachment configuration. For example: jupiter:/usr/accting/fin/accrec.gdb
• UNIX paths are case sensitive.
• The server process must have permissions to read and write the database file at the operating system level.
• The security database that contains users and passwords must also be writeable by the server process.
• The server process must have permissions to create files in the InterBase home directory. It must be able to write to, and perhaps create, the log file and other temporary files.