Communications problems
in [DB2]
|
Prev: logbufsz sizing
Next: db2cli.ini
From: Will Honea on 8 Jan 2010 01:27 Running Express-C V9.7 on Linux, I've got one machine that (probably from my own messing around) has lost TCPIP communications. Note that it did work after installation. The problem I'm having is that I cannot re-configure the communications to TCPIP on that instance now. Using the "setup communications" action from db2cc shows tcpip as a detected protocol but it won't allow selection of that protocol. The really confusing part comes from using the online documentation where they declare that "setup communications" is deprecated in V9.7 and may not be available in the future and the "Help" link on that screen comes back blank. Short of a full re-installation, how do I get tcpip re-enabled? -- Will Honea
From: Frederik Engelen on 8 Jan 2010 02:13 On 8 jan, 07:27, Will Honea <who...(a)yahoo.com> wrote: > Running Express-C V9.7 on Linux, I've got one machine that (probably from my > own messing around) has lost TCPIP communications. Note that it did work > after installation. The problem I'm having is that I cannot re-configure > the communications to TCPIP on that instance now. Using the "setup > communications" action from db2cc shows tcpip as a detected protocol but it > won't allow selection of that protocol. The really confusing part comes > from using the online documentation where they declare that "setup > communications" is deprecated in V9.7 and may not be available in the > future and the "Help" link on that screen comes back blank. Short of a full > re-installation, how do I get tcpip re-enabled? > > -- > Will Honea What is the output from db2set -all and db2 get dbm cfg | grep SVCE ? -- Frederik Engelen
From: Will Honea on 9 Jan 2010 02:17 Frederik Engelen wrote: > On 8 jan, 07:27, Will Honea <who...(a)yahoo.com> wrote: >> Running Express-C V9.7 on Linux, I've got one machine that (probably from >> my own messing around) has lost TCPIP communications. Note that it did >> work after installation. The problem I'm having is that I cannot >> re-configure the communications to TCPIP on that instance now. Using the >> "setup communications" action from db2cc shows tcpip as a detected >> protocol but it won't allow selection of that protocol. The really >> confusing part comes from using the online documentation where they >> declare that "setup communications" is deprecated in V9.7 and may not be >> available in the future and the "Help" link on that screen comes back >> blank. Short of a full re-installation, how do I get tcpip re-enabled? >> >> -- >> Will Honea > > What is the output from > > db2set -all > > and > > db2 get dbm cfg | grep SVCE > > ? boss(a)main:~> db2set -all [g] DB2SYSTEM=main [g] DB2INSTDEF=boss [g] DB2ADMINSERVER=dasadmin boss(a)main:~> db2 get dbm cfg | grep SVCE TCP/IP Service name (SVCENAME) = db2c_boss SSL service name (SSL_SVCENAME) = This is a freshly installed server instance in a sandbox for testing. I switched to use SSL layer as I want to extend access to remote clients, had issues, tried to back it out and got hung up here. The rest of the server is installation defaults. -- Will Honea
From: Frederik Engelen on 10 Jan 2010 12:57 On 9 jan, 08:17, Will Honea <who...(a)yahoo.com> wrote: > Frederik Engelen wrote: > > On 8 jan, 07:27, Will Honea <who...(a)yahoo.com> wrote: > >> Running Express-C V9.7 on Linux, I've got one machine that (probably from > >> my own messing around) has lost TCPIP communications. Note that it did > >> work after installation. The problem I'm having is that I cannot > >> re-configure the communications to TCPIP on that instance now. Using the > >> "setup communications" action from db2cc shows tcpip as a detected > >> protocol but it won't allow selection of that protocol. The really > >> confusing part comes from using the online documentation where they > >> declare that "setup communications" is deprecated in V9.7 and may not be > >> available in the future and the "Help" link on that screen comes back > >> blank. Short of a full re-installation, how do I get tcpip re-enabled? > > >> -- > >> Will Honea > > > What is the output from > > > db2set -all > > > and > > > db2 get dbm cfg | grep SVCE > > > ? > > boss(a)main:~> db2set -all > [g] DB2SYSTEM=main > [g] DB2INSTDEF=boss > [g] DB2ADMINSERVER=dasadmin > boss(a)main:~> db2 get dbm cfg | grep SVCE > TCP/IP Service name (SVCENAME) = db2c_boss > SSL service name (SSL_SVCENAME) = > > This is a freshly installed server instance in a sandbox for testing. I > switched to use SSL layer as I want to extend access to remote clients, had > issues, tried to back it out and got hung up here. The rest of the server > is installation defaults. > > -- > Will Honea Try db2set DB2COMM=TCPIP and db2stop/db2start. I believe this will work. -- Frederik Engelen
From: Will Honea on 10 Jan 2010 14:20
Frederik Engelen wrote: > On 9 jan, 08:17, Will Honea <who...(a)yahoo.com> wrote: >> Frederik Engelen wrote: >> > On 8 jan, 07:27, Will Honea <who...(a)yahoo.com> wrote: >> >> Running Express-C V9.7 on Linux, I've got one machine that (probably >> >> from my own messing around) has lost TCPIP communications. Note that >> >> it did work after installation. The problem I'm having is that I >> >> cannot re-configure the communications to TCPIP on that instance now. >> >> Using the "setup communications" action from db2cc shows tcpip as a >> >> detected protocol but it won't allow selection of that protocol. The >> >> really confusing part comes from using the online documentation where >> >> they declare that "setup communications" is deprecated in V9.7 and may >> >> not be available in the future and the "Help" link on that screen >> >> comes back blank. Short of a full re-installation, how do I get tcpip >> >> re-enabled? >> >> >> -- >> >> Will Honea >> >> > What is the output from >> >> > db2set -all >> >> > and >> >> > db2 get dbm cfg | grep SVCE >> >> > ? >> >> boss(a)main:~> db2set -all >> [g] DB2SYSTEM=main >> [g] DB2INSTDEF=boss >> [g] DB2ADMINSERVER=dasadmin >> boss(a)main:~> db2 get dbm cfg | grep SVCE >> TCP/IP Service name (SVCENAME) = db2c_boss >> SSL service name (SSL_SVCENAME) = >> >> This is a freshly installed server instance in a sandbox for testing. I >> switched to use SSL layer as I want to extend access to remote clients, >> had issues, tried to back it out and got hung up here. The rest of the >> server is installation defaults. >> >> -- >> Will Honea > > Try > > db2set DB2COMM=TCPIP > > and db2stop/db2start. I believe this will work. Thank you, that worked. Now that you provided the answer, it turns out that this is pretty clear in the documentation (once you know what you're looking for) and it led to correcting the problems I was having with SSL in the first place. Interesting side note: using the control center I still cannot configure the protocol via the setup communications screen - it refuses to accept changes - but it does track manually entered changes as above. V9.5 allows protocol changes from that same screen. -- Will Honea |