R12.2 Apps DBA. Powered by Blogger.

Release 12.2 ORA-01578: ORACLE data block corrupted

No comments :
ERROR
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'))
Block corruption after database recovery in table FND_OAM_CONTEXT_FILES due to nologging operations,
that reported the error ORA-01578: ORACLE data block corrupted (file # xxx, block # xxxxxx) in the alert.log file.
Solution:
1. sqlplus apps
SQL> EXEC FND_CONC_CLONE.SETUP_CLEAN;
SQL> COMMIT;
SQL> EXIT;
2. Run AutoConfig on all tiers, first on the DB tiers and then on the APPS tiers, to repopulate the required system tables.

No comments :

Post a Comment

Note: only a member of this blog may post a comment.