Migration from Oracle to DB2 UDB v8.1

[Nikhil]

Folks:

We are in the midst of planning a migration effort from Oracle v8/9 to
DB2 UDB v8.1 on AIX. I would really appreciate if someone could give
me some pointers and links which compare the two databases. Our time
frame is 3-6 months and meanwhile development would continue in the
Oracle environment. We would like to give our developers a list of
do's and don'ts (with regards to data-models, stored procs, triggers,
use of blobs/clobs,...) that would make the subsequent migration
easier.

Also, if you can point me to some sites that lists the replication
issues in UDB, that would be great. Specifically, we are looking for
replication in EEE environment, replication involving triggers, BLOBS,
CLOBS, identity columns, etc...

Thanks in advance for your prompt response.

Regds,
Nikhil

[Joachim Müller]

Nikhil,

IBM has some nice sites for your migration:

http://www7b.software.ibm.com/dmdd/zones/porting/index.html

Regards, Joachim Müller

"Nikhil" <ngad...@hotmail.com> schrieb im Newsbeitrag
news:b3c8c1a0.03051...@posting.google.com...

[Blair Kenneth Adamache]

Don't use rowid - use sequence if you need a rowid type function.

You'll need to be on Fixpak 2 of v8.1 or later to replicate data from
multi-partition tables.

There's an Oracle porting guide here:

http://www7b.boulder.ibm.com/dmdd/library/techarticle/0205wilkins/0205wilkins.html

Locking and concurrency is one place where Oracle can differ quite a bit
from DB2 (and other databases).

If this is an issue, here are some articles on locking:

http://www-3.ibm.com/software/data/pubs/papers/readconsistency/readconsistency.pdf

http://www-3.ibm.com/software/data/pubs/papers/locking/locking.pdf

[Serge Rielau]

I'm curious about your enviroment. Is this BI, OLTP or mixed workload?
What kind of triggers?

Cheers
Serge

--
Serge Rielau
DB2 UDB SQL Compiler Development
IBM Software Lab, Toronto

Visit DB2 Developer Domain at
http://www7b.software.ibm.com/dmdd/

[Dmitry]

Hi,

>Our time frame is 3-6 months and meanwhile development
>would continue in the Oracle environment. We would like
>to give our developers a list of do's and don'ts (with regards
>to data-models, stored procs, triggers, use of blobs/clobs,...)
>that would make the subsequent migration easier.

As regards the data migration including blobs I don't think you will have
any problems. Migration tools allow you to easily migrate the data.

You should care for stored procedures and triggers. Oracle developers like
to use object extensions, Oracle supplied packages (working with LOBs,
files, sending emails and so on). It is difficult to estimate work required
without knowing your procedures and triggers.

Best regards, Dmitry
--
SQLWays - Database migration software for IBM DB2, Oracle, SQL Server,
Sybase and MySQL.
http://www.ispirer.com/products

"Nikhil" <ngad...@hotmail.com> wrote in message
news:b3c8c1a0.03051...@posting.google.com...

[Daniel Morgan]

Dmitry wrote:

It is also critical to remember that Oracle's database architecture is
completely different and that code written for MVCC (multiversioning) may well
corrupt data in other environments such as DB2.

--
Daniel Morgan
http://www.outreach.washington.edu/extinfo/certprog/oad/oad_crs.asp
damo...@x.washington.edu
(replace 'x' with a 'u' to reply)

[eltonb]

Your migration project may well be done and dusted but if you're not
you might want to check in2j (http://www.in2j.com) from
Quintessence Systems.

in2j is an automated migration tool which migrates Oracle PL/SQL code
into Java. As an option, in2j will generate DB2-compliant SQL plus all
of the components you need to deploy your Java code to DB2.

You can download a trial version of in2j and just run it against your
Oracle server-code.

Hope this helps.

Elton

--
Posted via http://dbforums.com