SQL5043N Support for one or more communications ... and SQL8011W

[dba2adm]

I am trying to test the DB2 V8.1 partitioning on the RedHat Linux EL 3
AS. I installed v8.1 successfully using db2_install and installed the
FP5.

Now, I created an ESE instance and edited the db2nodes.cfg (the 1st
line was created by default, I added the 2nd line)

[db2inst1@db01 db2inst1]$ cat sqllib/db2nodes.cfg

0 db01.prince.com 0 #created by db2icrt -s ese ..
1 db01.prince.com 1 #added by me for testing partitioning feature

[db2inst1@db01]$ db2start #works just fine db2nodes.cfg has only one
entry
05-22-2004 12:39:20 1 0 SQL1063N DB2START processing was
successful.
05-22-2004 12:39:27 0 0 SQL5043N Support for one or more
communications protocols failed to start successfully. However, core
database manager functionality started successfully.
SQL8011W One or more database partitions does not have a valid DB2
license key installed for the "DB2 Enterprise Server Edition" product.
SQL1063N DB2START processing was successful.
[db2inst1@db01 db2inst1]$ tail sqlib/db2dump/db2diag.log

ADM7007E The SVCENAME DBM configuration parameter, "60001", 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.

[db2inst1@db01]$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) =
DB2_db2inst1

[db2inst1@db01 db2inst1]$ grep 6000 /etc/services
DB2_db2inst1 60001/tcp
DB2_db2inst1_1 60002/tcp
DB2_db2inst1_2 60003/tcp
DB2_db2inst1_END 60004/tcp

[root@db01]# netstat -natep | grep 6000
tcp 0 0 127.0.0.1:60001 0.0.0.0:* LISTEN 502 63709
14411/db2fcmdm
tcp 0 0 127.0.0.1:60002 0.0.0.0:* LISTEN 502 63714
14419/db2fcmdm

How do I fix this error?

Thanks.

[Ian]

db*****@yahoo.com wrote:

I am trying to test the DB2 V8.1 partitioning on the RedHat Linux EL 3
AS. I installed v8.1 successfully using db2_install and installed the
FP5.

Now, I created an ESE instance and edited the db2nodes.cfg (the 1st
line was created by default, I added the 2nd line)

[db2inst1@db01 db2inst1]$ cat sqllib/db2nodes.cfg

0 db01.prince.com 0 #created by db2icrt -s ese ..
1 db01.prince.com 1 #added by me for testing partitioning feature

[db2inst1@db01]$ db2start #works just fine db2nodes.cfg has only one
entry
05-22-2004 12:39:20 1 0 SQL1063N DB2START processing was
successful.
05-22-2004 12:39:27 0 0 SQL5043N Support for one or more
communications protocols failed to start successfully. However, core
database manager functionality started successfully.
SQL8011W One or more database partitions does not have a valid DB2
license key installed for the "DB2 Enterprise Server Edition" product.
SQL1063N DB2START processing was successful.

[db2inst1@db01]$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) =
DB2_db2inst1

[db2inst1@db01 db2inst1]$ grep 6000 /etc/services
DB2_db2inst1 60001/tcp
DB2_db2inst1_1 60002/tcp
DB2_db2inst1_2 60003/tcp
DB2_db2inst1_END 60004/tcp

These ports are used for the DB2 FCM to communicate between partitions,
not for client communication (SVCENAME) with the instance.

You need to create another entry in /etc/services for TCPIP client
communication (the default created when db2 installs is something
like 'db2cdb2inst1', on port 50000) and update the SVCENAME param.


-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

[dba2adm]

Thanks Ian for the response.

I already tried changing the port, but am getting the similar kind of
error.

ADM7007E The SVCENAME DBM configuration parameter, "14465", 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.
[db2inst1@db01]$ sudo netstat -pante | grep 144
tcp 0 0 127.0.0.1:14465 0.0.0.0:* LISTEN 502 5664 2407/db2fcmdm
tcp 0 0 127.0.0.1:14466 0.0.0.0:* LISTEN 502 6285 2406/db2fcmdm
[db2inst1@db01]$ grep DB2 /etc/services
DB2_db2inst1 80001/tcp
DB2_db2inst1_1 80002/tcp
DB2_db2inst1_2 80003/tcp
DB2_db2inst1_END 80004/tcp

[db2inst1@db01]$ db2 get dbm cfg | grep -i svce
TCP/IP Service name (SVCENAME) = 80001

It looks, whatever, I do to the service name, it takes the port used
by db2fm daemon. I will try bring down the daemon. Any idea to fix
this.

Thanks
--------------------------------------------------------------------

Ian <ia*****@mobileaudio.com> wrote in message news:<40**********@corp.newsgroups.com>...

db*****@yahoo.com wrote:

I am trying to test the DB2 V8.1 partitioning on the RedHat Linux EL 3
AS. I installed v8.1 successfully using db2_install and installed the
FP5.

Now, I created an ESE instance and edited the db2nodes.cfg (the 1st
line was created by default, I added the 2nd line)

[db2inst1@db01 db2inst1]$ cat sqllib/db2nodes.cfg

0 db01.prince.com 0 #created by db2icrt -s ese ..
1 db01.prince.com 1 #added by me for testing partitioning feature

[db2inst1@db01]$ db2start #works just fine db2nodes.cfg has only one
entry
05-22-2004 12:39:20 1 0 SQL1063N DB2START processing was
successful.
05-22-2004 12:39:27 0 0 SQL5043N Support for one or more
communications protocols failed to start successfully. However, core
database manager functionality started successfully.
SQL8011W One or more database partitions does not have a valid DB2
license key installed for the "DB2 Enterprise Server Edition" product.
SQL1063N DB2START processing was successful.

[db2inst1@db01]$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) =
DB2_db2inst1

[db2inst1@db01 db2inst1]$ grep 6000 /etc/services
DB2_db2inst1 60001/tcp
DB2_db2inst1_1 60002/tcp
DB2_db2inst1_2 60003/tcp
DB2_db2inst1_END 60004/tcp

These ports are used for the DB2 FCM to communicate between partitions,
not for client communication (SVCENAME) with the instance.

You need to create another entry in /etc/services for TCPIP client
communication (the default created when db2 installs is something
like 'db2cdb2inst1', on port 50000) and update the SVCENAME param.


-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

[Ian]

db*****@yahoo.com wrote:

[db2inst1@db01]$ grep DB2 /etc/services
DB2_db2inst1 80001/tcp
DB2_db2inst1_1 80002/tcp
DB2_db2inst1_2 80003/tcp
DB2_db2inst1_END 80004/tcp

[db2inst1@db01]$ db2 get dbm cfg | grep -i svce
TCP/IP Service name (SVCENAME) = 80001

It looks, whatever, I do to the service name, it takes the port used
by db2fm daemon. I will try bring down the daemon. Any idea to fix
this.

Your /etc/services should have entries similar to this:

db2cdb2inst1 50000/tcp # This is for SVCENAME
DB2_db2inst1 80001/tcp # This is used by FCM - NOT SVCENAME!!
DB2_db2inst1_1 80002/tcp # This is used by FCM - NOT SVCENAME!!
DB2_db2inst1_2 80003/tcp # This is used by FCM - NOT SVCENAME!!
DB2_db2inst1_END 80004/tcp # This is used by FCM - NOT SVCENAME!!

The first entry is the port that DB2 clients communicating via TCP/IP use.
The SVCENAME dbm config parameter references this.

The other 4 entries are for EEE (DPF) only, for the FCM (fast
communications manager). DB2 uses these ports for inter-partition
communication.

The problem is that you're trying to use one of the FCM ports for client
communication, and this is why you have the error.

With the above entries in /etc/services, you would set SVCENAME to
'db2cdb2inst1':

db2 update dbm cfg using svcename db2cdb2inst1
You should read the "Quick Beginnings Guide for DB2 Servers," chapter 10
(Installing Partitioned DB2 servers (UNIX)). These topics are covered in
detail.



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

[dba2adm]

Thanks Ian. It works perfect now.

db*****@yahoo.com wrote in message news:<90**************************@posting.google. com>...

Thanks Ian for the response.

I already tried changing the port, but am getting the similar kind of
error.

ADM7007E The SVCENAME DBM configuration parameter, "14465", 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.
[db2inst1@db01]$ sudo netstat -pante | grep 144
tcp 0 0 127.0.0.1:14465 0.0.0.0:* LISTEN 502 5664 2407/db2fcmdm
tcp 0 0 127.0.0.1:14466 0.0.0.0:* LISTEN 502 6285 2406/db2fcmdm
[db2inst1@db01]$ grep DB2 /etc/services
DB2_db2inst1 80001/tcp
DB2_db2inst1_1 80002/tcp
DB2_db2inst1_2 80003/tcp
DB2_db2inst1_END 80004/tcp

[db2inst1@db01]$ db2 get dbm cfg | grep -i svce
TCP/IP Service name (SVCENAME) = 80001

It looks, whatever, I do to the service name, it takes the port used
by db2fm daemon. I will try bring down the daemon. Any idea to fix
this.

Thanks
--------------------------------------------------------------------

Ian <ia*****@mobileaudio.com> wrote in message news:<40**********@corp.newsgroups.com>...

db*****@yahoo.com wrote:

I am trying to test the DB2 V8.1 partitioning on the RedHat Linux EL 3
AS. I installed v8.1 successfully using db2_install and installed the
FP5.

Now, I created an ESE instance and edited the db2nodes.cfg (the 1st
line was created by default, I added the 2nd line)

[db2inst1@db01 db2inst1]$ cat sqllib/db2nodes.cfg

0 db01.prince.com 0 #created by db2icrt -s ese ..
1 db01.prince.com 1 #added by me for testing partitioning feature

[db2inst1@db01]$ db2start #works just fine db2nodes.cfg has only one
entry
05-22-2004 12:39:20 1 0 SQL1063N DB2START processing was
successful.
05-22-2004 12:39:27 0 0 SQL5043N Support for one or more
communications protocols failed to start successfully. However, core
database manager functionality started successfully.
SQL8011W One or more database partitions does not have a valid DB2
license key installed for the "DB2 Enterprise Server Edition" product.
SQL1063N DB2START processing was successful.

[db2inst1@db01]$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) =
DB2_db2inst1

[db2inst1@db01 db2inst1]$ grep 6000 /etc/services
DB2_db2inst1 60001/tcp
DB2_db2inst1_1 60002/tcp
DB2_db2inst1_2 60003/tcp
DB2_db2inst1_END 60004/tcp

These ports are used for the DB2 FCM to communicate between partitions,
not for client communication (SVCENAME) with the instance.

You need to create another entry in /etc/services for TCPIP client
communication (the default created when db2 installs is something
like 'db2cdb2inst1', on port 50000) and update the SVCENAME param.


-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----