This is false gap so can be ignored: primary switched from 11378 to 11379 in 2 mins, meanwhile standby has not finished archiving 11378 before it saw 11379, hence gap was detected and FAL sent to get 11378
from primary. however it was not needed.

More information please see following note: ORA-16401 and ORA-16055 reported in primary alert.log when redolog switch is over frequently ( Doc
ID 1243177.1 )

there is no real gap so error can be ignored. make
sure log file switch doesn't happen that frequently so there will be no false gap detected.

ignore the error as there is no real gap. Also increase the size of online redo log of primary database so it won't switch frequently.

ignore the error as there is no real gap. Also increase the size of online redo log of primary database so it won't switch frequently.

ignore the error as there is no real gap. Also increase the size of online redo log of primary database so it won't switch frequently.

ORA-16401
and ORA-16055 reported in primary alert.log when redolog switch is over frequently (文档 ID 1243177.1)

- RedoLog switch happens very frequently before the above Error reported
- The requested ArchiveLog by FAL requests the current Log Sequence or the Sequence currently being archived

CHANGES

There is no change made.

CAUSE

The Problem here is that the Primary Database is switching Logs too frequently.

Using ARCH to send the archives, every time there's a log switch the Primary has to send the Archivelog to the Standby, meanwhile another Log Switch occurred on the Primary which causes also another Archivelog to be sent to the Standby, but the first one has
not finished yet, a GAP is formed and detected by the Standby. At this Time the first Archivelog is also sent as FAL Request, but this one will fail because the first one is still being archiving, locked, so the second one fails.