DBSERVERALIASES

Home | Previous Page | Next Page Configuring and Monitoring Dynamic Server > Configuration Parameters >

DBSERVERALIASES

onconfig.std value

None

if not present

None

separators

Comma

range of values

Up to 128 lowercase characters for each dbserver alias. Up to 32 values separated by commas. The value for DBSERVERALIASES follows the same rules as the DBSERVERNAME parameter (see DBSERVERNAME).

takes effect

When the database server is shut down and restarted. In addition, you might need to update the sqlhosts file or registry of each database server.

MaxConnect users

To use MaxConnect with more than one communication protocol, specify additional dbservernames in the DBSERVERALIASES parameter in the ONCONFIG file. The value of the INFORMIXSERVER environment variable on the client must match either the DBSERVERNAME or one of the entries of the DBSERVERALIASES parameter.

refer to

The following topics in the chapter on client/server communications in the IBM Informix Administrator's Guide:

ONCONFIG parameters for connectivity
Using multiple connection types

DBSERVERALIASES specifies a list of alternative dbservernames. If the database server supports more than one communication protocol (for example, both an IPC mechanism and the TCP network protocol), you must describe each valid connection to the database server with an entry in the sqlhosts file or registry. DBSERVERALIASES lets you assign multiple aliases to a database server, so each entry in the sqlhosts file or registry can have a unique name.

Important::

You can specify up to 32 DBSERVERALIASES for a database server. If you attempt to define more than 32 DBSERVERALIASES, a warning message displays twice on the console. If you attempt to specify the DBSERVERALIASES all on one line, and the line exceeds 512 bytes, the excess bytes are truncated.

For each alternate name listed in DBSERVERALIASES, the database server starts an additional listener thread. If you have many client applications connecting to the database server, you can distribute the connection requests between several listener threads and reduce connection time. To take advantage of the alternate connections, instruct some of your client applications to use a CONNECT TO dbserveralias statement instead of CONNECT TO dbservername.