After several tests on different machines we found that it was not a version problem, but a environment problem. What happened is that one of our DBAs had created a Unix alias to bring the instance up in her profile and that did not set up the environment properly even though the database came up the last time she bounced the database.
Specifically, the LD_LIBRARY_PATH was environment variable was SYS$HOSED as we used to say in the VAX world. The fix is to make sure you bring up the Oracle Instance under the Oracle account. We bounced the instance in the middle of the night and everything is fine now. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Johnson, Michael INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
