"Jurgen Haan" <jurgen@fake.dom> wrote in message
news:47065196.3030300@fake.dom...
> Steve Rainbird wrote:
>
>>
>>
>> This what another dba sent to me about the errors he is getting.
>>
>> "I found where to configure it. However, when the database restarts, I
>> get the following error: I'm guessing at the licensing error. Perhaps the
>> 64 bit version requires a license in order to connect remotely.
>>
>>
>>
>> Support for one or more communications protocols failed to start
>> successfully. However, core database manager functionality
>> started successfully.
>>
>> Explanation:
>>
>> Communication protocol support did not start successfully for one
>> or more protocols. Possible reasons can include the following:
>>
>> o Communication subsystem configuration error.
>>
>> o Communication subsystem call failure.
>>
>> o Database manager configuration error.
>>
>> o System call failure.
>>
>> o Database manager licensing error. "
>>
>> Thanks again for all your help.
>>
>>
>
> "Support for one or more communications protocols failed to start"
>
> I think that means that TCPIP is activated in db2set, but the combination
> of the /etc/services file and the SVCENAME parameter in "db2 get dbm cfg"
> do not match.
>
> But I'm not entirely sure.



Don't think so.

$ db2set
DB2COMM=TCPIP
$
$ grep db2c_db2 /etc/services
db2c_db2 50000/tcp
$


TCP/IP Service name (SVCENAME) = db2c_db2
Discovery mode (DISCOVER) = SEARCH
Discover server instance (DISCOVER_INST) = ENABLE



--
Steve