Change did not propagate to Standby

Question

Hi,
Recently I re-sized my UNDO & TEMP tablespaces (created a new tablespace and deleted the old one) on a 4-Node cluster database running on Linux x64 with 10.2.0.4. This is a production database configured with a 4-Node Standy (with same configuration). Surprisingly, the change was implemented on the Primary cluster, but it did not propagate to the Standby. Any idea why!?
I clearly remember from before, that when I deleted a normal tablespace from the Primary cluster, it got deleted from Standby cluster as well. But this time the change did not implement.
Thanks in advance,
Arindam

Answer 1

We have ASM Storage system. And yup, the configuration is identical @ the PRIMARY & STANDBY end (both are 4-node RHEL Cluster running 10.2.0.4 RDBMS).
Ravi - Below is the result of your queries.
STANDBY:_
SQL> select inst_id,process,status,thread#, sequence# from gv$managed_standby;
INST_ID PROCESS STATUS THREAD# SEQUENCE#
1 ARCH CLOSING 4 37059
1 ARCH CLOSING 4 37060
1 MRP0 WAIT_FOR_LOG 3 21524
4 ARCH CLOSING 4 37061
4 ARCH CLOSING 3 21521
3 ARCH CLOSING 1 25087
3 ARCH CLOSING 4 37063
3 RFS IDLE 1 25088
2 ARCH CLOSING 3 21523
2 ARCH CLOSING 2 17502
2 RFS IDLE 0 0
INST_ID PROCESS STATUS THREAD# SEQUENCE#
2 RFS IDLE 0 0
2 RFS IDLE 0 0
2 RFS IDLE 4 37064
2 RFS IDLE 0 0
2 RFS IDLE 2 17503
2 RFS IDLE 3 21524
SQL> select thread#,max(sequence#) from v$log_history group by thread#;
THREAD# MAX(SEQUENCE#)
1 25087
2 17502
3 21523
4 37063
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
THREAD# MAX(SEQUENCE#)
1 25087
2 17502
3 21523
4 37063
PRIMARY:_
SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
THREAD# MAX(SEQUENCE#)
1 25087
2 17502
3 21523
4 37063
Hope this helps.
Arindam