Troubleshooting Standby database recover failed with ORA-19906 ORA-10576 ORA-19909
常常有客户配置oracle dataguard 1对多或级连(cascade) standby， 当需要一个测试环境时，通常考虑拿一个standby激活或snapshot dg，但如果在激活为可读写数据库时(Failover)，如果提前DG参数没有清理，可能导致剩余standby database无法继续应用日志，这里简单记录。
ORA-01110
Troubleshooting ORA-01578 ORA-01110 ORA-26040 NOLOGGING corrupted block
The following errors have recently occurred in our database( Oracle 19c RAC):
ORA-01578: ORACLE data block corrupted (file # xxx, block # yyyyy)
ORA-01110: data file xxx: ‘xxxxxxxxxxxxxxxxx.dbf’
ORA-26040: Data block was loaded using the NOLOGGING option
如何修复ORA-01111, ORA-01110, ORA-01157 errors on Standby database
在oracle DATAGUARD环境，STANDBY_FILE_MANAGEMENT 参数控制standby database的文件管理。当启用自动备用文件管理时(AUTO)，Primary数据库上的操作系统文件添加和删除将在备用数据库上复制。将此参数设置为MANUAL可能会导致MRP进程crash，也可能因为备库的映射错误或磁盘空间不足等原因，中止应用产生gap, 在standby db 的alert日志中可以发现备用数据库出现ORA-01111、ORA-01110、ORA-01157错误，备数据库中创建的文件为UNNAMED or MISSING的文件名。 下面记录修复方法. 错误日志 Errors in file /u01/app/oracle/diag/rdbms/orclstdy/orclstdy/trace/orclstdy_mrp00_11317.trc: ORA-01111: name for data file 11 is unknown – rename to correct file ORA-01110: data file 11: ‘/u01/app/oracle/product/11.2.0.4/db/dbs/UNNAMED00011’ ORA-01157: cannot identify/lock data file 11 – see DBWR trace file ORA-01111: name for data file 11 is unknown – rename to … Read more