OraEasy

Introduction Oracle 19c is the Long-Term Support (LTS) release in Oracle's database roadmap, so with 12c now past its extended support window, upgrading is less optional than it used to be. Beyond staying supported, 19c brings performance and stability improvements that make the move worthwhile on its own. This is the first post in a four-part series covering the ways to get a database from 12c to 19c, starting with the most common route: DBUA. Methods of Upgrade Across this series, we'll cover four ways to perform the upgrade: Using DBUA (Database Upgrade Assistant) Using the manual method Using autoupgrade.jar Using RMAN and catctl.pl DBUA is the GUI-driven option and the one most DBAs reach for first, since it handles prechecks, fixups, and the catalog upgrade through a single wizard with minimal manual intervention. This article walks through that path step by step. Prerequisites 12c binary installed with the database. 19c binary installed without a datab...

Introduction In the previous posts, we covered the installation of Oracle GoldenGate (OGG) and the database configuration for both Oracle and MySQL environments. If you haven't gone through those yet, the links are below. Oracle GoldenGate 23ai Installation for Oracle Oracle GoldenGate 23ai Installation for MySQL Prepare Database for GoldenGate Replication This is the final post in the series. Here we'll configure Extract and Replicat for real-time replication from Oracle to MySQL. We'll cover four parts: Extract configuration Distribution Path Initial load using csvsql Replicat configuration Prerequisites Oracle GoldenGate software installed on both the source and target servers. Database configuration for GoldenGate completed on the source and target databases. Environment Used in This Guide Server Source (Oracle) Target (MySQL) OGG (Oracle) OGG (MySQL) Hostname orcl.oraeasy.c...

Introduction Oracle Data Guard (ODG) is a high-availability, disaster recovery, and data protection feature provided by Oracle Database. It ensures the availability of critical data by maintaining one or more synchronized standby databases as replicas of a primary database. These standby databases can be used for disaster recovery, reporting, or backups, minimizing downtime and data loss in the event of unexpected failures. This is the third guide in our standby database setup series. We've already covered the manual RMAN backup and restore method and the RMAN Duplicate for standby method . This guide covers a third approach: restoring the standby directly from the primary's service using individual RMAN restore ... from service commands, rather than one combined DUPLICATE statement. Like RMAN Duplicate, this streams data live over the network from the primary rather than through staged backup files, so it's best suited for smaller databases with good network bandwid...