Based on the conversation from this thread:
https://groups.google.com/g/debezium/c/A3XqlP2Dgl4

It would be helpful from a DEBUGGING point of view that when ORA-01291 is thrown, we resolve which particular log file(s) caused the error and report the name in the exception and/or log messages prior. This would enable users to easily interface with the DBA to determine why the error occurred with the provided filename & potentially sequence or SCN range metadata.

Implementation Details
When a LogMiner session is started, LogMiner populates a table called V$LOGMNR_LOGS, and this table maintains several key pieces of information we should always log by default, including:

1. FILENAME
2. THREAD_ID
3. THREAD_SQN
4. LOW_SCN
5. NEXT_SCN
6. DICTIONARY_BEGIN
7. DICTIONARY_END
8. TYPE
9. INFO

The output should be restricted to only entries from the table that have STATUS=4.