As far as I understand, the COPY YES just generates a straight copy of the
source file. It is made up of each successfully parsed record (parsing is
in phase on of the load) and is concurrent with the building of the uinput
buffers that are smashed into the target table.
When phase one is done, load has to deal with index build and so on and by
that time, I believe the copy is done.
This is not being copied in page, extent struture. I think that each
succesfully parsed record is structured properly to be moved into the row in
the target table and it is that structure which is also copied, record by
recordm, into the target copy file.
I don't know TSM and DB2 well enough to say but at least as the file is
ready, its size is known and TSM could be told. I just don't know if DB2
does that with TSM.
Regards, Pierre.
--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
"Joachim Klassen" <Jo*******@email.coma écrit dans le message de news:
11**********************@m58g2000cwm.googlegroups. com...
Hi all,
a couple of questions regarding LOAD COPY YES:
when does a LOAD COPY YES start to write its backup image ? After LOAD
Phase or after BUILD or DELETE phase?
What gets backed up - data pages only or index pages as well?
When I use TSM as backup target, will DB2 send an estimate of the
backup size to TSM before backup starts?
TIA for any answer
Joachim