|
|
|
|
|
|
|
|
| Re: ORA-01034: ORACLE not available, ORA-27101: shared memory realm does not exist [message #51380 is a reply to message #50237] |
Mon, 20 May 2002 06:56   |
Ian Corrie
Messages: 1
Registered: May 2002
|
Junior Member |
|
|
I was consistantly receiving this error straight after installing Oracle 8.1.7 on a W2K box, no errors had occured during any installation.
The problem was solved by uninstalling my old instance, manually cleaning the windows registry of references to the now non-existent Oracle instance and most importantly PHYSICALLY DISCONNECTING THE BOX FROM THE LOCAL NETWORK.
After installing under these conditions Oracle worked straight away.
|
|
|
|
| Same, with Oracle answer [message #51447 is a reply to message #51380] |
Thu, 23 May 2002 06:56 |
PhilZe
Messages: 1
Registered: May 2002
|
Junior Member |
|
|
Article-ID: <Note:122183.1>
Circulation: PUBLISHED (EXTERNAL)<Help:KRSTATUS.PUBLISHED>
Folder: network.General <Topics:3735.0>
Topic: Miscellaneous <Articles:3735.0.8857.1>
Title: ORA-27101 "Shared Memory Realm Does Not Exist" Connecting
Via Net8
Document-Type: PROBLEM
Impact: LOW
Skill-Level: NOVICE
Updated-Date: 16-MAR-2002 04:50:18
References:
Shared-Refs:
Authors: BMSMITH.US
Attachments: NONE
Content-Type: TEXT/PLAIN
Keywords: ORA-1034; ORA-27101; CONNECT; FAIL;
Errors: ORA-1034; ORA-27101;
Products: 115/NET (XX);
Platforms: GENERIC;
*************************************************************
This article is being delivered in Draft form and may contain
errors. Please use the MetaLink "Feedback" button to advise
Oracle of any issues related to this article.
*************************************************************
Problem Description
-------------------
You are attempting to connect to an Oracle8i database from a client using
sqlplus and receive the following errors:
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
You have installed 8.1.7 on the same server in a seperate ORACLE_HOME.
Solution Description
--------------------
1) For local (BEQ/IPC) connections:
Verify that the ORACLE_SID environment variable is set and points to a valid
8.1.7 database that is up and running.
% echo $ORACLE_SID
junk
% ps -ef |grep smon
oracle 24603 1 0 15:22:51 ? 0:02 ora_smon_JUNK
In this scenario, because the ORACLE_SID value is case-sensitive on Unix
platforms, a database called 'junk' is not running as it does not exist - it
should be 'JUNK' i.e. upper case.
To fix the issue, set the ORACLE_SID value correctly or to a valid instance.
% setenv ORACLE_SID JUNK (for csh)
% ORACLE_SID=JUNK;export ORACLE_SID (for ksh, sh)
2) For remote (TCP/listener) connections:
Review the listener.ora currently used to startup the listener and verify
the ORACLE_HOME value is correct for all listed Oracle8i databases.
If the ORACLE_HOME points to the 8.1.7 software, however the database was
created using a different version (e.g. 8.1.6 or 8.1.5), then this error can
occur.
Explanation
-----------
Previously, when the ORACLE_HOME or ORACLE_SID were set incorrectly, in the
'oracle' or client user's environment, only ora-1034 was reported e.g.:
ORA-01034 "ORACLE not available"
With 8.1.7, error ORA-27101 reports that the shared memory key generated by the
client does not match any currently existing keys. This is to be expected if
the ORACLE_HOME used by the client is not the same as that used to startup the
database or when the ORACLE_SID value is not correctly referencing the right
instance.
Additional Search Words
-----------------------
listener, tnslsnr, parameter, hashing algorithm, attach, SGA
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
