OraEasy

Introduction This is the second post in our four-part series on upgrading Oracle Database from 12c to 19c. We previously covered the GUI-driven Upgrade Using DBUA . This time, we'll do the same upgrade by hand: starting the 19c instance in UPGRADE mode ourselves, running dbupgrade directly, and working through the catalog scripts and timezone fixups without a wizard managing the sequence for us. Methods of Upgrade As a reminder, Oracle supports four approaches for this upgrade: Using DBUA (Database Upgrade Assistant) Using the manual method Using autoupgrade.jar Using RMAN and catctl.pl The manual method takes more hands-on steps than DBUA, but it gives full visibility into every phase, which is useful when you want to understand exactly what the upgrade is doing, or when DBUA isn't available in a given environment. Prerequisites 12c binary installed with the database. 19c binary installed without a database. Sufficient disk space for tablespace and archiv...

Introduction Failover occurs when the primary database is completely lost or becomes inaccessible. In such events, the standby database is promoted to serve as the new primary to ensure service continuity. The original primary does not automatically transition to a standby role, particularly if it is damaged or unrecoverable. If Flashback Database is not enabled on the original primary, it becomes necessary to re-create the primary database from scratch, using a method such as RMAN Duplicate. Prerequisites Oracle Data Guard should already be configured between the primary and standby. This guide assumes the primary database is completely lost. Environment Used in This Guide Server Primary Standby Hostname Source Target IP 192.168.80.51 192.168.80.111 OS OEL 9 OEL 9 SID ORCLDC ORCLDR Service Name ...