I have a weird issue where half of the streams on an intelligent Oracle policy fail with status 58 but half will complete successfully.
If I set 12 streams 6 will run, 6 will fail. If I set 6 streams 3 will run 3 will fail. Anyone seen this kind of activity before?
nslookup is returning 2 names to the IP address. I am thinking it may well be something to do with that. Looking to get that resolved first.
Does the failing streams have the correct client name ?
Without more information, my best suggestion is to go thorugh the steps in posts below:
https://www.veritas.com/community/forums/general-database-backup-error-troubleshooting
If you havn't already. The database one hasn't been updated for OIP, but is still valid except for the manually running the script.
All connectivity tests passed. As some streams work I didn't think it would be connectivity.
6 streams start writing immediately after about 30 seconds 6 streams will immediately go to status 58. So it's not a timeout issue.
Failed streams have an unable to write progress log messages
That was my thinking as there is 50% success. Two interfaces on the client and they both have an seperate entry in the hosts file. Solaris 10 client btw.
Tbis isn't a RAC is it?
No. single server.
Do you have the required network interface set on the client? It has 2, but you don't want to give a choice on which one to use. Same thing from the master, 1 client, 1 name, 1 ip address.
Master server has only 1 interface.
On the client I have set the preferred network as:
PREFERRED_NETWORK = 0/0 ONLY "Client Interface IP"
but no joy. The host routing table indicates that backup traffic would go through the interface I want anyway.
I've successfully run flat file backups with multiple streams however.
You will need logs to troubleshoot.
I know that OIP use additional logs - best to look them up in NBU for Oracle manual.
dbclient (777 permissions) on the clientshould be a good start along with these server logs:
Master: bprd (NBU must be restarted when this folder is first created)
Media server: bpbrm
A work-around would be create old-fashioned script on the client and initiate it from Oracle policy.
If that works fine, go back to OIP and troubleshoot using logs...
