Have you tried something like
python recoverSys.py --command "RECOVER DATABASE UNTIL TIMESTAMP '<your timestamp>' CLEAR LOG"
?
Yes, as you can read in my first post.
I am not aware of any other option to "skip" the recovery of log entries. And due to the sequential nature of the redo logs, skipping corrupt entries will lead to inconsistencies, which is why there is no option for that.
Yes, that sounds logical. That's why I was wondering what the sentence means "
The trace file will say something like cannot find or cannot read a log segment at a hexadecimal address, the only resolution to a corrupt log segment is to do a recovery that does not involve that log segment"
in SAP HANA System Down, HANA not starting - Technology Troubleshooting Guide - SCN Wiki
-- Micha