Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!drn.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!news.tiscali.de!tiscali!newsfeed1.ip.tiscali.net!proxad.net!fdn.fr!freenix!sn-xit-04!sn-xit-12!sn-xit-09!sn-post-01!supernews.com!corp.supernews.com!not-for-mail
From: DA Morgan <damorgan@psoug.org>
Newsgroups: comp.databases.oracle.server
Subject: Re: Migrating from Ingres to Oracle
Date: Wed, 14 Dec 2005 12:41:17 -0800
Organization: Ye 'Ol Disorganized NNTPCache groupie
Message-ID: <1134592871.533160@jetspin.drizzle.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <BlHnf.316$Hs.26650@news.optus.net.au>
In-Reply-To: <BlHnf.316$Hs.26650@news.optus.net.au>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cache-Post-Path: jetspin.drizzle.com!unknown@oracle.advtechserv.com
X-Cache: nntpcache 3.0.1 (see http://www.nntpcache.org/)
X-Complaints-To: abuse@supernews.com
Lines: 48
Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:257837

Michael Martin wrote:
> Has anyone migrated from Ingres to Oracle recently? Where there any major 
> issues?
> What about migrating;
> . procedure/rules to PL/SQL
> . data types
> . indexes & key, foreign constraints etc
> . non ANSI SQL
> . embedded SQL/C
> . JDBC, ODBC
> . other third party products (tuxedo etc)
> . any other issues
> 
> If you migrated, why did you go from Ingres to Oracle?
> 
> Thanks
> Michael 

 From my experience ... I've helped with a few but the most recent was
some years ago ... you should plan on rewriting everything.

In Ingres you had one type of table ... in Oracle many and lookup
tables should most likely be turned into IOTs (index organized tables).
In Ingres you didn't have near the available index types you will now
have so you need to determine, on a case-by-case basis whether B*Tree
or Bitmap or Compressed or Function based, etc. indexes will give you
what you paid for.

But there are plenty of questions that need to be answered.
1. How much data?
2. How long for the migration?
3. What is the customer expectation?
4. What Oracle expertise in your shop?
etc.

My first instinct would be to dump the data to ASCII files and
reload it.

I'd go JDBC over ODBC given the choice and be sure to thoroughly
learn about BULK COLLECT and FORALL statements. Stay away from
cursor loops except in very specialized circumstances.

HTH
-- 
Daniel A. Morgan
http://www.psoug.org
damorgan@x.washington.edu
(replace x with u to respond)
