I'm reading Oracle docs that talk about the various configuration of standby dbs.

One setup it talks about is manually applying archive logs (versus managed, where it applies logs continuesly and automatically). One benefit it states for doing it in this manner is to protect from data corruption. In a situation where the primary database has become corrupted, the standby would still be intact because you have not yet applied the archive logs and would be able to activate the standby (unaffected by the corruption on the primary)

My question is, does anyone know if they are talking about corruption as in data FILE corruption (at the bit level) OR are they talking about data corruption where records or data were inadvertently changed/deleted, etc....

My common sense tells me corruption at the bit level on the primary database would have NO affect the standby because the standby applies changes to itself in a LOGICAL manner, meaning it applies the transactions, not copy physical media to itself....(except for the actual archive logs it needs to apply transactions from)

Can anyone confirm this??