Oracle rman db restore
This line clearly states the reason for the block corruption:

ORA-26040: Data block was loaded using the NOLOGGING option


NOLOGGING operations are not logged in the redo as traditional operations, the amount of information logged is greatly reduced to an extent, where data recovery is not possible. Because of this, if you did not make a backup of the affected datafiles after these operations had finished, those modifications can not be recovered with archivelogs, and you will receive the above error.

NOLOGGING should be handled with care, and because of the above, you should perform a backup after performing a NOLOGGING operation. If your backup was created earlier, you will not be able to fully recover data using this backup, even if you have the archivelogs.

So, perform the backup after the NOLOGGING operations was finished.

Another way is to control the NOLOGGING attribute of your objects. You can set this at table, index, LOB segment, tablespace level. You can set it to LOGGING, so operations on the object will be logged (or this will be the default inherited value in case of tablespace).

Finally, you can enable FORCE LOGGING at the tablespace or database level, so operations will be logged regardless of the object level setting.