Use of CHANGELIMIT in COPY utility (=> old copies)

Billy Larsen

Use of CHANGELIMIT in COPY utility (=> old copies)
In order to minimize the copy actions made every week at our shop (all
objects are concerned even if thery are not active) , i want to use this
option : only tablespaces having updates will be copied.

I will be careful with Modify for not deleting all objects on n age.

With this method , we will have , for example, an old copy with 1 year
age , but the logs(archive) are only kept for 18 days.

I will be careful with Modify for not deleting all objects on n age.

However, Is there any problem when i will try a RECOVER TABLESPACE xx.yy
(to current , not tocopy or torba) ?

I don't see any problem , as syslgrnx will tell to the Recover process what
log portion to read , and as there is no update , it won't need any log.

But maybe i don't see others problems ?
Can you please advice ?

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

Michael Ebert

Re: Use of CHANGELIMIT in COPY utility (=> old copies)
(in response to Billy Larsen)
You must be careful that SMS doesn't expire and delete your IC datasets. It
may have rules that override your expiration date specification.
Maybe use something like this: copy every changed object every x days +
unconditionally copy everything every y days....

Dr. Michael Ebert
DB2 Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany




From: Billy Larsen <[login to unmask email]>@IDUGDB2-L.ORG on 14-01-2005
05:02 CST

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>

Sent by: DB2 Data Base Discussion List <[login to unmask email]>



To: [login to unmask email]


cc:






Subjec [DB2-L] Use of CHANGELIMIT in COPY
t: utility (=> old copies)








In order to minimize the copy actions made every week at our shop (all
objects are concerned even if thery are not active) , i want to use this
option : only tablespaces having updates will be copied.

I will be careful with Modify for not deleting all objects on n age.

With this method , we will have , for example, an old copy with 1 year
age , but the logs(archive) are only kept for 18 days.

I will be careful with Modify for not deleting all objects on n age.

However, Is there any problem when i will try a RECOVER TABLESPACE xx.yy
(to current , not tocopy or torba) ?

I don't see any problem , as syslgrnx will tell to the Recover process what
log portion to read , and as there is no update , it won't need any log.

But maybe i don't see others problems ?
Can you please advice ?

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm