Monday, September 7, 2009

How to: ORA-16817: unsynchronized Fast-Start Failover configuration


DG 2009-09-04-13:29:19 0 2 0 RSM0: HEALTH CHECK WARNING: ORA-16817: unsynchronized Fast-Start Failover configuration
DG 2009-09-04-13:29:19 0 2 696687836 Operation CTL_GET_STATUS continuing with warning, status = ORA-16817
DG 2009-09-04-13:29:19 0 2 696687836 Operation CTL_GET_STATUS continuing with warning, status = ORA-16817



There is no much information could be found on metalink for this error code, but from the error message, valuable information is available from Oracle Documentation:

ORA-16817: unsynchronized Fast-Start Failover configuration
Cause: The Fast-Start Failover target standby database was not synchronized with the primary database. As a result, a Fast-Start Failover could not happen automatically in case of a primary database failure.
Action: Ensure that the Fast-Start Failover target standby database is running and that the primary database can ship redo logs to it. When the standby database has received all of the redo logs from the primary database, the primary and standby databases will then be synchronized. The Data Guard configuration may then failover automatically to the standby database in the event of loss of the primary database.

This can be confirmed by checking "v$archived_log".




SQL> select SEQUENCE# ,APPLIED,STATUS from v$archived_log
2 where first_time > sysdate -4/24;


SEQUENCE# APP S
---------- --- -
16 YES A
17 NO A
17 YES A
18 NO A
18 YES A
19 YES A
20 YES A
29 NO A
24 NO A
25 NO A
26 NO A

SEQUENCE# APP S
---------- --- -
27 NO A
28 NO A
30 NO A
39 NO A
40 NO A
41 NO A
42 NO A
43 NO A
44 NO A
45 NO A
46 NO A

SEQUENCE# APP S
---------- --- -
47 NO A
48 NO A