************************************************************* 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 directoryYou 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_JUNKIn 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
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 directoryYou 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_JUNKIn 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
改小一下，重新启动一下；考虑还做过哪些改动呢？向前走一定要想到能不能回来~
startup pfile='.../initSID.ora'
or
startup spfile='.../spfileSID.ora'
sqlplus "/ as sysdba"
C:\SVRMGRL
SVRMGRL>
SVRMGRL>CONNECT INTERNAL
SVRMGRL>STARTUP
如果运行SVRMGRL不正常，还是，备份原来的数据库，重新安装，然后在关掉服务
覆盖回来。