Hi Bill,If you think the error is generated on the client side (I suspect it is), then you might find some interesting information by tracing the sqlplus execution. If it's missing a file, you'll see the ENOENT error in the trace output. Start sqlplus like this:
strace -o /tmp/sqlplus-trace.log sqlplus <sqlplus-args>As soon after the error as possible, exit sqlplus, open the logfile in an editor and search for ENOENT from the bottom up (in vi, that's "ctrl-G, ?ENOENT"). I suspect that will help you determine/confirm the file that sqlplus can't find. Searching for login.sql should also get a hit or two in that trace output.
Dan William Wagman wrote:
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? -----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 oracleEnter password: O/S Message: No such file or directoryDisconnected 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.
-- //www.freelists.org/webpage/oracle-l