ORA-16829: fast-start failover configuration is lagging
Cause: The fast-start failover target standby database was not within the lag limit specified by the FastStartFailoverLagLimit configuration property. As a result, a fast-start failover could not happen in the event of a primary database failure.
Action: Ensure that the fast-start failover target standby database is running and applying redo data and that the primary database is successfully trasmitting redo data. If this condition persists consider raising the value of the FastStartFailoverLagLimit configuration property.
Oracle ORA-16829将出现，如果数据库实例尝试进行快速启动故障转移，但相关配置步骤未能成功完成。
1.检查Fast-Start Failover配置是否正确。
2.单步运行Fast-Start Failover配置过程，尝试解决错误。
3.检查Cluster Synchronization Service的状态。
4.检查网络和节点之间的同步。
5.重新运行Fast-Start Failover配置脚本，重新配置Fast-Start Failover。
6.检查相关的系统变量，检查连接的检查点是否匹配。
7.如果检查点不匹配，尝试恢复数据库到所需的检查点。
8.重新检查并调整系统时区和系统时间。
9.重新运行系统检查点配置默认值脚本。