Not all commands have a WAIT=YES option available. If the command has
WAIT=YES, use it. It's really the easiest way. PITFALL: A TSM script
containing a long-running command with WAIT=YES should never be run from
a live console, not even for testing and debugging. It should only be
started by an adm
Thanks, trying to go through this one. Actually I have an RMAN script which
backups the DB.
It is coded in the schedule as a run script. I need to figure out if it
completed ok and in this
case run another task to backup data files on another server. So I need to
setup a trigger
for that. All pr
On Dec 24, 2012, at 12:31 PM, nkir wrote:
> Thank you! I know about these options. But how exactly I can apply them?
> How to check that DB backup was successful and I can proceed next task?
>
> +--
> |This was sent by kniko...@
Thank you! I know about these options. But how exactly I can apply them?
How to check that DB backup was successful and I can proceed next task?
+--
|This was sent by kniko...@gmail.com via Backup Central.
|Forward SPAM to ab...@b
We used the storage array to give a copy of the DB and logs to the new TSM
servers. Our DBs where 100GB - 280GB (4 of them). We went from 5.4 to 6.2.
The 5.4 to 5.5 upgrade took between 7 and 44 minutes. 44 was the odd one out
of 8 runs, less than 10 minutes was the normal run. I practiced th
