Yes, when you originally login "whenever os error" is false. Dick Goulet Senior Oracle DBA PAREXEL International 978.313.3426 information transmitted in this communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer. -----Original Message----- From: William Wagman [mailto:wjwagman@xxxxxxxxxxx] Sent: Tuesday, December 09, 2008 5:20 PM To: Goulet, Richard; oracle-l@xxxxxxxxxxxxx Subject: RE: Unexpected behavior if whenever oserror set Richard, Neither system, either the 9i or the 10g installation has a login.sql however there is glogin.sql in the $ORACLE_HOME/sqlplus/admin directory of each server. That brings up the interesting question as to why # sqlplus / works but when connected a SQL> connect <different user> generates the error. I would expect that if the login.sql is not found I would get the same error when initially invoking sqlplus. Am I missing something? Thanks. Bill Wagman Univ. of California at Davis IET Campus Data Center wjwagman@xxxxxxxxxxx (530) 754-6208 -----Original Message----- From: Goulet, Richard [mailto:Richard.Goulet@xxxxxxxxxxx] Sent: Tuesday, December 09, 2008 1:24 PM To: William Wagman; oracle-l@xxxxxxxxxxxxx Subject: RE: Unexpected behavior if whenever oserror set Sqlplus is looking for login.sql. Dick Goulet Senior Oracle DBA PAREXEL International 978.313.3426 information transmitted in this communication is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please destroy any copies, contact the sender and delete the material from any computer. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of William Wagman Sent: Tuesday, December 09, 2008 4:13 PM To: oracle-l@xxxxxxxxxxxxx Subject: Unexpected behavior if whenever oserror set Greetings, I'm running 9.2.0.8.0 EE on RHEL4 64-bit. Setting whenever oserror exit generates the following behavior... [oracle@critpinndev pinntest ~]$ sqlplus / SQL*Plus: Release 9.2.0.8.0 - Production on Tue Dec 9 13:05:55 2008 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Connected to: Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production SQL> whenever oserror exit SQL> connect oracle Enter password: O/S Message: No such file or directory Disconnected from Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production This does *not* fail on a 10.2.0.4.0 installation also running EE on RHEL4 64-bit and I don't know if this is due to a difference between 9i and 10g or something else. I suspect it is something else. One difference I find is that the environment variable OLDHOME is not set for the 9i server but setting it does not resolve the problem. I have checked the files in the $ORACLE_HOME/sqlplus/admin directory and find no difference that I believe would make a difference, each contains a glogin.sql. I haven't been able to determine what the missing file is. Help resolving this would be appreciated. Thanks. Bill Wagman Univ. of California at Davis IET Campus Data Center wjwagman@xxxxxxxxxxx (530) 754-6208 -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l