Discussion Locked

Unix to Oracle: What are the problems ?

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am the Quality Assurance Manager
for a small (40-60 people) manufacturing
firm. Our customer base is primarily the
commercial nuclear power industry and the
DoE. Historically the problem areas for
these customers is in the documentation
side (i.e., product certifications,
metrics etc.).
Management has decided to switch from a
unix based software package to Oracle. In
the past, damage control versus quality
control has been the norm. Aside from the
obvious "Get involved at the beginning!",
what should I be on the look-out for ?

5 replies

by smithjj

1. List your current functions of your system.
2. List the current data fields.
3. Export your data to an ASCII type file.
4. Create the proper field mapping from your old system to your new.
5. import your data to your Oracle application.
6. LIst the functions of your new system.
7. Map the functions from the old system to the new.
8. Develop training to migrate from the old to the new system. Focus on each old function, then add the new ones.

Good luck!

by nucthat1

Don't quite know how the proposed answer resolves my question: what pitfalls should I look out for ?

by mmoran

Jim,

Was a little confused at your statement switching from a UNIX system to an Oracle system - as Oracle is a database that runs on the UNIX platform (as well as NT). Are they purchasing an application that utilizes Oracle, or writing one from scratch?

Send me a couple more details, and I think I can have quite a bit of insight for you - I've been doing these types of conversions for 15 years.

Miriam

This discussion is closed to new replies.