A new version of the preupgrade.jar January 2018 (Build 11) is available now.
Please download it from MOS Note:884522.1.:
Please always download the most recent version as this one is much newer with a lot of improvements compared to the version you get with the default installation. Major changes since the first drop are:
- Added load only capabilities.
- Improved the interaction with OS
- Added more obsolete/deprecated parameters
- Improved IPC calls on Windows
- Added functionality for aud$unified table partitions.
- Added preupgrade and postupgrade automatic fixups
- Check for JAVAVM mitigation patch
- Added parameters checking when a dynamic parameter has been changed at spfile only
- Update parameter such as memory limits.
- Adds UTF-8 characterset 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.
- Adds a check to validate APEX version.
- Modifies check tempts_notempfile, it should also consider tablespace groups
- Changes severity of new_time_zones_exist to warning
- Adds pga_aggregate_limit check
- Adds support for very large temporary tablespace groups (new in Build 11)
ist das auch in Windows verfügbar und hilft bei 220.127.116.11 auf 18.104.22.168?
fuer Upgrades nach 22.214.171.124 gibt es ueber MOS 884522.1 das preupgrd.sql – das preupgrade.jar prueft spezielle Dinge fuer 12.2 ab. In der Regel machst Du wahrscheinlich nicht so viel falsch, aber offiziell musst Du bitte das preupgrd.sql (mit utluppkg.sql) verweden (ist im zip mit drin).
kann man das jar auch unter Windows zur Migation von 126.96.36.199 nach 188.8.131.52 hernehmen?
Ist der DBUA von der Version Oktober Vidos besser oder unverändert?
am DBUA selbst gibt es keine Unterschiede – mein DBUA hat (nach Einspielen des Januar 2018 BPs) immer noch den Zeitstempel “June 15”. Er setzt aber auf dem preupgrade.jar auf. Fixes, die da drin sind, bekommt der DBUA also automatisch auch.
Why can’t you guys go in English? so that we can understand your questions/answers in comments section very clearly?
Simply because the question was asked in German 😉
But you are right.
Can I use the same script on Windows for an upgrade to 184.108.40.206 as well?
And I answered:
– the preupgrade.jar works on Windows as well
– but for an upgrade to Oracle 220.127.116.11 you should use the preupgrd.sql including the utluppkg.sql as this is the designated upgrade script for 12.1 upgrades.
Most likely preupgrade.jar won’t harm but I’d still use the script meant for the destination release.
And it can be downloaded from within the same MOS Note.
Any command to know what the build version of the pre-upgrade tool that is in $ORACLE_HOME/rdbms/admin
I realized the disappearance of the version number as well a few weeks ago. I did ask the team to include it again in the next downloadable version. Sorry for the inconvenience but as far as I see there’s no way to tell the version used right now from the tool itself.
(1) The version/build is mentioned in the preupgrade_fixups.sql and postupgrade_fixups.sql
(2) I filed a bug 27460985 – my upgrade team mates will fix it and include it into the preupgrade.log and the screen output when you run preupgrade.jar with TERMINAL option.
quick update: Team fixed it, the next downloadable version will include it into the log output and the log file.
Cheers and thanks for your input,
Thank you Mike I see the following in the log.
Report generated by Oracle Database Pre-Upgrade Information Tool Version
18.104.22.168.0 Build: 12.
Can I replace the files in $ORACLE_HOME/rdbms/admin with files that I download from MOS, so that I can avoid telling folks to download it from MOS.
Of course you can 🙂