I’m tempted to copy and paste my blog post about DBMS_OPTIM_BUNDLE from February 2019, and exchange only 126.96.36.199 with 19c. But in this case the root cause is different. So this blog post is meant for Oracle 19.3.0 to be precise – in case you miss
DBMS_OPTIM_BUNDLE … again … ?!?
Information about DBMS_OPTIM_BUNDLE
You will find a lot of information about
DBMS_OPTIM_BUNDLE, what it does, since which release it exists and much more in these blog posts:
- In case you are missing DBMS_OPTIM_BUNDLE (Feb 11, 2019)
- DBMS_OPTIM_BUNDLE Package in Oracle 12.2 and 18c (Mar 8, 2019)
- DBMS_OPTIM_BUNDLE – only available in Oracle 188.8.131.52 … or not? (Jul 25, 2017)
- Package differences between Oracle 184.108.40.206 and Oracle 220.127.116.11 (Jun 23, 2015)
- Bug 27009164 – support for dbms_optim_bundle for CDBs
- Bug 29259128 – REGRESSION: PACKAGE SYS.DBMS_OPTIM_BUNDLE MISSING FROM RU OCT. 2018 (unpublished bug – hence no link added)
Where’s DBMS_OPTIM_BUNDLE in Oracle 19.3.0?
Several colleagues from ACS Support and Consulting called or mailed me the past weeks with a question: Where is
DBMS_OPTIM_BUNDLE in Oracle 19.3.0? And all of them were right: It is not there.
To make things a bit more complicated, the well known workaround did not work either. In previous release you could create the package with:
But these scripts don’t exist in Oracle 19c.
What has happened?
Actually the creation of
DBMS_OPTIM_BUNDLE via these two scripts was just a workaround. As the package has to exist since Oracle 18.104.22.168, the only file where it must be created within is
catproc.sql. I won’t explain why it didn’t make it into
catproc. But for Oracle 19c the code got changed. And once the code was adjusted, a problem with
PRAGMA got detected. This led to the unfortunate situation that the package is not in 19.3.0. And of course, the scripts don’t exist either as they are not meant to be there anymore.
But … this is not a real issue as there are no optimizer fixes in 19.3.0 to enable or disable with
The package will appear again in 19.4.0 – and will be in
catproc.sql for databases created since 19.4.0.