There’s a new and improved version of the preupgrade.jar (build 5 – May 2017) available for download from MyOracle Support:
The same note will get you access also to the most recent builds of preupgrd.sql for upgrades to Oracle Database 12.1 and utlu112i.sql for the unlikely event you’ll have to upgrade a database to Oracle 11.2.0.4.
Please always exchange the version getting installed by default with the version we offer via MOS Note:884522.1 as the downloadable version is usually much newer and improved over the one getting deployed with the installation image.
MOS Note:884522.1 – Download always the newest preupgrade.jar
The most important changes over the previous version are:
- Adds UTF-8 character set capabilities
- Adds a check to see if CONCURRENT STATISTICS are set when RESOURCE MANAGER IS OFF
- Adds a block of code which will be run if the DEPEND_USR_TABLES check is run after the database has been upgraded
- A new autofixup function is also added, which will automatically be run by the postupgrade_fixups.sql script
Find an example on how to use preupgrade.jar here:
–Mike
Hi
I thought I would get a good start and let the preupgrade script double check my manual checks before the upgrade. Followed the https://docs.oracle.com/database/122/UPGRD/using-preupgrade-information-tool-for-oracle-database.htm#UPGRD-GUID-C0219AF1-AD43-4097-B358-E53E48958647.
Brilliant I thought. Double checked environment.
The output was a bit of a surprise.
File name too long
I have shortened the PATH , put the java location , first and last in the path. The Oracle path is 1 character longer than the standard most people user (/u01/app/oracle/product1/12.1.0). Any ideas?
Dave,
where and when did you get “File name too long”. Can you please copy/paste the output of your xterm?
Have you used the most recent preupgrade.jar package from MOS Note:884522.1? If not, please give it a try and see if the error happens again.
You can also drop me an email to “firstname.lastname@oracle.com” if you prefer that.
Cheers
Mike