Skip to main content

Posts

Reinstate old Primary Database after Failover

Introduction: Reinstating an old primary database after a failover involves transforming the old primary which may have been disabled or fallen out of sync, into a working standby database again. This process, often performed using Flashback Database or managed through DGMGRL, enables it to realign with the new primary without requiring a full database rebuild. In this article, we will Reinstate old primary database after the failover. Methods to reinstate: Using Flashback Database. Using Data Guard Broker (DGMGRL). Prerequisites: Flashback Database must be enabled on the old primary. Flashback logs must be available covering the failover point. Standby redo log should exist. Old Primary must not be opened in R/W after failover. DG broker should be configured (for DGMGRL method). Environment: Source Database Hostname oradbdc.oraeasy.com SID oradbdc Database Vers...

Oracle Restart || Standalone database with ASM

Introduction: Oracle Restart is a high-availability feature of Oracle Grid Infrastructure for standalone servers that automatically restarts Oracle Database components, such as the database instance, listener, and Oracle Automatic Storage Management, after hardware or software failures, or following a server reboot. In this article, we will see how to install the Oracle Restart 19c step by step. Prerequisites: Below are the minimum requirements for Linux environment. CPU - 2core RAM - 8GB Disk space - 45GB (/u01) Raw Disk storage - 50GB (For ASM disks) Grid and Databse binary. Download here. Must have root user or sudo access. Disable the firewall. Environment: Hostname orares.oraeasy.com OS OL 7.3 Grid/Database Version 19c (19.3) Grid Home /u01/app/grid/19c/grid_1 Database Home /u01/app/oracle/19c/db_1 ASM SID +ASM ...