Standby database max availability..delay of committed changes at primary

Question

Hi,
I have setup a single instance physical standby database for a 3 node RAC primary database (10.2.0.3 on Solaris 10).
The log_archive_dest_2 is set as "SERVICE=SDSMK LGWR SYNC AFFIRM NET_TIMEOUT=30 VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=SDSMK"
at the primary db.
The primary database is running in Maximum availability mode.
The query "select protection_mode from v$database" gives "MAXIMUM AVAILABILITY" on both primary and standby databases.
Now I performed an insert into a table at primary db, COMMITTed the update and issued "ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL" at standby. I could not see the above added row in the table at standby. If I understand correctly, since the standby db is up, the network link is up and all the managed standby processes are up, the change should have been propogated at the standby aswell. Did I miss anything? Also how can I find how long the standby database is lagging interms of committed transactions at primary db?
Thanks,
Sreekanth

Answer 1

on primary:
SQL> insert into sds.test1 values(17);
1 row created.
SQL> commit;
Commit complete.
SQL> SELECT THREAD#, MAX(SEQUENCE#) FROM V$LOG_HISTORY GROUP BY THREAD# order by thread#;
THREAD# MAX(SEQUENCE#)
1 660
2 849
3 619
SQL> select current_Scn from v$database;
CURRENT_SCN
719552723
SQL>
on standby:
SQL> SELECT THREAD#, MAX(SEQUENCE#) FROM V$LOG_HISTORY GROUP BY THREAD# order by thread#;
THREAD# MAX(SEQUENCE#)
1 660
2 849
3 619
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> SELECT THREAD#, MAX(SEQUENCE#) FROM V$LOG_HISTORY GROUP BY THREAD# order by thread#;
THREAD# MAX(SEQUENCE#)
1 660
2 849
3 619
SQL> alter database open;
Database altered.
SQL> the change in test1 table is not seen here.