cat phase.log

 

Argument list for [/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catctl.pl]
For Oracle internal use only    A = 0
Run in                          c = 0
Do not run in                   C = 0
Input Directory                 d = /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin
Echo OFF                        e = 1
Simulate                        E = 0
Forced cleanup                  F = 0
Log Id                          i = 0
Child Process                   I = 0
Log Dir                         l = 0
Priority List Name              L = 0
Upgrade Mode active             M = 0
SQL Process Count               n = 0
SQL PDB Process Count           N = 0
Open Mode Normal                o = 0
Start Phase                     p = 0
End Phase                       P = 0
Reverse Order                   r = 0
AutoUpgrade Resume              R = 0
Script                          s = 0
Serial Run                      S = 0
RO User Tablespaces             T = 0
Display Phases                  y = 1
Debug catcon.pm                 z = 0
Debug catctl.pl                 Z = 0

catctl.pl VERSION: [19.0.0.0.0]
STATUS: [Production]
BUILD: [RDBMS_19.3.0.0.0DBRU_LINUX.X64_190417]


/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/orahome = [/u01/app/oracle/product/19.0.0/dbhome_1]
/u01/app/oracle/product/19.0.0/dbhome_1/bin/orabasehome = [/u01/app/oracle/product/19.0.0/dbhome_1]
catctlGetOraBaseLogDir = [/u01/app/oracle/product/19.0.0/dbhome_1]

Analyzing file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catupgrd.sql

Log file directory = [/tmp/cfgtoollogs/upgrade20210309025244]

27 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catupgrd.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catalog.sql
37 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catalog.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catproc.sql
35 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catproc.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catptabs.sql
68 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catptabs.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catpdbms.sql
241 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catpdbms.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catpdeps.sql
86 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catpdeps.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catpprvt.sql
305 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catpprvt.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catpexec.sql
32 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catpexec.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/cmpupgrd.sql
21 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/cmpupgrd.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbupgrd.sql
8 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbupgrd.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbload.sql
90 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbload.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/ord/im/admin/imupgrd.sql
10 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/ord/im/admin/imupgrd.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/md/admin/sdoupgrd.sql
5 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/md/admin/sdoupgrd.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmd.sql
8 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmd.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdloc.sql
13 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdloc.sql
Next path: /u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdsdo.sql
13 scripts found in file /u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdsdo.sql

[phase 0] type is 1 with 1 Files

@catupstr.sql

[phase 1] type is 1 with 5 Files

@cdstrt.sql @cdfixed.sql @catcdbviews.sql @catblock.sql 
@cdcore.sql

[phase 2] type is 1 with 1 Files

ora_restart.sql

[phase 3] type is 2 with 19 Files

@cdplsql.sql @cdsqlddl.sql @cdmanage.sql @cdtxnspc.sql 
@cdenv.sql @cdrac.sql @cdsec.sql @cdobj.sql 
@cdjava.sql @cdpart.sql @cdrep.sql @cdaw.sql 
@cdsummgt.sql @cdtools.sql @cdexttab.sql @cddm.sql 
@cdclst.sql @cdhcs.sql @cdadr.sql

[phase 4] type is 1 with 1 Files

ora_restart.sql

[phase 5] type is 1 with 7 Files

@catptt.sql @catldr.sql @cdoptim.sql @catsum.sql 
@catexp.sql @cddst.sql @cdend.sql

[phase 6] type is 1 with 1 Files

@catpstrt.sql

[phase 7] type is 1 with 2 Files

@catptyps.sql @catpgrants.sql

[phase 8] type is 1 with 1 Files

ora_restart.sql

[phase 9] type is 2 with 67 Files

@catnodpobs.sql @catbac.sql @prvtrctv.plb @catactx.sql 
@prvtuttv.plb @catsvrmg.sql @prvtlsis.plb @prvtlsss.plb 
@cattrans.sql @catrule.sql @catpitr.sql @catdip.sql 
@catrls.sql @catar.sql @catfga.sql @catamgt.sql 
@catidxu.sql @cattsm.sql @catchnf.sql @catodm.sql 
@catkppls.sql @catsscr.sql @catqueue.sql @cathae.sql 
@catadvtb.sql @cataitb.sql @catsch.sql @catol.sql 
@catdpb.sql @catcrc.sql @dbmscr.sql @dbmsutil.sql 
@catdbfus.sql @catalrt.sql @catatsk.sql @catmntr.sql 
@catsqlt.sql @catumftv.sql @catsmbvw.sql @catwrrtb.sql 
@catsumat.sql @catlmnr.sql @catdef.sql @catadrvw.sql 
@catrepv.sql @catpexe.sql @cattlog.sql @catcapi.sql 
@catpspi.sql @catts.sql @catnacl.sql @catredact.sql 
@catproftab.sql @catpstdy.sql @catratmask.sql @catqitab.sql 
@catappcont.sql @catjsonv.sql @catrsa.sql @catappcontainer.sql 
@cathmgr.sql @catmvrs.sql @cataclsrv.sql @catdbl.sql 
@catgdtab.sql @catimfstab.sql @catimime.sql

[phase 10] type is 1 with 1 Files

ora_restart.sql

[phase 11] type is 1 with 1 Files

@catpspec.sql

[phase 12] type is 1 with 1 Files

ora_restart.sql

[phase 13] type is 2 with 94 Files

@utlinad.sql @utlsmtp.sql @utlurl.sql @utlenc.sql 
@utlgdk.sql @utlcstk.sql @utlcomp.sql @utli18n.sql 
@utllms.sql @dbmsplsw.sql @utlnla.sql @dbmspdb.sql 
@dbmsappcon.sql @dbmstrns.sql @dbmsrwid.sql @dbmspclx.sql 
@prvthpclxi.plb @dbmserlg.sql @dbmsspu.sql @dbmsapin.sql 
@dbmssyer.sql @dbmspipe.sql @dbmsalrt.sql @dbmsdesc.sql 
@prvthpexpi.plb @dbmspexp.sql @dbmsjob.sql @prvtstataggs.plb 
@prvtstatadv.plb @dbmsstts.sql @dbmsddl.sql @dbmsedu.sql 
@dbmspp.sql @prvthddl.plb @prvthsye.plb @prvtzhlp.plb 
@dbmsodbo.sql @dbmshier.sql @dbmsidxu.sql @prvthidx.plb 
@dbmspsp.sql @dbmstran.sql @dbmsxa.sql @dbmstxfm.sql 
@dbmsread.sql @prvtreut.plb @dbmspb.sql @dbmspbt.sql 
@dbmsplts.sql @dbmspitr.sql @utlrefld.sql @utlcoll.plb 
@dbmstrst.sql @dbmsrlsa.sql @dbmsrpr.sql @dbmsobtk.sql 
@dbmslm.sql @dbmslmd.sql @prvtlmes.plb @utlcxml.sql 
@dbmsfga.sql @dbmsamgt.sql @dbmstypu.sql @dbmsres.sql 
@dbmstxin.sql @dbmsdrs.sql @dbmsdg.sql @dbmssum.sql 
@dbmshord.sql @dbmsxfr.sql @dbmsmap.sql @dbmsfi.sql 
@dbmsdbv.sql @dbmstcv.sql @dbmscoll.sql @dbmspbp.sql 
@dbmshpro.sql @dbmscov.sql @dbmssrv.sql @dbmschnf.sql 
@dbmsxpln.sql @prvsxplni.plb @utlmatch.sql @dbmsdbvn.sql 
@dbmspool.sql @dbmsrcad.sql @prvthcrc.plb @prvtkpps.plb 
@dbmsaq.plb @dbmsaqad.sql @dbmsaq8x.plb @dbmsaqem.plb 
@prvtaqxi.plb @dbmsslrt.sql

[phase 14] type is 1 with 1 Files

ora_restart.sql

[phase 15] type is 2 with 120 Files

@dbmsmntr.sql @dbmshm.sql @catsqltk.sql @dbmsir.sql 
@prvtsss.plb @dbmsocm.sql @dbmslobu.sql @dbmsmp.sql 
@dbmsaddm.sql @prvttxfs.plb @dbmsrmin.plb @dbmsrmad.sql 
@dbmsrmpr.sql @dbmsrmpe.plb @dbmsrmge.plb @dbmsrmpa.plb 
@prvtrmie.plb @prvthjob.plb @prvtdputh.plb @dbmsmeta.sql 
@dbmsmetb.sql @dbmsmetd.sql @dbmsmet2.sql @dbmsdp.sql 
@dbmsdpmt.sql @prvthpd.plb @prvthpdi.plb @prvthpvi.plb 
@dbmsbsdesc.sql @prvtdtde.plb @prvtcia.plb @prvtsum.plb 
@prvtjdbs.plb @dbmsslxp.sql @prvssmgu.plb @dbmsmb.sql 
@dbmsawr.sql @dbmsumf.sql @prvsemxi.plb @prvsemx_admin.plb 
@prvsemx_dbhome.plb @prvsemx_memory.plb @prvsemx_perf.plb @prvsemx_cell.plb 
@dbmsperf.sql @prvsemx_rsrcmgr.plb @prvsemx_sql.plb @prvsrept.plb 
@prvsrepr.plb @prvshdm.plb @prvsrtaddm.plb @prvs_awr_data_cp.plb 
@prvscpaddm.plb @prvsadv.plb @prvsawr.plb @prvsawri.plb 
@prvsumfi.plb @prvsawrs.plb @prvsash.plb @prvsawrv.plb 
@prvssqlf.plb @dbmswrr.sql @dbmsfus.sql @prvsfus.plb 
@prvsfusc.plb @dbmsuadv.sql @dbmsspm.sql @prvsspmi.plb 
@prvssmb.plb @prvssmbi.plb @dbmsstr.sql @dbmssqls.sql 
@dbmsspa.sql @prvsautorepi.plb @dbmsautorep.sql @dbmsratmask.sql 
@dbmsdiag.sql @dbmsrepl.sql @dbmskzxp.sql @dbmscu.sql 
@dbmsdst.sql @dbmscomp.sql @dbmsilm.sql @dbmspexe.sql 
@prvthpexei.plb @dbmscapi.sql @dbmsfuse.sql @dbmsfspi.sql 
@dbmspspi.sql @dbmsdnfs.sql @dbmsadr.sql @dbmsadra.sql 
@prvsadri.plb @xsrs.sql @xssc.sql @xsacl.sql 
@xsds.sql @xsns.sql @xsdiag.sql @xssess.sql 
@dbmsredacta.sql @dbmssqll.sql @dbmsgwm.sql @dbmsappcont.sql 
@dbmsscnc.sql @dbmsspd.sql @prvsspdi.plb @dbmsfs.sql 
@dbmssqlm.sql @catprofp.sql @prvtsys.plb @dbmspart.sql 
@dbmsrupg.sql @dbmstsdp.sql @dbmsinmem.sql @dbmsdbcomp.sql 
@dbmsapre.sql @dbmsinmemadmin.sql @dbmshadp.sql @dbmsbdcluacc.sql


[phase 16] type is 1 with 1 Files

ora_restart.sql

[phase 17] type is 1 with 22 Files

@dbmsmeti.sql @dbmsmetu.sql @dbmsqopi.sql @dbmstf.sql 
@dbmshmgr.sql @dbmsaclsrv.sql @dbmstns.sql @catappcdbviews.sql 
@prvthesh.plb @dbmsrsa.plb @prvthisagt.plb @prvthisutl.plb 
@dbmsol.sql @prvtols.plb @prvthpp.plb @setpdb.sql 
@dbmsmemoptimize.sql @dbmsmemoptimizeadmin.sql @dbmsai.sql @prvsaii.plb 
@prvssqlci.plb @prvssqlqi.plb

[phase 18] type is 1 with 1 Files

ora_restart.sql

[phase 19] type is 2 with 32 Files

@prvthdbu.plb @catost.sql @dbmshae.sql @catxpend.sql 
@prvtotpt.plb @prvthlut.plb @prvthlin.plb @prvthsdp.plb 
@dbmsrman.sql @dbmsbkrs.sql @dbmspplb.sql @dbmstrig.sql 
@dbmsrand.sql @dbmsjdwp.sql @catxs.sql @dbmssnap.sql 
@prvtxrmv.plb @depsaq.sql @prvthlrt.plb @catadv.sql 
@dbmscred.sql @catcredv.sql @cataqsch.sql @catrssch.sql 
@catplug.sql @prvtsql.plb @prvtssql.plb @prvtlmd.plb 
@prvtlmcs.plb @prvtlmrs.plb @prvtlmss.plb @prvthpv.plb


[phase 20] type is 1 with 1 Files

ora_restart.sql

[phase 21] type is 1 with 3 Files

@prvtkupc.plb @prvtaqiu.plb @catlsby.sql

[phase 22] type is 1 with 1 Files

ora_restart.sql

[phase 23] type is 2 with 25 Files

@cataivw.sql @catmetviews.sql @prvthpw.plb @prvthpm.plb 
@prvthpfi.plb @prvthpf.plb @prvthdpi.plb @dbmsodm.sql 
@prvtitrg.plb @prvtsms.plb @depssvrm.sql @deptxn.sql 
@catstr.sql @prvthsts.plb @prvthfgr.plb @prvthfie.plb 
@prvthcmp.plb @catpexev.sql @depscapi.sql @depspspi.sql 
@catwrrvw.sql @dbmsjdcu.sql @dbmsjdmp.sql @prvthpc.plb 
@prvt_awr_data.plb

[phase 24] type is 1 with 1 Files

ora_restart.sql

[phase 25] type is 2 with 12 Files

@catmetgrant1.sql @catldap.sql @prvtocm.sql @prvthpci.plb 
@catilm.sql @catemxv.sql @catnaclv.sql @dbmsnacl.sql 
@catpvf.sql @dbmswlm.sql @cathive.sql @catuat.sql


[phase 26] type is 1 with 1 Files

ora_restart.sql

[phase 27] type is 1 with 1 Files

ora_load_without_comp.sql

[phase 28] type is 1 with 3 Files

@prvtrepl.sql @catpstr.sql @catumfusr.sql

[phase 29] type is 1 with 1 Files

ora_load_with_comp.sql

[phase 30] type is 1 with 1 Files

ora_restart.sql

[phase 31] type is 1 with 1 Files

@catcdbviews.sql

[phase 32] type is 1 with 1 Files

ora_restart.sql

[phase 33] type is 2 with 0 Files


[phase 34] type is 1 with 1 Files

ora_load_without_comp.sql

[phase 35] type is 1 with 293 Files

@prvthpu.plb @prvthpui.plb @prvtbpui.plb @prvtidxu.plb 
@prvtadmi.plb @prvtbpu.plb @prvtutils.plb @prvtrlsa.plb 
@prvti18n.plb @prvtcred.plb @prvtfile.plb @prvtrawb.plb 
@prvttcp.plb @prvtinad.plb @prvtsmtp.plb @prvthttp.plb 
@prvturl.plb @prvtenc.plb @prvtgdk.plb @prvtlob.plb 
@prvtlobu.plb @prvtcstk.plb @prvtcomp.plb @prvtlms2.plb 
@prvtnla.plb @prvttrns.plb @prvtsess.plb @prvtrwid.plb 
@prvtpclxi.plb @prvtpclx.plb @prvterlg.plb @prvtapin.plb 
@prvtsyer.plb @prvtlock.plb @prvtpipe.plb @prvtalrt.plb 
@prvtdesc.plb @prvtbpexpi.plb @prvtpexp.plb @prvtzexp.plb 
@prvtstts.plb @prvtddl.plb @prvtpp.plb @prvtkppb.plb 
@prvtodbo.plb @prvthier.plb @prvtutil.plb @prvtpsp.plb 
@prvttran.plb @prvtxa.plb @prvtany.plb @prvtread.plb 
@prvtpb.plb @prvtpbt.plb @prvtxpsw.plb @prvtcoll.plb 
@prvttrst.plb @prvtodci.plb @prvtrpr.plb @prvtobtk.plb 
@prvtxmlt.plb @prvturi.plb @prvtxml.plb @prvtcxml.plb 
@prvtemxi.plb @prvtemx_admin.plb @prvtemx_dbhome.plb @prvtemx_memory.plb 
@prvtemx_perf.plb @prvtemx_cell.plb @prvtperf.plb @prvtemx_rsrcmgr.plb 
@prvtemx_sql.plb @prvtrep.plb @prvtrept.plb @prvtrepr.plb 
@prvtfga.plb @prvtamgt.plb @prvttypu.plb @prvtjdwp.plb 
@prvtjdmp.plb @prvtres.plb @prvtcr.plb @prvttxin.plb 
@prvtdrs.plb @prvtdg.plb @prvtfi.plb @prvtmap.plb 
@prvtdbv.plb @prvttcv.plb @prvtpbp.plb @prvthpro.plb 
@prvtcov.plb @prvtbdbu.plb @prvtsrv.plb @prvtpool.plb 
@prvtkzxs.plb @prvtkzxp.plb @prvtcrc.plb @prvtrc.plb 
@prvtaq.plb @prvtaqdi.plb @prvtaqxe.plb @prvtaqis.plb 
@prvtaqim.plb @prvtaqad.plb @prvtaq8x.plb @prvtaqin.plb 
@prvtaqal.plb @prvtaqjm.plb @prvtaqmi.plb @prvtaqme.plb 
@prvtaqem.plb @prvtaqip.plb @prvtaqds.plb @prvtsqdi.plb 
@prvtsqds.plb @prvtsqis.plb @prvthm.plb @prvtwlm.plb 
@prvtsqtk.plb @prvtkjhn.plb @prvtir.plb @prvtssb.plb 
@prvttxfm.plb @prvtrmin.plb @prvtrmad.plb @prvtrmpr.plb 
@prvtrmpe.plb @prvtrmge.plb @prvtrmpa.plb @prvtjob.plb 
@prvtbsch.plb @prvtesch.plb @prvtol.plb @prvtoli.plb 
@prvtlm.plb @prvtlmcb.plb @prvtlmrb.plb @prvtlmsb.plb 
@prvtlmeb.plb @prvtwrr_report.plb @prvtwrr.plb @prvtrupg.plb 
@prvtrupgis.plb @prvtlog.plb @prvtcapi.plb @prvtawrv.plb 
@prvtdput.plb @prvtmeta.plb @prvtmeti.plb @prvtmetu.plb 
@prvtmetb.plb @prvtmetd.plb @prvtmet2.plb @prvtbdpi.plb 
@prvtdp.plb @prvtdpmt.plb @prvtbpc.plb @prvtbpci.plb 
@prvtbpw.plb @prvtbpm.plb @prvtbpfi.plb @prvtbpf.plb 
@prvtbpp.plb @prvtbpd.plb @prvtbpdi.plb @prvtbpv.plb 
@prvtbpvi.plb @prvtbsdesc.plb @prvtdpcr.plb @prvtciai.plb 
@prvtplts.plb @prvtpitr.plb @prvtreie.plb @prvtrwee.plb 
@prvtrcmp.plb @prvtchnf.plb @prvtedu.plb @prvtlsby.plb 
@prvtlsib.plb @prvtlssb.plb @prvtsmv.plb @prvtsma.plb 
@prvtbxfr.plb @prvtbord.plb @prvtjdbb.plb @prvtslrt.plb 
@prvtslxp.plb @prvtatsk.plb @prvtmntr.plb @prvtsmgu.plb 
@prvtdadv.plb @prvtadv.plb @prvtmb.plb @prvtawr.plb 
@prvtawrs.plb @prvtawri.plb @prvtumf.plb @prvtumfi.plb 
@prvtash.plb @prvtsqlf.plb @prvtsqls.plb @prvtxplni.plb 
@prvtxpln.plb @prvtsqli.plb @prvtsqlt.plb @prvtai.plb 
@prvtaii.plb @prvtautorepi.plb @prvtautorep.plb @prvtfus.plb 
@prvtfusc.plb @prvtmp.plb @prvthdm.plb @prvtaddm.plb 
@prvtrtaddm.plb @prvt_awr_data_cp.plb @prvtcpaddm.plb @prvtuadv.plb 
@prvtsqlu.plb @prvtspai.plb @prvtspa.plb @prvtratmask.plb 
@prvtspmi.plb @prvtspm.plb @prvtsmbi.plb @prvtsmb.plb 
@prvtwrk.plb @prvtsmaa.plb @prvtstatadvi.plb @prvtstat.plb 
@prvtstai.plb @prvtstatagg.plb @prvtsqld.plb @prvtspcu.plb 
@prvtodm.plb @prvtkcl.plb @prvtdst.plb @prvtcmpr.plb 
@prvtilm.plb @prvtpexei.plb @prvtpexe.plb @prvtfuse.plb 
@prvtfspi.plb @prvtpspi.plb @prvtdnfs.plb @prvtfs.plb 
@prvtadri.plb @prvtadr.plb @prvtadra.plb @prvtds.plb 
@prvtxsrs.plb @prvtsc.plb @prvtacl.plb @prvtns.plb 
@prvtdiag.plb @prvtkzrxu.plb @prvtnacl.plb @prvtredacta.plb 
@prvtappcon.plb @prvtpdb.plb @prvttlog.plb @prvtsqll.plb 
@prvtappcont.plb @prvtspd.plb @prvtspdi.plb @prvtpprof.plb 
@prvtsqlm.plb @prvtpart.plb @prvtrupgib.plb @prvtpstdy.plb 
@prvttsdp.plb @prvtscnc.plb @prvtinmem.plb @prvtdbcomp.plb 
@prvtapre.plb @prvtinmemadmin.plb @prvttf.plb @prvtkubsagt.plb 
@prvthadoop.plb @prvtbdcluacc.plb @prvthmgr.plb @prvtaudutl.plb 
@prvtrsa.plb @prvtbisagt.plb @prvtbisutl.plb @prvtprocess.plb 
@prvtpq.plb @prvtaclsrv.plb @prvtbgg.plb @prvttns.plb 
@prvtbggei.plb

[phase 36] type is 1 with 1 Files

ora_load_with_comp.sql

[phase 37] type is 1 with 1 Files

ora_restart.sql

[phase 38] type is 1 with 6 Files

@catfusrg.sql @prvtmemoptimize.plb @prvtmemoptimizeadmin.plb @prvtsqlci.plb 
@prvtsqlqi.plb @prvtsqlq.plb

[phase 39] type is 1 with 1 Files

ora_restart.sql

[phase 40] type is 1 with 3 Files

@catmetinsert.sql @catpcnfg.sql @catdph.sql

[phase 41] type is 1 with 1 Files

ora_restart.sql

[phase 42] type is 2 with 13 Files

@catmetgrant2.sql @execemx.sql @execcr.sql @caths.sql 
@catemini.sql @execaq.sql @execsvrm.sql @exechae.sql 
@execsec.sql @execbsln.sql @dbmspump.sql @olappl.sql 
@execrep.sql

[phase 43] type is 1 with 1 Files

ora_restart.sql

[phase 44] type is 2 with 11 Files

@execstr.sql @execsvr.sql @execstat.sql @execsmb.sql 
@catsnmp.sql @wpiutil.sql @owainst.sql @catilmini.sql 
@execocm.sql @exectsdp.sql @execqopi.sql

[phase 45] type is 1 with 1 Files

ora_restart.sql

[phase 46] type is 2 with 3 Files

@execrsa.plb @execschlb.plb @execpdb.sql

[phase 47] type is 1 with 1 Files

ora_restart.sql

[phase 48] type is 1 with 1 Files

@catpend.sql

[phase 49] type is 1 with 1 Files

ora_restart.sql

[phase 50] type is 1 with 1 Files

@catupprc.sql

[phase 51] type is 1 with 1 Files

@cmpupstr.sql

[phase 52] type is 1 with 1 Files

ora_restart.sql

[phase 53] type is 1 with 2 Files

@cmpupjav.sql @cmpupnjv.sql

[phase 54] type is 1 with 1 Files

ora_restart.sql

[phase 55] type is 1 with 0 Files


[phase 56] type is 1 with 3 Files

-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbustr.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbuo.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbus.sql

[phase 57] type is 1 with 3 Files

-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxmlt.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxmlu.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxmld.sql

[phase 58] type is 2 with 10 Files

-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxmlp.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxtbix.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxidx.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catsodaview.sql 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxdbpi.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxsch.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxres.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxdbz.sql 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdbutil.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdb0.plb

[phase 59] type is 2 with 25 Files

-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxdb.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxutil.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxrc.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxdbc.sql 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxdba.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxreg.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxschlsb.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxlsb.sql 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxdbrepos.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxtr.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxidx.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxvr.sql 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxmls.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxdbh.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxdbdt.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxslp.sql 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdr0.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxev.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdz0.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxsch0.plb 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsjson.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmssodacoll.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmssodadom.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmssodautil.sql 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmssodapls.sql

[phase 60] type is 1 with 4 Files

-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/dbmsxdbr.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxdbr.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxdbv.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catvxutil.sql


[phase 61] type is 1 with 1 Files

ora_load_without_comp.sql

[phase 62] type is 1 with 32 Files

-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxsch.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdbr.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxslp.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdbz.plb 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxmlt.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxutil.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxrc.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxres.plb 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdbdl.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtcsx.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdb.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdba.plb 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxreg.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdbp.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxschlsb.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxlsb.plb 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxdbrepos.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxev.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxtr.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxidx.plb 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxmlstreams.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxmld.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxmlp.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxsch.plb 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxsfsclient.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtxschnpb.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtjson.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtsodautil.plb 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtsodadml.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtsodacoll.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtsodadom.plb -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/prvtsodapls.plb


[phase 63] type is 1 with 1 Files

ora_load_with_comp.sql

[phase 64] type is 2 with 6 Files

-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxdbpv.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxdbeo.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbinstd.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxdbapp.sql 
-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxdbdl.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catxdbz1.sql

[phase 65] type is 1 with 2 Files

-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/catmetx.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbloadend.sql

[phase 66] type is 1 with 3 Files

-CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbud.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xrdupgrd.sql -CPXDB@/u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/xdbuend.sql

[phase 67] type is 1 with 1 Files

ora_restart.sql

[phase 68] type is 1 with 0 Files


[phase 69] type is 1 with 1 Files

-CPORDIM@/u01/app/oracle/product/19.0.0/dbhome_1/ord/im/admin/imupstrt.sql

[phase 70] type is 2 with 2 Files

-CPORDIM@/u01/app/oracle/product/19.0.0/dbhome_1/ord/im/admin/imclnjav.sql -CPORDIM@/u01/app/oracle/product/19.0.0/dbhome_1/ord/im/admin/imupmain.sql

[phase 71] type is 1 with 1 Files

ora_restart.sql

[phase 72] type is 2 with 2 Files

-CPORDIM@/u01/app/oracle/product/19.0.0/dbhome_1/ord/im/admin/imuprun.sql -CPORDIM@/u01/app/oracle/product/19.0.0/dbhome_1/ord/im/admin/imuploc.sql

[phase 73] type is 1 with 2 Files

-CPORDIM@/u01/app/oracle/product/19.0.0/dbhome_1/ord/im/admin/imupend.sql @cmpupord.sql

[phase 74] type is 1 with 1 Files

ora_restart.sql

[phase 75] type is 1 with 0 Files


[phase 76] type is 1 with 1 Files

-CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/sdoupgrdh.sql

[phase 77] type is 1 with 2 Files

-CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdh.sql -CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/mdprivs.sql

[phase 78] type is 1 with 1 Files

ora_restart.sql

[phase 79] type is 1 with 1 Files

-CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdloch.sql

[phase 80] type is 1 with 1 Files

ora_restart.sql

[phase 81] type is 2 with 3 Files

-CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdlocp1.sql -CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdlocp2.sql -CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdlocj.sql

[phase 82] type is 1 with 1 Files

ora_restart.sql

[phase 83] type is 1 with 1 Files

-CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdloct.sql

[phase 84] type is 1 with 1 Files

ora_restart.sql

[phase 85] type is 1 with 1 Files

-CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdsdoh.sql

[phase 86] type is 1 with 1 Files

ora_restart.sql

[phase 87] type is 2 with 4 Files

-CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdsdop1.sql -CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdsdop2.sql -CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdsdop3.sql -CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdsdop4.sql


[phase 88] type is 1 with 1 Files

ora_restart.sql

[phase 89] type is 1 with 1 Files

-CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdsdot.sql

[phase 90] type is 1 with 1 Files

ora_restart.sql

[phase 91] type is 1 with 2 Files

-CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/catmdt.sql -CPSDO@/u01/app/oracle/product/19.0.0/dbhome_1/md/admin/sdoupgrdt.sql

[phase 92] type is 1 with 1 Files

ora_restart.sql

[phase 93] type is 1 with 1 Files

@cmpupsdo.sql

[phase 94] type is 1 with 1 Files

ora_restart.sql

[phase 95] type is 1 with 1 Files

@cmpupmsc.sql

[phase 96] type is 1 with 1 Files

ora_restart.sql

[phase 97] type is 1 with 1 Files

@cmpupend.sql

[phase 98] type is 1 with 1 Files

@catupend.sql

[phase 99] type is 1 with 1 Files

@catmmig.sql

[phase 100] type is 1 with 1 Files

@catappupgend.sql

[phase 101] type is 1 with 1 Files

@catshutdownpdb.sql

[phase 102] type is 1 with 1 Files

@catshutdown.sql

[phase 103] type is 1 with 1 Files

@catuppst.sql

[phase 104] type is 1 with 1 Files

@catresults.sql

[phase 105] type is 1 with 1 Files

@catappupgend.sql

[phase 106] type is 1 with 1 Files

@catshutdownpdb.sql

[phase 107] type is 1 with 1 Files

@catshutdown.sql

Total Number of Phases: 108

Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8

AutoUpgrade with Source and Target Database Homes on Same Server – 19c New Feature

DB Upgrade using AutoUpgrade tool:

It is a feature that is enhanced in oracle 19c and it is mainly used to automate the upgrade process.it not only automates the database upgrade but also performs the pre-upgrade steps and the post upgrade steps automatically.it just simplifies the upgrade activity, previously we have to use dbua/manual method/datapump methods to upgrade the database now we can upgrade the number of databases using AutoUpgrade utility within the short span of time.

Note :   If you are doing AutoUpgrade on same server it is not necessary to run the upgrade mode you can stop with the deploy mode, our database will be upgraded.

On the other hand if you are performing AutoUpgrade on different servers it is necessary to run all the mode till upgrade mode.(i.e. analyze, fixups, deploy, upgrade)

AutoUpgrade is available for Oracle Database Enterprise Edition, and Oracle Database Standard Edition. It is not available for Oracle Database Express Edition.

AutoUpgrade Support is available for Oracle Database 12c Release 2 (12.2) and Oracle Database 18c (18.5) target homes. For both Oracle Database 12c Release 2 (12.2) and Oracle Database 18c (18.5) target homes.

Advantages of AutoUpgrade Utility:

  • Time saving method (completes the upgrade in a short time)
  • can upgrade multiple Oracle Database deployments at the same time, using a single configuration file, customized as needed for each database deployment.
  • preventing the issues before upgrade.
  • It automatically performs the preupgrade and post upgrade steps/checks.

AUTOUPGRADE PROCESSING MODES:

Generally AutoUpgrade processes in four modes, they are ,

  • Analyze

It performs a read only pre-upgrade analysis of databases before upgrade and detects any issues which may prevent the successful completion of upgradation.it should be run in the source database like normal operations.

  • Fixups

In Fixups mode it checks the same as it have done in the analyze mode, so that it can identify issues that require fixing. In Fixup Mode, the AutoUpgrade utility detects and identifies both fixes that require manual intervention and AutoUpgrade utility can clear the fix during upgrade.

  • Deploy

In deploy mode it confirms that our database has been successfully upgraded and it copies the sqlnet.ora, listener.ora, tnsnames.ora from source to target home.

  • Upgrade

An upgrade completes with either deploy or upgrade, after this we can run our post upgrade checks.in this we can run our custom scripts on the upgraded databases in accordance with the configuration file that we have created. After this the upgraded oracle database starts with a new oracle home.

AutoUpgrade utility jobs pass through a series of phases, called stages, during which specific actions are performed.

AutoUpgrade has the following stages,

SETUP
PREUPGRADE
PRECHECKS
GRP
PREFIXUPS
DRAIN
DBUPGRADE
POSTCHECKS
POSTFIXUPS
POSTUPGRADE

Overview steps:

Step:1 Check for the autoupgrade.jar file version which is already present in the database.($ORACLE_HOME/rdbms/admin/preupgrade.jar)

Step:2 Then we have to download the latest autoupgrade.jar version and then we have to share the file in /home/oracle location and check the version of the file.

Step:3 Our database which we are going to upgrade must be in archivelog mode and flashback should be enabled.

Step:4 Create a configuration file which consists of source Sid, log directory, start time of the upgrade, target home, source db version.

Step:5 Once we run the analyze mode it checks for any issues and also it analyses the source database, it will estimate the time when the upgrade will get completed, jobs that are running, status of the jobs ,once it is completed without any error we can run the fixups mode here also the same it detects and fixes the bugs that is either by manual or bugs that is fixed automatically during upgrade.

Step:6 After this the next stage is deploy and upgrade both are same which upgrades our database, it confirms that our database is upgraded successfully. here it transfers the listener.ora, tnsnames.ora files from source home to target’s home. Then we can start our upgraded database in the new oracle home.

Step:7 Then check time zone version of upgraded database.

Step:1 Check for the autoupgrade.jar version which is already present. The autoupgrade.jar file is available in the Oracle 19c database software in the $ORACLE_HOME/rdbms/admin directory.

Step:2 Then download the latest version of autoupgrade.jar from the MOS note 2485457.1

Step:3 Create the configuration files containing the parameters where the logs should be stored, dbid, database name to be upgraded, source and target version home.

Step:4 Enable the archive log mode in the database which is to be upgraded.

Step:5 Analyze the database to be upgraded using the analyze mode and fixups the issues by running fixups mode.

There are three main commands in this upgrade to check the status of the upgrade.

lsj       –   list the jobs which are running.

tasks  –  to see the tasks of the jobs and their status.

status – it gives an overall summary of the upgrade, here we can see the no of container and non-container databases, job finished successfully, job aborted and jobs which are in progress state.

Other than these there are some commands which helps you to perform the AutoUpgrade in a better way.

Running  Analyze mode:

Please find the detailed logfiles mentioned below.

prechecks_hongkong.log

hongkong_checklist.log

Running fixups mode:

Please find the detailed logfiles mentioned below.

prefixups_hongkong.log

hongkong_preupgrade.log

Step:6 After these above steps are completed successfully we can proceed the upgrade process using deploy and upgrade modes.

Running deploy mode:

Our database is upgraded successfully from 12c to 19c using AutoUpgrade tool.

Please find the detailed logfiles mentioned below.

drain_hongkong.log

autoupgrade_20210309.log

autoupgrade_20210309_user.log

Here I am checking whether database is upgraded or not by running the 19c environment file and logging in to the database and also verify the name, open mode and timezone version.


Please find the detailed logfiles mentioned below.

postchecks_hongkong.log

postfixups_hongkong.log

postupgrade.log

The below mentioned logfiles contains the overall summary for AutoUpgrade.

upg_summary.log

cat phase.log

Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8

UPGRADE ORACLE DATABASE FROM ORACLE 12.2.0.1 TO 19C USING DBUA

What is upgradation?

Upgradation is the process of replacing an older version/software with a new version of the product. It transforms the existing Oracle Database Environment into a new Environment. Upgradation can be done within the similar OS or with a different platform.

NOTE: It is important that we should apply the latest PSU or proactive bundle patch, RU, or RUR patch before starting an upgrade.

Why do we need to upgrade?

Upgrading a database generally fixes the bugs, internal errors and other technical issues which can be identified and resolved as soon as possible thereby it reduces the downtime.

You can perform a direct upgrade to the new release from the following releases: 
• 11.2.0.4 
• 12.1.0.1 and 12.1.0.2 
• 12.2.0.1

For example: Here I am converting my db from 12.2.0 (base version) to a 19.0.0 (higher version)  

Types of Upgrade:

We can upgrade our DB  in any one of the following  methods,

1)DBUA (Database Upgrade Assistant)

2)Manual Method

3)Data Pump

4)Transportable Tablespaces

DATABASE UPGRADE ASSISTANT  (DBUA) :

DBUA is a GUI method that checks all pre-requisties themselves.it checks for all the pre-requisties such as configuring the listener, recompiling the invaid objects, upgrading the time zone, running the preupgrade_fixups.sql,postupgrade_fixups.sql, configuring the enterprise manager (EM) database express, creating a Guaranteed Restore Point and all the things by itself.DBUA only performs the upgradation process if it satisfies all the above-mentioned things.

In the manual method, we should perform all the pre-requisties things manually.

Overview of steps to Upgrade a Database:

PRE-UPGRADE STEPS:

  1.  Create a new directory called backup, Take a backup of listener.ora,tnsnames.ora,spfile and password files ,then move all the files to the newly created directory called backup.
  2. Create a new directory called upgrade,Run the preupgrade.jar file which is in  the location
(/u01/app/oracle/product/12.2.0.1/db_1/jdk/bin/java -jar /u02/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/preupgrade.jar),Move the summary of the preupgrade.script to the upgrade directory.

3.Three files named preupgrade.log,preupgrade_fixups.sql,postupgrade_fixups.sql files will be created after running the preupgrade.script.

4.We should execute the below scripts,

Before upgrade – @/u01/preupgrade/preupgrade_fixups.sql

After upgrade    – @/u01/preupgrade/postupgrade_fixups.sql

5.Then check the preupgrade.log whether it is completed without any errors.

6. Verify the tablespace sizes for upgrade. (enable the AUTO EXTENT ON and set the maximum size for tablespaces)

 7. Gather the dictionary statistics query to get the statistical data of fixed objects. we should gather dictionary statistics before and after the upgrade to maintain better DB performance.Because dictionary tables are modified and created during the upgrade.

8.Purge the recyclebin

9.Refresh all the materialised views before upgrade.

10.Run preupgrade_fixups.sql (/u01/upgrade/preupgrade_fixups.sql) before the upgrade.

11. You should enable the archive log list.

12.Create the flashback restore point before performing upgrade,it is important suppose if dbupgrade fails you can recover the database from this restore point.

13.Set the db_recovery_file_dest_size=10GB

UPGRADE TASK:

After we have completed all our pre-upgrade steps, Now it is time to upgrade our DB using dbua(GUI Method), All the steps will be taken by this.

Once you run the dbua command ,a log will be generated in the location (/u01/app/oracle/cfgtoollogs/dbua/upgrade2020-04-23_10-46-32PM) we can check this log file if any error occurs)

14.We should choose the database which is to be upgraded for 19c.

15. Next choose to Create a Guranteed Restore Point or RMAN backup in case of failure of upgrade. Double-check our restore point

16. Configure a new listener or upgrade the existing listener which is running up from 12.2.20.1 home to target 19c home.

17.Check if all the pre-requisites that we mentioned are correctly mentioned in the GUI.

POST UPGRADE STEPS:

 18.Put an entry of current database in the vi /etc/oratab file.

 19. Verify the timezone version of the upgraded database. (it should be changed to 32)

 20. Then check for any invalid objects in the database after the upgrade.

 21.We have to verify the DBA_REGISTRY view,it displays the information about the components loaded in the database.

 22. Now we can drop the restore point that we have created already before the upgrade.

 23.Update the compatible parameter value, it will be set in the base database version we have to update the upgraded db version in the compatible parameter value.

 24. Finally check the listener.ora and tnsnames.ora files it should be updated to an upgraded db version.

Step:1 create a new directory for backup and for the upgrade.

[oracle@orcldbs u01]$ mkdir backup
[oracle@orcldbs u01]$ ls
app  backup  oradata                              
[oracle@orcldbs u01]$ mkdir preupgrade
[oracle@orcldbs u01]$ ls
app  backup  oradata  preupgrade

Step:2 Take backup of listener.ora,tnsnames.ora.spfile,password file.

Step:3 Run the pre-upgrade jar script,a log(preupgrade.log  will be generated after running the script and send it to the /u01/preupgrade)

[oracle@orcldbs db_1]$ /u02/app/oracle/product/12.2.0.1/db_1/jdk/bin/java -jar /u01/app/oracle/product/19.0.0/dbhome_1/rdbms/admin/preupgrade.jar FILE DIR /u01/preupgrade
==================
PREUPGRADE SUMMARY
==================
  /u01/preupgrade/preupgrade.log

  /u01/preupgrade/preupgrade_fixups.sql

  /u01/preupgrade/postupgrade_fixups.sql

Execute fixup scripts as indicated below:

Before upgrade:
Log into the database and execute the preupgrade fixups

@/u01/preupgrade/preupgrade_fixups.sql

After the upgrade:
Log into the database and execute the postupgrade fixups

@/u01/preupgrade/postupgrade_fixups.sql

Preupgrade complete: 2021-01-30T01:54:48

Step:4 Log in to the database and run the preupgrade_fixups.sql

[oracle@orcldbs db_1]$ !sq
sqlplus / as sysdba
SQL*Plus: Release 12.2.0.1.0 Production on Sat Jan 30 01:55:09 2021
Copyright (c) 1982, 2016, Oracle.  All rights reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
SQL> @/u01/preupgrade/preupgrade_fixups.sql
Executing Oracle PRE-Upgrade Fixup Script
Auto-Generated by:       Oracle Preupgrade Script
                         Version: 19.0.0.0.0 Build

Generated on:            2021-01-30 01:54:46
For Source Database:        GERMANY
Source Database Version: 12.2.0.1.0
For Upgrade to Version:  19.0.0.0.0
Preup                             Preupgrade
Action                            Issue Is
Number  Preupgrade Check Name     Remedied    Further DBA Action
------  ------------------------  ----------  --------------------------------
    1.  dictionary_stats          YES         None.

    2.  pre_fixed_objects         YES         None.

    3.  tablespaces_info          NO          Informational only.
                                              Further action is optional.
    4.  rman_recovery_version     NO          Informational only.
                                             Further action is optional.

PL/SQL procedure successfully completed.

Step:5  Gather the dictionary statistics it should be gathered after performing the upgrade.

SQL> SET ECHO ON;
SET SERVEROUTPUT ON;
EXECUTE DBMS_STATS.GATHER_DICTIONARY_STATS;

PL/SQL procedure successfully completed.

Step:6 Purge the recycle bin.it is mainly used to release the storage space used,since we have enabled the GRP we can purge the recycle bin.

PURGE DBA_RECYCLEBIN;

SQL>DBA_RECYCLEBIN purged.

Step:7 Refreshing the Materialised views update all its indexes.

 SQL>  declare
list_failures integer(3) :=0;
begin
DBMS_MVIEW.REFRESH_ALL_MVIEWS(list_failures,'C','', TRUE, FALSE);
end;

PL/SQL procedure successfully completed.

Step:8 Enable the archive log mode it is mandatory to perform an db upgrade.

SQL> archive log list
Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            /u01/app/oracle/product/12.2.0.1/db_1/dbs/arch
Oldest online log sequence     1
Current log sequence           2
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 2432696320 bytes
Fixed Size                  8623592 bytes
Variable Size             654314008 bytes
Database Buffers         1761607680 bytes
Redo Buffers                8151040 bytes
Database mounted.

SQL> alter database archivelog;

Database altered.

SQL> archive log list;

Database log mode              Archive Mode
Automatic archival             Enabled
Archive destination            /u01/app/oracle/product/12.2.0.1/db_1/dbs/arch
Oldest online log sequence     1
Next log sequence to archive   2
Current log sequence           2

SQL> show parameter rec

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
buffer_pool_recycle                  string

control_file_record_keep_time        integer     7

db_recovery_file_dest                string

db_recovery_file_dest_size           big integer 0

db_recycle_cache_size                big integer 0

db_unrecoverable_scn_tracking        boolean     TRUE

ldap_directory_access                string      NONE

ldap_directory_sysauth               string      no

recovery_parallelism                 integer     0

recyclebin                           string      on

remote_recovery_file_dest            string

SQL> select flashback_on from v$database;

FLASHBACK_ON
------------------
NO


SQL> select name,open_mode,log_mode from v$database;

NAME      OPEN_MODE            LOG_MODE
--------- -------------------- ------------
GERMANY   MOUNTED              ARCHIVELOG


SQL> show parameter db_recovery_file_dest_size

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_recovery_file_dest_size           big integer 0

SQL> alter database open;

Database altered.

Step:9 set the db_recovery_fil_dest_size to 10 gb for recovery purpose.

SQL> alter system set db_recovery_file_dest_size=10G;

System altered.

Step:10 create the GRP (Guarantee Restore Point) ,suppose if any failure occurs during upgradation we can easily go to the before upgrade of db (ie  looks like as if our db before upgradation)it is used for recovery purpose.

SQL> create restore point pre_upgrade guarantee flashback database;

Restore point created.
SQL> select NAME,GUARANTEE_FLASHBACK_DATABASE,TIME from V$restore_point;

NAME                                                                      TIME                                                        GUA

PRE_UPGRADE                                            30-JAN-21 02.26.08.000000000 AM             YES                                                           

Step:11 We have done all the things to be done before the upgrade. Now it’s time to run the DBUA a GUI Utility to perform the upgrade.

11.1  you have to choose the database which you need to upgrade, here I am choosing Germany db for upgrade to 19.0.0  which is in version 12.2.0 and click next.

 

 

 

11.2 second window shows the Pre Upgrade Recommendations and Post Upgrade Recommendations and then click next.

 

 

 

 

11.3 in this screen click the following checkboxes,

Enable Parallel Upgrade

Recompile Invalid Objects During Post Upgrade

Upgrade Timezone Data

After that you have to browse the locations of preupgrade_fixups.sql,postupgrade_fixups.sql

 

 

 

 

11.4 In this screen you can specify any of the recovery option for the database in case of upgrade failure.

Here I am using Flashback and Guaranteed Restore Point.

There are methods are also available such that RMAN backup , use latest available full RMAN backup. if you have your own backup and restore strategy you can also use  that.

 

 

 

 

11.5 Select the 12c listener, it should be up and running.

 

 

 

 

11.6 select the Configure Enterprise Manager (EM) database express check box and click next.

 

 

 

 

11.7 Finally this window shows the Database Upgrade summary you can verify all your selections that you have choose above are correctly mentioned and proceed further.

 

 

 

 

11.8 After that Oracle upgrade process starts.

 

 

 

 

11.9 when the upgradation process is over it give an upgrade results which db is upgraded from which version to which version. You can check here for information.

 

 

 

 

Step:12 Put an entry of the current database in the vi /etc/oratab file.

[oracle@orcldbs ~]$ cat /etc/oratab | grep -i germany
germany:/u01/app/oracle/product/19.0.0/dbhome_1:N
[oracle@orcldbs ~]$[oracle@orcldbs admin]$ export ORACLE_SID=germany
[oracle@orcldbs admin]$ sqlplus / as sysdba

SQL*Plus: Release 19.0.0.0.0 - Production on Sat Jan 30 04:09:40 2021
Version 19.3.0.0.0
Copyright (c) 1982, 2019, Oracle.  All rights reserved.
Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.3.0.0.0

SQL>  SELECT name from v$database;       

NAME
----------------
GERMANY

Step:13 check the timezone version for the upgraded db (GERMANY) it has changed from 26(12c) to 32(19c).

SQL>  SELECT version FROM v$timezone_file;

   VERSION
----------------           
     32

Step:14 Check for any invalid objects in upgraded database.

select count(1) from dba_objects where status='INVALID';

  COUNT(1)
------------------
     0            

Step:15 Verify the dba_registry, it should be verified before and after the upgrade because it display information about the components loaded in the database.

SQL> col COMP_ID for a10
col COMP_NAME for a40
col VERSION for a15
set lines 180
set pages 999

select COMP_ID,COMP_NAME,VERSION,STATUS from dba_registry;

COMP_ID    COMP_NAME                                                               VERSION              STATUS
---------- ---------------------------------------- --------------- --------------------------------------------

CATALOG    Oracle Database Catalog Views                                         19.0.0.0.0             VALID

CATPROC    Oracle Database Packages and Type                                     19.0.0.0.0             VALID

JAVAVM     JServer JAVA Virtual Machine                                          19.0.0.0.0             VALID

XML         Oracle XDK                                                           19.0.0.0.0             VALID

CATJAVA    Oracle Database Java Packages                                         19.0.0.0.0             VALID

APS        OLAP Analytic Workspace                                               19.0.0.0.0             VALID

RAC        Oracle Real Application Clusters                                      19.0.0.0.0             OPTION OFF

XDB        Oracle XML Database                                                   19.0.0.0.0             VALID

OWM        Oracle Workspace Manager                                              19.0.0.0.0             VALID

CONTEXT   Oracle Text                                                            19.0.0.0.0             VALID

ORDIM    Oracle Multimedia                                                       19.0.0.0.0             VALID

SDO      Spatial                                                                 19.0.0.0.0             VALID

XOQ      Oracle OLAP API                                                         19.0.0.0.0             VALID

OLS      Oracle Label Security                                                   19.0.0.0.0             VALID

DV       Oracle Database Vault                                                   19.0.0.0.0             VALID


15 rows selected.

Step:16  we have upgraded our db to a higher version, hence we can drop the guaranteed restore point.

SQL> drop restore point pre_upgrade; 

Restore point dropped. 

Step:17 check the compatible parameter it will be in 12.2.0 compatible value we have to set the compatible value to 19.0.0

SQL> show parameter COMPATIBLE

NAME                                                        TYPE                VALUE

------------------------------------                      ----------- ------------------------------
compatible                                                  string                12.2.0

noncdb_compatible                                           boolean               FALSE
SQL> ALTER SYSTEM SET COMPATIBLE = '19.0.0' SCOPE=SPFILE;

System altered.

SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup

ORACLE instance started.
Total System Global Area 2432695144 bytes
Fixed Size                                8899432 bytes
Variable Size                            536870912 bytes
Database Buffers                        1879048192 bytes
Redo Buffers                             7876608 bytes
Database mounted.
Database opened.

SQL> ALTER SYSTEM SET COMPATIBLE = '19.0.0' SCOPE=SPFILE;

System altered.

SQL> show parameter COMPATIBLE

NAME                                                        TYPE                VALUE

------------------------------------                    ----------- ------------------------------

compatible                                                 string              19.0.0

noncdb_compatible                                         boolean              FALSE

SQL>

Step:18 Verify whether the listener and tns files are changed to the upgraded version.(19.0.0)

[oracle@orcldbs ~]$ ps -ef | grep tns

root        15     2  0 Jan29 ?        00:00:00 [netns]
oracle    2165     1  0 02:35 ?        00:00:00 /u02/app/oracle/product/12.2.0.1/db_1/bin/tnslsnr LISTENER -inherit
oracle    6055     1  0 02:49 ?        00:00:00 /u01/app/oracle/product/19.0.0/dbhome_1/bin/tnslsnr LISTENER -inherit
oracle   25603 28937  0 04:16 pts/0    00:00:00 grep --color=auto tns


[oracle@orcldbs ~]$
[oracle@orcldbs ~]$ lsnrctl status
LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 30-JAN-2021 04:17:17
Copyright (c) 1991, 2019, Oracle.  All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.26)(PORT=1521)))

STATUS of the LISTENER
------------------------

Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 19.0.0.0.0 - Production
Start Date                30-JAN-2021 02:49:58
Uptime                    0 days 1 hr. 27 min. 18 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF

Listener Parameter File   /u01/app/oracle/product/19.0.0/dbhome_1/network/admin/listener.ora
Listener Log File         /u01/app/oracle/diag/tnslsnr/orcldbs/listener/alert/log.xml

Listening Endpoints Summary...

  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.26)(PORT=1521)))

  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=orcldbs.localdomain)(PORT=5500))(Security=(my_wallet_directory=/u01/app/oracle/admin/trichy/xdb_wallet))(Presentation=HTTP)(Session=RAW))

Services Summary...
Service "oraprod" has 2 instance(s).
Instance "oraprod", status UNKNOWN, has 1 handler(s) for this service...
Instance "oraprod", status READY, has 1 handler(s) for this service...

Service "oraprodXDB" has 1 instance(s).
Instance "oraprod", status READY, has 1 handler(s) for this service...

Service "germany" has 1 instance(s).
 Instance "germany", status READY, has 1 handler(s) for this service...

Service "germanyXDB" has 1 instance(s).
Instance "germany", status READY, has 1 handler(s) for this service...

The command completed successfully 
[oracle@orcldbs ~]$

Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter: https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8

 

 

19C RMAN CONCEPTS

rman

19c RMAN CONCEPTS:

RECOVER DATAFILE WITHOUT RMAN BACKUP
RECOVER THROUGH RESETLOGS
BLOCK CHANGE TRACKING
RECOVER LOSS OF ALL CONTROL FILE USING AUTO BACKUP
RECOVER LOSS OF ALL ONLINE REDO LOGS 
POINT IN TIME RECOVERY 
RMAN-06183: datafile or datafile copy xyz.dbf larger than MAXSETSIZE
RMAN Database Restore ASM
DATABASE INCARNATION USING RMAN
Restore Tablespace using RMAN
RESTORE SPFILE USING RMAN
RMAN backup Full Database
RMAN Backup Tablespace
RMAN Backup Particular Datafile
RMAN Backup Spfile
RMAN Backup Current Control file
RMAN Backup Archive log Until Sequence
RMAN Backup Archive log Between Sequence
RMAN Backup Archive log Between SCN
RMAN Backup Archive log Until SCN
RMAN Backup Database Plus Archive log
RMAN Backup Database Includes A Control file
RMAN Backup Archive log and All Delete Input
RMAN Backup Archive log All and Skip Inaccessible
LEVEL 0 and LEVEL 1 Backup And Recovery using RMAN
CROSSCHECK BACKUPS Using RMAN
RESTORE CONTROL FILE USING RMAN
Backup-based Cloning of a database using RMAN
RECOVERY CATALOG DATABASE IN RMAN
RMAN ORA ERRORS
DBVERIFY
END-OF-FILE ERROR
LEVEL 0 INCREMENTAL BACKUP
point-in-time recovery using RMAN in 19c
Recover a loss of all online redo log files

Thank you for giving your valuable time to read the above information. If you want to be updated with all our articles send us the Invitation or Follow us:

Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter: https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8

AutoUpgrade 21c Release: New Features/Enhancements

Belong to Below environment:

Oracle Database – Enterprise Edition – Version 12.2.0.1 and later
Oracle Database – Standard Edition – Version 12.2.0.1 and later

Overview:

Oracle Database AutoUpgrade allows DBAs to upgrade one or many databases without human intervention, all with one command and a single configuration file.

Advantages:

AutoUpgrade enables customers to upgrade one or many Oracle databases at the command-line with a single command and a single configuration file. AutoUpgrade will run the preupgrade tasks, perform automated fixups where needed, execute the database upgrade, and finish by taking care of post-upgrade tasks. It includes automatic retry and fallback, the possibility to schedule upgrades for future points in time, and the ability to set, change or remove initialization parameters as desired. It saves time and money by upgrading hundreds of databases with one command and replacing bespoke high maintenance upgrade solutions.

Download

The most recent version of AutoUpgrade can be downloaded via this link: version 20201214.

Supported Target Versions

AutoUpgrade Tool can be used on upgrading to below Oracle Database releases:

  • Oracle Database 21c (21.3 and newer)
  • Oracle Database 19c (19.3 and newer)
  • Oracle Database 18c (18.5 and newer)
  • Oracle Database 12c Release 2 (12.2 + DBJAN2019RU and newer)

How to Install

As of the January 2019 Release Updates (DBJAN2019RU) and beyond, AutoUpgrade Support is available for Oracle Database 12c Release 2 (12.2) and Oracle Database 18c (18.5) target homes. For both Oracle Database 12c Release 2 (12.2) and Oracle Database 18c (18.5) target homes, you must download the AutoUpgrade Tool and place it under $ORACLE_HOME/rdbms/admin.

In Oracle Database 19c (19.3) and later target Oracle homes, the autoupgrade.jar file exists by default. However, before you use AutoUpgrade, Oracle recommends that you download the latest version and replace the one already existing under $ORACLE_HOME/rdbms/admin.

Limitations

  • Database restoration option is not available on an Oracle Database Standard Edition.

AutoUpgrade 21c Release: New Features/Enhancements

  • Non-CDB to PDB Upgrades
    • AutoUpgrade can upgrade and convert a non-CDB to a PDB in a new CDB in a single operation, or upgrade and then convert a Non-CDB database to a PDB in a pre-existing CDB
    • Support for RAC and SI databases
  • Unplug-plug upgrade
    • AutoUpgrade can perform an unplug of a pluggable database (PDB) from an earlier release source container database (CDB), plug it into a later release target CDB, and then complete all the steps required to upgrade the PDB to the target CDB release
  • Supports RAC upgrades (Only for Linux or Unix-based systems)
    • Configuration of the RAC management system in the source and target home is automated
    • Supports native file systems, ASM and ACFS
    • Oracle Restart
    • Pluggable databases are supported in a RAC environment
  • Ability to pass catctl_options (via config file)
    • This enables the DBA to control the level of parallelism for a specific upgrade.
  • Restore capability
    • AutoUpgrade restore job option allows the DBA to restore database back to source home if upgrade failed or succeeded
  • Clear the recovery for a specific job by adding clear_recovery_data on the command line and use jobs parameter to specific exactly which jobs recovery data must be cleared.
  • Upgrades on Data Guard environments
    • AutoUpgrade can detect Oracle Data Guard configurations, and defer shipping logs to standby databases configured for the primary database. It will also detect and defer shipping logs to standby database if the deployment is configured manually. Upon a successfully upgrade of the primary database, upgrades to the standby database must be performed and monitored by the DBA.
  • AutoUpgrade performance improvements
    • utlrp compilations moved out of upgrade into a post fixup
    • Improved resume operations: AutoUpgrade keeps track and skips over PDBs databases that have been upgraded successfully
    • Replay support was added for upgrades 21 or higher
  • AutoUpgrade supports upgrade on CDBs with proxy pdbs
  • AutoUpgrade supports upgrade on CDB’s with application containers
  • Added additional JSON status information
  • Integrated classic pre-upgrade functionality
    • The -preupgrade clause of AutoUpgrade replaces the functions previously performed by the manual Pre-Upgrade Information Tool (preupgrade.jar) in previous releases The -mode clause takes one of three values:
      • analyze: Check your system for readiness to upgrade
      • fixups: Perform fixups as needed on your source Oracle Database release in preparation for upgrade
      • postfixups: Perform fixups on your target Oracle Database release after upgrade is completed.
      • Reports are identical to what the preupgrade.jar originally produced.
  • Starting Oracle Release 21c, Enterprise Manager, DBUA and ORAchk use AutoUpgrade to perform database upgrade readiness.
  • Starting Oracle Release 21c, FPP performs database upgrades using AutoUpgrade
  • Enhanced management of databases using Transparent Data Encryption (TDE)

Reference oracle support Doc id :  2485457.1

Thank you for giving your valuable time to read the above information.
If you want to be updated with all our articles send us the Invitation or Follow us:
Ramkumar’s LinkedIn: https://www.linkedin.com/in/ramkumardba/
LinkedIn Group: https://www.linkedin.com/in/ramkumar-m-0061a0204/
Facebook Page: https://www.facebook.com/Oracleagent-344577549964301
Ramkumar’s Twitter : https://twitter.com/ramkuma02877110
Ramkumar’s Telegram: https://t.me/oracleageant
Ramkumar’s Facebook: https://www.facebook.com/ramkumarram8