Bingo. orapr1@r3prdci1>which sqlplus /oracle/PR1/920_64/bin/sqlplus Now the problem is why the heck is that still in the path. I suspect it has to do with our AIX Systems Administrators and their invocation of HACMP (which was dismantled but all the scripts left in place). orapr1@r3prdci1>echo $PATH /oracle/PR1/102_64/bin:/usr/sap/PR1/SYS/exe/run:/usr/bin:/etc:/usr/sbin:/usr/ucb:/usr/bin/X11:/sbin:/usr/java14/jre/bin:/usr/java14/bin:/usr/tivoli/tsm/client/ba/bin:/usr/tivoli/tsm/client/oracle/bin64:/usr/local/scripts:/usr/local/scripts/operator:/opt/CA/UnicenterNSM/atech/services/bin On Tue, Nov 4, 2008 at 3:41 AM, Nigel Thomas <nigel.cl.thomas@xxxxxxxxxxxxxx > wrote: > David > > None of your tests so far show you which directory you are actually in. It > is possible that some kind soul has put a sqlplus shell script earlier in > the PATH than the Oracle sqlplus executable which does something like: > > cd some-directory > $ORACLE_HOME/rdbms/bin/sqlplus > > So: to check this, you try the following: > > orapr1@r3prdci1> *which sqlplus* > > On most unixes *which* should tell you if you have a script in the way > (and where it is hiding). > > Otherwise, try > > orapr1@r3prdci1> *pwd* > > orapr1@r3prdci1> *sqlplus user/pass* > SQL>* !pwd* > > Are you in the same directory as before? > > Another way you could end up in a different directory is if your shell (eg > ksh) runs a login, .profile, or other startup file (like .bashrc) which > includes a *cd* command. Check *man ksh* for the files that are executed > when you launch a new shell. > > HTH > > Regards Nigel > >