Which migration approach is best for 4.0 to 4.2 upgrade

dataservices job design
1

HI All,

We are currently working on migration of 4.0 jobs to 4.2 Sp1 version. Our repository in 4.0 is SQLserver and in 4.2 we built on DB2 10.1, I came across 2 methods of migration

  1. atl import
  2. repository upgrade

For our scenario which is best to use, any suggestions. and I am nto aware of steps invovled in repositroy upgrade, could some one give insight into these details.

Thanks in advance
Pavani

pavani_yerra (BOB member since 2010-04-28)

2

You’re rather limited in how you can do the upgrade since you are moving from SQL Server to DB2.

  1. Create 4.0 repository in DB2 using the 4.0 Repository Manager
  2. Export repository from SQL Server to an ATL file using either 4.0 Designer or the 4.0 AL_ENGINE.
  3. Import the ATL file using either 4.0 Designer or the 4.0 AL_ENGINE.
  4. Upgrade the repository using 4.2 Repository Manager.

eganjp :us: (BOB member since 2007-09-12)

3

If we do direct import of Atl file from 4.0 to 4.2 cause any issues to the build. We cannot create a DB2 repository in 4.0 that’s the constraint.

pavani_yerra (BOB member since 2010-04-28)

4

Why can’t you create a 4.0 repository in DB2?

eganjp :us: (BOB member since 2007-09-12)

5

I verified PAM and DB2 is still supported…

ganeshxp :us: (BOB member since 2008-07-17)

6

we do not have sign off from Business on this requirement. and the current 4.2 installation is on brand new servers. Please let me know if we are good with atl migration or we need to go for repository upgrade too.

Regards
Pavani

pavani_yerra (BOB member since 2010-04-28)

7

I wouldn’t take any chances. Do the upgrade like I posted above.

eganjp :us: (BOB member since 2007-09-12)

8

Hello,

I plan to upgrade my BODS environment from BODS 4.1 SP1 Patch to BODS 4.2 SP1 (with the correct IPS version also)
I would like to avoid repository upgrade, but do the following way:

  • export my BODS 4.1 jobs as .atl
  • scratch my BODS 4.1 repository DB
  • uninstall BODS 4.1
    - install new BODS 4.2 repository DB
  • install BODS 4.2
  • import my BODS4.1 .atl into the new BODS 4.2 repository

(I m not able to test it now, because I have access problems on the SAP support site since several days, that prevents me from downloading the kits/patches :frowning: )

Do you think those BODS 4.1 atl will work as-they-are on BODS 4.2 without any job modification ?

Thanks,

dida (BOB member since 2013-01-23)

9

dida, you should not use ANY of the information in this thread as guidance for YOUR upgrade if the repository DBMS is not changing.

eganjp :us: (BOB member since 2007-09-12)

10

Jim’s approach is the only approach to perform an actual DS UPGRADE.
There is no such thing as a “ATL Upgrade”.

Importing a DS 4.0/4.1 ATL file into a DS 4.2 repository will NOT upgrade your structures contained within those jobs to meet the new DS 4.2 structures - you are basically “ramming” the ETL script down the throat of your DS 4.2 repository and you really have no idea what the impact is. (Think square peg, round hole.)

ErikR :new_zealand: (BOB member since 2007-01-10)