ORA-12170: TNS:Connect timeout occurred
点击(此处)折叠或打开
- ORA-12170: TNS:Connect timeout occurred
- Cause: The client failed to establish a connection and complete authentication in the time specified by the SQLNET.INBOUND_CONNECT_TIMEOUT parameter in the sqlnet.ora file. This error may be a result of network or system delays, or it may indicate that a malicious client is trying to cause a denial-of-service attack on the database server.
- See Also:
- \"Configuring the Listener and the Oracle Database To Limit Resource Consumption By Unauthorized Users\" further information about setting the SQLNET.INBOUND_CONNECT_TIMEOUT parameter
- Action: If the error occurred due to system or network delays that are normal for the particular environment, then perform these steps:
- Turn on tracing to determine where clients are timing out.
- See Also:
- \"Tracing Error Information for Oracle Net Services\"
- Reconfigure the SQLNET.INBOUND_CONNECT_TIMEOUT parameter in sqlnet.ora to a larger value.
- If you suspect a malicious client, then perform these steps:
- Locate the IP address of the client in the sqlnet.log file on the database server to identify the source.
- For example, the following sqlnet.log excerpt shows a client IP address of 10.10.150.35.
- Fatal NI connect error 12170.
- VERSION INFORMATION:
- TNS for Solaris: Version 10.1.0.2.0
- Oracle Bequeath NT Protocol Adapter for Solaris: Version 10.1.0.2.0
- TCP/IP NT Protocol Adapter for Solaris: Version 10.1.0.2.0
- Time: 03-JUL-2002 13:51:12
- Tracing to file: /ora/trace/svr_13279.trc
- Tns error struct:
- nr err code: 0
- ns main err code: 12637
- TNS-12637: Packet receive failed
- ns secondary err code: 12604
- nt main err code: 0
- nt secondary err code: 0
- nt OS err code: 0
- Client address: (ADDRESS=(PROTOCOL=tcp)(HOST=10.10.150.35)(PORT=52996))
- Beware that an IP address can be forged.
- If the time out occurs before the IP address can be retrieved by the database server, then enable listener tracing to determine the client that made the request.
- See Also:
- Tracing Error Information for Oracle Net Services
- Restrict access to the client. For example, you can configure parameters for access rights in the sqlnet.ora file.
- See Also:
- \"Configuring Database Access Control\"
- TNS-12500/ORA-12500: TNS: listener failed to start a dedicated server process
- Cause: The listener failed to start the oracle program. Possible reasons include:
- The maximum number of processes allowed for a single user was exceeded
- The listener does not have execute permission on the oracle program
- The associated Windows service is not started
- In some cases, these errors can be caused by the same conditions which cause TNS-12549/ORA-12549, TNS-00519, TNS-12540/ORA-12540, TNS-00510, and TNS-12560/ORA-12560 errors.
- Action: Perform the appropriate action:
- Increase the number of processes by setting the PROCESSES parameter in the database initialization file to a larger value.
- Check the listener.log file for detailed error stack information.
- ORA-12514: TNS:listener does not currently know of service requested in connectdescriptor
- Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that has either not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
- Action: Perform these steps:
- Wait a moment and try to connect a second time.
- Check which services are currently known by the listener by executing the Listener Control utility STATUS or SERVICES command.
来自 “ ITPUB博客 ” ，链接：https://blog.itpub.net/29477587/viewspace-1078684/ ，如需转载，请注明出处，否则将追究法律责任。
请登录后发表评论
登录
全部评论
