You are talking about 3 different things here
- prevent the ScriptoutputTimeout.
The default settings of this option in global conf are 15 minutes
You correctly identified this as being in the 'global' file. This timeout is used when running pre-exec or post-exec scripts, and the 15 minute default timeout is not enough to allow the script to finish. I suggest that you run the script in stand-alone mode, aoutside of DP, and see how long it takes. Then, in the 'global' file, find the line
# ScriptOutputTimeout=TimeoutInMinutes
make a copy of the line, edit one of the lines to remove the # sign and the 'space' that follows, and set it to the value you want, for example, to increase the timeout to 30 minutes
ScriptOutputTimeout=30
# ScriptOutputTimeout=TimeoutInMinutes
Save the file, stop and restart DP
=================
[61:1002] The BMA named "ORA_BACKUP_2" on host ux-rbg11.xxxxxxxxx.com
reached its inactivity timeout of 8400 seconds.
Tis can usually be reolved by implementing KeepAlive on the server giving the error, in your case 'ux-rbg11'. I wrote several support tips on implementing KeepAlive on different platforms, you may be able to find one that is appropriate for you by searching the forum for 'KeepAlive'. Let me know if you can't find it, and I will send you a copy
I would really suggest that you implement KeepAlive on servers pro-actively, but, at least, I woudl do it also on any disk agents involved with this backup
================
[61:1002] The VBDA named "Database Validation EADP" on host lnx-rbg01.xxxxxxxx.com
reached its inactivity timeout of 300 seconds.
If this is from the same session as the previous error, it may straighten itself out once you get KeepAlive implemented, and are no longer getting the 8400 second MA timeout. However, if not, again, in the 'global' file, find this line
# SmPeerID=WaitForInMinutes
# default: 5 minutes
Edit as before, set the value to no more than 15 minutes, but, it will probably need a lot less than that