Teradata Database 3130 超出响应限制? [英] Teradata Database 3130 Response limit exceeded?
问题描述
[Teradata Database] [3130] 超出响应限制
我不知道是什么导致了这个随机错误消息.当我调用数据库以进行 SELECT 或执行存储过程时会发生这种情况.我希望我有更多关于如何重现这个的信息，但它似乎是间歇性的.
I have no idea what is causing this random error message. It happens when I am making a call to the database for a SELECT or to execute a stored procedure. I wish I had more information on how to reproduce this, but it appears to be intermittent.
这个错误究竟意味着什么?什么类型的条件会导致这种情况?
What does this error actually mean? What types of conditions could cause this?
我发现当我构建我的 ASP.NET 应用程序 (vs2012) 时问题消失了.就好像与连接相关的东西被缓存在我机器上的某个地方.在我通过重建回收应用程序池后，它会重置所有内容.下次发生这种情况时，我将尝试保存 web.config 文件，该文件会自动回收应用程序池，而无需重建 DLL.
I've discovered that the issue goes away when I build my ASP.NET app (vs2012). It's like something related to connections is being cached somewhere on my machine. After I recycle the app pool with a rebuild, it resets everything. The next time this happens, I will try saving the web.config file which automatically recycles the app pool without rebuilding the DLL.
推荐答案
这是摘自 Messages 手册:
This is a cut&paste from the Messages manual:
3130 超出响应限制.
3130 Response limit exceeded.
说明:TDBMS 限制为 16 个未完成的响应.单次会议.如果应用程序允许响应堆积，会出现这个错误.响应是来自 SELECT 的响应集陈述.响应由 TDBMS 保存，直到我们知道用户是完成它，此时它被取消.有两种情况:
Explanation: There is a TDBMS limit of 16 outstanding responses for a single session. If responses are allowed to pile up by an application, this error will occur. A response is the response set from a SELECT statement. A response is kept by the TDBMS until we know the user is done with it at which point it is cancelled. There are two scenarios:
如果 KeepResp 为 OFF，则当所有行都返回到应用程序并且主机已经通知响应结束.
If KeepResp is OFF, the response is automatically cancelled when all rows have been returned to the application and the host has been notified of the end of the response.
如果 KeepResp 为 ON，则响应将被保留，直到用户明确取消为止.在每种情况下，响应都可以通过以下方式显式取消应用程序.一旦不再需要它.
If KeepResp is ON, the response is held until explicitly cancelled by the user. In each case, the response can be explicitly cancelled by the application.as soon as it is no longer needed.
生成者:调度员.
谁:最终用户.
补救措施:响应是会话的属性并且将如果会话被注销，则自动自动取消.取消旧响应并重新提交请求或事务.
Remedy: The responses are the property of the session and will automatically automatically be cancelled if the session is logged off. Cancel an old response and resubmit the request or transaction.
正如您已经注意到的，这通常是由行为不当的应用程序引起的，服务器端打开的结果集过多.关闭它们是客户的责任:-)
As you already noticed this is usually caused by a misbehaving application, too many open result sets on the server side. It's the client's responsibility to close them :-)
这篇关于Teradata Database 3130 超出响应限制?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
