RMAN Reports an ORA-19566: Exceeded Limit Of 0 Corrupt Blocks From Backup And No Segment Associated
(Doc ID 457422.1)
Last updated on SEPTEMBER 16, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 9.2.0.1 and laterOracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
1. Attempting a backup using RMAN, you receive the following error,
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ch1 channel at 09/01/2007 19:38:44
ORA-19566: exceeded limit of 0 corrupt blocks for file /<path>/<datafilename>.dbf
2. Performing an DBV on the above file shows a corrupt block.
dbv file=/<path>/<datafilename>.dbf blocksize=16384
DBVERIFY: Release 9.2.0.4.0 - Production on Thu Aug 30 18:06:59 2007
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
DBVERIFY - Verification starting : FILE = /<path>/<datafilename>.dbf
Page 91880 is influx - most likely media corrupt
***
Corrupt block relative dba: 0x048166e8 (file 18, block 91880)
Fractured block found during dbv:
Data in bad block -
type: 0 format: 0 rdba: 0x00000000
last change scn: 0x0000.00000000 seq: 0x0 flg: 0x00
consistency value in tail: 0x00000001
check value in block header: 0x0, block checksum disabled
spare1: 0x0, spare2: 0x0, spare3: 0x0
***
DBVERIFY - Verification complete
Total Pages Examined : 128000
Total Pages Processed (Data) : 10475
Total Pages Failing (Data) : 0
Total Pages Processed (Index): 1154
Total Pages Failing (Index): 0
Total Pages Processed (Other): 645
Total Pages Processed (Seg) : 0
Total Pages Failing (Seg) : 0
Total Pages Empty : 115725
Total Pages Marked Corrupt : 1
Total Pages Influx : 1
Please note Page number (One which is highlighted) reported in dbverify output at the start is the Oracle block number having the corruption.
3. The following SQL statement is executed to determine that there is no segment associated
SELECT tablespace_name, segment_type, owner, segment_name
FROM dba_extents
WHERE file_id = 18
and 91880 between block_id AND block_id + blocks - 1;
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |