"Steve Rainbird" <news.nospam@rainbird.me.nospam.uk> wrote in message
news:5mmutaFegq60U1@mid.individual.net...
> "Jurgen Haan" <jurgen@fake.dom> wrote in message
> news:470634B1.5090403@fake.dom...
>> Well, it seems that your server on 192.168.1.2 is not configure to talk
>> TCP/IP.
>>
>> To check this, you can log in on the server, and execute a db2set.
>> if there's no line saying: DB2_COMM=TCPIP then you should probably add
>> this by using db2set.
>>
>> Furthermore, if you do so, check in your /etc/services that there's an
>> entry like 'db2 50000/tcp'.
>> if not, add it. DB2 needs to know on what port to run its service.
>> And finally, check your DBM settings by executing a 'db2 get dbm cfg'
>> there should be a 'SVCENAME' please set this one to the corrosponding
>> setting in your services.
>>
>> You can do this by, for example, executing:
>> 'db2 UPDATE DBM CFG USING SVCENAME db2'
>>
>> Now restart your instance (db2stop/db2start)
>>
>> Good luck.
>>
>> Steve Rainbird wrote:
>>>
>>> Then I tried to connect and got the following.
>>>
>>> $ db2 connect to pear
>>> SQL30081N A communication error has been detected. Communication
>>> protocol
>>> being used: "TCP/IP". Communication API being used: "SOCKETS".
>>> Location
>>> where the error was detected: "192.168.1.2". Communication function
>>> detecting
>>> the error: "connect". Protocol specific error code(s): "111", "*", "*".
>>> SQLSTATE=08001
>>> $
>>>
>>>
>>> Any ideas?
>
>
> Thanks Jurgen you have been very helpful.
>
> I can now connect from "ruby" to a database on "amber" but not vice versa.
> They both look to have been setup identically except that "ruby" is 64 bit
> and "amber" is 32. This shouldn't cause a problem should it?
>
> --
> Steve
>
>
>


BTW in case it matters we are currently using DB2 Express-C.

--
Steve

<snip>>
>>
>
>
> BTW in case it matters we are currently using DB2 Express-C.
>
> --
> Steve
>
>
>

Looks like this may be the problem. The machine the 64bit database is on
has 6GB memory. DB2 Express-C has limit of 4GB I believe.


--
Steve

Steve Rainbird wrote:

> $ 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
>
>

That does indeed look like it should.
Hmmm.
What does db2diag report?

"Jurgen Haan" <jurgen@fake.dom> wrote in message
news:470656BA.30503@fake.dom...
> Steve Rainbird wrote:
>
>> $ 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
>>
>>
>
> That does indeed look like it should.
> Hmmm.
> What does db2diag report?



Jurgen,

Thanks for that that was very informative.

It says

MESSAGE : ADM7007E The SVCENAME DBM configuration parameter, "50000", is
configured with a port or a service name. When it is configured
with
a service name, the TCP/IP services files is used to map the
service
name to a port number. The port specified in this field is being
used by another process. Resolve this problem by either deleting
the
process using the port or use another port.

We have decided to trash the instance and start again.

I will let you know what happens.

Thanks again

--
Steve

"Steve Rainbird" <news.nospam@rainbird.me.nospam.uk> wrote in message
news:5mn4crFe8ie3U1@mid.individual.net...
> "Jurgen Haan" <jurgen@fake.dom> wrote in message
> news:470656BA.30503@fake.dom...
>> Steve Rainbird wrote:
>>
>>> $ 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
>>>
>>>
>>
>> That does indeed look like it should.
>> Hmmm.
>> What does db2diag report?
>
>
>
> Jurgen,
>
> Thanks for that that was very informative.
>
> It says
>
> MESSAGE : ADM7007E The SVCENAME DBM configuration parameter, "50000", is
> configured with a port or a service name. When it is configured
> with
> a service name, the TCP/IP services files is used to map the
> service
> name to a port number. The port specified in this field is being
> used by another process. Resolve this problem by either deleting
> the
> process using the port or use another port.
>
> We have decided to trash the instance and start again.
>
> I will let you know what happens.
>
> Thanks again
>
> --
> Steve
>


Jurgen,

Before we trashed it we just made a check to see if anything else was using
port 50000 and guess what. An HP driver had decided to use it.

Got rid of this and now its working fine,

Thanks again for all your help.

--
Steve