« Data migration testing project - what are the key things to consider? | Main | Does any available technology allow for complex data mapping modeling and auto-code generation? »
Friday
Oct032008

Need advice on migrating from Tandem to Oracle with zero downtime and synchronisation

We need to migrate customer and financial data for a cable company from legacy system to new system with almost zero downtime.

Cutoff is performed for cycles B,C,D and finally A. ( 1,8,16,22 of the month respectively). Conversion will take place after 22nd Cutoff.

The legacy system is on Tandem platform.

Our architecture is to extract from tandem DB->create UF/IF (Intermediary files)->load to Oracle DB. So the target system is Oracle DB.

One Approach is to perform staged conversion and to migrate when there is the lowest delta in changes between cutoff and ongoing conversion window (estimated 24 hours).

We are not sure how it can be done on the tandem SQL since the data do not contain any timestamp.

Any suggestions on this or suggestions for any other better approach will be highly appreciated.

Thanks

References (27)

References allow you to track sources for this article, as well as articles that were written in response to this article.

Reader Comments (1)

John Platten says...
Posted 03 October 2008
I worked on a project with a near identical situation recently: (possibly even the same company?)

The answer in our case was that the team who controlled the Tandem box worked out how they were going to identify which customers moved when, and they had to write additional software to do that. Then there is the question of existing customers in difficult states such as new service requests, plus any failed uploads - all of which would have to be managed with by the Tandem team again dealing with the consequences programmatically without disrupting the flow of the non-stop system.

It's coping with a non-stop source complex ...Yes.

The general answer is that you can't afford to "stand off" as much from the legacy day to day operations teams as you might in a standard migration, or treat the source as "just tables" The problem is a shared one with a shared solution.

Regards

John Platten

Vivamex Limited
www.sapdatamigration.co.uk
www.vivamex.com

Mon, October 20 | Unregistered CommenterJohn Platten
Member Account Required
You must have a member account on this website in order to post comments. Log in to your account to enable posting.