I think this is more of a mandate on install rather than just a good idea. Unless your SAs can *guarantee* that each OS is at the exact patch level as the one you created the install on, you *must* "relink all" after your copy. Got into a world of hurt doing that on HP-UX once. My (late) $.02, Rich -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Nuno Souto Sent: Thursday, September 28, 2006 6:36 PM To: Oracle-L@xxxxxxxxxxxxx Subject: Re: Cloning Oracle versus Installing from OUI Quoting MVR <yoursraju007@xxxxxxxxx>: > I proposed a plan to make a good working Oracle home(with all the > patches installed) and making an image and using the same image for > all other nodes with the same platform and hardware. The process is > tar, untar them and to run clone.pl for the home on target node. This > saves us lot of time(for installing 10g R2 using OUI). But my > teammates are not okay with that stating that it may get us some > problems. We have already cloned it for multiple boxes and ZERO > issues. But still people are afraid to put that home in prod. > No problems with this sort of approach. Just make sure that you can re-make oracle after the clonable base-set is created: you may well need to do so at some stage for emergency patches or OS updates. Beats the heck out of running OUI across long-distance connections, even in silent response mode. Why Oracle had to ditch the character mode install in favour of the OUI gui abortion still beats me to this day: it's like, they never tried the darn thing themselves on a slow line? What, customers should not have remote data centres reachable only by slow lines? Yeah! Right... -- Cheers Nuno Souto from sunny Sydney -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l