ORA-01578 Encountered while Recovering Transaction on Object
(Doc ID 2470377.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.3 and laterInformation in this document applies to any platform.
Symptoms
Alert log shows below error even after doing dbms_repair.
SMON: Restarting fast_start parallel rollback
SMON: ignoring slave err,downgrading to serial rollback
ORACLE Instance ADMINQA (pid = 13) - Error 1578 encountered while recovering transaction (1, 24) on object 78160.
Errors in file /opt/oracle/diag/rdbms/adminqa/ADMINQA/trace/ADMINQA_smon_26586.trc:
ORA-01578: ORACLE data block corrupted (file # 5, block # 1714977)
ORA-01110: data file 5: '/opt/oracle/oradata2/ADMINQA/admnq2_data_01.dbf'
Wed Sep 05 15:51:10 2018
Dumping diagnostic data in directory=[cdmp_20180905155110], requested by (instance=1, osid=26586 (SMON)), summary=[abnormal process termination].
1.
BEGIN
DBMS_REPAIR.ADMIN_TABLES (
TABLE_NAME => 'REPAIR_TABLE',
TABLE_TYPE => dbms_repair.repair_table,
ACTION => dbms_repair.create_action,
TABLESPACE => 'USERS');
END;
/
2.
SET SERVEROUTPUT ON
DECLARE num_fix INT;
BEGIN
num_fix := 0;
DBMS_REPAIR.FIX_CORRUPT_BLOCKS (
SCHEMA_NAME => 'ADMNQ2',
OBJECT_NAME=> 'A_UPC_KROGER',
OBJECT_TYPE => dbms_repair.table_object,
REPAIR_TABLE_NAME => 'REPAIR_TABLE',
FIX_COUNT=> num_fix);
DBMS_OUTPUT.PUT_LINE('num fix: ' || TO_CHAR(num_fix));
END;
/
3.
BEGIN
DBMS_REPAIR.SKIP_CORRUPT_BLOCKS (
SCHEMA_NAME => 'ADMNQ2',
OBJECT_NAME => 'A_UPC_KROGER',
OBJECT_TYPE => dbms_repair.table_object,
FLAGS => dbms_repair.skip_flag);
END;
/
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 |