AutoConfig Is Failing With Data File Corruption After Database Recovery
Last updated on JUNE 21, 2016
Applies to:Oracle Applications Technology Stack - Version 184.108.40.206 to 12.1.3 [Release 11.5.10 to 12.1]
Information in this document applies to any platform.
On : 12.1.1 version, Database for Application Technology
When attempting to run autoconfig for a database recovered from crash using archive logs, the following error occurs.
The database alert log shows :
ORA-01578: ORACLE data block corrupted (file # xxx, block # xxxxxx)
ORA-01110: data file xxx: '/datafile/apps_ts_tx_data*.dbf'
ORA-26040: Data block was loaded using the NOLOGGING option
The related database trace files shows :
dbkedDefDump(): Starting incident default dumps (flags=0x2, level=3, mask=0x0)
----- Current SQL Statement for this session (sql_id=xxx) -----
UPDATE FND_OAM_CONTEXT_FILES SET PATH = :B1 , LAST_SYNCHRONIZED = SYSDATE, TEXT = :B4 , LAST_UPDATE_DATE = SYSDATE, LAST_UPDATED_BY = FND_GLOBAL.USER_ID, LAST_UPDATE_LOGIN = FND_GLOBAL.LOGIN_ID, NODE_NAME = :B2 , VERSION = :B3 , STATUS = 'S' WHERE (NODE_NAME = :B2 AND PATH = :B1 AND NAME NOT IN ('METADATA', 'TEMPLATE') AND (STATUS IS NULL OR UPPER(STATUS) IN ('S','F'))) OR (PATH = :B1 AND NAME IN ( 'METADATA', 'TEMPLATE'))
Database recovered from crash using archive logs
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms