Oracle中的IDLE超时参数 [英] IDLE timeout parameter in Oracle

问题描述

我们遇到了一个情况，我们的一个进程需要3小时的计算，而不触及数据库。在调用该过程之前所进行的连接会被 Oracle 服务器关闭，以及任何后续查询或commit throws connection closed exception。

We are stuck in a situation where one of our processes is taking 3 hours of computing without touching the database. The connection that was taken before calling the process gets closed by the Oracle server and any subsequent query or commit throws connection closed exception.

我们认为这个问题与Oracle关闭因为某种原因空闲的连接有关。

It appears to us that the problem is related to Oracle closing the connection that is idle for that long for some reason.

我们尝试在sqlnet.ora中更改EXPIRE_TIMEOUT，但是没有帮助。

We tried changing EXPIRE_TIMEOUT in sqlnet.ora but that didn't help either.

我们能做什么来解决这个问题？

What can we do to resolve this problem?

推荐答案

尝试使用连接时会出现什么错误？

What is the error you get when you try to use the connection?

Oracle默认情况下不会因不活动而关闭连接。您可以使用IDLE_TIME配置配置文件，以使Oracle关闭不活动的连接，但它听起来不像您这样做。您还可以配置Oracle来检测死锁连接并在客户端没有响应时关闭连接 - 如果客户端被埋了三个小时，则可能没有及时响应。但这似乎不太可能广告需要额外的配置步骤。

Oracle by default will not close a connection due to inactivity. You can configure a profile with an IDLE_TIME to cause Oracle to close inactive connections, but it doesn't sound like you've done that. You can also configure Oracle to detect dead connections and close the connection if the client doesn't respond-- if the client is buried for three hours, it's possible that it's not responding in a timely fashion. But that seems less likely ad requires additional configuration steps.

我的经验更有可能是您的网络中断了连接。例如，如果通过防火墙连接，防火墙将频繁关闭空闲时间过长的连接。

The more likely situation in my experience is that your network is dropping the connection. If you are connecting via a firewall, for example, the firewall will frequently close connections that have been idle too long.

您收到的实际Oracle错误讯息会指出这些替代方式中哪一个会导致您的问题。

The actual Oracle error message you are receiving will indicate which of these alternatives is causing your problem.

这篇关于Oracle中的IDLE超时参数的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！