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
------------------------------