Peter, I agree with Safra. The absolute best practice is to run the application on a separate server. But given that this probably can't happen, I would install the Oracle client as a separate Oracle home on the DB server. This way, you can control security of the Database Oracle home better - don't let the application account even get there. Tom From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Harel Safra Sent: Wednesday, January 19, 2011 7:24 AM To: pjhoraclel@xxxxxxxxx Cc: oracle-l Subject: Re: Best practice for Oracle clients with a single instance database I'd install two homes for the advantages you specified. Harel Safra Sent from my phone On Jan 19, 2011 12:27 PM, "Peter Hitchman" <pjhoraclel@xxxxxxxxx<mailto:pjhoraclel@xxxxxxxxx>> wrote: > Hi, > Having over the past couple of years started to work with RAC, where > the application code runs from another server with an Oracle client > install, I am back setting up a single instance where the application > code will run on the > same machine. It occurred to me that it might make sense to still > install an Oracle runtime or instant client for the application to > use, as well as the database install, because that way I could > upgrade one without interfering with the other. On the down side it > means there will be an extra oracle home to maintain and if the > releases are different, I might run into issues with the oraenv/dbhome > programmes. > > What do most people out there do, with single instance set-ups? > > Thanks > Pete > -- > //www.freelists.org/webpage/oracle-l > >