The archivelogs of node2 are not reaching its corresponding dataguard instance
Hello.
When I connect to the dataguard instance and check a sequence, for example, sequence 14909 I found that thread1 of this sequence is already in the dataguard while thread2 of this sequence has not yet arrived.
I know that thread1 is the one sent by the first node instance of rac and that thread 2 is the one sent by the second node instance of dataguard.
A lot of sequences of type thread 2 are still not found in the dataguard instance and therefore they are not arriving at the same time that the thread1 sequences are arriving. I think this is happening is because the node2 instance was shut down one day for about an hour.
When I connect to the dataguard instance and check a sequence, for example, sequence 14909 I found that thread1 of this sequence is already in the dataguard while thread2 of this sequence has not yet arrived.
I know that thread1 is the one sent by the first node instance of rac and that thread 2 is the one sent by the second node instance of dataguard.
A lot of sequences of type thread 2 are still not found in the dataguard instance and therefore they are not arriving at the same time that the thread1 sequences are arriving. I think this is happening is because the node2 instance was shut down one day for about an hour.
0