prefixups_hongkong.log

2021-03-09 02:51:56.325 INFO Starting log for hongkong - Utilities.createLogger 
2021-03-09 02:51:56.400 INFO Running fixup [PURGE_RECYCLEBIN][hongkong][PLSQL][PURGE DBA_RECYCLEBIN
/
] - FixUpTrigger.executeFixUp 
2021-03-09 02:51:56.400 INFO Begin [/home/oracle/u03/app/oracle/product/12.2.0/db_1/bin/sqlplus, -silent, /, as, sysdba] - ExecuteProcess.startSqlPlusProcess 
2021-03-09 02:51:56.401 INFO Begin Setting Oracle Environment - ExecuteProcess.startSqlPlusProcess 
2021-03-09 02:51:56.401 INFO [(SQLPATH=/home/oracle/u03/app/oracle/autoupgrade/hongkong/hongkong:/home/oracle/u03/app/oracle/autoupgrade/cfgtoollogs/upgrade/auto/sql), (ORACLE_SID=hongkong), (ORACLE_UNQNAME=hongkong), (ORACLE_PATH=/home/oracle/u03/app/oracle/autoupgrade/hongkong/hongkong:/home/oracle/u03/app/oracle/autoupgrade/cfgtoollogs/upgrade/auto/sql), (ORACLE_BASE=/home/oracle/u03/app/oracle), (TWO_TASK=N/A), (ORACLE_HOME=/home/oracle/u03/app/oracle/product/12.2.0/db_1), (TNS_ADMIN=N/A), (LDAP_ADMIN=N/A), (PERL5LIB=N/A)] - ExecutionEnv.addEnvToProcess 
2021-03-09 02:51:56.401 INFO Starting - ExecuteProcess.setLibsForSqlplus 
2021-03-09 02:51:56.401 INFO Finished - ExecuteProcess.setLibsForSqlplus 
2021-03-09 02:51:56.401 INFO End Setting Oracle Environment - ExecuteProcess.startSqlPlusProcess 
2021-03-09 02:51:56.401 INFO Begin Creating process - ExecuteProcess.startSqlPlusProcess 
2021-03-09 02:51:56.401 INFO End Creating process - ExecuteProcess.startSqlPlusProcess 
2021-03-09 02:51:56.402 INFO Executing SQL [PURGE DBA_RECYCLEBIN
/
] in [hongkong, container:null] - ExecuteSql$SQLClient.run 
2021-03-09 02:51:56.475 INFO # PURGE_RECYCLEBIN - Check.runFix 
2021-03-09 02:51:56.476 INFO Finished fixup [PURGE_RECYCLEBIN][hongkong][SUCCESSFUL] - FixUpTrigger.executeFixUp 

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

upg_summary.log

Oracle Database Release 19 Post-Upgrade Status Tool 03-09-2021 03:31:3
Database Name: HONGKONG

Component                           Current        Full                    Elapsed Time
Name                                Status         Version                 HH:MM:SS

Oracle Server                       UPGRADED       19.3.0.0.0              00:19:26
JServer JAVA Virtual Machine        UPGRADED       19.3.0.0.0              00:01:46
Oracle XDK                          UPGRADED       19.3.0.0.0              00:00:48
Oracle Database Java Packages       UPGRADED       19.3.0.0.0              00:00:09
OLAP Analytic Workspace             UPGRADED       19.3.0.0.0              00:00:16
Oracle Label Security               UPGRADED       19.3.0.0.0              00:00:07
Oracle Database Vault               UPGRADED       19.3.0.0.0              00:00:22
Oracle Text                         UPGRADED       19.3.0.0.0              00:00:30
Oracle Workspace Manager            UPGRADED       19.3.0.0.0              00:00:29
Oracle Real Application Clusters    UPGRADED       19.3.0.0.0              00:00:00
Oracle XML Database                 UPGRADED       19.3.0.0.0              00:01:37
Oracle Multimedia                   UPGRADED       19.3.0.0.0              00:00:40
Spatial                             UPGRADED       19.3.0.0.0              00:05:50
Oracle OLAP API                     UPGRADED       19.3.0.0.0              00:00:10
Datapatch                                                                  00:03:41
Final Actions                                                              00:03:48
Post Upgrade                                                               00:00:19

Total Upgrade Time: 00:37:14

Database time zone version is 26. It is older than current release time
zone version 32. Time zone upgrade is needed using the DBMS_DST package.

Grand Total Upgrade Time: [0d:0h:46m:15s]

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

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

Manual DataGuard Switchover

Switch over:

It is reversal of role between a standby database and a primary database. The primary database assumes role of standby database and the standby database assumes role of primary database after the switchover. There is no data loss in a switchover. This is generally a planned activity.

Overview steps:

Step:1 Check the db name, open mode, database role of the primary and standby databases.

Step:2 select switchover status on primary & standby db.

Step:3 Check that there is no active users connected to the databases.

Step:4 Switch the current online redo log file on primary database and verify that it has been applied in the standby database.

Step:5 Connect with primary database and initiate the switchover.

Step:6 Bounce the primary db and check the switchover status.

Step:7 Then convert the physical standby into primary db.(stop the MRP process)

Step:8 Open the new standby db in read only mode.

Step:9 Apply the redo log files in newly created standby.(start the MRP process).Check whether the logs are applying in the new standby db.

Step:1 Check the db name, open mode, database role of the primary and standby databases.

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

NAME              OPEN_MODE     DATABASE_ROLE
--------- -------------------- ----------------
CANADA            READ WRITE       PRIMARY

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

NAME             OPEN_MODE      DATABASE_ROLE
--------- -------------------- ----------------
CANADA           READ ONLY     PHYSICAL STANDBY

Step:2 Check that there is no active users connected to the databases.

SQL>select osuser, username from v$session;

       OSUSER                                 USERNAME
--------------------------------    -------------------------
       oracle                                  oracle
                                               sys

Step:4 Check the log sequence number in primary and standby db(before switchover).

Step:3 In this step primary db is converted into standby by giving the following command.

SQL>alter database commit to switchover to physical standby with session shutdown;

Database altered

SQL>alter database mount standby database;

Database altered

Step:5 Check name, open_mode, database_role of new standby database.

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

NAME      OPEN_MODE            DATABASE_ROLE    
--------- -------------------- ---------------- 
CANADA   READ ONLY             PHYSICAL STANDBY

Step:6 Then start to apply the redo log (MRP process) on primary(current standby).

SQL>alter database recover managed standby database disconnect from session;

Database altered

Step:7 Check the log sequence number in the current standby.

SQL>  select max(sequence#) from v$archived_log where applied='YES';

MAX(SEQUENCE#)
--------------
            10

Step:8 Now we have to stop the MRP process in old standby.

SQL> alter database recover managed standby database cancel;

Database altered.

Step:9 Conversion of standby to primary db and also check the name, open mode, database role of standby db.

alter database commit to switchover to primary with session shutdown;

Database altered.

Step:10 Check name, open_mode, database_role of new primary database.

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

NAME      OPEN_MODE            DATABASE_ROLE    
--------- -------------------- ---------------- 
CANADA   READ WRITE             PRIMARY

Switch over activity has been completed successfully…..!!!

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

Reinstate Failed Primary into Physical Standby

REINSTATE:

After failover we have to reinstate the primary db to physical standby. For that we have to find out the scn  in the new primary db- (standby_became_primary_scn parameter from v$database) where at the particular scn the standby database has became the primary database. Using this scn in our old primary db we have to flashback our db to this particular scn and then we have to convert our old primary to physical standby.

Note: To perform the reinstate process we have to ensure that the flashback must be enabled in the primary db which got crashed.

Overview Steps:

Step:1 Find out the standby_became_primary_scn value in the new primary db from v$database view.

Step:2 Flashback the old primary db to this particular scn value that is taken from the new primary db.

Step:3 Then convert the primary db to physical standby and bounce the database.

Step:4 Check for the name, open_mode, database_role it is changed to physical standby, we have performed the reinstate task successfully.

Step;5 verify whether the standby is in sync with the primary after reinstate.

Step:1 Get the value of standby_became_primary_scn from the new primary db.

Step:2 Flashback the old primary db to this scn value.

Step:3 Convert the primary db into physical standby, then bounce the database.

Step:4 Now the database_role has changed from primary to physical standby, reinstate  performed successfully.

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

 

Reinstate Failed Primary into Physical Standby

REINSTATE:

After failover we have to reinstate the primary db to physical standby. For that we have to find out the scn  in the new primary db- (standby_became_primary_scn parameter from v$database) where at the particular scn the standby database has became the primary database. Using this scn in our old primary db we have to flashback our db to this particular scn and then we have to convert our old primary to physical standby.

Note: To perform the reinstate process we have to ensure that the flashback must be enabled in the primary db which got crashed.

Overview Steps:

Step:1 Find out the standby_became_primary_scn value in the new primary db from v$database view.

Step:2 Flashback the old primary db to this particular scn value that is taken from the new primary db.

Step:3 Then convert the primary db to physical standby and bounce the database.

Step:4 Check for the name, open_mode, database_role it is changed to physical standby, we have performed the reinstate task successfully.

Step;5 verify whether the standby is in sync with the primary after reinstate.

Step:1 Get the value of standby_became_primary_scn from the new primary db.

Step:2 Flashback the old primary db to this scn value.

Step:3 Convert the primary db into physical standby, then bounce the database.

Step:4 Now the database_role has changed from primary to physical standby, reinstate  performed successfully.

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

 

Oracle 19c Binaries and Database installation

Here , I am going to install 19c binaries database software, but I already moved the 19c software to my VM and i also unzipped it. Just I am running the ./runInstaller file as a oracle user.

Follow the steps to install 19c database software,

Step:1 in this window choose Set up Software only option and click Next. It means that we are only installing the software.

 

 

 

Step:2 The second page asks for whether we are installing single instance database or RAC Installation, choose single instance db installation and click Next.

Step:3 Here we have to choose the type of the edition we are going to install,either Enterprise edition or Standard Edition 2,choose Enterprise edition and click Next.

 

Step:4 Then it asks for Oracle base location, choose ‘/u01/app/oracle’ as location and then click Next.

 

Step:5 Choose inventory location(/u01/app/oraInventory) and oraInventory group as oinstall.

 

Step:6 in this window select OSDBA , OSOPER , OSBACKUPDBA , OSDGDBA , OSKMDBA , OSRACDBA group as oinstall and proceed further.

Step:7 It shows for root script execution configuration ,here don’t choose any of the option go to the next window.

Step:8 This window asks to perform the prerequisite checks, for us two of the checks completed with warning. click Next.

Step:9 Yes we have completed all the steps this is the summary page of our software installation, check the details if it is correct proceed further.

Step:10 Our 19c software installation is in progress.

Step:11 When the software is in progress,you have to run the following two scripts as “root” user.

Step:12 The oracle 19c software was installed successfully.

Step:13 Previously we have installed the 19c software, we are proceeding with the database creation. Using dbca create the database, choose create a database option and click Next.

Step:14 In this window choose advanced configuration.

Step:15 choose database type as oracle single instance database and you have to choose a template for your database. here I choose general purpose or transaction processing as a template for my db.

Step:16 In this specify the global database name and Sid ,it is nothing but the name you give to your database.

Step:17  We have to choose the attributes for your database, either we can use default storage attributes or you can specify the customized attributes.

Step:18 you have to enable the Fast Recovery Area option it is used to recover your database, then click Next.

Step:19 create a new listener, enter the listener name and port number for your listener, it very important to configure a listener for your db.

Step:20 configure the oracle data vault option if you want. it helps us to protect our application data by providing powerful security controls.

Step:21 it asks for storage option either we want to use ASMM or MSMM.I am choosing Automatic Shared Memory Management and set the required SGA,PGA values.

Step:22 select use Unicode (AL32UTF8) character set and choose National character set, default language, default territory as follows,

National character set :AL16UTF16

Default language: American

Default territory: United states

Step:23 Select the management option as ‘configure Enterprise Manager (EM) database express check box.

Step;24 Create the password credentials for your db, here I use the same administrative passwords for all accounts.

Step:25 We have completed all the above mentioned configurations, we have yet one more step left to create a database. Choose the create database check box.

Step:26 check with all the configurations are correctly configured and proceed further.

Step:27 After that the database creation is in progress.

Step:28 we have successfully completed the database and we can now connect to our database. Here I have connected to my db and checked the name, open_mode of my database.

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

Convert Physical standby to Logical standby Database

 

Overview Steps:

Step:1 verify the name, open mode, roles in primary and standby databases.

Step:2 Look into the max(sequence#) value from v$thread view on both sides.

Step:3 Check for unsupported datatypes in logical standby in primary db.

Step:4 Find the tables without unique identifier in primary database.

Step;5 At Primary Database, Build a Log Miner in redo data So that sql apply can Interpret the redo changes.

Step:6 Enable the log _archive_dest_3 parameter for primary db.

Step:7 logical supplemental is automatically enabled by executing this, if not already enabled.

Step:8 Cancel recovery at Physical Standby Database.

Step:9 Create a spfile and then mount the database. In order to create logical standby at the mount stage.

Step:10 Enable the log _archive_dest_3 parameter for standby db.

Step:11 Open the database with reset log option.

Step:12 Then start the logical recovery.

Step:13 verify the database has been converted to logical standby databases.

Step:1 Check name, open_mode, database_role of primary and standby databases.

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

NAME             OPEN_MODE      DATABASE_ROLE
--------- -------------------- ----------------
CANADA           READ ONLY      PHYSICAL STANDBY

Step:2 Verify the max(sequence#)  from v$thread view on both the sides, it should have same max(sequence#) value.

on primary side

SQL> select max(sequence#) from v$thread;

MAX(SEQUENCE#)
--------------
     24

on standby side

SQL> select max(sequence#) from v$thread;

MAX(SEQUENCE#)
--------------
     24

Step:3 Check for unsupported datatypes in logical standby in primary db and Find the tables without unique identifier in primary database.

Step:4 execute dbms_logstdby.build,While executing this,logical supplemental is automatically enabled,if not already enabled and also enable the log_archive_dest_3 parameter.

SQL>execute dbms_logstdby.build;

PL/SQL Procedure successfully completed.

Step:5 Cancel recovery at physical standby database.

SQL>alter database recover managed standby cancel;

Database altered

Step:6 start the db at mount stage and issue the following command to convert the physical standby to logical standby.

SQL>alter database recover to logical standby standby;

Database altered

Step:7 open the database with resetlog option.

SQL>alter database open resetlogs;

Database altered

Step:8 perform the logical recovery.

SQL>alter database start logical standby apply immediate;

Database altered

Step:9 check whether database role of db has changed from physical standby to logical standby.once it is altered it is clear that we have successfully converted our physical standby into logical standby.

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

  NAME            DATABASE_ROLE
---------     -------------------- 
 CANADA          LOGICAL STANDBY

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

Converting a physical standby database into snapshot standby database

What is snapshot standby database?

It allows to perform read-write operation on the standby database.ie converting the physical standby to snapshot standby database. On that, we can do all types of testing or it can be used as a development database. After our testing process is over we can convert our snapshot standby database in to physical standby database and changes done to the snapshot standby will be reverted.

A snapshot standby database receives and archives redo data but it does not apply the redo data from the primary database.

NOTE: FRA (Fast Recovery Area) must be configured in physical standby database but it is not necessary to have flashback enabled.

Overview steps:

Step:1 verify open_mode, database_role of the standby db it should be in read only with apply, physical standby

Step:2 cancel the recovery process(MRP)

Step:3 Enable the flashback_mode in standby, it can be enabled after specifying the location of the db_recovery_file_dest (db recovery area)

Step:4 Then we can convert our physical standby to snapshot standby database.

Step:1 check the open_mode, database_role of the database.

SQL> select open_mode from v$database;

OPEN_MODE
--------------------
READ ONLY WITH APPLY

SQL> select database_role from v$database;

DATABASE_ROLE
----------------
PHYSICAL STANDBY

Step:2 we must stop the redo apply process using the following command.

SQL> alter database recover managed standby database cancel;

Database altered.

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

SQL> startup mount
ORACLE instance started.
Total System Global Area     243268216 bytes
Fixed Size                     8895096 bytes
Variable Size                180355072 bytes
Database Buffers              50331648 bytes
Redo Buffers                   3686400 bytes
Database mounted.

Step:3 Enable the flashback to convert it into snapshot standby database.

SQL> alter database flashback on;

Database altered.

SQL> show parameter db_recovery_file_dest

NAME                                 TYPE                  VALUE
--------------------------------   -----------    ------------------------------
db_recovery_file_dest              string       /u01/app/oracle/fast_recovery_area/  
db_recovery_file_dest_size         big integer            8256M
SQL> select database_role from v$database;

DATABASE_ROLE
----------------
PHYSICAL STANDBY

SQL> select status from v$instance;

STATUS
------------
MOUNTED

Step:5 Convert the physical standby to snapshot standby using below command.

SQL> alter database convert to snapshot standby;

Database altered

Step:6 Mount the db and open it.

SQL> select open_mode from v$database;

OPEN_MODE
--------------------
MOUNTED

SQL> alter database open;

Database altered.

Step:7 select the name of the restore point, gurantee_flashback_database information’s from v$restore_point view, where gurantee_flashback_database parameter tells that whether flashback log files will be kept to ensure a flashback to this point.

SQL> select NAME,GUARANTEE_FLASHBACK_DATABASE from v$restore_point;

   NAME                                                      GUA

----------------------------------------------------  ----------------
  SNAPSHOT_STANDBY_REQUIRED_02/18/2021 01:27:55              YES


Step:8 check the role of the  db whether it has converted into snapshot standby.

SQL> select database_role from v$database;

DATABASE_ROLE
----------------
SNAPSHOT STANDBY

Step:9 Now I am performing some DML operations, creating a table student and adding 100000 rows in it.

SQL> create table student(id number(5));

Table created.

SQL> begin
for i in 1 .. 100000 loop
insert into student values(1);
end loop;
end;

PL/SQL procedure successfully completed.

SQL> select count(*) from student;

COUNT(*)
----------
100000

SQL> commit;
Commit complete.

SQL> shut immediate

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

SQL> startup mount
ORACLE instance started.

Total System Global Area      243268216 bytes
Fixed Size                      8895096 bytes
Variable Size                 180355072 bytes
Database Buffers               50331648 bytes
Redo Buffers                    3686400 bytes
Database mounted.

Step:10 Converting snapshot standby db to physical standby.

SQL> alter database convert to physical standby;

Database altered.
SQL> select database_role,open_mode from v$database;

DATABASE_ROLE        OPEN_MODE
---------------- --------------------
PHYSICAL STANDBY      MOUNTED

SQL> select status from v$instance;

STATUS
------------
MOUNTED

SQL> shut immediate

ORA-01109: database not open

Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.

Total System Global Area     243268216 bytes
Fixed Size                     8895096 bytes
Variable Size                180355072 bytes
Database Buffers              50331648 bytes
Redo Buffers                   3686400 bytes
Database mounted.
Database opened.
SQL> select open_mode from v$database;

OPEN_MODE
--------------------
READ ONLY

Step:11 Hence we converted our snapshot standby to physical standby, the DML operations that we have done in snapshot standby cannot be retrieved here.

SQL> select * from student;
select * from student
*
ERROR at line 1:
ORA-00942: table or view does not exist

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