环境是12.2.0.1 version, Oracle Data Guard备库今天故障恢复了一下，RMAN恢复后发现备库Alert一直报错，但是备库主库同步一致，数据一致。

2018-07-05T23:42:22.184048+08:00

Errors in file /u01/app/oracle/diag/rdbms/dwjrstdydb/dwjrstdydb/trace/dwjrstdydb_m000_129832.trc:

ORA-01110: data file 7: '/u01/app/oracle/oradata/dwjrstdydb/users01.dbf'

2018-07-05T23:42:22.258112+08:00

Errors in file /u01/app/oracle/diag/rdbms/dwjrstdydb/dwjrstdydb/trace/dwjrstdydb_m000_129832.trc:

ORA-01110: data file 8: '/u01/app/oracle/oradata/dwjrstdydb/dwjrdbpdb/system01.dbf'

2018-07-05T23:42:22.332476+08:00

Errors in file /u01/app/oracle/diag/rdbms/dwjrstdydb/dwjrstdydb/trace/dwjrstdydb_m000_129832.trc:

ORA-01110: data file 9: '/u01/app/oracle/oradata/dwjrstdydb/dwjrdbpdb/sysaux01.dbf'

2018-07-05T23:42:22.406769+08:00

Errors in file /u01/app/oracle/diag/rdbms/dwjrstdydb/dwjrstdydb/trace/dwjrstdydb_m000_129832.trc:

ORA-01110: data file 10: '/u01/app/oracle/oradata/dwjrstdydb/dwjrdbpdb/undotbs01.dbf'

2018-07-05T23:42:22.481081+08:00

Errors in file /u01/app/oracle/diag/rdbms/dwjrstdydb/dwjrstdydb/trace/dwjrstdydb_m000_129832.trc:

ORA-01110: data file 11: '/u01/app/oracle/oradata/dwjrstdydb/dwjrdbpdb/users01.dbf'

参考MOS文档:

ORA-01110 For All Files In Standby Database (文档 ID 2322290.1)

CHANGES

New or Upgraded Standby on 12.2.0.1

CAUSE

Unpublished Bug 24844841 : PHSB:CDB M000 REPORTED ORA-1110 ON ADG WHEN A DATAFILE IS ADDED ON PRIMARY

is logged for error ORA-1110 being reported incorrectly on the Standby database alert log when a datafile change is made on the primary.

The bug is fixed in 19.1.

Backport requests can be made for 12.1 & 12.2

Rediscovery:

=========

Function kcidr_file_header_check_common is File Header check which cause of this issue. If you see this in the Stack Trace and Standby opens Read only successfully then you are most likely encountering this bug.

SOLUTION

To Solve the issue:

Apply fix of Bug 24844841. Please check for backports for your version and operating system.

If patch#24844841 is not available then please open an SR to request.

To Workaround:

Restart the standby database and managed recovery.

特此记录一下，好记性不如烂笔头~