Concurrent Copy

Antonis Galaios

Concurrent Copy
Hello listers,



I'm trying to figure out the advantages and disadvantages of a full image copy with the option CONCURRENT and a full image copy with SHRLEVEL CHANGE. We are in DB2 for z/OS V8.

Any ideas ?



Áíôùíçò Ãáëáéïò

DB2 DBA for z/OS

IBM Certified Solutions Expert

DB2 UDB V7.1/V8.1 Database Administration






P Think before you print.

Disclaimer:
This e-mail is confidential. If you are not the intended recipient, you should not copy it, re-transmit it, use it or disclose its contents, but should return it to the sender immediately and delete the copy from your system.
EFG Eurobank Ergasias S.A. is not responsible for, nor endorses, any opinion, recommendation, conclusion, solicitation, offer or agreement or any information contained in this communication.
EFG Eurobank Ergasias S.A. cannot accept any responsibility for the accuracy or completeness of this message as it has been transmitted over a public network. If you suspect that the message may have been intercepted or amended, please call the sender.


______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Jack Campbell

Re: Concurrent Copy
(in response to Antonis Galaios)
Galeos,

I've used SHRLEVEL CHANGE in the past when there is no available "backup
window" and updates occur against the table 24*7.....be aware you can only
perform a PIT (to log point) recovery for this kind of imagecopy. The
imagecopy would be the start point, with all the necessary log records applied
(using a log apply tool) to recover the tablespace to a consistent point.


As for shrlevel(concurrent) - a lot depends on which vendor toolset you are
using. Whilst concurrent is supposed to produce the equivalent of a shrlelvel
(reference) copy, by selecting pre-update page images for the copy......there
may be a number of things to set-up to enable this. For example if you are
using BMC COPY, you will need the XBM tool enabled to cpature the pre-
update pages in memory.

Regards

Jack

______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html

Jack Campbell

Re: Concurrent Copy
(in response to Jack Campbell)
Galeos,

just realized I was a little unclear on recover using shrlevel change.....using
the base db2 toolset you can recover to LOGPOINT (e.g. a quiesce point).

The use of a log apply tool would be used if you wanted to recover to some
point before or after the quiesce point

The quiesce is used (before copy) to externalize all updates from the buffer.
The quiesce (after copy) to create a recover point.

Regards

jack

______________________________________________________________________

* IDUG 2009 Melbourne, Australia * 18-20 March * http://IDUG.ORG/Events *
______________________________________________________________________




IDUG.org was recently updated requiring members to use a new password. You should have gotten an e-mail with the temporary password assigned to your account. Please log in and update your member profile. If you are not already an IDUG.org member, please register at http://www.idug.org/component/juser/register.html