Has it ever worked before?
Do you have the executable bit set on /usr/openv/netbackup/ext/db_ext/oracle/samples/rman/wcpmig1_archiv.sh ?
Are there permissions for the Oracle user to write to the NBU Oracle client's log folders on the client and if you used the NBU template which is looks like you did, can you see /usr/openv/netbackup/ext/db_ext/oracle/samples/rman/wcpmig1_archiv.sh.out ?
We've had this issue off an on since upgrading to 8.2 and are still looking into it with support. All I can say is good luck and I'll update if I ever find anything.
If you do not have access to the Oracle client, maybe a good idea to ask the dba to join this discussion?
I am firstly curious to understand what the following means:
... they told script is correctly initated.
How is script initiated?
From NBU scheduler or from cron or cmd on the client?
Will the dba be willing to share the script, script output and NBU logs?
All troubleshooting needs to be done on the client - very little (nothing?) that we can do from NBU master/media server.
Error 29 means that some commands from the script return an error. You need RMAN output script to check if for any errors. You can create the folders:
then re-produce the error and try to find the error in these logs. If you don't have direct access to the client you can use Logging Assistant it really helps in such cases.