How to Resolve ORA-1578 /ORA-26040 Nologging operation in 12.2 on Standby database
(Doc ID 2378500.1)
Last updated on AUGUST 07, 2020
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
This Article is Useful for Customer who don't want the Primary database to be in Force logging mode in Primary- Standby configuration and would want to have to their application perform certain No logging operation to have some performance benefit at the same time ensure that Standby database doesn't get affected By No logging Corruption Message.
A Nologging operations indicates that a DML operations like Insert/update/dlete have not been logged into the redo logfile.
If Force logging is not enabled on Primary database ,when MRP is run on Standby database and it comes across
no logging operation it will mark the Block as Corrupt and proceed with the recovery.When Such blocks are
accessed it reports the Ora-1578/ORA-26040.
12.2 new Feature allows us to recover such no logging operations using Rman command ,without having to restore a fresh copy of datafile from primary or Enabling Force logging on Primary database.
This can be achieved by using the new Rman command
RMAN>RECOVER DATABASE NONLOGGED BLOCK
This document explains the steps for the same.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document