Most of you may not care about the checks our Pre Upgrade Check tool preupgrade.jar does. But some may. Especially in cases where you plan to run a command line upgrade unattended via a script. Therefore this List of PREUPGRADE checks executed by preupgrade.jar may help you.
List of PREUPGRADE checks executed by preupgrade.jar
As a result of a joint initiative between our Upgrade Development team and the Support group dealing with upgrade-related SRs we released this MOS Note:
- MOS Note: 2380601.1
Database Preupgrade tool check list
Purpose of the new MOS note is to give you a complete list of checks we execute when you run preupgrade.jar (see MOS Note: 884522.1). The list tells you in detail what we are checking – and if a check can be fixed automatically or not.
–Mike
Hi Mike, it is nice Oracle note.
Is any way to check what exactly is executed in pre/postupgrade_fixups.sql scripts?
For example: fixup_result := dbms_preup.run_fixup(‘underscore_events’); does not look safe to execute outside change window but it probably just generate output : ‘Manual fixup recommended.” – (is it true for all checks with ‘Manual’ fixup value ?)
Hi Leszek,
both scripts are safe to be executed – for the manual fixups you are required to take action. A typical issue with 11g source upgrades is the Audit table in SYSTEM – it has to be moved to SYS with olspreupgrade.sql. But we won’t execute this for you as it will move audit records around and create a temp structure. Therefore, preupgrade_fixups.sql does not do harm to your database – and will log such missing things (OLS_SYS_MOVE — not passed).
Cheers,
Mike
That is a very useful document. Thanks a lot for compiling it and making it available. It will for sure make our automation easier.
Welcome, Daniel 🙂
Cheers,
Mike
Mike,
As I started the database in upgrade mode, I got an error: It was because the init parameter LOG_CHECKPOINTS_TO_ALERT was set to NO instead of TRUE or FALSE. Not sure when this was done or why 11g never complained about it. I was hoping that preupgrade.jar would catch such init parameters.
Thanks,
Arun
Arun,
I believe only a manual edit could have lead to this strange parameter value. I tried to change it in my 11.2.0.4 database – the default is always FALSE since Oracle 11g:
SQL> alter system set log_checkpoints_to_alert=’NO’;
alter system set log_checkpoints_to_alert=’NO’
*
ERROR at line 1:
ORA-00922: missing or invalid option
SQL> alter system set log_checkpoints_to_alert=NO;
alter system set log_checkpoints_to_alert=NO
*
ERROR at line 1:
ORA-00922: missing or invalid option
SQL> alter system set log_checkpoints_to_alert=’NO’ scope=spfile;
alter system set log_checkpoints_to_alert=’NO’ scope=spfile
*
ERROR at line 1:
ORA-00922: missing or invalid option
SQL> alter system set log_checkpoints_to_alert=NO scope=spfile;
alter system set log_checkpoints_to_alert=NO scope=spfile
*
ERROR at line 1:
ORA-00922: missing or invalid option
Cheers,
Mike