| Author |
Message
|
| thomaszheng |
 Posted: Wed Mar 22, 2006 7:08 am Post subject: remote odbc access problem |
 |
|
Acolyte
Joined: 01 Mar 2006
Posts: 62
|
Hi,
I did catalog tipip node, and catalog db, and set "service/port mappling" in the services file.
then I do "connect to dbname" this command show protocal error.
have I done all the need steps? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Mar 22, 2006 7:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Can we see the protocol error message?
Maybe you need to use "connect to dbname <username> using <password>".
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| thomaszheng |
| Posted: Wed Mar 22, 2006 7:23 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2006
Posts: 62
|
Here is the error message:
SQL 30081N A commuication error has been detected. Communication protocol being used: "TCP/IP". Communication API being used: "SOCKETS". location where the error was detected: "10.122.5.71". Communication function detecting the error" "connect". Protocol specific error code(s): "146", "*", "*". SQLSTATE=08001 |
|
| Back to top |
|
|
| JT |
| Posted: Wed Mar 22, 2006 7:39 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
Error 146 is ECONNREFUSED (connection refused).
You may have specified the wrong port number where DB2 is listening.
Show us the exact syntax of the 'catalog tcpip' command? |
|
| Back to top |
|
|
| thomaszheng |
| Posted: Wed Mar 22, 2006 7:48 am Post subject: |
|
|
Acolyte
Joined: 01 Mar 2006
Posts: 62
|
Here it is:
CATALOG TCPIP NODE BRDBNODE REMOTE 10.122.5.71 SERVER DB2_db2admin remote_instance db2admin OSTYPE SUN
I just copied the "service/port number mapping" from target server to remote access server into the services file. is this is enough? |
|
| Back to top |
|
|
| vk |
| Posted: Wed Mar 22, 2006 12:46 pm Post subject: |
|
|
Partisan
Joined: 20 Sep 2005
Posts: 302
Location: Houston
|
The error is thrown on the server side, when the client tries to connect to the database. This is some firewall issue, where the ports are not properly opened for clients.
Contact you DBA person for getting this resolved.
Regards,
VK. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 22, 2006 12:49 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You can try recataloging the node using the Port number directly instead of using the service name.
I don't think this will work, but it's a quick thing to try and if it works then you've saved some time.
but yes, you should work with the DBA to confirm that you have the right port, that there is not a firewall in the way, and that the database is set up to receive TCP/IP connections on that port.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| thomaszheng |
| Posted: Wed Mar 22, 2006 1:16 pm Post subject: |
|
|
Acolyte
Joined: 01 Mar 2006
Posts: 62
|
thank jefflowrey!!!
now both service name and port number catalog are working. thanks for all the help from you and others!!!! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Mar 22, 2006 1:22 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
What was changed?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| thomaszheng |
| Posted: Wed Mar 22, 2006 1:41 pm Post subject: |
|
|
Acolyte
Joined: 01 Mar 2006
Posts: 62
|
| I just get rid of optional parameter of the catalog node command, spent one day working on it. |
|
| Back to top |
|
|
|
|
