首页 > 编程知识 正文

脚本错误解决办法,证书错误解决办法

时间:2023-05-05 02:44:52 阅读:268914 作者:3621

alert.log 错误   Fatal NI connect error 12170.   VERSION INFORMATION:         TNS for Solaris: Version 11.2.0.1.0 - Production         Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.1.0 - Production         TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.1.0 - Production   Time: 09-SEP-2011 10:19:05   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: 145     nt OS err code: 0   Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.201.54.197)(PORT=65205)) Fri Sep 09 10:19:36 2011   这个问题可在 metalink  [ID 1286376.1] 中查到 ‘Fatal NI connect error 12170', 'TNS-12535: TNS:operation timed out' Reported in 11g Alert Log     问题描述:   Suggested Actions: - Search the corresponding text version of the listener log located on the database server for the corresponding client connection referenced by the Client address details referenced in the alert log message. For the message incident below you would search the listener log for the 'Client address' string: (ADDRESS=(PROTOCOL=tcp)(HOST=10.159.34.117)(PORT=1092)) The search of the listener log should find the most recent connection before the time reference displayed in the alert log message, e.g. '22-JAN-2011 21:48:23'. -Corresponding listener log entry: 22-JAN-2011 21:20:12 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=AMN11264.us.oracle.com)(CID=(PROGRAM=D:appmcassadyproduct11.2.0dbhome_1binsqlplus.exe)(HOST=mcassady-lap)(USER=mca ssady))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.159.34.117)(PORT=1092)) * establish * AMN11264.us.oracle.com * 0 - Alert log entry: ------------ Fatal NI connect error 12170. VERSION INFORMATION: TNS for Solaris: Version 11.2.0.1.0 - Production Oracle Bequeath NT Protocol Adapter for Solaris: Version 11.2.0.1.0 - Production TCP/IP NT Protocol Adapter for Solaris: Version 11.2.0.1.0 - Production Time: 22-JAN-2011 21:48: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: 145 nt OS err code: 0 Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.159.34.117)(PORT=1092)) ------------   问题分析:   Note the time of the client corresponding client connection(s) in the listener log.  Here you may find a particular client, set of clients or particular applications that are improperly disconnecting causing the timeout errors to be raised and recorder in the database alert log. You may choose to revert from the new Automatic Diagnostic Repository (ADR) method to prevent the Oracle Net diagnostic details from being written to the alert log(s) by setting the following Oracle Net configuration parameters:   解决方法: To revert to Oracle Net Server tracing/logging, set following parameter in the server's sqlnet.ora : DIAG_ADR_ENABLED = OFF Also, to back out the ADR diag for the Listener component, set following parameter in the server's listener.ora: DIAG_ADR_ENABLED_ = OFF    - Where the would be replaced with the actual name of the configured listener(s) in the listener.ora configuration file.  For example, if the listener name is 'LISTENER', the parameter would read: DIAG_ADR_ENABLED_LISTENER = OFF -Reload or restart the TNS Listener for the parameter change to take effect.

版权声明:该文观点仅代表作者本人。处理文章:请发送邮件至 三1五14八八95#扣扣.com 举报,一经查实,本站将立刻删除。