Datum 13.08.2007   Keywords Procedure for moving data

Merging data


 If you have an application that is currently running on independent DB2  subsystems, you might decide that it is an application that will work well  in a data sharing group. In that case, you must move the data and merge  the catalog definitions for that data from the independent DB2 subsystems  into the data sharing group. Because the DB2 subsystems still exist, you  cannot reuse their subsystem names when installing the subsystems as new  members into the data sharing group.


 DB2 does not provide an automated way to move catalog definitions from an  independent DB2 subsystem into the catalog of the data sharing group. If  you have procedures and tools in place now to move applications from test  to production, or to handle merging databases from enterprise  reorganizations or mergers, those same procedures can be used to move  applications into the data sharing group.


 Existing distributed applications


 If you move existing data to the data sharing group, it is likely that the  location name of objects will change. Existing distributed applications  that remotely reference an object by its three-part name must be changed  to the new name. And any aliases on that table must also be dropped and  recreated with the new location name.


 Any application containing explicit SQL CONNECT statements that reference  an old location name must be modified. Any DB2 plan that uses an old  location name for the CURRENTSERVER keyword must be bound again.


 Procedure for moving data ->
 http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/com.ibm.db2.doc.dshare/bjnzinst1006257.htm



P.S. Please pass my address to anyone interested in DB2 HOTLINE - thank you.

With kind regards
Michael Dewert, Software Group
DB2 Development
DB2 Information Management Software