This is a recent log from an Oracle Redo Log Backup:
2021-05-12 00:32:29 :: Preparing for backup
2021-05-12 00:32:32 :: Redo log backup interval is 2 hours
2021-05-12 02:32:32 :: Backed up 3,6 GB of redo logs for 2 databases: PRODB;RIGES at 6,3 MB/s with bottleneck: Target (Network)
2021-05-12 04:32:35 :: Backed up 8,7 GB of redo logs for 2 databases: PRODB;RIGES at 7,0 MB/s with bottleneck: Target (Network)
2021-05-12 06:32:37 :: Backed up 46,3 MB of redo logs for 2 databases: PRODB;RIGES at 803,0 KB/s with bottleneck: Target (Network)
2021-05-12 08:32:39 :: Backed up 19,6 MB of redo logs for 2 databases: PRODB;RIGES at 378,5 KB/s with bottleneck: Target (Network)
2021-05-12 08:32:41 :: New redo log backup interval started at 2021-05-12 08:32:41
2021-05-12 08:32:42 :: Enumerating Oracle databases
2021-05-12 08:32:48 :: Performing Oracle redo log backup for RIGES;PRODB
2021-05-12 08:32:48 :: Saving 129,8 MB of redo logs to backup repository
2021-05-12 08:32:48 :: Deleted archive logs: PRODB;RIGES
2021-05-12 08:32:48 :: Collected redo log does not match any existing database backup: PRODB
2021-05-12 08:33:50 :: Redo log backup completed at 1,9 MB/s with bottleneck: Target (Network)
2021-05-12 08:33:50 :: Waiting for redo log backup interval to expire
What does "Collected redo log does not match any existing database backup: PRODB" mean? It even generates an e-mail from the main backup job, saying that the job failed. But we are doing a backup of that server/database every night, so I don't understand what the error is all about. Without really knowing anything about it, the error seems a little misplaced...
Regards,
PJ