On a regular basis the Database Upgrade Team releases new and improved versions of the preupgrade tools via a MyOracle Support note. And it’s time again: the September 2017 releases of preupgrade.jar and preupgrd.sql are available for download.
September 2017 releases of preupgrade.jar and preupgrd.sql are available
Please ALWAYS download the most recent versions of preupgrade.jar for upgrades to Oracle Database 12.2 and preupgrd.sql (including utluppkg.sql) for Oracle Database 12.1.0.2 upgrade from MOS Note: 884522.1. The version you’ll download is way newer than the version you’ll get with the base installation.
preupgrade.jar – Rel.7 – September 2017
Please find the most recent version of preupgrade.jar in this MOS note. Furthermore see the list of improvements and changes:
preupgrd.sql – Rel.17 – September 2017
In case you plan to upgrade to Oracle Database 12.1.0.2 please see MOS Note 884522.1 for the download link of preupgrd.sql including the packages in utluppkg.sql. Furthermore find a description of the improvements:
You can find an example on how to execute preupgrade.jar in an Oracle Multitenant environment here.
–Mike (on behalf of the Oracle Database Upgrade Development Team)
Note: Even preupgrade.jar from preupgrade_12201_cbuild_009_lf.zip is not checking for PGA_AGGREGATE_LIMIT >= 2GB.
One of my upgrades from 12.1 to 12.2 failed due to the fact that PGA_AGGREGATE_LIMIT was set to a lower value.
Andreas,
when I try to set PGA_AGGREGATE_LIMIT to a value below 2G on 12.1.0.2 I receive the following error:
SQL> alter system set pga_aggregate_limit=1G;
alter system set pga_aggregate_limit=1G
*
ERROR at line 1:
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-00093: pga_aggregate_limit must be between 2048M and 100000G
But I have (always) the newest BP, in this case the October 2017 Bundle Patch.
Which patch level did your database have, and what exact errors were you seeing.
Would be great if you could pass me this on as I can do further investigation then.
Cheers
Mike
Ok, workaround to this limitation:
SQL> alter system set pga_aggregate_limit=1G scope=spfile;
System altered.
SQL> startup force
ORACLE instance started.
Total System Global Area 1048576000 bytes
Fixed Size 2932336 bytes
Variable Size 369099152 bytes
Database Buffers 671088640 bytes
Redo Buffers 5455872 bytes
Database mounted.
Database opened.
SQL> show parameter pga
NAME TYPE VALUE
———————————— ———– ——————————
pga_aggregate_limit big integer 1G
pga_aggregate_target big integer 1G
Set to 1G now.
Executing preupgrade.jar:
And you are correct – no warning gets displayed.
Let me investigate this further.
Cheers
Mike (and sorry for the inconvenience!!!)
Hi Mike
Release 10 from November 2017 has the pga_aggregate_limit check included now:
…
+ Update NUMERIC INITIALIZATION PARAMETERS to meet estimated minimums.
Parameter 12.2.0.1.0 minimum
——— ——————
pga_aggregate_limit 2147483648
…
br
Andreas
Thanks Andreas – I had in my mind that Cindy built a fix for it into the preupgrade.jar.
Thanks for the update and confirming 🙂
Cheers and have a great weekend,
Mike
I couldn’t find instructions on how to run the pre-upgrade script, :884522.1. It only show how to download.
Doc ID 884522.1
preupgrade_12201_cbuild_014_lf.zip
MOS Note:884522.1
How to Download and Run Oracle’s Database Pre-Upgrade Utility preupgrd.sql – Build 12
True – and thanks for this hint. I’ll ask my colleague to add the appropriate links to the documentation of each tool.
https://docs.oracle.com/en/database/oracle/oracle-database/12.2/upgrd/using-preupgrade-information-tool-for-oracle-database.html#GUID-C0219AF1-AD43-4097-B358-E53E48958647
Cheers,
Mike