I do the same thing, though mine is called oraenvset. There are case statements and more for each db version. Like LD_LIBRARY_PATH is no longer needed in 10. etc. Sets the prompt to the host. Glogin sets the prompt for any database. Oracle 10 client will set the prompt in an oracle 9 database even after one is logged in elsewhere before connecting to it. Joel Patterson Database Administrator 904 727-2546 ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Still Sent: Monday, May 18, 2009 12:39 PM To: gmei@xxxxxxxxxxxxxx Cc: oracle-l@xxxxxxxxxxxxx Subject: Re: Fw: OT - Getting fired for database oops On Mon, May 18, 2009 at 8:56 AM, Guang Mei <gmei@xxxxxxxxxxxxxx> wrote: 1. Try not to open too many telnet/ssh or sqlplus sessions at the same time. I usually keep one or two. If I need to log into another db, I get out the current session(s) and log into the new db. If one needs to have prod and dev sessions both open, then try to set different background colors so one won't be confused. Using different colors is helpful. Personally I usually do that on Windows. On linux/unix I have a modified version of oraenv called 'koraenv'. (works in bash to BTW) Among other things, when the user is 'oracle', koraenv calls an xtitle function from .bashrc. This sets the title of my putty windows to ORACLE_SID - username pwd I used this last Friday to work on patching 7 databases in 2 hours. A separate putty ssh session was opened for each database, the environment set and the xtitle set accordingly. Using a detailed checklist for each database, I could keep track of which step I was on for each database, and knew which window each was in. It's a fair bit of work beforehand to get everything setup, but it's the only way I could get all these done in 2 hours. Lot of excellent suggestions in your post Guang, thanks. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist