报告错误：ORA-0000：正常，成功完成 In Oracle APEX Tabular Form
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/24698413/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Report error: ORA-0000: normal, successful completion In Oracle APEX Tabular Form
提问by Ashwin
Im getting Report error: ORA-0000: normal, successful completion Oracle Apexin a Tabular Form Report.
我收到报告错误：ORA-0000：在表格报告中正常、成功完成 Oracle Apex。
I cant able to proceed with any operations in the Tabular Forms such as Add Rows and Delete Checked Operation.
我无法在表格形式中进行任何操作，例如添加行和删除选中的操作。
Is this an error or some kind of notification exception?
这是错误还是某种通知异常？
Few columns in this tabular form is done through cascading from another column in the same tabular form using Application Process. Will this be a reason for this error?
此表格形式中的几列是通过使用 Application Process 从同一表格形式中的另一列级联完成的。这会是这个错误的原因吗？
I checked many forums, but I couldnt get a proper solution to solve this. Kindly help me out in this. Thanks in Advance!
我查了很多论坛，但我找不到合适的解决方案来解决这个问题。请帮我解决这个问题。提前致谢！
回答by Thobani Zuma
This actually means there is no error i.e An operation has completed normally, having met no exceptions.
这实际上意味着没有错误，即操作已正常完成，没有遇到任何异常。
Action: No action required.
行动：不需要行动。
回答by elfekz
The same problem we faced, there is a firewall between db server and application server, but later we noticed that. When we listen to tcp network we notice FIN ACK flags. This flag closes the connection for a long time without request, I mean if it was idle for a long time. However, in the db server side, there was no check to see if there was a connection. The situation was corrected by restarting again. We continued by removing the firewall between db and application server.
我们遇到了同样的问题，db server 和 application server 之间有防火墙，但后来我们注意到了。当我们监听 tcp 网络时，我们会注意到 FIN ACK 标志。这个标志会在没有请求的情况下长时间关闭连接，我的意思是它是否长时间空闲。但是在db server端，并没有检查是否有连接。重新启动后，情况得到纠正。我们继续移除数据库和应用服务器之间的防火墙。
