ORA-12537 TNS:連線關閉
今天遇到:ORA-12537 TNS:連線關閉,監聽正常,叢集正常,資料庫正常,查了一下才發現問題。
LISTENER日誌報錯
TNS-12546: TNS:permission denied
TNS-12560: TNS:protocol adapter error
TNS-00516: Permission denied
設定限制登入
tcp.validnode_checking=yes
tcp.invited_nodes=(136.3.67.11,136.1.10.11,136.1.10.12,136.1.10.13,136.1.10.14,136.1.10.7,136.1.10.8,136.1.10.6,10.0.1.11,10.0.1.12,10.0.1.6,10.0.1.7,10.0.1.8)
What is Validnode Verification and How to Use It (Doc ID 462933.1)
metalink
In this Document
Goal
Fix
APPLIES TO:
Oracle Net Services - Version 9.2.0.1.0 and later
Information in this document applies to any platform.
GOAL
How to control access to the database and understand validnode checking.
FIX
You can configure the sqlnet.ora file to allow and deny access to the database via the validnode checking parmeters. (Earlier versions of Oracle, 8i and lower used the protocol.ora file)
TCP.VALIDNODE_CHECKING
Use to specify whether to screen access to the database.Value is either YES or ON
TCP.EXCLUDED_NODES
Use to specify which clients using the TCP/IP protocol are denied access to the database. Hostname and ipaddress can be used
TCP.INVITED_NODES
Use to specify which clients using the TCP/IP protocol are allowed access to the database. Hostname and ipadddress can be used.
Example sqlnet.ora file (set where database is running)
TCP.VALIDNODE_CHECKING = YES
TCP.EXCLUDED_NODES= (138.3.33.33)
TCP.INVITED_NODES=(138.4.44.44, hammer)
Would cause the SQL*plus from client "138.3.33.33" to error
sqlplus scott/tiger@orcl
SQL*Plus: Release 10.2.0.1.0 - Production on Tue Oct 16 11:48:40 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
ERROR:
ORA-12537: TNS:connection closed
Level 16 listener trace will show
nttvlser: valid node check on incoming node 138.3.33.33
nttvlser: Denied Entry: 138.3.33.33
nttcon: exit
nserror: entry
nserror: nsres: id=1, p=65, ns=12546, ns2=12560; nt[0]=516, nt[1]=0, nt[2]=0; ora[0]=0, ora[1]=0, ora[2]=
Listener log will show
16-OCT-2007 11:48:40 * 12546
TNS-12546: TNS:permission denied
TNS-12560: TNS:protocol adapter error
TNS-00516: Permission denied
But would allow connections from machines "138.4.44.44" and "hammer" to pass.Please note that without the servers host name or ip address in the invited list, then PMON will not register with the listener.
Any changes to the values requires the TNS listener to be reloaded
All host names must be resolvable or the TNS listener will not start
Invited list takes precedence over excluded listed
All entries must be on one line(Best to add entries via Net Manager)
SCAN and TCP.INVITED_NODES will require the SCAN VIPs and Node Vips to be added to the Grid Infrastructure SQLNET.ORA file.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/7728585/viewspace-774363/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 客戶端連線資料時會報“ORA-12537:TNS連線已關閉”客戶端
- 客戶端連線EBS 11i VIS報ORA-12537: TNS: 連線已關閉 錯誤的解決客戶端
- ORA-12537 TNS:資料庫連線錯誤資料庫
- tns連線非常慢
- httpWebRequest請求錯誤,基礎連線已經關閉: 連線被意外關閉HTTPWeb
- 關於jetty連線關閉問題Jetty
- 11.2.0.4 通過 scan ip 連線資料庫報TNS-12537 連線關閉問題總結資料庫
- 使用screen讓關閉ssh連線時不關閉程式
- 日常Bug排查-連線突然全部關閉
- mysql階段04 連線工具, 連線方式, 啟動關閉mysqlMySql
- TNS-12170 連線超時
- ORA-12170:TNS:連線超時
- ORA-12170: TNS: 連線超時
- ORA-12170 TNS 連線超時
- 資料庫連線未關閉的問題資料庫
- 求助:(javax.transaction.xa.XAException: 關閉的連線))JavaException
- mac 關閉ipv6 連線乙太網Mac
- ORA-12537: TNS:connection closed問題解決
- WebSocket:從建立連線到關閉的完整流程Web
- Oracle備庫TNS連線失敗的分析Oracle
- 【Oracle】ORA-12537: TNS:connection closed 問題處理Oracle
- ora-12537 TNS:connection closed的問題處理
- RAC環境關閉CLUSTER後導致連線緩慢
- 求救:jdbc與mysql透過Servlet操作後連線關閉不了JDBCMySqlServlet
- 如果HTTP客戶端關閉連線Servlet怎麼得到通知?HTTP客戶端Servlet
- TNS-12520 TNS-12519 連線錯誤處理
- TNS-12520 TNS-12519 連線錯誤處理
- TNS-12518: TNS: 監聽程式無法分發客戶機連線
- 我為 Netty 貢獻原始碼 | 且看 Netty 如何應對 TCP 連線的正常關閉,異常關閉,半關閉場景Netty原始碼TCP
- win7系統開啟或關閉自動連線無線網路Win7
- Oracle 11gR2 RAC連線報錯ora-12537錯誤Oracle
- 網路學習筆記(一):TCP連線的建立與關閉筆記TCP
- 遠端連線關閉,專案就停止的解決辦法
- 11G的SYS連線阻止SHUTDOWN IMMEDIATE關閉資料庫資料庫
- 網路 保證在關閉連線前, 把資料發出去
- 關於面向連線與面向無連線
- 【譯】 WebSocket 協議第七章——關閉連線(Closing the Connection)Web協議
- 資料庫外連線,自然連線,內連線,條件連線,等值連線關係及詳解資料庫