"Begin backup" does not stop tables being updated. It causes Oracle to
log sufficient information to cope with a table being updated while
being backed up. You need to specify to ADSM that it should tolerate
files being changed during backup by specifying a management class which
allows this. This is correct in this particular instance but not in most
others.

We have tested this, it does work.

Ian

T. R. Rhodes wrote:
>
>       ID TRR  MS 2604
>       208-526-9903
>
>  We are trying to backup an oracle data base live by using the oracle
>  alter tablespace table.space.name begin backup
>
>  After this oracle command has been given then we issue the adsm command to
> backup the table space.  This works as along as no update action is being 
> done,
>  however if the table space is being updated while the backup is being done
>  then we get the table space is being changed and the backup is skipped.
>
>  Has anyone tried this and can you till me why after the begin backup command
>  issued that oracle will continue to change the table space
>
>  Thanks in advance for any help.
>
> tuner of the OMEGA SERVER
> LMITC
> mail trr AT inel DOT gov

--
-------------------------------------------------------------------
-------------------------------------------------------------------
Ian Northeast                                 Tel: +44 171 441 1232
Ian Northeast                                 Tel: +44 171 441 1232
Technical Services Projects Manager           Fax: +44 171 441 1357
P&O Nedlloyd Limited
Beagle House
Braham Street
London E1 8EP                  Email: i.northeast AT poclk.demon.co DOT uk
UK
-------------------------------------------------------------------
=========================================================================