We all know that when we're going to apply Monitor, SQL or Flash patches to D3 that we need to shut down D3 first. But I'll bet very few of us know that we need to shut down the ODBC server as well if it's running. The reason is that patches are usually linked to the ODBC server as well. So if you leave the ODBC server running, shut down D3, apply a Monitor patch, then start D3, you'll have D3 running one version and the ODBC server running another. This can wreak havoc on your system.
As of D3/Unix 10.3, the plot thickens because of added features. Not only to we have the ODBC server, we also have the new mvWorkstation listener. This needs to be stopped as well. And when 10.3.3 is released, three more players: the d3net service and the d3api server and slave.
Here's a list of the actual binaries:
/usr/bin/d3
/usr/bin/odbcsrv
/usr/bin/d3WSListener
/usr/bin/d3netsvc
/usr/bin/d3api_server
/usr/bin/d3api_slave
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
Page 1 / 1
We all know that when we're going to apply Monitor, SQL or Flash patches to D3 that we need to shut down D3 first. But I'll bet very few of us know that we need to shut down the ODBC server as well if it's running. The reason is that patches are usually linked to the ODBC server as well. So if you leave the ODBC server running, shut down D3, apply a Monitor patch, then start D3, you'll have D3 running one version and the ODBC server running another. This can wreak havoc on your system.
As of D3/Unix 10.3, the plot thickens because of added features. Not only to we have the ODBC server, we also have the new mvWorkstation listener. This needs to be stopped as well. And when 10.3.3 is released, three more players: the d3net service and the d3api server and slave.
Here's a list of the actual binaries:
/usr/bin/d3
/usr/bin/odbcsrv
/usr/bin/d3WSListener
/usr/bin/d3netsvc
/usr/bin/d3api_server
/usr/bin/d3api_slave
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
As of D3/Unix 10.3, the plot thickens because of added features. Not only to we have the ODBC server, we also have the new mvWorkstation listener. This needs to be stopped as well. And when 10.3.3 is released, three more players: the d3net service and the d3api server and slave.
Here's a list of the actual binaries:
/usr/bin/d3
/usr/bin/odbcsrv
/usr/bin/d3WSListener
/usr/bin/d3netsvc
/usr/bin/d3api_server
/usr/bin/d3api_slave
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
Thanks for that very useful bit of information.
I used to shutdown the D3 ODBC service manually, but since April 08, the D3 SHUTDOWN program does it for you. It's revision [27] according to the source code. I used to have it in my USER-SHUTDOWN macro but took it out after the update. Since I don't have D3 V10.x.x yet, will the SHUTDOWN program be updated to shutdown the services you mentioned in your post?
------------------------------
Walter Kiess
SA Police Super
------------------------------
Hi Brian,
Thanks for that very useful bit of information.
I used to shutdown the D3 ODBC service manually, but since April 08, the D3 SHUTDOWN program does it for you. It's revision [27] according to the source code. I used to have it in my USER-SHUTDOWN macro but took it out after the update. Since I don't have D3 V10.x.x yet, will the SHUTDOWN program be updated to shutdown the services you mentioned in your post?
------------------------------
Walter Kiess
SA Police Super
------------------------------
Thanks for that very useful bit of information.
I used to shutdown the D3 ODBC service manually, but since April 08, the D3 SHUTDOWN program does it for you. It's revision [27] according to the source code. I used to have it in my USER-SHUTDOWN macro but took it out after the update. Since I don't have D3 V10.x.x yet, will the SHUTDOWN program be updated to shutdown the services you mentioned in your post?
------------------------------
Walter Kiess
SA Police Super
------------------------------
As far as the mvWorkstation listener in 10.3.1 and the other listeners in the future, I don't have an answer at this point. I'll need to check.
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
Hmmm. SHUTDOWN shut down the ODBC server as well? What version of D3?
As far as the mvWorkstation listener in 10.3.1 and the other listeners in the future, I don't have an answer at this point. I'll need to check.
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
As far as the mvWorkstation listener in 10.3.1 and the other listeners in the future, I don't have an answer at this point. I'll need to check.
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
We're still using D3 version 9.2.2
------------------------------
Walter Kiess
SA Police Super
------------------------------
Hmmm. SHUTDOWN shut down the ODBC server as well? What version of D3?
As far as the mvWorkstation listener in 10.3.1 and the other listeners in the future, I don't have an answer at this point. I'll need to check.
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
As far as the mvWorkstation listener in 10.3.1 and the other listeners in the future, I don't have an answer at this point. I'll need to check.
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
402 stopodbcserver: * Stop the ODBC server if running on NT
403 *
404 if nt then
405 crt "Stopping the D3 ODBC Service"
406 execute "!net stop d3odbcsv" Capturing xx;* [28] Add capturing
407 end
408 *
409 return
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
OK, just had a look at SHUTDOWN and followed change tag 27. If you look down around lint 402, you'll see it's doing a platform test and ONLY shutting down the ODBC server on the D3/Windows platform. That's apparently not implemented for D3/Unix, and my guess is they can't because you could be shutting down one VME while another VME is still running. D3/Windows does not support multiple VMEs running on the same host:
402 stopodbcserver: * Stop the ODBC server if running on NT
403 *
404 if nt then
405 crt "Stopping the D3 ODBC Service"
406 execute "!net stop d3odbcsv" Capturing xx;* [28] Add capturing
407 end
408 *
409 return
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
402 stopodbcserver: * Stop the ODBC server if running on NT
403 *
404 if nt then
405 crt "Stopping the D3 ODBC Service"
406 execute "!net stop d3odbcsv" Capturing xx;* [28] Add capturing
407 end
408 *
409 return
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
------------------------------
Walter Kiess
SA Police Super
------------------------------
Yes, we are using D3 for Windows and there is only one VME. I've not had to administer a multiple VME environment and am thus unaware of the idiosyncrasies of such.
------------------------------
Walter Kiess
SA Police Super
------------------------------
------------------------------
Walter Kiess
SA Police Super
------------------------------
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
We all know that when we're going to apply Monitor, SQL or Flash patches to D3 that we need to shut down D3 first. But I'll bet very few of us know that we need to shut down the ODBC server as well if it's running. The reason is that patches are usually linked to the ODBC server as well. So if you leave the ODBC server running, shut down D3, apply a Monitor patch, then start D3, you'll have D3 running one version and the ODBC server running another. This can wreak havoc on your system.
As of D3/Unix 10.3, the plot thickens because of added features. Not only to we have the ODBC server, we also have the new mvWorkstation listener. This needs to be stopped as well. And when 10.3.3 is released, three more players: the d3net service and the d3api server and slave.
Here's a list of the actual binaries:
/usr/bin/d3
/usr/bin/odbcsrv
/usr/bin/d3WSListener
/usr/bin/d3netsvc
/usr/bin/d3api_server
/usr/bin/d3api_slave
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
As of D3/Unix 10.3, the plot thickens because of added features. Not only to we have the ODBC server, we also have the new mvWorkstation listener. This needs to be stopped as well. And when 10.3.3 is released, three more players: the d3net service and the d3api server and slave.
Here's a list of the actual binaries:
/usr/bin/d3
/usr/bin/odbcsrv
/usr/bin/d3WSListener
/usr/bin/d3netsvc
/usr/bin/d3api_server
/usr/bin/d3api_slave
------------------------------
Brian Cram
Senior Technical Support Engineer
Rocket Software
------------------------------
What's the best way to shutdown ODBC then, after shutting down D3 - kill the service in Linux? Thanks
------------------------------
Jacky Yang
sanmar canada
------------------------------
Hi Brian,
What's the best way to shutdown ODBC then, after shutting down D3 - kill the service in Linux? Thanks
------------------------------
Jacky Yang
sanmar canada
------------------------------
What's the best way to shutdown ODBC then, after shutting down D3 - kill the service in Linux? Thanks
------------------------------
Jacky Yang
sanmar canada
------------------------------
# ps -ef | grep odbc | grep -v grep
root 18915 1 0 09:42 pts/1 00:00:00 /usr/bin/odbcsrv -p1603
#
# kill 18915
# ps -ef | grep odbc | grep -v grep
#
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
I'd just find the process, kill the process and try to find it again to make sure it's killed:
# ps -ef | grep odbc | grep -v grep
root 18915 1 0 09:42 pts/1 00:00:00 /usr/bin/odbcsrv -p1603
#
# kill 18915
# ps -ef | grep odbc | grep -v grep
#
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
# ps -ef | grep odbc | grep -v grep
root 18915 1 0 09:42 pts/1 00:00:00 /usr/bin/odbcsrv -p1603
#
# kill 18915
# ps -ef | grep odbc | grep -v grep
#
------------------------------
Brian S. Cram
Principal Technical Support Engineer
Rocket Software
------------------------------
------------------------------
Jacky Yang
sanmar canada
------------------------------
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
