DB2 LUW

IBM DB2 (DB2 LUW, DB2 z/OS, DB2 for i, DB2 AS/400, DB2 iSeries)

IBM DB2 database has a long history and is available on a myriad of IBM mainframes and operating systems. Its original roots are in 70s, when IBM’s researcher Edgar F. Codd described the theory of relational databases and relational algebra. However, DB2 (or IBM Database 2) name was officially assigned to a product in 1983. IBM, ironically, failed to recognize the potential of Codd’s innovation and Oracle ended up actually beating IBM to market with its SQL language implementation.

Today, IBM DB2 is still going strong and is capable of supporting legacy (read - extremely old) applications, as well as providing latest features. It is very reliable and fast database, used in enterprise market. TPC-C and TPC-H industry benchmarks show excellent performance of DB2.

Competing with Oracle, DB2 is supposedly able to run 98% of Oracle SQL code without changes, allowing even very large codebases to migrate from Oracle to DB2 relatively quickly. DB2 is able to reach great performance levels.

It is believed that most of world's data still resides on IBM DB2 mainframes.

Even though they all share DB2 name, DB2 variants (DB2 Linux/Unix/Windows, DB2 for z/OS, and DB2 for i) are actually completely different databases. Full Convert Pro supports all of them.

Full Convert supports DB2 LUW database directly.

DB2 LUW data types we support

Integral

bigint, integer, smallint

Decimal

decimal (dec, numeric, fixed), double (float, double precision), real (decfloat)

Text

char (character), clob (long varchar, character large object), nchar (national character), nclob (dbclob, national character large object), nvarchar (national character varying), varchar (longvar, vargraphic, vargraph, varg, longvarg, character varying)

Binary

binary (graphic), varbinary (varbin, binary varying)

Date/Time

date, time, timestamp (timestmp), timestz

Large objects

blob (binary large object), clob (long varchar, character large object), nclob (dbclob, national character large object), xml

Other

boolean, uniqueidentifier

Export DB2 LUW database

It may make sense to migrate your data away from DB2 LUW. You may want to do it permanently or just need to share your tables with a collague in a different format.

We will copy all your tables with their data and apply indexing and relationships exactly as they are in your current DB2 LUW database. In a nutshell, you get exactly the same database in another database engine. Each time you run the migration, we will copy all the tables again. Of course, we have a built-in scheduler, so you can run this overnight and have a fresh database copy in the morning.

Take a look at the quick tutorials below to see how it's done.