It's the latter. Run Rman remotely? That sounds weird.
As for the other suggestions:
For some reason our Unix admins have disabled/not loaded the
Yes I'd use a shell script that I can throw into the background
except that I've got people waiting & I really don't have time to write
the script in the first place.
Lastly the keep alive ping idea was suggested by our Network
folks, but the unsympathic VPN folks already thought of that and
disabled the ping as "data". Therefore Putty and Ultraedit's keep alive
Course they don't kill off idle UDP sessions for some silly
reason. Namely they don't want their e-mail connections broken. OH
Senior Oracle DBA
On Behalf Of Peter Hitchman
Sent: Monday, October 25, 2010 9:26 AM
Subject: Re: Rman Question
I think the problem needs clarification. Is it that the rman session
is connecting to a databse over a VPN that times out or is it that a
OS session over a VPN that is running rman gets dropped. The latter
can be solved by using screen/nohup, but as Stephane said it will not
help the former. But it seems odd to me, if the former is the case, to
even try to run rman like this, is there a good reason not to run it
on the database machine itself?