This content has been marked as final. Show 2 replies
1. Is it expected that the log on the standby node may not be identical to the log on the production node, and is there any pattern to the differences?
I would expect them to be the same.
2. Is it expected that the stream written to the network during log transfers may not match the production log?
ORA-00317 - tells me your file transfers are either corrupt or incomplete.
The "will differ by 2 bytes at 100 and 101" statement just confirms this.
3. Is there a better way to troubleshoot this?
This MOS doc might be worth a look.
NetApp: Using 'nolock' NFS Mount Option with non-RAC Systems Results in Database Corruption [ID 430920.1]
OERR: ORA-27054 NFS file system where the file is created or resides is not mounted with correct options" [ID 338086.1]
It's not a very common error. If you have Oracle support I would use it.
Thanks for the reply! I neglected to mention that the logs that differ by a few bytes on the standby node get applied just fine - which is why I thought it might be possible that the log transfer process might alter the file a bit - though if that were the case, I would expect ALL log files to differ with the same byte count and location. The log files that are corrupted are obviously so - they are full of nulls.
Of the two links you suggested - when I'm switching between the working NFS mount and the non-working NFS mount, the mount options are the same, so I don't think that can be the issue. The only difference in the NFS mounts is that one sits behind a 10G LACP interface, the other sits behind a 1G interface - shouldn't really be an issue that I can see. I DO see a few errors on the 1G link - which I find highly suspect - but I can't explain why the errors would only manifest during the DG log transfer and not an ssh copy. I am working with NetApp on that topic, but I wanted to try troubleshooting this from the Oracle side as well.