Are you tailing the alert log to make sure you havent run out of archive
log space or something along those lines?
On Mon, Nov 5, 2018 at 11:11 AM Tim Gorman <tim.evdbt@xxxxxxxxx> wrote:
3 hours is an unusually long time, but if you're testing in an
environment with slow I/O, it doesn't sound too odd. The majority of
time used by an upgrade is a single-threaded stream of DDL and DML
statements run from SQL*Plus; I think the only thing that runs in
parallel are the object recompilations at the end.
Are you able to gather an AWR report? Certainly you can start a 10046
extended trace on the upgrade session?
On 11/5/18 08:58, Jeff Chirco wrote:
I am working on upgrading a database from 11.2.0.4 to 12.2.0.1.
Single instance non CDB. The upgrade is taking 2 hours and 50
minutes. I am running the command line version of the upgrade and
using parallel. Any tips to make this go faster? I already have APEX
18.1 installed however I am noticing it is becoming invalid during the
upgrade and I have to reinstall it afterwards.
Thanks
--
//www.freelists.org/webpage/oracle-l
