Learning Visually with Examples [Electronic resources] نسخه متنی

17.9. Case Study

You want to enable your DB2 database server running on Linux to accept client connections using TCP/IP. (This process is covered in Chapter 6, Configuring Client and Server Connectivity.) The first thing you need to do is to set the DB2COMM registry variable to TCPIP, for example:

db2set db2comm=tcpip 

Then you stop and restart the instance for the setting of DB2COMM to take effect. However, when you start the instance again, you get the following message:

[View full width]
SQL5043N Support for one or more communications protocols failed to start successfully.
 However, core database manager functionality started successfully.

You are not sure why this error would occur. You decide to look for more information about this error in the administration notification log, which is under the

$HOME /sqllib/db2dump directory on Linux/UNIX systems. You open the file and the last entry in this file shows:

[View full width]
2004-06-07-16.24.57.229642   Instance:sylviaq   Node:000
PID:264502(db2sysc)   TID:1   Appid:none
common communication  sqlcctcpconnmgr Probe:50
ADM7006E The SVCENAME DBM configuration parameter was not configured. Update the SVCENAME
 configuration parameter using the service name defined in the TCP/IP services file.
2004-06-07-16.24.58.747410   Instance:sylviaq   Node:000
PID:442506(db2star2)   TID:1   Appid:none
base sys utilities  DB2StartMain Probe:911
ADM7513W Database manager has started.

The first message indicates that the SVCENAME parameter needs to be updated. The second message indicates that although the TCP/IP support failed to start, the instance is started regardless. This corresponds to the SQL5043N message.

You remember from Chapter 6 that to enable TCP/IP support on a DB2 server, you must also update the SVCENAME parameter to indicate the TCP/IP port number the DB2 instance is going to use. You execute the following command:

db2 update dbm cfg using svcename 50000 

When you restart the instance, the error went away. The message you get is:

SQL1063N DB2START processing was successful.