Oracle：OALL8 处于不一致状态

发布于 2024-07-15 22:02:51 字数 1019 浏览 5 评论 0原文

作为升级 JRun 的一部分，我们将从 1.4 JVM 迁移到 1.6 JVM。现在我收到一个非常奇怪的 Oracle 数据库错误：“OALL8 处于不一致状态”。我已经确定了插入根本不使用绑定变量的查询的问题 - 所有内联参数。如果我在没有任何绑定变量的情况下运行查询，则会收到上述错误。一旦我用绑定变量替换其中一个硬编码值 - 一切都会正常工作，不会出现错误。

另一个奇怪的地方是，执行查询后，它实际上被提交到数据库。我可以从另一个会话进行连接并查看插入的行。我尝试将查询包装在事务中，它似乎成功了，因为在没有显式事务的情况下，查询的行为没有变化。

以下是相关详细信息：

Java 版本：1.6.0_12-b04
虚拟机版本：11.2-b01（热点服务器）
Oracle 服务器：10.2.0.4
Oracle 客户端：11.1.0.7.0 到 ojdbc6.jar

更新： 我正在使用 cfqueryparam - 它们在 Oracle 世界中称为绑定变量。虽然这确实解决了眼前的问题，但我们有一个相当大的遗留代码库，作为从 CF7 升级到 CF8 的一部分，我们实际上无法遍历所有代码库来更新查询。

尽管我已经确定了一种失败的特定情况（并将其封装在 mxunit 测试中），但这并不意味着没有其他领域可能会出现问题。我真的很想有一个解决方案来消除 OALL8 错误，而不是围绕它进行编码。

更新 2： 与我们的 DBA 核实后，他将一个名为 CURSOR_SHARING 的参数设置为 SIMILAR。 Oracle 默认值是 EXACT。发生的情况是，当 ColdFusion 将查询交给执行时，Oracle 将所有文字值转换为绑定变量，这似乎使 ColdFusion 感到困惑。将设置转回 EXACT 可以使文字查询正常工作。

更新 3：Oracle 最终向我们发布了 JDBC 的带外补丁。它被识别为 JDBC 错误。最新的驱动程序最终更新时应包含它。如果您有支持，您还可以通过他们的 TAR 系统请求补丁。

原文

As part of upgrading JRun, we are moving from a 1.4 JVM to a 1.6 JVM. Now I am getting a really strange oracle db error: "OALL8 is in an inconsistent state". I have pinned down the problem to insert queries that do not use bind variables at all - all inline parameters. If I run the query without any bind variables, I get the above error. As soon as I replace one of the hard coded values with a bind variable - everything works without error.

The other strange bit is that after executing the query, it is in fact committed to the database. I can connect from another session and see the inserted row. I have tried wrapping the query in a transaction and it seems to succeed as the behavior is unchanged from the query without an explicit transaction.

Here are the relevant details:

Java Version: 1.6.0_12-b04
Virtual Machine Version: 11.2-b01 (HotSpot Server)
Oracle Server: 10.2.0.4
Oracle Client: 11.1.0.7.0 through ojdbc6.jar

Update: I am using cfqueryparam - they are called bind variables in the oracle world. While that does solve the immediate problem, we have a rather large legacy code base that we can't realistically go through all of to update the queries as part of upgrading from CF7 to CF8.

Even though I have pinned down one specific situation that fails (and encapsulated it in an mxunit test) - that doesn't mean there aren't other areas where this may be an issue. I would really like to have a solution in place that removes the OALL8 error rather than coding around it.

Update 2: After checking with our DBA he had set a parameter called CURSOR_SHARING to SIMILAR. The Oracle default is EXACT. What is happening is when ColdFusion hands the query off to be executed, Oracle is turning all the literal values to bind variables and that appears to be confusing ColdFusion. Turning the setting back to EXACT allows the literal queries to work just fine.

Update 3: Oracle finally issued us an out-of-band patch for JDBC. It was identified as a JDBC error. The latest drivers should include it when they are finally updated. If you have support you can also request the patch through their TAR system.

分享到QQ

分享到微博