6.4 Alternative ways for data movement

 < Day Day Up > 



6.4 Alternative ways for data movement

Beside the MTK, there are many other tools and products for data movement. Here we show you some of them. You should chose the tool according to your environment and the amount of data.

6.4.1 Data movement through named pipes

As described in 6.1, "Data conversion process" on page 212, you need additional disk space during the data movement process. To avoid the space for the flat files, you can use named pipes on UNIX-based systems. To use this function, the writer and reader of the named pipe must be on the same machine. You must create the named pipe on a local file system before exporting data from the Oracle database.

Because the named pipe is treated as a local device, there is no need to specify that the target is a named pipe. In the following is an AIX example:

  1. Create a named pipe:

     mkfifo /u/dbuser/mypipe 

  2. Use this pipe as the target for data unload operation:

     <data unload routine> > /u/dbuser/mypipe 

  3. Load data into DB2 UDB from the pipe:

     <data load routine> < /u/dbuser/mypipe 

The commands in step 2 and 3 show you only the principle of using the pipes. To unload and load the data, use the routines discussed in this chapter.

Note 

It is important to start the pipe reader after starting the pipe writer. Otherwise, the reader will find an empty pipe and exit immediately.

6.4.2 DB2 Information Integrator

In a high availability environment, you have to move the data during production activity. A practical solution is the replication facility of the DB2 Information Integrator.

IBM DB2 Information Integrator provides integrated, real-time access to diverse data as if it were a single database, regardless of where it resides. You are able to hold the same data both in Oracle and in DB2 UDB. You are free to switch to the new DB2 database when the functionality of the ported database and application is guaranteed.

The replication server, former known as DB2 Data Propagator, lets users manage data movement strategies between mixed relational data sources including distribution and consolidation models.

Data movement can be managed table-at-a-time such as for warehouse loading during batch windows, or with transaction consistency for data that is never off-line. It can be automated to occur on a specific schedule, at designated intervals, continuously, or as triggered by events. Transformation can be applied in-line with the data movement through standard SQL expressions and stored procedure execution.

For porting data, you can use the replication server to support data consolidation, moving data from Oracle to DB2 UDB.

You can get more information about replication in the redbook A Practical Guide to DB2 UDB Data Replication V8, SG24-6828-00, and in the DB2 Information Integrator Guide.

6.4.3 Third party tools

In 2.1.2, "Understanding and choosing migration tools" on page 30, we introduce some third party tools. The products are:

  • SQLWays (Ispirer Systems)

  • DataStage (Ascential)

  • DataJunction

These products are good for moving data between different databases.



 < Day Day Up > 



Oracle to DB2 UDB Conversion Guide2003
Oracle to DB2 UDB Conversion Guide2003
ISBN: N/A
EAN: N/A
Year: 2004
Pages: 132

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net