oracle database connected in ideal instance

[Shah Gaurang B.]

We are facing one problem related to oracle database connectivity.When any DBA except oracle (user) trying to connect with oracle database (version 9.2.0.5.0 )on HP-UX 11.11 giving error "Error: connected to ideal instance ". As per the Customer DBA they checked all the parameters of DATABASE restriction policy but he didn't find any problem in it so customer want to check all settings of users who are not able to connect .We had configured our system in trusted mode from the beginning and other things are working fine.

Pl. guide me how to solved this problem.

thanks in advance to all

[Yogeeraj_1]

hi,

please post the exact error message. (copy-paste)

Also, is the listener running?
(to check run: lsnrctl status)


kind regards
yogeeraj

[RAC_1]

Do you get any additional error message/information?

How exactly users connect? First telnet/ssh and then oracle login? This more seems as a oracle problem. You can check general errors in syslog.log/dmesg.

May be putting this post in database section will help.

[Victor Fridyev]

Hi,

Could you look on ownership and permissions of $ORACLE_HOME/bin/oracle* files and compare them with the output:
-rwsr-s--x 1 oracle dba 179813784 Sep 15 2005 oracle*
-rwsr-s--x 1 oracle dba 179813784 Sep 15 2005 oracleO*

Sometimes relink and running of root.sh can help.

[Shah Gaurang B.]

Dear Yogeeraj,

Error is:

export ORACLE_SID=SWOM
AKJ @ INDRSWIFT01: /home/AKJ>sqlplus '/as sysdba'

SQL*Plus: Release 9.2.0.5.0 - Production on Mon Aug 28 15:01:57 2006

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

Connected to an idle instance.

[A. Clay Stephenson]

There is a huge difference between an "ideal" and an "idle" instance. This simply means that the listener has connected you a an Oracle instance that has not yet been started. Your DBA needs to start this instance.

[spex]

SQL> startup

[Steven E. Protter]

Shalom,

I hope the message is idle.

Of so, the solution is to start the database as noted above.

For the sake of completeness, an upgrade to the latest oracle patch set, as difficult as I know that is would be helpful in elminating fugure issues.

I'm guessing this is actually an environment problem and you connect to an idle instance because the ORACLE_SID variable is incorrectly set.

SEP

[KapilRaj]

I too think it is a bad ORACLE_SID variable

[FredLam]

I would like to suggest
1. First check the Instance is up
ps -ef|grep ora_
a list of process showing,
see whether there are your SID process
e.g. SID=ORCL,
ora_pmon_ORCL
2. Check your listener is up
ps -ef|grep tns
3. Check your environment variable
ORACLE_SID=
ORACLE_HOME=
PATH=$ORACLE_HOME/bin
optional TNS_ADMIN=$ORACLE_HOME/network/admin
4. Check your listener.ora, tnsnames.ora and sqlnet.ora
5. Try sqlplus on same machine to connect the instance as oracle
6. Try sqlplus on same machine to connect the instance as other unix a/c with dba group

Normally, step 5 should work, if not, please post information from step 1 to step 4.
I assume your case is step 6.

If step 5 succes (because of IPC connection), and step 6 not.
This is because the variable setting is not yet exported in ksh / sh (but is auto set in csh).

There is another variable TWO_TASK you could make use to set to ORACLE_SID, such that it connects through listner.

Hopes that help.