HP3000-L Archives

July 2003, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Shahan, Ray" <[log in to unmask]>
Reply To:
Shahan, Ray
Date:
Fri, 25 Jul 2003 08:33:48 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (69 lines)
Jay, I worked on a project several (actually, many) years ago where we
migrated an NCR system that was KSAM file based to an hp that was ALLBASE
based (hp's answer (sort of) to Oracle).  What we found was that most of the
pitfalls were a result of trying to "make-a-better-system" while also trying
to migrate the data.  Once we set about just making the ALLBASE DB mimic the
KSAM files, we had a much better success rate.  Mind you, bad data still
gave us fits, but we could at least do parallel functionality with respect
to the current programs/reports/etc. to prove that we had migrated the data
correctly.

After we got the data migrated, then we started to do the
"let's-make-this-the-greatest-system-ever-devised" thing.

So, in a nutshell, to ensure a timely and accurate migration...do not try to
enhance/modify your system with the new tools/etc. until you actually have
the data migrated.  The migration should be a project in and of itself.


HTH,


Ray Shahan

"There is so much good in the worst of us,
and so much bad in the best of us,
that it behooves none of us
to talk about the rest of us"
                  --Robert Louis Stevenson?

> -----Original Message-----
> From: Jay Chandru [SMTP:[log in to unmask]]
> Sent: Thursday, July 24, 2003 8:33 PM
> To:   [log in to unmask]
> Subject:      Data migration from Turbo Image to Oracle Apps (11i)
>
> Data migration from Turbo Image to Oracle Apps (11i)
>
> 1. Identify the databases and datasets that are to be migrated
> 2. Map fields of each dataset to fields in a relational database
> 3. Establish the relation ships in the relational database
> 4. Apply validations and correction routines to the data in relational
> database
> 5. populate oracle internal tables from the relational database
> 6. run oracle interface to populate the oracle apps tables
> 7. Repeat this process until the data migrated is clean
>
> If anybody has worked on a similar assignment or anybody who has an idea
> about the possible holes in such a migration or any damn knowledge of the
> same, pls. share
>
> Thank you,
> Jay
>
> _________________________________________________________________
> They are beautiful. They are in danger.
> http://server1.msn.co.in/Slideshow/BeautyoftheBeast/index.asp Our
> four-legged friends.
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

#####################################################################################
This e-mail message has been scanned for Viruses and Content and cleared
by MailMarshal
#####################################################################################

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2