應用服務器：Windows Server 2008 R2 Enterprise
故障現象：項目側同事反映應用服務器上的程序連接數據庫報錯：ORA-12560: TNS: 協議適配器錯誤
1.故障重現
在應用服務器上使用sqlplus和PL/SQL工具登錄 連接數據庫服務器均報錯： ``` ORA-12154: TNS: 無法解析指定的連接標識符 ```2.定位問題
## 2.1 ping測試網絡 ## ping 數據庫IP地址 網絡通暢 ``` C:\Users\Administrator>ping 192.168.1.100正在 Ping 192.168.1.100 具有 32 字節的數據:
來自 192.168.1.100 的回復: 字節=32 時間<1ms TTL=64
來自 192.168.1.100 的回復: 字節=32 時間<1ms TTL=64
來自 192.168.1.100 的回復: 字節=32 時間<1ms TTL=64
來自 192.168.1.100 的回復: 字節=32 時間<1ms TTL=64
192.168.1.100 的 Ping 統計信息:
數據包: 已發送 = 4，已接收 = 4，丟失 = 0 (0% 丟失)，
往返行程的估計時間(以毫秒為單位):
最短 = 0ms，最長 = 0ms，平均 = 0ms
## 2.2 tnsping測試端口 ##
tnsping 數據庫IP地址，報錯：TNS-12560：TNS：協議適配器錯誤
C:\Users\Administrator>tnsping 192.168.1.100
TNS Ping Utility for 32-bit Windows: Version 11.2.0.1.0 - Production on 27-1月 -
2016 09:55:56
Copyright (c) 1997, 2010, Oracle. All rights reserved.
已使用的參數文件:
D:\app\administrator\product\11.2.0\client_1\network\admin\sqlnet.ora
已使用 EZCONNECT 適配器來解析別名
嘗試連接 (DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTOCOL=TCP)(HOST
=192.168.1.100)(PORT=1521)))
TNS-12560: TNS: 協議適配器錯誤
## 2.3 登錄數據庫主機 ##
SecureCRT工具登錄數據庫主機服務器報錯：
An operation on a socket could not be performed because the system lacked
sufficient buffer space or because a queue was full.
## 2.4 嘗試其他機器連接 ##
發現其他機器是可以登錄到數據庫服務器的，進一步查看數據庫相關信息，也發現一切正常：
- 數據庫服務正常
- 數據庫監聽正常
- 防火牆/SELINUX均未啟用
- 其他與應用服務器同一網段的主機測試到數據庫的連接也正常
看起來非常詭異，不過到現在也確定了不是數據庫服務器那邊的原因，不是網絡的原因。
<h1 id="3">3.解決問題</h1>
## 3.1 兩個ORA錯誤的官方解釋 ##
ORA-12560
$ oerr ora 12560
12560, 00000, "TNS:protocol adapter error"
// *Cause: A generic protocol adapter error occurred.
// *Action: Check addresses used for proper protocol specification. Before
// reporting this error, look at the error stack and check for lower level
// transport errors. For further details, turn on tracing and reexecute the
// operation. Turn off tracing when the operation is complete.
ORA-12154
$ oerr ora 12154
12154, 00000, "TNS:could not resolve the connect identifier specified"
// *Cause: A connection to a database or other service was requested using
// a connect identifier, and the connect identifier specified could not
// be resolved into a connect descriptor using one of the naming methods
// configured. For example, if the type of connect identifier used was a
// net service name then the net service name could not be found in a
// naming method repository, or the repository could not be
// located or reached.
// *Action:
// - If you are using local naming (TNSNAMES.ORA file):
// - Make sure that "TNSNAMES" is listed as one of the values of the
// NAMES.DIRECTORY_PATH parameter in the Oracle Net profile
// (SQLNET.ORA)
// - Verify that a TNSNAMES.ORA file exists and is in the proper
// directory and is accessible.
// - Check that the net service name used as the connect identifier
// exists in the TNSNAMES.ORA file.
// - Make sure there are no syntax errors anywhere in the TNSNAMES.ORA
// file. Look for unmatched parentheses or stray characters. Errors
// in a TNSNAMES.ORA file may make it unusable.
// - If you are using directory naming:
// - Verify that "LDAP" is listed as one of the values of the
// NAMES.DIRETORY_PATH parameter in the Oracle Net profile
// (SQLNET.ORA).
// - Verify that the LDAP directory server is up and that it is
// accessible.
// - Verify that the net service name or database name used as the
// connect identifier is configured in the directory.
// - Verify that the default context being used is correct by
// specifying a fully qualified net service name or a full LDAP DN
// as the connect identifier
// - If you are using easy connect naming:
// - Verify that "EZCONNECT" is listed as one of the values of the
// NAMES.DIRETORY_PATH parameter in the Oracle Net profile
// (SQLNET.ORA).
// - Make sure the host, port and service name specified
// are correct.
// - Try enclosing the connect identifier in quote marks.
//
// See the Oracle Net Services Administrators Guide or the Oracle
// operating system specific guide for more information on naming.
## 3.2 windows應用服務器信息 ##
使用systeminfo命令查看這台windows應用服務器信息的部分內容：
C:\Users\Administrator>systeminfo
主機名: XXXXWEB1
OS 名稱: Microsoft Windows Server 2008 R2 Enterprise
OS 版本: 6.1.7600 暫缺 Build 7600
OS 制造商: Microsoft Corporation
OS 配置: 主域控制器
OS 構件類型: Multiprocessor Free
注冊的所有人:
注冊的組織:
產品 ID: xxxxx-OEM-xxxxxxx-xxxxx
初始安裝日期: 2014/1/26, 21:31:46
系統啟動時間: 2014/9/5, 13:42:21
系統制造商: HP
系統型號: ProLiant BL460c Gen8
系統類型: x64-based PC
處理器: 安裝了 2 個處理器。
[01]: Intel64 Family 6 Model 45 Stepping 7 GenuineIntel ~2000
Mhz
[02]: Intel64 Family 6 Model 45 Stepping 7 GenuineIntel ~2000
Mhz
BIOS 版本: HP I31, 2013/12/20
可以看到，服務器據上一次啟動，已經運行了一年多。
而從上面CRT連接報出的錯誤信息初步確定是此台windows服務器的socket資源耗盡。
對windows不是很了解，簡單粗暴的重啟應用服務器后解決了此問題。