Does oracle workbench support earlier versions of DB2 not UDB

Question

HI all,
In our company we are migrating the DB2 (I think version 2.xx ) of OS2 to Oracle in windows ,
Does the Oracle Workbench support for the earlier versions of DB2,
if yes how?
if no then what is the way to migrate?
This is an urgent requirment, so pls. provide me a solution.
Thanks
Murali.v

Answer 1

DB2 v2 would be at least 10 years back. That may be out of even SQLWays window for DB2.
If indeed stuck without a tool.....
Assuming that there are very few stored procs, triggers, and proprietary SQL views. (MWB DB2 plug-in wouldn't have solved those anyway). The "physical" design of the DB (tablespaces , indexes , etc. ) are likely completely lost using these approaches. There are a couple of ways to accelerate the doing it by hand approach.
1. [ this is somewhat of a tangent] export the DDL (if you can) and push it into a more modern version of DB2 and have the MWB move that. Use the offline mode to generate suggestive scripts and SQL*Loader control files ( and perhaps also the new Oracle DDL. may have to make some tweaks to it and control files).
pros:
if there is a large amount of DDL mapping of types is done automatically.
cons:
may not be a handy version of DB2 UDB around. (a DB2 Express-C v 7 isn't
prominent on the IBM site anymore. However, may be other versions around at
you site.)
probably would have to tweak the tablespace/index/etc declarations in the
exported DDL. [ large assumption here is that not using a signficant amount
of deprecated features. If the editing process too complicated effectively
cheaper just to proceed to option 3 below. ]
the data export utility script may need tweaks.
[ if you have LOBS and/or binary columns you're likely to run into problems. ]
2. Similar approach is to do a DDL capture into a tool like ERWin.
[Not sure if there is a generic DDL capture mode in Jdeveloper that would even talk to DB2 v2  to create a UML model ]
You then tweak that "design model" and instantiate into Oracle. ( as mentioned in another reply there are some issues you'll likely encounter. For example, some types don't map and the MWB docs can help. )
pros:
much of the straightforward DDL just moves over.
cons:
may be no tool that can do the design capture for DB2 v2 (was legacy embedded
solution that ran for years that nobody touched. )
with generic mapping loose lots of specifics.
no control files, no export scripts, no warnings,
3. as mentioned before. Edit the exported DDL. ( I'd strip out tables , indexes, etc. ) and just get it to load before moving one to additional Oracle specifics on those aspects.
pros/cons mostly same as above, but even more manual work.