Hi folks looking for suggestions.
upgrading from 4.2 sp3 (windows - ms sql 2008) to 4.2 sp6 (linux - sybase)
what will be best way to migrate repos with no issues?
just import atl files? or with repo smanager canwe upgrade from ms sql 2008 to sybase ?
Moving from one DBMS to another is the same without regard to which DBMS. Export the repository to an ATL and then import that ATL file into a new database/schema on the new DBMS. ATL files are platform agnostic. This isn’t a 100% solution for a Central Repository since the export process only picks up the most recent version of each object.
If you really want to maintain all versions of your central repository then you’ll need to perform a migration of your own. It isn’t all that difficult to do. Just write some ETL to migrate the data in every table in the old repository to the new repository. I would exclude AL_MACHINE_INFO in that migration.
Check the patch notes from the SP6 patches - we had a number of big problems upgrading our customers to SP6, after Sp5 had been very stable for us. There had been a flurry of patches for SP6, very shortly after release so we weren’t the only one that ran into these issues.
In the end, we went back to SP5, skipped SP6 and then went on with SP7 and SP8.
Interestingly, we didn’t have that many issues with our customers that went straight to SP6 (new installation) but pretty much all of the SP6 upgrades ran into issues. Seeing that you will doing a new installation on Linux you may be lucky.
Also check the DS 4.2 PAM documentation. Only the last 2 Service Pack releases are under SAP Mainstream Support. That being SP8, SP7 and SP6. The last patch for SP6 is Patch 6.6 - I would not expect to see many more SP6-based patches to be released. As soon as SAP releases SP9 for DS 4.2, SP6 will automatically “fall off the boat”.
In essence, if you are on SP6, Patch 6 and you run into any issues, you will most likely need to upgrade to a newer SP + Patch version anyway.