Results 1 to 5 of 5
  1. #1
    Join Date
    Nov 2003
    Posts
    24

    Question Unanswered: Connection problem with Enterprise Manager as normal user

    Local System: Oracle Enterprise Manager 9.2.0.1.0
    Target System: Oracle8i Enterprise Edition Release 8.1.7.3.0 - 64bit Production

    #1:
    Starting the Enterprise Manager standalone i can connect to ma target db without a problem, as a normal user with login system/manager.

    #2:
    Logging into the Oracle Management Server as an admin.

    Connect to the same db as normal user again with systenm/manager.

    now this error pops up:
    ----
    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist
    SRV4 Error: 2: No such file or directory
    ----

    now i connect as sysdba and the connection works.
    but clicking on schema or users or something, and another error pops up saying "ORACLE not available".


    env from traget machine:
    Code:
    _=/usr/bin/env
    LANG=C
    _INIT_UTS_RELEASE=5.8
    HZ=100
    _INIT_UTS_MACHINE=sun4u
    PATH=/usr/bin::/usr/local/bin:/usr/ucb:/orainst/oracle817//bin:.
    NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P1
    _INIT_UTS_VERSION=Generic_108528-13
    ORACLE_BASE=/orainst/oracle817/
    EDITOR=vi
    _INIT_RUN_NPREV=0
    _INIT_NET_STRATEGY=none
    LOGNAME=oracle
    _INIT_UTS_NODENAME=sun220r
    _INIT_UTS_ISA=sparc
    MAIL=/var/mail/oracle
    ORACLE_SID=sun220r
    PS1=oracle@sun220r$
    _INIT_PREV_LEVEL=S
    SHELL=/usr/bin/ksh
    ORA_NLS33=/orainst/oracle817//ocommon/nls/admin/data
    HOME=/export/home/oracle
    _INIT_UTS_SYSNAME=SunOS
    LD_LIBRARY_PATH=/orainst/oracle817//lib:/usr/lib:/ubm/lib
    TERM=xterm
    ORACLE_HOME=/orainst/oracle817/
    PWD=/export/home/oracle
    TZ=MET
    _INIT_RUN_LEVEL=3
    _INIT_UTS_PLATFORM=SUNW,Ultra-60
    listener.ora from target machine:

    Code:
    EXTPROC_LISTENER =
      (DESCRIPTION =
        (ADDRESS = (PROTOCOL = IPC) (KEY = PLSExtProcKey))
      )
    
    SID_LIST_EXTPROC_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = PLSExtProc)
          (SID_NAME = sun220r)
          (ORACLE_HOME = /orainst/oracle817/)
          (PROGRAM = extproc)
        )
      )
    
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
     (ADDRESS_LIST =
            (ADDRESS = (PROTOCOL = TCP)(HOST = sun220r)(PORT = 1521))
          )
        )
      )
    
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = sun220r.lala.com)
          (ORACLE_HOME = /orainst/oracle817/)
          (SID_NAME = sun220r)
        )
      )
    tnsnames.ora from Management server:
    Code:
    SUN220R.LALA.COM =
      (DESCRIPTION =
        (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = sun220r)(PORT = 1521))
        )
        (CONNECT_DATA =
          (SID = sun220r)
          (SERVER = DEDICATED)
        )
      )
    does someone have an idea?

    jhp
    black_

  2. #2
    Join Date
    Apr 2003
    Location
    Greenville, SC (USA)
    Posts
    1,155
    I'm not sure but when I see

    ORA-01034: ORACLE not available
    ORA-27101: shared memory realm does not exist

    That usually tells me that I have a problem with the database not
    being up and running... Sounds like you are connecting to a repository database, but when you try to connect to another database, it may not be mounted and open ...

    HTH
    Gregg

  3. #3
    Join Date
    Nov 2003
    Posts
    24
    But if im connecting with the Manager in standalone mode, it works without a problem.

    its also working connecting from the console, through sqlplus.

    jhp
    black_

  4. #4
    Join Date
    Apr 2003
    Location
    Greenville, SC (USA)
    Posts
    1,155
    Is the database opened in exclusive mode ???

  5. #5
    Join Date
    Nov 2003
    Posts
    24
    Jeeehaaa, i finally found my problem.

    And now the bad news, i corrected the oracle_sid value and it still doesn't work. :/

    * fact: Oracle Enterprise Manager 2.2
    * fact: Oracle Server - Enterprise Edition 8.1.7
    * fact: Enterprise Manager Console
    * symptom: Connect as NORMAL from OEM fails
    * symptom: Actions in OEM after connection fails
    * symptom: ORA-01034: ORACLE not available
    * symptom: ORA-27101: shared memory realm does not exist
    * symptom: Connect as SYSDBA or SYSOPER role from OEM succeed
    * symptom: SQL*Plus connection succeeds
    * cause: This problem occurs if there is a mismatch between setting of $ ORACLE_HOME and entries in /etc/oratab or /var/opt/oracle/oratab. Example: Installation of $ORACLE_HOME in the environment points to /u01/app/oracle/product/8.1.7 for instance ORCL In oratab the entry for ORCL instance is: ORCL:/opt/oracle/home/8.1.7:Y Instance was discovered from Oracle Enterprise Manager (OEM) after ORCL instance was started with $ORACLE_HOME pointing to /u01/app/oracle/product/8.1. 7 manually without using oraenv and/or dbstart (E.g. $ORACLE_HOME pointing to /opt/oracle/home/8.1.7) In this case all connects using NORMAL role from Oracle Enterpise Manager (OEM) will fail with ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Any connect against the same instance using SYSDBA or SYSOPER role does not give any errors immediate but any attempt to do anything else against ORCL will fail with ORA-01034: Oracle not available. Oracle Enterprise Manager (OEM) uses the oratab file during the discover process and/or connect and discovers this directory does not exist since environment points to another directory. It is easy to simulate this problem by manually after starting up the ORCL instance change $ORACLE_HOME to an invalid path. A connect as internal will work since this use SYSDBA role but any select as select * from v$instance will fail since no instance is using this $ORACLE_HOME. Connect internal always work since the SYSDBA role is involved when creating new instances.



    fix:

    Change the entry in oratab to match your $ORACLE_HOME environment variable and
    restart the instance. Also rediscover the database from Oracle Enterprise
    Manager (OEM) console will fix the connection problem.
    jhp
    black_

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •