Oracle Database 19c is available for Exadata on-prem for quite a few weeks now. But even if you didn’t download it yet, you may want to use the new 19.2 preupgrade.jar tool to check and examine your database. For this purpose you can find the Oracle 19c preupgrade.jar and preupgrade checks available and documented on MOS.
Oracle 19c preupgrade.jar and preupgrade checks
I received several emails already from customers asking whether they can get the most recent Oracle 19c preupgrade tool without downloading the entire 19c software stack. And thanks to my team mates, the tool is available now in the 19.2 version from March 2019:
And in addition, the Upgrade Team documented the new preupgrade checks as well in:
This doesn’t mean you’ll have to upgrade now. But you can check your database already if you want.
–Mike
Pls fix disk discovery in gridsetup.sh
As manual instructions in the no udev case of
asmcmd. afd_label dev –init
/gridsetul.sh
fails to show any disks on asm page of the install.
Kinda reminds me o11.2.0.1 didnt find drives on a virgin install as well.
Also very slow to start like you could have lunch before it asks for 1st prompt.
Will try it in 18c.
Please log an SR and have Support file a bug.
GRID ==> Clusterware and RAC groups at Oracle.
You can also pass me the SR number and I’ll happily forward it to the RAC team for an extra check.
Cheers,
Mike
I am reading document Database Preupgrade tool check list. (Doc ID 2380601.1). I came across REPCAT_SETUP section that says Advanced Replication is no longer supported beyond 12.2. It also mentions about removing all MV sites. Does this mean that Materialized Views are not supported anymore as of 12.2?
We use Materialized Views under 11.2.0.4 and we need to upgrade to 19c. Are we affected?
Thank you,
Michel
Michel,
the message says “Advanced Replication is not supported beyond 12.2. All related objects will be removed during the upgrade process. It is advised to remove all Master sites first (if any), for more information and steps to remove a Master site look at section 7-31 of the Oracle Database Advanced Replication Management API Reference. It is advised to remove all MV sites (if any), for more information and steps to remove a MV site look at sections 8-1 to 8-10 of the Oracle Database Advanced Replication Management API Reference.”
It refers to MV sites in terms of part of a Advanced Replication setup.
Of course, MVs by itself are still fully supported.
Cheers,
Mike
Greetings Mike,
I am Sreedhar Bobbadi from WellsFargo. Does the DBAUTO upgrade too run the preupgrade information tool ?
if yes then I need to upgrade the pre-upgrade information tool in target Oracle home first. In my case its 19c.
Hi,
it has preupgrade.jar embedded – you don’t need to download it in addition.
Cheers,
Mike
Hi Mike,
Did you run into slow upgrade from 12.1 to 19c.
atcon::set_log_file_base_path: catcon: See [/u01/app/rdbms/product/19400LDB1/cfgtoollogs/txa01c2_rdu/upgrade20191220082546/catupgrdlcproto_*.lst] files for spool files, if any
Number of Cpus = 96
Database Name = txa01c2_rdu
DataBase Version = 19.0.0.0.0
LCPROTO Open Mode = [MIGRATE]
Generated PDB Inclusion:[LCPROTO]
CDB$ROOT Open Mode = [OPEN]
Components in [LCPROTO]
Installed [APS CATALOG CATJAVA CATPROC CONTEXT DV JAVAVM OLS ORDIM OWM RAC SDO XDB XML XOQ]
Not Installed [APEX EM MGW ODM WK]
——————————————————
Phases [0-107] Start Time:[2019_12_20 08:27:03]
Container Lists Inclusion:[LCPROTO] Exclusion:[NONE]
——————————————————
*********** Executing Change Scripts ***********
Serial Phase #:0 [LCPROTO] Files:1 Time: 119s
*************** Catalog Core SQL ***************
Serial Phase #:1 [LCPROTO] Files:5 Time: 1772s
Restart Phase #:2 [LCPROTO] Files:1 Time: 1s
*********** Catalog Tables and Views ***********
Parallel Phase #:3 [LCPROTO] Files:19 Time: 112s
Restart Phase #:4 [LCPROTO] Files:1 Time: 1s
************* Catalog Final Scripts ************
Serial Phase #:5 [LCPROTO] Files:7 Time: 579s
***************** Catproc Start ****************
Serial Phase #:6 [LCPROTO] Files:1
Thanks,
Deepankur
Hi Deepankur,
this is very unusual – and none of the phases should take so long.
Please check the logs why for instance Phase1 has taken half an hour.
Then open an SR, upload the logs and the alert.log and check with Oracle Support.
Cheers,
Mike
Check the Options installed.
Some of the Default GUI Installers add unnecessary options that can be checked out prior to installation.
These will delay the upgrade significantly.
SELECT * FROM DBA_REGISTRY;
SELECT * FROM v$OPTION;
MOS DOC ID 1317265.1
col name for a70
set lines 2000
select name,version,detected_usages,total_samples,last_sample_date from dba_feature_usage_statistics
order by detected_usages desc
/