By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,086 Members | 1,452 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,086 IT Pros & Developers. It's quick & easy.

Problem setting up new instance.

P: n/a

Folks,

I am having hard time figuring out the problem I have with setting up new
DB2 instance. This is 22nd instance I am creating on the server and I
have never encounterd this problem. My server and client (2 different
systems) are running AIX 5.3 and DB2 8.2.

On server I have created instance as follows:

# ./db2icrt -a client -p 60085 -u db2fenc1 -s ese db2inst22
DBI1070I Program db2icrt completed successfully.

$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) = 60085

I grant connect priviledge to public.

When I check /etc/services I see following:

DB2_db2inst22 60084/tcp
DB2_db2inst22_1 60085/tcp
DB2_db2inst22_2 60086/tcp
DB2_db2inst22_END 60087/tcp
Why does the first entry start with one port less than what I specified?
What are other ports used for?

When I check the entries for one of the other instance the entries start
with the port number specified on create instance statement:

DB2_db2inst21 60080/tcp
DB2_db2inst21_1 60081/tcp
DB2_db2inst21_2 60082/tcp
DB2_db2inst21_END 60083/tcp

$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) = 60080
I catalog node and database on the client system, but when I try to connect
to the database I get following error:

$ db2 connect to mydb
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "10.90.10.125". Communication function
detecting the error: "connect". Protocol specific error code(s): "79", "*",
"*". SQLSTATE=08001
errno 79 -Connection refused.

netstat command on server shows that it is listening to the port:

# netstat -an | grep 60085
tcp4 0 0 *.60085 *.* LISTEN

On server and client DB2COMM is set to tcpip

$ db2set
DB2COMM=tcpip
I have setup 21 other instances on the server and some of them are cataloged
on the same client as above, but I do not have any problem with them.

What am I missing?

Thanks
--
Hemant Shah /"\ ASCII ribbon campaign
E-mail: No************@xnet.com \ / ---------------------
X against HTML mail
TO REPLY, REMOVE NoJunkMail / \ and postings
FROM MY E-MAIL ADDRESS.
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
Apr 5 '07 #1
Share this Question
Share on Google+
6 Replies


P: n/a
Did you remember to open the new ports on the server's firewall?

Phil Sherman
Hemant Shah wrote:
Folks,

I am having hard time figuring out the problem I have with setting up new
DB2 instance. This is 22nd instance I am creating on the server and I
have never encounterd this problem. My server and client (2 different
systems) are running AIX 5.3 and DB2 8.2.

On server I have created instance as follows:

# ./db2icrt -a client -p 60085 -u db2fenc1 -s ese db2inst22
DBI1070I Program db2icrt completed successfully.

$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) = 60085

I grant connect priviledge to public.

When I check /etc/services I see following:

DB2_db2inst22 60084/tcp
DB2_db2inst22_1 60085/tcp
DB2_db2inst22_2 60086/tcp
DB2_db2inst22_END 60087/tcp
Why does the first entry start with one port less than what I specified?
What are other ports used for?

When I check the entries for one of the other instance the entries start
with the port number specified on create instance statement:

DB2_db2inst21 60080/tcp
DB2_db2inst21_1 60081/tcp
DB2_db2inst21_2 60082/tcp
DB2_db2inst21_END 60083/tcp

$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) = 60080
I catalog node and database on the client system, but when I try to connect
to the database I get following error:

$ db2 connect to mydb
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "10.90.10.125". Communication function
detecting the error: "connect". Protocol specific error code(s): "79", "*",
"*". SQLSTATE=08001
errno 79 -Connection refused.

netstat command on server shows that it is listening to the port:

# netstat -an | grep 60085
tcp4 0 0 *.60085 *.* LISTEN

On server and client DB2COMM is set to tcpip

$ db2set
DB2COMM=tcpip
I have setup 21 other instances on the server and some of them are cataloged
on the same client as above, but I do not have any problem with them.

What am I missing?

Thanks

Apr 5 '07 #2

P: n/a
While stranded on information super highway Phil Sherman wrote:
Did you remember to open the new ports on the server's firewall?

Phil Sherman
This is on internal network and there is no firewall involved.
>

Hemant Shah wrote:
>Folks,

I am having hard time figuring out the problem I have with setting up new
DB2 instance. This is 22nd instance I am creating on the server and I
have never encounterd this problem. My server and client (2 different
systems) are running AIX 5.3 and DB2 8.2.

On server I have created instance as follows:

# ./db2icrt -a client -p 60085 -u db2fenc1 -s ese db2inst22
DBI1070I Program db2icrt completed successfully.

$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) = 60085

I grant connect priviledge to public.

When I check /etc/services I see following:

DB2_db2inst22 60084/tcp
DB2_db2inst22_1 60085/tcp
DB2_db2inst22_2 60086/tcp
DB2_db2inst22_END 60087/tcp
Why does the first entry start with one port less than what I specified?
What are other ports used for?

When I check the entries for one of the other instance the entries start
with the port number specified on create instance statement:

DB2_db2inst21 60080/tcp
DB2_db2inst21_1 60081/tcp
DB2_db2inst21_2 60082/tcp
DB2_db2inst21_END 60083/tcp

$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) = 60080
I catalog node and database on the client system, but when I try to connect
to the database I get following error:

$ db2 connect to mydb
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "10.90.10.125". Communication function
detecting the error: "connect". Protocol specific error code(s): "79", "*",
"*". SQLSTATE=08001
errno 79 -Connection refused.

netstat command on server shows that it is listening to the port:

# netstat -an | grep 60085
tcp4 0 0 *.60085 *.* LISTEN

On server and client DB2COMM is set to tcpip

$ db2set
DB2COMM=tcpip
I have setup 21 other instances on the server and some of them are cataloged
on the same client as above, but I do not have any problem with them.

What am I missing?

Thanks

--
Hemant Shah /"\ ASCII ribbon campaign
E-mail: No************@xnet.com \ / ---------------------
X against HTML mail
TO REPLY, REMOVE NoJunkMail / \ and postings
FROM MY E-MAIL ADDRESS.
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
Apr 5 '07 #3

P: n/a

This is strange. I manually edited the /etc/services file on the server
and changed the port numbers as follows:
DB2_db2inst22 60085/tcp
DB2_db2inst22_1 60086/tcp
DB2_db2inst22_2 60087/tcp
DB2_db2inst22_END 60088/tcp

and now I am able to connect to the database.

I am not sure why the db2icrt command adds entry that starts with one port
number less than what was specified on the command line.

What are the other three ports used for?

Thanks.

While stranded on information super highway Hemant Shah wrote:
>
Folks,

I am having hard time figuring out the problem I have with setting up new
DB2 instance. This is 22nd instance I am creating on the server and I
have never encounterd this problem. My server and client (2 different
systems) are running AIX 5.3 and DB2 8.2.

On server I have created instance as follows:

# ./db2icrt -a client -p 60085 -u db2fenc1 -s ese db2inst22
DBI1070I Program db2icrt completed successfully.

$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) = 60085

I grant connect priviledge to public.

When I check /etc/services I see following:

DB2_db2inst22 60084/tcp
DB2_db2inst22_1 60085/tcp
DB2_db2inst22_2 60086/tcp
DB2_db2inst22_END 60087/tcp
Why does the first entry start with one port less than what I specified?
What are other ports used for?

When I check the entries for one of the other instance the entries start
with the port number specified on create instance statement:

DB2_db2inst21 60080/tcp
DB2_db2inst21_1 60081/tcp
DB2_db2inst21_2 60082/tcp
DB2_db2inst21_END 60083/tcp

$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) = 60080
I catalog node and database on the client system, but when I try to connect
to the database I get following error:

$ db2 connect to mydb
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "10.90.10.125". Communication function
detecting the error: "connect". Protocol specific error code(s): "79", "*",
"*". SQLSTATE=08001
errno 79 -Connection refused.

netstat command on server shows that it is listening to the port:

# netstat -an | grep 60085
tcp4 0 0 *.60085 *.* LISTEN

On server and client DB2COMM is set to tcpip

$ db2set
DB2COMM=tcpip
I have setup 21 other instances on the server and some of them are cataloged
on the same client as above, but I do not have any problem with them.

What am I missing?

Thanks
--
Hemant Shah /"\ ASCII ribbon campaign
E-mail: No************@xnet.com \ / ---------------------
X against HTML mail
TO REPLY, REMOVE NoJunkMail / \ and postings
FROM MY E-MAIL ADDRESS.
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
--
Hemant Shah /"\ ASCII ribbon campaign
E-mail: No************@xnet.com \ / ---------------------
X against HTML mail
TO REPLY, REMOVE NoJunkMail / \ and postings
FROM MY E-MAIL ADDRESS.
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
Apr 5 '07 #4

P: n/a
Ian
Hemant Shah wrote:
Folks,

I am having hard time figuring out the problem I have with setting up new
DB2 instance. This is 22nd instance I am creating on the server and I
have never encounterd this problem. My server and client (2 different
systems) are running AIX 5.3 and DB2 8.2.

On server I have created instance as follows:

# ./db2icrt -a client -p 60085 -u db2fenc1 -s ese db2inst22
DBI1070I Program db2icrt completed successfully.

$ db2 get dbm cfg | grep SVC
TCP/IP Service name (SVCENAME) = 60085

I grant connect priviledge to public.

When I check /etc/services I see following:

DB2_db2inst22 60084/tcp
DB2_db2inst22_1 60085/tcp
DB2_db2inst22_2 60086/tcp
DB2_db2inst22_END 60087/tcp
These ports are used by the FCM for inter-partition communication.

Generally this only applies to systems that use DPF. However, you
should not use these for the client connection port, it's a bad
practice -- because if you do start using DPF, you'll have to make
changes to either the client connection port or change these entries.

I usually have 5 ports on a system that uses DPF with 4 partitions per
server:

db2cdb2inst22 50084/tcp # DB2 Client Communication
DB2_db2inst22 60084/tcp # DB2 FCM
DB2_db2inst22_1 60085/tcp # DB2 FCM
DB2_db2inst22_2 60086/tcp # DB2 FCM
DB2_db2inst22_END 60087/tcp # DB2 FCM
One other note: db2icrt does not add these entries to /etc/services
-- they must have been added earlier, either by hand or by db2setup.

Apr 6 '07 #5

P: n/a
Ian wrote:
One other note: *db2icrt does not add these entries to /etc/services
-- they must have been added earlier, either by hand or by db2setup.
Actually, db2icrt does add the FCM ports to /etc/services.
Apr 6 '07 #6

P: n/a
Ian
Darin McBride wrote:
Ian wrote:
>One other note: db2icrt does not add these entries to /etc/services
-- they must have been added earlier, either by hand or by db2setup.

Actually, db2icrt does add the FCM ports to /etc/services.
Really? In DB2 v8.2? When did that start?
Apr 6 '07 #7

This discussion thread is closed

Replies have been disabled for this discussion.