Fatal NI connect error 12170.報錯處理
檢視db alter日誌,有大量的Fatal NI connect error 12170報錯
***********************************************************************
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.2.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
Time: 20-DEC-2013 16:54:23
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.211)(PORT=1521))
***********************************************************************
說明:這個問題是由於Automatic Diagnostic Repository中的 Oracle Net diagnostic在預設的情況下是開啟的,
當資料庫和客戶端的連線超過特定時間,就會把這樣的資訊寫入到alert日誌中,所以這不是一個致命的問題,但大篇幅的顯示此錯誤,
還是遮蔽的好
***********************************************************************
Fatal NI connect error 12170.
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.2.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.2.0 - Production
Time: 20-DEC-2013 16:54:23
Tracing not turned on.
Tns error struct:
ns main err code: 12535
TNS-12535: TNS:operation timed out
ns secondary err code: 12560
nt main err code: 505
TNS-00505: Operation timed out
nt secondary err code: 110
nt OS err code: 0
Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.211)(PORT=1521))
***********************************************************************
說明:這個問題是由於Automatic Diagnostic Repository中的 Oracle Net diagnostic在預設的情況下是開啟的,
當資料庫和客戶端的連線超過特定時間,就會把這樣的資訊寫入到alert日誌中,所以這不是一個致命的問題,但大篇幅的顯示此錯誤,
還是遮蔽的好
解決方法:
listener.ora
INBOUND_CONNECT_TIMEOUT_LISTENER =
0
DIAG_ADR_ENABLED_LISTENER = OFF
sqlnet.ora
DIAG_ADR_ENABLED =
OFF
SQLNET.INBOUND_CONNECT_TIMEOUT =0
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/25462274/viewspace-2122239/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Fatal NI connect error 12170.Error
- Fatal NI connect error 12170 錯誤Error
- Fatal NI connect error 12170Error
- [重慶思莊每日技術分享]-alert頻繁出現12170. Fatal NI connect errorError
- Alert Log中“Fatal NI connect error 12170”錯誤問題Error
- Fatal NI connect error 12170 TNS-12535 TNS-00505Error
- Fatal NI Connect Error 12170, 'TNS-12535: TNS:operation timed outError
- Fatal NI connect error 12170 TNS-12535 TNS-00505 解決辦法Error
- Fatal NI connect error 12170 TNS-12535/TNS-00505 TNS:operation timed outError
- Mysql報錯Fatal error:Can't open and lock privilege tablesMySqlError
- Win10 video dxgkrnl fatal error 怎麼處理Win10IDEError
- 【Linux】curl: (35) SSL connect error問題處理LinuxError
- 15-錯誤處理(Error)Error
- 執行flutter run命令報錯::ERROR: Could not connect to lockdownd, error code -17FlutterError
- GTID複製報錯處理:Last_Error: Error 'Can't drop database 'test';ASTErrorDatabase
- windows終端輸入pip install requests報錯:Fatal error in launcherWindowsError
- 記一次報錯 symlink(): Protocol error 問題處理ProtocolError
- 錯誤處理:如何通過 error、deferred、panic 等處理錯誤?Error
- ORA-00257: archiver error. Connect internal only, until freed 錯誤的處理方法HiveError
- Extjs報錯處理JS
- DG報錯的處理
- errpt報錯處理
- Host is not allowed to connect to this MySQL server 錯誤的處理方法MySqlServer
- 【六褘-Git】程式碼提交碼雲,報錯 fatal: refusing to merge unrelated histories處理方法;Git
- FATAL - Fatal error: Target Interaction Manager failed at StartupErrorAI
- Golang 學習——error 錯誤處理淺談GolangError
- 【ERROR】ORA-8103錯誤分析處理Error
- Flutter在iOS裝置執行報錯fatal error: 'Flutter/Flutter.h' file not foundFlutteriOSError
- Gulp壓縮報錯處理
- rails gem報錯的處理AI
- Javascript程式碼報錯處理JavaScript
- 各種報錯處理方法
- MySQL 5.5初始化資料庫報錯FATAL ERROR: Could not find my_print_defaultsMySql資料庫Error
- Camunda 流程執行錯誤處理ERROR BOUNDARY EVENTError
- Too many open files報錯處理
- Mysql自動處理同步報錯MySql
- yum groupinstall報錯,處理方法
- ORA-02429 報錯處理