Help on RC/Migrator (moving one partition's data from prod totest)

Rob Crane

Help on RC/Migrator (moving one partition's data from prod totest)
You can go about it in two ways. Incase you were not aware you can also
edit objects as part of a Migration Strategy so that might be a good
option if you don't plan on doing this all the time. If you plan on
doing it several times then creating a Global Change member has merit.

1) RC/M strategy, specify UNLOAD/LOAD options in the utility MODEL you
are using. Change the parm to UNLOAD PART x where x is the part you
want. Start with the TS and use the A option to get all dependent
objects. Once you have those, go in an edit them to change according to
your description.

2) RC/M strategy, specify UNLOAD/LOAD options in the utility MODEL you
are using. Change the parm to UNLOAD PART x where x is the part you
want. Start with the TS and use the A option to get all dependent
objects. Once you have those, create a global change member that
represents all of your changes, associate the global change to the
strategy.

Typically what I see in requests like this is the user will want part 36
today, and part 34 tomorrow. I would just migrate the structure and
change the parts 1-35 to be small in size. Then you can easily cleanup
the test db using your partition scheme, etc. And adding a couple more
parts of data is just and alter instead of another TS create, etc..


"Philip Nelson (DBA)" wrote:
>
> Not strictly DB2, but using a DB2 tool. Hopefully I can get a quick
> answer from a user who has done this already. I guess that will be
> quicker than going through Tech Support (although I will raise the call
> anyway).
>
> We have the CA/Platinum tools and want to achieve the following in
> RC/Migrator.
>

> Our data warehouse has 36 partitions (36 months worth of data) for
> certain tablespaces.
>
> A developer wants a test database with only the latest month's data.
>
> So we need to :
>
> Copy tablespaces (but change from partitioned to non-partitioned with
> the size being equal to the size of one partition).
>
> Copy all tables / indexes and the like, getting rid of partitioning keys
> and any other "partition type" references.
>
> Extract and move data from one partition of production into the new
> structure.
>
> Is this possible automatically using RC/Migrator ?
>
>
>



Eric Pearson

Re: Help on RC/Migrator (moving one partition's data fro m prod to test)
(in response to Rob Crane)
I have had to do this before.
Easiest is to do the migration without a data unload (with
small PRIQTY/SECQTY),
alter the new tablespace to segmented, then LOAD the
new table from a partition unload of the prod one.

Regards,
eric pearson
NS ITO Database Support


-----Original Message-----
From: [login to unmask email] [mailto:[login to unmask email]
Sent: Tuesday, December 18, 2001 8:01 AM
To: [login to unmask email]
Subject: Re: Help on RC/Migrator (moving one partition's data fro m prod
to test)


Philip,

I don't think you can get that generated automatically by RC/M.

Wouldn't it be simpler, though, to copy the structure across as is, but edit
down the sizes of the other 35 partitions to nominal one-track efforts? You
can do that in RC/M reasonably easily, although it's a little laborious.

Mike Holmans
Database Consultant
BT Affinitis Computing Partners
[login to unmask email]

This post is solely the opinion of its author and does not necessarily
reflect BT's view


>>-----Original Message-----
>>From: Philip Nelson (DBA) [mailto:[login to unmask email]
>>Sent: Tuesday, December 18, 2001 11:22 AM
>>To: [login to unmask email]
>>Subject: [DB2-L] Help on RC/Migrator (moving one partition's data from
>>prod to test)
>>
>>
>>Not strictly DB2, but using a DB2 tool. Hopefully I can get a quick
>>answer from a user who has done this already. I guess that will be
>>quicker than going through Tech Support (although I will
>>raise the call
>>anyway).
>>
>>We have the CA/Platinum tools and want to achieve the following in
>>RC/Migrator.
>>
>>Our data warehouse has 36 partitions (36 months worth of data) for
>>certain tablespaces.
>>
>>A developer wants a test database with only the latest month's data.
>>
>>So we need to :
>>
>>Copy tablespaces (but change from partitioned to non-partitioned with
>>the size being equal to the size of one partition).
>>
>>Copy all tables / indexes and the like, getting rid of
>>partitioning keys
>>and any other "partition type" references.
>>
>>Extract and move data from one partition of production into the new
>>structure.
>>
>>Is this possible automatically using RC/Migrator ?
>>
>>
>>To change your subscription options or to cancel your
>>subscription visit the DB2-L webpage at
http://www.ryci.com/db2-l. The owners of the list can be reached at
[login to unmask email]