"Jurgen Haan" <jurgen@fake.dom> wrote in message
news:47064DC6.60200@fake.dom...
> Steve Rainbird wrote:
>> <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.
>>
>>
>
> Not entirely sure about that.
> I'm running an Express-C on a 64bit server with 16GB memory.
> Ofc it only uses 4GB at the moment. (It's a failover machine for when our
> WSUE machine goes offline. It's running a testenvironment on express-C and
> when our pri. machine explodes, we can reinstall the failover machine to
> run the WSUE. Financial matter, in case anyone is wondering why the ***
> we're running an express-c on a 64bit machine).
>
> In our production environment, we're using an 64bit linux db2 WSUE machine
> using 16GB memory. Our clients are 32bit linux machines running the db2
> client. So we're using 32bit clients to connect to a 64bit db server.
>
> In our test environment, we're using an 64bit linux with 16GB running db2
> express-C to which 32bit linux machines running the db2 client are
> connecting.
>
> So I think, at least at one point, we have a very similar situation to
> yours, and it works without a hassle. We even have 32bit windows machines
> connecting to our test environment using QUEST and DB2CC.
>
> What kind of errors do you get?
>
> Regards, Jurgen.
>



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.



--
Steve