View Single Post
  #6 (permalink)  
Old September 24th, 2007, 08:00
ianlo ianlo is offline
Senior Member and Blogger
 
Join Date: Dec 2006
Location: Singapore
Posts: 149
Blog Entries: 5
Thanks: 5
Thanked 11 Times in 10 Posts
Groans: 0
Groaned at 1 Time in 1 Post
Rep Power: 2
ianlo is on a distinguished road
Send a message via AIM to ianlo Send a message via Skype™ to ianlo
Re: Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

Quote:
Originally Posted by sknmail@rediffmail.com View Post
Thanks Ian.
Do you have any feedback on the issues that exists from your sites where OTM 55 CU3 is installed.

Based on the issues encountered, do you think CU3 is a stable Release to apply on.

- Thanks,
Suresh
Hi Suresh,

Thats a difficult question to answer as each implementation will have its own fair share of issues to be resolved. I can only give you some memorable ones however I cannot guarantee that you will/will not encounter them. The best way to do this is through multiple rounds of regression testing.

1) Implement 5.5 in test env
2) Execute detailed regression testing
3) Identify and record issues from (2) and fix them
4) Retest (until no more issues)
5) Rehearse migration
6) Fix issues
7) Rehearse migration (until confident)

That was our approach and we took no less than 3 months to test and re-test and 1 solid month of migration rehearsals. Even then, we had issues during the migration!

What I can share is this:

1) Watch out for integration - files with UTF-8 BOM will be rejected in 5.5
2) Watch out for Agents and Direct SQLs executing in them - esp note that $Gid is now $gid!
3) Watch out for your custom stored procedures / triggers (if any) - schema changes have caused me some stomach aches.
4) Test, test, test and RE-TEST!
5) Pray and hope for a smooth migration

Hope this helps!

Ian
Reply With Quote