Wednesday, 11 July 2012

ArchiveLog Shipping Take more time On Physical standby


Log Shipping define the time lag.....?

I have create one demonstration  it's work ,but i am not sure any exact solution for this problem ,if you have find the exact solution give the post on this blog.

some time log shipped gap (delay shipped & apply on physical standby , and that's a big problem see)

---primary will be go
sequence 5
sequence 6
sequence 7
sequence 8
sequence 9 log 

---but standby work on
sequence 5
sequence 6
sequence 7
shipped & applied 

but not primary shipped 8,9 log on standby why ?

my machine has been restart 2 -3 time (I have create Physical standby  on Single Machine)
(OR network issue problem then generate this problem) 
after the work database not properly shutdown 


when up the database 
1.standby
2.primary


NOTE:
after few time spend
primary generate 10,11,log 
but standby shipped & applied on 8,9

what the solution.?

##solution
--primary
alter system set log_archive_dest_state_2='defer';
select max(sequence#) from v$archived_log;

--standby
select max(sequence#) from v$archived_log;


OS command use CP log from primary to standby location 
and register these logs on standby 

--Primary & Standby both are same
select max(sequence#) from v$archived_log;

alter system set log_archive_dest_state_2='enable';

No comments: