ORA-12545:Oracle SID突然停止工作

我有一个令人困惑的问题。我在Linux上安装了Oracle11g，运行良好。我能够使用基于SID的连接字符串从其他机器远程连接，例如

sqlplusmyschema@192.168.184.102：1521:orcl

然后由于某种莫名其妙的原因，它停止了工作。我不知道我或其他人是怎么搞的

现在，我只能使用服务名称或基于TNSNAME的方法进行远程连接

sqlplusmyschema@192.168.184.102：1521/orcl

sqlplusmyschema@ORCL

这两种方法都可以工作，而且效果很好，但我有一些应用程序依赖于SID连接模式，我可以更改这些模式。能不能有个善良的灵魂帮我找出我错过了什么

以下是我的配置：

LISTENER.ORA：

[oracle@dbora112 ~]$ cat  /opt/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
# listener.ora Network Configuration File: /opt/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
# Generated by Oracle configuration tools.

LISTENER =
  (DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
      (ADDRESS = (PROTOCOL = TCP)(HOST = dbora112)(PORT = 1521))
    )
  )

ADR_BASE_LISTENER = /opt/u01/app/oracle

侦听器状态：

[oracle@dbora112 ~]$ lsnrctl status

LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 04-MAR-2015 14:50:05

Copyright (c) 1991, 2011, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.3.0 - Production
Start Date                04-MAR-2015 14:37:12
Uptime                    0 days 0 hr. 12 min. 52 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /opt/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/listener.ora
Listener Log File         /opt/u01/app/oracle/diag/tnslsnr/dbora112/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=dbora112)(PORT=1521)))
Services Summary...
Service "orcl" has 1 instance(s).
  Instance "orcl", status READY, has 1 handler(s) for this service...
Service "orclXDB" has 1 instance(s).
  Instance "orcl", status READY, has 1 handler(s) for this service...
The command completed successfully

TNSNAMES.ORA：

[oracle@dbora112 ~]$ cat /opt/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
# tnsnames.ora Network Configuration File: /opt/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.

ORCL =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.184.102)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SID = orcl)
    )
  )

LISTENER_ORCL =
  (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.184.102)(PORT = 1521))

SQLNET：

[oracle@dbora112 ~]$ cat /opt/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
# sqlnet.ora Network Configuration File: /opt/u01/app/oracle/product/11.2.0/dbhome_1/network/admin/sqlnet.ora
# Generated by Oracle configuration tools.

NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

ADR_BASE = /opt/u01/app/oracle

可以使用TNS连接，没有问题

[oracle@dbora112 ~]$ sqlplus schema/xxx@ORCL

SQL*Plus: Release 11.2.0.3.0 Production on Wed Mar 4 14:54:10 2015

Copyright (c) 1982, 2011, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>

使用服务名称可以毫无问题地连接

[oracle@dbora112 ~]$ sqlplus schema/xxx@192.168.184.102/ORCL

SQL*Plus: Release 11.2.0.3.0 Production on Wed Mar 4 14:55:52 2015

Copyright (c) 1982, 2011, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL>

无法与SID连接

[oracle@dbora112 ~]$ sqlplus schema/xxx@192.168.184.102:orcl

SQL*Plus: Release 11.2.0.3.0 Production on Wed Mar 4 14:56:38 2015

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

ERROR:
ORA-12545: Connect failed because target host or object does not exist

数据库实例（SID）

---

这可能是因为Oracle无法将主机名解析为IP。你能用nslookup解析你的主机名吗？即

nslookup主机名

还要确保反向查找正常工作：

nsipaddr

---

由于您可以使用TNS别名进行连接，即使用连接描述中的SID，因此SID可以正常工作

但您的EasyConnect字符串不正确：

easy或缩写连接标识符具有以下语法：

[/]主机[：端口][/service\u名称]

不能将SID与Easy Connect一起使用，只能使用服务名称；因此，您可以通过以下方式进行连接：

sqlplus schema/xxx@192.168.184.102:orcl

甚至

sqlplus schema/xxx@192.168.184.102:1521:orcl

。。。根本不可能成功。您可以使用旧样式将该表单与JDBC URL一起使用：

jdbc:oracle:thin:@192.168.184.102:1521:orcl

。。。但这与SQL*Plus连接不同，尽管看起来很相似

如果您试图检查该表单的JDBC连接是否正常工作，则无法使用SQL*Plus执行此操作，但TNS别名检查正在验证它是否按照预期进行了设置，只要它使用相同的主机、端口和SID即可。使用较新的JDBC语法可能更好，但从这个问题上看，您似乎无法改变这一点

---

.

能否显示

show parameter service

的输出OP使用的是IP地址而不是主机名，因此不需要查找，它使用的是服务名-似乎只有SID存在问题，SID和主机名之间没有链接。

jdbc:oracle:thin:@192.168.184.102:1521:orcl