OracleBackup & recovery

Corrupt blocks found by RMAN

Blocks RMAN has flagged as corrupt. The view is filled by backups and by RMAN VALIDATE, so run a validate first if you haven't recently.

Not yet verified. How scripts are tested

1-- Refresh the list first (in RMAN):2--   RMAN> VALIDATE CHECK LOGICAL DATABASE;3 4CLEAR COLUMNS5SET LINESIZE 100 PAGESIZE 100 TRIMOUT ON TAB OFF6COLUMN file#           HEADING "FILE#"  FORMAT 999997COLUMN block#          HEADING "BLOCK#" FORMAT 99999999998COLUMN blocks          FORMAT 999,9909COLUMN corruption_type HEADING "TYPE"   FORMAT A1210 11SELECT file#, block#, blocks, corruption_type12FROM v$database_block_corruption13ORDER BY file#, block#;

Save it as ora-corruption.sql and run it with SQL> @ora-corruption.

Open in denrepoRelated tool: RMAN command builder

Helps with

• ORA-01578: ORACLE data block corrupted (file # %s, block # %s)
• ORA-08102: index key not found, obj# %s, file %s, block %s (%s)

More Oracle scripts: Backup & recovery

• RMAN backup history with run time in hoursRun in the target database as SYSDBA, not the recovery catalog. The first report lists every RMAN job (full, incremental and archivelog) with start,…
• RMAN backup jobs in the last 7 daysStatus, duration and output size of each RMAN job, newest first.
• Running RMAN job progressPercent complete and time remaining for each RMAN channel that's working right now.
• Datafiles without a recent backupDatafiles with no backup of any kind in the last two days, or none at all. A new datafile added after the last full backup shows up here first.
• RMAN configuration (non-default settings)The persistent CONFIGURE settings stored in the control file, the same list SHOW ALL marks as changed. Check retention and control file autobackup…
• Fast Recovery Area usageFRA size, used and reclaimable space, then what's using it by file type. Real used % is the number that matters: at 100% the database stops archiving…