从 Oracle DB 检索数据时，Asp.net Web 应用程序崩溃
我在windows server 2003上有一个asp.net网站。该应用程序连接到oracle 10g R2数据库，数据层由subsonic生成。 数据库和应用程序分别位于不同的服务器上。
在开发机器上应用程序正常运行。但是在生产服务器上，与数据库通信的页面中出现服务器错误。
问题是错误不会一直发生，它时断时续，我无法调试它，因为它不会在本地发生。如果我刷新页面。一切正常。但再次刷新后，错误可能会再次显示。 我们开始收到 Oracle 客户端错误，例如：
- Transaction has completed; it is no longer usable
- Invalid operation. The connection is closed
- Unable to load DLL 'oramts.dll'
- Attempted to read or write protected memory at
System.Data.Common.UnsafeNativeMethods.OraMTSJoinTxn
我认为该错误是由于过载或性能造成的。
有人对上述问题有任何想法吗？
I have an asp.net website on a windows server 2003. The application connects to an oracle 10g R2 Database and the data layer is generated by subsonic.
The database and the application are on separate servers each.
On development machine the application runs normally. But On production server, there is a server error that occurs in pages that communicates with the database
The problem is that the error does not happen all the time, it is on and off and i can not debug it since it does not happen locally. if i refresh the page. everything works fine. but with another refresh the error might show again.
And we started getting oracle client errors such as:
- Transaction has completed; it is no longer usable
- Invalid operation. The connection is closed
- Unable to load DLL 'oramts.dll'
- Attempted to read or write protected memory at
System.Data.Common.UnsafeNativeMethods.OraMTSJoinTxn
I think the error is due to overload or performance.
Does anyone have an idea about the above problem?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我们通过将应用程序和数据库移动到另一台机器来设法解决这个问题。
我最有可能认为，这是服务器性能问题，或者应用程序和数据库之间的网络中断（每个都位于单独的服务器计算机上）。
我们消除了代码错误情况，因为如果是这样，应用程序将不会随时运行，但页面会时不时地加载，或者如果您继续按 f5。
我们不断收到 Oracle 客户端错误。
We managed to solve this problem, by moving the application and the database, each to another machine.
I most probably think, it was a server performance issue, or network disrupt between the application and the database (each was on a separate server machine).
We eliminated the code error case, since if it was so, the application wouldn't run at anytime but the pages were loading every now and then, or if you keep hitting f5.
And we kept getting oracle client errors.