hello guys, there is discussion like this in this forum but there are ways to solve this problem and i need to know if it must be solved or not.
i created physical standby and it was working great. created archive_log files had scn number exactly the same as primary, but then my fellow colleague restarted the virtual machine on which standby was set, so obviously standby was shut downed.
in root i used command: service iptables stop;
then i started listener in oracle: lsnrctl start;
and then i used this commands in sqlplus:
1)startup nomount;
2)alter database mount standby database;
3)ALTER DATABASE RECOVER MANAGED STANDBY DATABASE disconnect from session;
this linked standby and primary cause i saw my archive_log files on both database being generated BUT:
i saw that my last archive_log file name on primary was 1_4359_870764186.dbf and on standby last dmp file was 1_4360_870764186.dbf(scn number is one times greater). then i looked more carefully and understood that the last dbf file on standby - 1_4360_870764186.dbf it was likely being modified all the time, cause as i refreshed, it's modify time was always equal to date. but it was not saving changes cause it's size was always same: 51201K;
then i tried to switch log manually and typed on primary: alter system switch logfile; which created archive_log on primary 1_4360_870764186.dbf and on standby 1_4361_870764186.dbf, i looked carefully on standby and realized that now 4361 was 51201K size and it was modified every minute, instead of 4360;
then i looked at sizes of 4360 archive_log file on both databases and they were equal; as was 4359 on both databases and every other log file;
so i have impression that log_files are switched correctly, their size and the scn are exactly the same. but for some reason standby database creates that last archive_log every minute, and it always has 51201K size.
in my alert log files is everything cool. it says:
Fri Jul 31 09:25:35 2015
Archived Log entry 27 added for thread 1 sequence 4360 rlc 870764186 ID 0xd6315b1a dest 2:
RFS[2]: Opened log for thread 1 sequence 4361 dbid -701415654 branch 870764186
Fri Jul 31 09:25:39 2015
Media Recovery Log /opt02/archive_log/1_4360_870764186.dbf
Media Recovery Waiting for thread 1 sequence 4361 (in transit)
yeah, it says that it is waiting for sequence 4361 which is not created on primary, and should not be created on standby but is created on standby as that last file, which's size as i have said is 51201K and is being modified every minute.
1)so question is, what is that?
2)why it was caused when i reunited standby and primary?
3)will it have bad effect on my standby database?(should i try to fix it, or should i recreate standby database? or should i leave it alone?)