Oracle RMAN backup status 13, timer expired
Hi all Sometimes, but not regularly, we experience one of our large Oracle backup ending with status 13. Archive logs is always successful, so is the FULLs. This applies to our diffs. We have a fe...
Forum Discussion
Thank you for your hints!
I suspect that the job is queued in NetBackup, and are waiting until resources are available. We have 2 streams pr Oracle Intelligent Policy, with a high priority setting in the policy. Other streams running in the same policy is exiting with staus 0.
I have asked Firewall team if they have settings that could explain the timeout after exactly 3 hrs.
Client Read Timeout set to default 300 sec.
No data written for failed stream.
Client Side Dedupe not used, neither is Copilot.
Will raise a support case when necessary.
Thanks again!
I also have the same issue ！
And increasing the client_read_timeout to 7200 or higher in the media server side does not resolve this problem 。
