use command:
c:\set|more
to look for ORACLE_SID and ORACLE_HOME in the list
of system variables and make sure these are set correctly.
c:\set|more
to look for ORACLE_SID and ORACLE_HOME in the list
of system variables and make sure these are set correctly.
calculated based on the contents of ORACLE_SID and ORACLE_HOME. When you
try to connect to the database, your process needs to find the shared
memory segment. It does so by matching your oracle_sid and oracle_home against
this hashed key. (In the case of a network connection, it does this by
using the oracle_sid and oracle_home in the listener.)
Check to see how your environment was set when you started the database
versus how it is set when you're trying to connect. In particular, if the
oracle_home path or the oracle_sid is different in any way,you'll get the
messages: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
In my case, I had the sid as lower case for the session that started the
database, and upper case in the listener.ora file.
输入用户名、密码、主机字符串后并提示以上错误
是否修改过配置文件,再查一查网络性病毒(如fixnimda,nonimda)。
但你没有打开,实例没有处于open状态
用 internal 或sys as sysdba 连接
startup open
或 alter database mount;
alter database open;检验 select status from v$instance;
应为 openoracle 817 有时不能自动启动,好像是一个bug
SQL> select * from v$sga;NAME VALUE
-------------------- ----------
Fixed Size 735896
Variable Size 285212672
Database Buffers 33554432
Redo Buffers 798720
大概是这句:
os_authen????????=(none)
就可以!
数据库没有open,我用手工方法启动
sqlplus下:sys/change_on_install as sysdba
startup
exit
calculated based on the contents of ORACLE_SID and ORACLE_HOME. When you
try to connect to the database, your process needs to find the shared
memory segment. It does so by matching your oracle_sid and oracle_home against
this hashed key. (In the case of a network connection, it does this by
using the oracle_sid and oracle_home in the listener.)
Check to see how your environment was set when you started the database
versus how it is set when you're trying to connect. In particular, if the
oracle_home path or the oracle_sid is different in any way,you'll get the
messages: ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
In my case, I had the sid as lower case for the session that started the
database, and upper case in the listener.ora file.