Skip to Content
author's profile photo Former Member
Former Member

BO DI Migration from 6.5 to XI R2

Hi All,

We are planning to migrate BO DI 6.5 to BO DI XI, Please share your experience with refards to same in terms of

1) Initial preparation that needs to taken care of before upgradation

2) Which method is good directly upgrading to BO DI XI or deinstall 6.5 and then install BO DI XI and do the server configuration.

3) Challenges Faced

4) Methedology Adopted.

5) Job Testing method after migration.

6) Benefits got for migration from 6.5 to XI.

Current configuration of our server is BO DI 6.5, Windows 2003 Service Pack1, 8 processor, 4 GB RAM.

Thanks In Advance

Hitesh

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Aug 11, 2008 at 12:57 PM

    Recently done an upgrade from 11.0.0.x to 11.7.3.0, the end of the R2 releases. R3 is the 12.x versions.

    1) Initial preparation that needs to taken care of before upgradation

    Review of the new features, what is usefull and what is not

    Recommended upgrade procedures

    Dry-runs of those procedures to get some feeling about it

    First repository upgraded and loads of runs of those jobs, performance, load, stability etc

    Testing of the new load balancing and new features around the server installation

    2) Which method is good directly upgrading to BO DI XI or deinstall 6.5 and then install BO DI XI and do the server configuration.

    It depends on how many boxes you have available. We choose to go for a complete new environment from scratch where there was new hardware, OS and DI installation. But that was also because the upgrade took months (200+ complex jobs, old documentation etc). With a small environment you can choose to install the new version beside your old version on the same box, but keep in mind that the jobs share a lot in comon (source, target, files etc). Strongly recommended is to use new repository schema's so that you can fall back to the old version and you do not mix old and new.

    3) Challenges Faced

    Outdated documentation. Test approach. A very few bugs due to upgrade. Changed logic due to upgrade.

    4) Methedology Adopted.

    Create new repo

    Impart atl's

    Upgrade repo

    Run jobs and compare output with old environment

    No changes: sign off

    Changes: explain changes or correct the job

    5) Job Testing method after migration.

    Biggest challenge was to find decent output of the jobs that could be compared with a tool. Either flat files, download files or dumps from tables in to flat files and then compare it.

    6) Benefits got for migration from 6.5 to XI.

    Really depends on your requirements. You are facing a 3-4 years difference in the tool, there is a lot different and improved.

    6.5 is not supported or going out of support very soon. Do still need support?

    New fancy features and tricks in 11.7.x are very cool, but do you need it?

    Stability and performance. Is your old environment stable?

    Do you want load balancing? 11.7.x is much better in that.

    Edit: crap, did not see that it was an old post...

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.