Re: ORA-01034: ORACLE not available

BS wrote:
> I did reestablished the environment after autoconfig. Another thing I
> noticed that I can connect if I use connect dbuser_at_db and I can't if
> just do connect dbuser.
>
> Any thoughts.
>
> Thanks

Interesting.

I am also just today running into a similar issue, and working to understand it.

W2K PC, 10g client, connecting to a 10.2.0.1g db on W2K3. I have a TNSNAMES entry for the target db. On the client PC, I set ORACLE_SID=<SID>, set ORACLE_HOME.

Results:

1. TNSPING <SID> - success - resolves, and returns a ping response time.
2. sqlplus user/pass_at_SID - success - SQLPlus loads
3. sqlplus user_at_SID (prompted for password) - success - SQLPlus loads
4. sqlplus (prompted for both user and password) - TNS Protocol adapter error

What is similar between this and your situation is that there is a difference in behavior between when the SID is explicitly listed in the connect string and when it is not.

It is almost as if the ORACLE_SID variable is not having any effect.

I haven't found a solid explanation for this yet, but I'm sure there is one and I just need to dig it up. Meanwhile, keying the SID in with the connect string will work for this specific situation.

BD Received on Thu Nov 16 2006 - 12:13:34 CST