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

DB2 per ODBC ansprechen

P: n/a
Hallo,

ich habe noch nicht viel Erfahrung mit der DB2.
Ich versuche jetzt von einem Client Rechner auf die DB2 auf dem Server
zuzugreifen.
Dazu habe ich mir den Run Time Client Lite geholt und den ODBC Treiber
installiert,
leider habe ich keine Ahnung wie ich den einrichte.
Kann mir da einer helfen, oder mir einen Link geben wo ich es genau
nachlesen kann?

Danke
Newie

Sep 13 '06 #1
Share this Question
Share on Google+
7 Replies


P: n/a
Newie wrote:
Hallo,

ich habe noch nicht viel Erfahrung mit der DB2.
Ich versuche jetzt von einem Client Rechner auf die DB2 auf dem Server
zuzugreifen.
Dazu habe ich mir den Run Time Client Lite geholt und den ODBC Treiber
installiert,
leider habe ich keine Ahnung wie ich den einrichte.
Kann mir da einer helfen, oder mir einen Link geben wo ich es genau
nachlesen kann?
Have you checked the CLI chapters in the DB2 Information Center.
Note that CLI~ODBC.

Cheers
Serge

<winkmitdemzaunpfahl>Wenn Du in Englisch fragst wird's wohl mehr
Antworten geben</winkmitdemzaunpfahl>
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/
Sep 13 '06 #2

P: n/a
Hi,

ok demnächst werde ich es in Englisch versuchen.....
Danke für die Antwort

Were can I find the DB2 Information Center???
Serge Rielau schrieb:
Newie wrote:
Hallo,

ich habe noch nicht viel Erfahrung mit der DB2.
Ich versuche jetzt von einem Client Rechner auf die DB2 auf dem Server
zuzugreifen.
Dazu habe ich mir den Run Time Client Lite geholt und den ODBC Treiber
installiert,
leider habe ich keine Ahnung wie ich den einrichte.
Kann mir da einer helfen, oder mir einen Link geben wo ich es genau
nachlesen kann?
Have you checked the CLI chapters in the DB2 Information Center.
Note that CLI~ODBC.

Cheers
Serge

<winkmitdemzaunpfahl>Wenn Du in Englisch fragst wird's wohl mehr
Antworten geben</winkmitdemzaunpfahl>
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/
Sep 13 '06 #3

P: n/a
Newie wrote:
Hi,

ok demnächst werde ich es in Englisch versuchen.....
Danke für die Antwort

Were can I find the DB2 Information Center???
www.google.com search: DB2 Information Center.
First hit :-)
http://publib.boulder.ibm.com/infoce.../v9//index.jsp
(replace v9 with v8 if needed)

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/
Sep 13 '06 #4

P: n/a
Hi,

thanks for the link.
Now I have starting reading the chapter, but I have already the next
question
Were can I find the name of my node "knotenname "???
I have no idea what the name is.

Newie

Serge Rielau schrieb:
Newie wrote:
Hi,

ok demnächst werde ich es in Englisch versuchen.....
Danke für die Antwort

Were can I find the DB2 Information Center???
www.google.com search: DB2 Information Center.
First hit :-)
http://publib.boulder.ibm.com/infoce.../v9//index.jsp
(replace v9 with v8 if needed)

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/
Sep 13 '06 #5

P: n/a
I think I found the node name but I have a next question

Trying to connect the database I get this error

"SQL30081N.........
...........Protokollspezifische(r) Fehlercode(s): "10061","*", "*".
SQLSTATE=08001"

Does anyone knows this error???

Thank you

Newie schrieb:
Hi,

thanks for the link.
Now I have starting reading the chapter, but I have already the next
question
Were can I find the name of my node "knotenname "???
I have no idea what the name is.

Newie

Serge Rielau schrieb:
Newie wrote:
Hi,
>
ok demnächst werde ich es in Englisch versuchen.....
Danke für die Antwort
>
Were can I find the DB2 Information Center???
www.google.com search: DB2 Information Center.
First hit :-)
http://publib.boulder.ibm.com/infoce.../v9//index.jsp
(replace v9 with v8 if needed)

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/
Sep 13 '06 #6

P: n/a
Newie wrote:
I think I found the node name but I have a next question

Trying to connect the database I get this error

"SQL30081N.........
..........Protokollspezifische(r) Fehlercode(s): "10061","*", "*".
SQLSTATE=08001"

Does anyone knows this error???
I would first try this on the server:
db2set DB2COMM = TCPIP

db2
? SQL30081
<snip>
o If <protocol= TCP/IP, <function= connect, <rc1=
ECONNREFUSED/WSAECONNREFUSED, AIX (79), Windows (10061),
linux (111),

SUN (146), HP (239), the attempt to connect was
rejected. Possible causes:

- The remote database server has not been cataloged correctly
at the client. In a client-gateway-server scenario,
ensure the host entries are cataloged correctly on the
gateway. See the Quick Beginnings guide for
assistance.

- The database manager configuration file at the server has not
been configured properly with the proper communication
parameters. Check that svcename has been configured
properly with the TCP/IP service name or port number and
that the port number is unique. If database manager
configuration parameters have been updated at the server,
the database manager must be stopped and re-started for
the changes to take effect. There might be a mismatch
between the TCP/IP service name or port number specified
on the server and on the client. Ensure the service name
maps to the correct port number by checking the services
file. You can check this by reading the services file or
checking the output of "netstat -a".

- The DB2COMM environment variable at the server does not
specify the communication protocol used by the client.
Check that TCPIP has been specified. Issue db2set to see
what has already been set. Issue db2set DB2COMM = TCPIP
to set the value.

- The database manager at the server has not been started, or
has not been started successfully, or has gone down. The
server should have returned SQL1063, and not SQL5043. If
you set the database manager configuration parameter,
diaglevel, to 4 using, db2 update dbm cfg using diaglevel
4, prior to issuing db2start, the administration
notification log will provide detailed information on
which protocols were started successfully. Check the
administration notification log.

- The server might be too busy to handle the volume of incoming
connections at this time.

- Network failure, contact your network administrator. You can
try a test using the protocol tester, pctt, to verify
this is not a DB2 problem.
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/
Sep 13 '06 #7

P: n/a
Hi Serge,

yeah it works!!!!
I have the run time client lite unistalled and new installed, this time
the full installation and not only the odbc driver, after that it
works.
I have a connection to my database.

Thank you for your answers.

mfg
Newie

Serge Rielau schrieb:
Newie wrote:
I think I found the node name but I have a next question

Trying to connect the database I get this error

"SQL30081N.........
..........Protokollspezifische(r) Fehlercode(s): "10061","*", "*".
SQLSTATE=08001"

Does anyone knows this error???
I would first try this on the server:
db2set DB2COMM = TCPIP

db2
? SQL30081
<snip>
o If <protocol= TCP/IP, <function= connect, <rc1=
ECONNREFUSED/WSAECONNREFUSED, AIX (79), Windows (10061),
linux (111),

SUN (146), HP (239), the attempt to connect was
rejected. Possible causes:

- The remote database server has not been cataloged correctly
at the client. In a client-gateway-server scenario,
ensure the host entries are cataloged correctly on the
gateway. See the Quick Beginnings guide for
assistance.

- The database manager configuration file at the server has not
been configured properly with the proper communication
parameters. Check that svcename has been configured
properly with the TCP/IP service name or port number and
that the port number is unique. If database manager
configuration parameters have been updated at the server,
the database manager must be stopped and re-started for
the changes to take effect. There might be a mismatch
between the TCP/IP service name or port number specified
on the server and on the client. Ensure the service name
maps to the correct port number by checking the services
file. You can check this by reading the services file or
checking the output of "netstat -a".

- The DB2COMM environment variable at the server does not
specify the communication protocol used by the client.
Check that TCPIP has been specified. Issue db2set to see
what has already been set. Issue db2set DB2COMM = TCPIP
to set the value.

- The database manager at the server has not been started, or
has not been started successfully, or has gone down. The
server should have returned SQL1063, and not SQL5043. If
you set the database manager configuration parameter,
diaglevel, to 4 using, db2 update dbm cfg using diaglevel
4, prior to issuing db2start, the administration
notification log will provide detailed information on
which protocols were started successfully. Check the
administration notification log.

- The server might be too busy to handle the volume of incoming
connections at this time.

- Network failure, contact your network administrator. You can
try a test using the protocol tester, pctt, to verify
this is not a DB2 problem.
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/
Sep 15 '06 #8

This discussion thread is closed

Replies have been disabled for this discussion.