scn gap on consecutive sequence number after switchover - RAC - 10.2.0.4 ?
edited Jan 15, 2013 2:50AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 1 commentAnswered
I found something which might be normal and I noticed that since I have a
script which check all the consecutive archivelog (first_change#,
last_change#) and its finds SCN gap if there is a hole.
Before putting my RAC 2 nodes database 10.2.0.4 with dataguard, I had no gap.
I think a do properly the switchover (using LGWR ASYNC), i don't find any error on both alert_log. The switchover seems to run well.
But when i ran my "gap script", i found the following oddity :
THREAD# SEQUENCE# FIRST_CHANGE# NEXT_CHANGE#
---------- ---------- ------------- ------------
2 118 5966403 5966562
2 119 5966562 5966577
2 120 5966577 5970293
2 121 5970293 5970310
2 122 5977084 5977094
Is this normal ? I don't think so..
Before putting my RAC 2 nodes database 10.2.0.4 with dataguard, I had no gap.
I think a do properly the switchover (using LGWR ASYNC), i don't find any error on both alert_log. The switchover seems to run well.
But when i ran my "gap script", i found the following oddity :
THREAD# SEQUENCE# FIRST_CHANGE# NEXT_CHANGE#
---------- ---------- ------------- ------------
2 118 5966403 5966562
2 119 5966562 5966577
2 120 5966577 5970293
2 121 5970293 5970310
2 122 5977084 5977094
Is this normal ? I don't think so..
0