ORA-6512

Does OJVM patching fail again with ORA-1403 in 19.31?

Posted on May 15, 2026 by Mike.Dietrich JVM Patch Recommendation 8

Some of you had been trapped by ORA-1403 during patching to Oracle Database 19.30. I blogged about this in February this year, and I had to update the blog post a few times until we collected all the issues. The root cause got fixed and included in Release Update 19.31. But over the past days I received a good number of messages about the issue being there in 19.31 again. So, does OJVM patching fail again with ORA-1403 in 19.31?. Yes, and no.

Does OJVM patching fail again with ORA-1403 in 19.31?

Photo by Towfiqu barbhuiya on Unsplash

Why do some see the error again?

First of …

ORA-1422 and ORA-6512 from SYS.DBMS_STATS in Post Upgrade

Ernst Leber sent me an email today. He hit an error at a customer upgrading to Oracle 19.9.0 on Exadata with AutoUpgrade. ORA-1422 and ORA-6512 from SYS.DBMS_STATS in Post Upgrade were signaled – and he better flashed back to the Guaranteed Restore Point. He found even a MOS note but still had questions. So time to blog about it in case you hit this error sequence as well.