I was emailed an interesting error recently at work that I've not seen previously. It was to do with the DBMS_PICKLER package being missing when using JDBC drivers from a WebLogic application. In this case we were upgrading from an earlier version of WebLogic to the latest (12.2) and that's where we started to see these errors.
This is what the stacktrace looked like...
That indicated that this had something to do with Array bindings, which I knew were used quite heavily in this case. However that wasn't the real issue. The earlier version of WebLogic we had didn't use JDBC drivers that made use of DBMS_PICKLER (11gR2 onwards), but WebLogic 12.2 has JDBC drivers that certainly do make use of it.
What the package does it no really relevant, it's an internal package that's to do with array and custom type binding. What is relevant is that it's owned by SYS. And JDBC appears to call the procedure as if it was in the SYS schema.
The trouble was...we had a table with the name 'SYS' that was inside the schema that the application was accessing. This table was created as part of some patching bug, but wasn't rolled back, so once we moved to new JDBC drivers, it all broke.
The solution was to rename that table to something other than SYS and everything went back to normal!
Hope you found this post useful...
...so please read on! I love writing articles that provide beneficial information,
tips and examples to my readers. All information on my blog is provided free of
charge and I encourage you to share it as you wish. There is a small favour I ask in return however -
engage in comments below, provide feedback, and if you see mistakes let me know.
If you want to show additional support and help me pay for web hosting and
domain name registration,
donations, no matter how small, are always welcome!
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...