My Oracle Support Banner

ORA-1578 / ORA-26040 Corrupt blocks by NOLOGGING - Error explanation and solution (Doc ID 794505.1)

Last updated on AUGUST 04, 2018

Applies to:

Oracle Database - Enterprise Edition - Version 7.1.6.0 to 12.2.0.1 [Release 7.1.6 to 12.2]
Information in this document applies to any platform.

Purpose

This note is intended to describe how Oracle reports a corruption caused by a NOLOGGING operation with ORA-1578 / ORA-26040 and how to fix the errors.

IMPORTANT

When ORA-26040 is not produced along with ORA-1578 the block is then corrupt by a different reason and RMAN Block Media Recovery can be used to repair the corruption. Refer to Doc ID 1578.1

 

Scope

This document is intended for Customers and Oracle Support.

Details

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
Purpose
Scope
Details
 DATAPUMP parameter DISABLE_ARCHIVE_LOGGING
 RMAN/DBV and Corrupt Blocks by NOLOGGING
 Monitoring NOLOGGING Operations
 Identify when a block was marked as NOLOGGING
 NOARCHIVELOG and NOLOGGING in SYSAUX tablespace / AWR, EM, etc
 Changes by RDBMS versions
 
 SOLUTION
 Is error after RMAN DUPLICATE?
 Is error produced in a PHYSICAL STANDBY Database?
 Identify the affected segment
 Is it a FREE Block?
 Is it an INDEX?
 Is it a TABLE?
 Is it a LOB?
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.