SEO

#1 (**permalink**) 02-27-2008, 11:31 AM

hi,
i have db2 8.2
My problem i need to copy a set of tables (~500 - 40Go) from the production
database to the integration database by script every sunday. The name of the
database are not the same.
In production database i have ~2000 tables (50Go).
There are foreign key between the tables but there are comprised in the set
of tables.

So which is the best way to do this ?

1) i can't use db2 replication (don't ask me why...)
2) i thought to isolate the set of tables in particular tablespaces and the
backup only the tablespaces and then restore them in the ingreatio database,
but i don't know if it is possible ( like oracle transportable tablespaces)
3) export the set of tables, then load them in the ingreation database to
bypass the FKs and then set integrity
4) export important tables from integration database, backup the prod db,
restore the prod db over the integration db, and then import/replace the
important tables i've exported earlier

any opinion or advice ?

thx

#2 (**permalink**) 02-27-2008, 11:32 AM

Nr 2) won't work, because you can only restore a tablespace to the
original tablespace.
Nr 3) will work.
You can also use federated access for a INSERT ... SELECT.
The advantage is, that you don't need file space for the export/load.
You can access the table data directly (federated system).

paul wrote:
> hi,
> i have db2 8.2
> My problem i need to copy a set of tables (~500 - 40Go) from the production
> database to the integration database by script every sunday. The name of the
> database are not the same.
> In production database i have ~2000 tables (50Go).
> There are foreign key between the tables but there are comprised in the set
> of tables.
>
> So which is the best way to do this ?
>
> 1) i can't use db2 replication (don't ask me why...)
> 2) i thought to isolate the set of tables in particular tablespaces and the
> backup only the tablespaces and then restore them in the ingreatio database,
> but i don't know if it is possible ( like oracle transportable tablespaces)
> 3) export the set of tables, then load them in the ingreation database to
> bypass the FKs and then set integrity
> 4) export important tables from integration database, backup the prod db,
> restore the prod db over the integration db, and then import/replace the
> important tables i've exported earlier
>
> any opinion or advice ?
>
> thx

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

sort of replication (how to)