Newbie Connection question

#11

Steve Rainbird wrote:

Quote:

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.

#12

"Jurgen Haan" <jurgen (AT) fake (DOT) dom> wrote

Quote:

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

#13

Steve Rainbird wrote:

Quote:

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

#14

"Jurgen Haan" <jurgen (AT) fake (DOT) dom> wrote

Quote:

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

#15

"Steve Rainbird" <news.nospam (AT) rainbird (DOT) me.nospam.uk> wrote

Quote:

"Jurgen Haan" <jurgen (AT) fake (DOT) dom> wrote in message
news:470656BA.30503 (AT) fake (DOT) 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

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Newbie Connection question

comp.databases.ibm-db2 comp.databases.ibm-db2

Re: Newbie Connection question - 10-05-2007 , 10:00 AM

Re: Newbie Connection question - 10-05-2007 , 10:14 AM

Re: Newbie Connection question - 10-05-2007 , 10:22 AM

Re: Newbie Connection question - 10-05-2007 , 10:43 AM

Re: Newbie Connection question - 10-05-2007 , 10:58 AM