DB-Switch does not work due to ORA-26040: Data block was loaded using the NOLOGGING option'

book

Article ID: 194280

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine CA Automic One Automation CA Automic Operations Manager CA Automic Oracle

Issue/Introduction

DB-Switch does not work due to ORA-26040: Data block was loaded using the NOLOGGING option'


Tried to switch over from active to standby. AWA did not start. Error-message:
20200619/095632.920 - U00003590 UCUDB - DB error: 'OCIStmtFetch', 'ERROR   ', '', 'ORA-01578: ORACLE data block corrupted (file # 5, block # 2220)
ORA-01110: data file 5: '/u08/oradata/GCHCAT_LUP/datafile/o1_mf_uc4_inde_gb6b8fo6_.dbf' 
ORA-26040: Data block was loaded using the NOLOGGING option' 
20200619/095632.921 - U00003410 Server 'GCH_TEDE#WP' version '12.2.2+hf.2.build.1551802534314' ended abnormally. 


Environment

Release : 12.2

Component : AUTOMATION ENGINE

Resolution

ORA-01578: This error is related to Disk corruption where oracle is installed . Oracle has some tools to correct this and you need to check with your DBA. Tools like dmbs repair or DBA has to find the corrupted block belonging table. Export and import this table to resolve the problem. There is no process or tool available from Automic side to correct this. 

ORA-26040 occurred because the automic table or index was loaded using the nologging option and recovered later due to above corruption .