WinXP中的ODBC连接限制在Win2K中没有吗？
我们每晚运行一个流程，使用 Crystal Reports 每天晚上生成大量（约 8000 份）报告。这实际上只是为每个客户运行一次的大约 14 个不同的报告。报告的数据源是 Windows ODBC 连接（通过控制面板）并连接到我们网络上的 Oracle 10g 实例。
我们当前的生产机器运行 Windows 2000 professional，我们最近购买了一台更新的机器来替换它，目的是在 Windows Server 2008 下运行它。在准备进行切换时，我们注意到测试在装有 Windows XP 的本地开发机器上运行会运行得很好，直到生成大约 950-1100 份报告。该数字各不相同，但一旦停止工作，就无法与该计算机建立连接，直到您等待大约 30 分钟、重新启动计算机或从其他计算机运行它。一旦它停止工作，我们就无法使用其他应用程序（例如 Toad）从该计算机连接到 Oracle 服务器，直到等待时间结束或重新启动计算机。今天我们决定在新机器上尝试一下，以防这只是我们的开发环境的异常，但新机器遇到了完全相同的问题。我们尝试查看 ODBC 连接的设置，每个屏幕都完全相同。我们确信所有安装的软件版本与生产完全匹配。
返回的错误是来自 Crystal 的超时错误：数据库连接器错误。当我们尝试重新启动应用程序时，我们立即遇到错误：
Unhandled Exception: System.Data.Odbc.OdbcException: ERROR [HY000] [Oracle][ODBC][Ora]ORA-12535: TNS:operation timed out
ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
ERROR [HY000] [Oracle][ODBC][Ora]ORA-12535: TNS:operation timed out
我们完全陷入了谷歌的搜索词，但我们认为这与生成的报告数量有关。
任何人都可以帮助解决这个问题吗？
We run a nightly process that generates a large number (~8000) of reports each night using Crystal Reports. This is really just about 14 different reports that get run once for each of our clients. The reports' data source is a windows ODBC connection (via the control panel) and connects to an Oracle 10g instance on our network.
Our current production machine runs Windows 2000 professional and we recently purchased a newer machine to replace it, with the intention of running it under Windows Server 2008. While preparing to make the switch, we noticed that test runs on our local development machines with Windows XP would run just fine until roughly 950-1100 reports had been generated. The number varies, but once it stops working, no connections can be made from the machine until you either wait about 30 minutes, restart the machine, or run it from someone else's machine. Once it stop working, we are unable to connect to the Oracle server using other applications as well, such as Toad, from that machine until waiting out the time or restarting the machine. Today we decided we would just try it out on the new machine in case it was just an anomaly with our development environment, but the new machine ran into the exact same problem. We have tried looking over the settings of the ODBC connection and every screen is exactly the same. We are certain the versions of all software installed match production exactly.
The error returned is a timeout error from Crystal: Database connector error. When we try to restart the application, we are immediately met with the error:
Unhandled Exception: System.Data.Odbc.OdbcException: ERROR [HY000] [Oracle][ODBC][Ora]ORA-12535: TNS:operation timed out
ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed
ERROR [HY000] [Oracle][ODBC][Ora]ORA-12535: TNS:operation timed out
We are completely stuck on search terms for google, but we think it has something to do with the number of reports getting generated.
Can anyone help with this issue?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
ORA-12535 是网络或防火墙问题。期间。
应用程序端没有什么可调查的，有
网络端要调查的一切，例如
- 是否有防火墙在起作用
- 是否有网络地址转换发挥作用
- 防火墙中是否打开了正确的端口
- Oracle 是否使用随机返回端口（默认情况下 Oracle 始终使用 2
tcp/ip 端口，第一个是固定的，并在 tnsnames.ora 中配置，
实际通信发生在随机端口上。如果这是一个问题
在你的网站上你需要解决这个问题）
- 您需要运行 netstat -r 来确定实际使用了哪些端口。
问题。
我的经验是，除了顽固的网络和/或防火墙
管理员介入，问题总能得到解决。我有
多次发布了解决此问题的常用方法，我知道
事实上，这里最新的海报并没有做出任何研究尝试
谷歌的档案。但我不会再发布它们。他们是
很容易找到，并且它们也记录在网络管理员中
手动的。少数人回应询问应该停止
奖励懒惰。如果这会让这个论坛消失，那就这样吧。
西布兰德·巴克
高级 Oracle DBA
***摘自：
http://database.itags.org/oracle/167383/*
ORA-12535 is a network or firewall issue. PERIOD.
There is nothing to investigate at the application side, there is
everything to investigate at the network side like
- is there any firewall in play
- is there any Network Address Translation into play
- have the correct ports been opened in the firewall
- is Oracle using random return ports (by default Oracle always uses 2
tcp/ip ports, the first one fixed, and configured in tnsnames.ora, the
actual communication takes place on a radom port. If that is a problem
at your site you need to fix that)
- You need to run netstat -r to identify which ports are actually used.
problems.
My experience is, that apart from stubborn network and/or firewall
administrators involved, the issue can always be resolved. I have
posted the usual methods to resolve this many times, and I am aware of
the fact most current posters here do not make any attempt to research
the archives at Google. Yet I am not going to post them again. They are
easy to find, and they are also documented in the Net administrators
manual. The small number of people responding to queries should stop
rewarding laziness. If this will make this forum go extinct, so be it.
Sybrand Bakker
Senior Oracle DBA
***Taken from:
http://database.itags.org/oracle/167383/*