db2 linux odbc startup problem

[GarethHarris]

I have db2 installed on a linux system to be used in
an astronomy data gathering and distribution project.

The database operates correctly for local programs
such as db2 cli and a python interface.

BUT I need for remote users to access this machine via odbc
to analyze data using excel spreadsheets,
AND apparently db2 is not starting up correctly as I get
this message in the log
============================================================
>>>>>tail ~/sqllib/db2dump/db2diag.log>>>>>
2001-06-06-11.11.28.246265 Instance:tidb2 Node:000
PID:28512(db2sysc) Appid:none
common_communication sqlcctcpconnmgr Probe:47
DIA3202C The TCP/IP call "bind" returned an errno="13".

2001-06-06-11.11.29.376287 Instance:tidb2 Node:000
PID:28509(db2star2) Appid:none
base_sys_utilities startdbm Probe:911
============================================================

BTW, the etc services file has:
>>>>>grep db2 /etc/services>>>>>
ibm-db2 523/tcp IBM-DB2 # IBM DB2 Database
ibm-db2 523/udp IBM-DB2 # IBM DB2 Database

and ps shows:
>>>>>ps -ax |grep db2>>>>>
28511 pts/3 S 0:00 db2wdog
28512 pts/3 S 0:00 db2sysc
28513 pts/3 S 0:00 db2gds
28514 pts/3 S 0:00 db2ipccm
28515 pts/3 S 0:00 db2resyn
28516 pts/3 S 0:00 db2srvlst
29107 pts/3 R 0:00 grep db2

======================================
Everything else appears OK.

So what is errno 13 and diag 3202?
I can't find them in IBM docs.

 

[2742]

Hi There
I'm not sure what the problem is but you won't find the answer to the error messages in any documentation. The errors that are produced in the db2diag.log can only be analyzed by IBM them selfs to determine the exact problem. Sometimes you can tell what they are talking about but not often.

I'm sorry i wasn't that helpful

 

[alphonsus]

Hi Gareth,
try using a higher port number (above 1024) and be sure that nobody's using it (50000/50001 are the default for DB2/Linux).

Ex:
db2cxxxx 50000/tcp # Connection port for DB2
db2ixxxx 50001/tct # Interrupt port for DB2

HTH,
Alphonsus.

 

[ebeaum]

Hello,

I think that the suggestion of Alphonsus is a good one. Moreover, make sure that your database manager is configured to accept TCPIP connections. (See get dbm cfg commands)

You can issue 'catalog tcpip node' commands and 'catalog database' commands in order to make sure that the access via TCPIP works well.

Regards

 

[GarethHarris]

PROBLEM SOLVED -
I cleaned out all DB2 related directories
and reran db2setup as root, repeating this until
the install script completes with no errors or
comments. If any error occurs, it leaves debris
which interferes with the next install attempt.
We also had some symlinks which gave db2 setup
some trouble until the correct one was used.
Now db2 works, cli works, python works - all on linux.
And odbc via windows retrieves for access and excel.

Thanks for the help...
BTW, I ended up with admin at port 523 and
instance access at 50000.

 

[Guest_imported]

Errno=13 is a general error number that is defined in every Operating System, it bascially mean there is a permission problem somewhere.

 

[gaussdb2]

hi i ma having TCP/IP related communication problem.i saw a post mentioning the same.i would request you to resolve the same.

heres the error that i am having.i havent worked much with db2.so dont know exactly what to chnage.i am using db2 on WIndows 2000.
----------------------------


SQL30081N A communication error has been detected. Communication protocol

being used: "TCP/IP". Communication API being used: "SOCKETS". Location

where the error was detected: "". Communication function detecting the error:

"connect". Protocol specific error code(s): "10060", "*", "*".

SQLSTATE=08001

 

[gaussdb2]

hi i am having TCP/IP related communication problem.i saw a post mentioning the same.i would request you to resolve the same.

heres the error that i am having.i havent worked much with db2.so dont know exactly what to chnage.i am using db2 on WIndows 2000.
----------------------------


SQL30081N A communication error has been detected. Communication protocol

being used: "TCP/IP". Communication API being used: "SOCKETS". Location

where the error was detected: "". Communication function detecting the error:

"connect". Protocol specific error code(s): "10060", "*", "*".

SQLSTATE=08001