![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I've the necessity to keep aligned my Company's DB2 Database with another DB2 Database. In the actual scenario, I have to export entire DB (Structure and data - i.e. db2look & db2move) and overvwrite entire database, in order to be sure that my Company DB is aligned. |
|
My question is: Exist a way to get only the differences from the source database? In which way you suggest me to keep only the delta (i. e. from a particular date) from the source database? |
#3
| |||
| |||
|
|
I'm confused. The same way, you are doing db2look and db2move, you could do a backup and restore. Since you are overwriting the target database anyway,what is the reason for export/import? There is also cross platform restore (except for windows), only the endianness has to match. You can also restore a database from a backup image taken on a 32–bit level into a 64–bit level, but not vice versa. |
#4
| |||
| |||
|
|
DESIRED OPERATIONS @ time 1: I copy entire database with db2move and db2look utilities. @ time 2: someone modify DB SOURCE data or structure / at the same time DEST DB become OLD @ time 3: HERE I NEED HELP ----->>> I WOULD COPY ONLY DIFFERENCES AND ADD-OVERWRITE ONLY DIFFERENCES. Is this possible? |
#5
| |||
| |||
|
|
Hi Elio, DESIRED OPERATIONS @ time 1: * * *I copy entire database with db2move and db2look utilities. @ time 2: * * *someone modify DB SOURCE data or structure / at the same time DEST DB become OLD @ time 3: * * *HERE I NEED HELP ----->>> I WOULD COPY ONLY DIFFERENCES AND ADD-OVERWRITE ONLY DIFFERENCES. Is this possible? In that case your only options are SQL or Q Replication. I'm not a zOS specialist, so you will have to talk to a DB2/z person, because CAPTURE has to run on the mainframe for replication. Oh, there might be another possibility. I don't know, if this works on DB2/z, but it definitely would be possible, if the source were on distributed. Configure federated database access on DB2/z to access the target tables via nicknames. Then define I/U/D triggers on your source tables to update the target tables... Hope this helps. -- Helmut K. C. Tessarek DB2 Performance and Development /* * *Thou shalt not follow the NULL pointer for chaos and madness * *await thee at its end. */ |
#6
| |||
| |||
|
|
I don't have the possibility to make two dbs communicate each other. |
![]() |
| Thread Tools | |
| Display Modes | |
| |