joeller wrote:There are two types of client-server connection mediums in Oracle. TCP. IPC (also called the "bequeath" protocol).
Thank you for replying. I am not clear about your explanation. The Oracle client has been used to connect to our database for years. This was done via an entry in the TNSNames.ora file. The entry used TCP/IP protocol. So I am not clear about the applicability of the issues with IPC protocol to our problem. Could you explain it further?
joeller wrote:Ypou posted that this:
But how is this an issue when I am not doing anything with the client, and every connection to the server from the client is via TNS using the TPC/IP protocol?
And also, as stated above, when the attempt is made for the user "sys" there is no problem.Correct. As the SGA and database instance does not need to exist for a SYSDBA connection - as this type of connection can be used on a clean system to create a database instance.
// identify the database instance to connect to /usr/lib/oracle/xe> export ORACLE_SID=orcl // initiating a successful "connection" - but the database does not // exist/is not running, as indicated by "idle instance" /usr/lib/oracle/xe> sqlplus "/ as sysdba" SQL*Plus: Release 10.2.0.1.0 - Production on Tue Nov 27 11:56:46 2012 Copyright (c) 1982, 2005, Oracle. All rights reserved. Connected to an idle instance. SQL> exit Disconnected // doing the exact same thing as a non-SYSDBA connection - this time around // the client driver expects to find a database instance called "orcl" /usr/lib/oracle/xe> sqlplus scott/tiger SQL*Plus: Release 10.2.0.1.0 - Production on Tue Nov 27 11:56:58 2012 Copyright (c) 1982, 2005, Oracle. All rights reserved. ERROR: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux Error: 2: No such file or directory Enter user-name: ERROR: ORA-01017: invalid username/password; logon denied Enter user-name: ERROR: ORA-01017: invalid username/password; logon denied SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus /usr/lib/oracle/xe>
Seems to me that the first thing that needs to be address is why no user except sys can log into SQLPlus without an initialization error. Seems to me if it was really an initialization error, that error would be presented on any attempt to login. So if it is not an initilization error, then what else would cause the database to return this error?As I've described above - a SYSDBA connection does not need an existing database instance to connect to. And the error that you are getting is from the client driver being unable to attach to/join the database instance - either because the instance does not exist, or because the server process/thread created by driver failed when attempting to join the running instance.
joeller wrote:Yes. That will simplify the problem.
Since both of the clients are 32 bit but the DB is 64 bit, then we should delete one or the other client from the PATH EV?
However, according to all the documentation I've seen to date on it, that ESRI software, "ArcSDE", that connects to the DB through the 32 bit client does appear to need the full client installation. (John please verify as per your recent conversation with the ESRI support tech.)A full client includes utilities (like SQL*Loader, export/import) and so on. Very few shrinkwrap clients I have dealt with, need to use these external client utilities.
But does a full client installation need to be "started" somehow? There is no service in the services window that indicates it is for an Oracle client. Should there be?No, not at all. For an ISV client to work, it needs the OCI driver (assuming it is not a JDBC client) from the Oracle client installation. Be that a full client install or an instant client unzip. This is done by setting PATH on Windows or setting LD_LIBRARY_PATH on Linux/Unix - in order for the kernel to find and load the required OCI driver for the client.