Migration to SAP DS 4.3

[Sharvari1]

Hi All,

We are planning to migrate to SAP DS 4.3 SP03 from SAP DS 4.2 SP10. 

SAP DS 4.3 will be on a new server (Linux). The current SAP DS 4.2 SP10 runs with Oracle 12c DB. We are also planning to upgrade the DB from Oracle 12c to Oracle 19c. Oracle 19c will also be installed on a new server.

We have about 10 repositories in Production and over 1000 jobs. Due to the criticality of the jobs, we plan to do a repository wise migration and testing (so that the whole Production environment is not affected)

Our migration plan is as below :

1. Migrate the Users and dependencies to new 4.3 system (all in one go) using Promotion Management

2. Select 4 repositories from the current Production system and migrate it using Promotion Management. Upgrade the repositories using Repository Manager tool from 4.2 to 4.2 version.

3. Dis-associate the Job Servers from the migrated repositories using Server Manager (at source).

4. Use Server Manager (at destination system- 4.3 ) and define Job Servers for Repositories)

Question :

Now as we can see, there will be some repositories (jobs) which will stay in the 4.2 System with the 12c version and some repositories which will be migrated to the 4.3 system and run with underlying 19c DB.

Will this approach work? We will ensure that the same jobs would not run in both the systems (so that there is no data redundancy). 

Additionally, will the above approach work if we do an in-place upgrade of Oracle 12c to Oracle 19c (DB Server will remain the same)?

Please help !!

@SAPSupport  @Sandra_Rossi @William_Yu1 @bill_froelich 

[jmuiruri]

@Sharvari1 

I am not sure what repository wise migration means , but i will assume you are referring to a scenario where you build a new environment and do the upgrade there giving you some kind of a Zero Downtime deployment.
1. Create a new database schema
2. Use the DS 4.2 Repository Manager to create a ds 4.2 repository in the new DB schema.
3. Use al_engine cli or designer to export the repository objects from the old DS 4.2 repository to an ATL file
4. Use al_engine cli or designer to import the ATL file to the new DS 4.2 repository
5. Use the new DS 4.3 Repository to upgrade the new DS 4.2 repositories to 4.3 version.
6. Use Promotion Management to migrate CMS repository objects. The list of Objects to be promoted can be found here https://help.sap.com/docs/SAP_DATA_SERVICES/5372c7960111477e9dea8931e087870c/2a3feccf1e014fd0ba9b829...
7. Modify the repositories in CMC to ensure they point to the new 4.3 repositories
7. Register the new repositories with the Job Server
8. End-to-End testing
9. Decommission the old environment.

Scenario: Migrate to a new environment

Regards Joe

[Sharvari1]

Hi @jmuiruri , thank you for the response!

Yes , We are looking to reduce downtime of our the environment.

I will explain repo-wise approach a bit :

Say we have 10 repositories in SAP DS 4.2 env.

During migration, we will migrate 6 repositories to SAP DS 4.3 env and keep the remaining 4 to the existing (SAP DS 4.2) environment. This will ensure that the jobs in the repositories that run in the 4.2 environment run and only the jobs belonging to the 6 repositories will be down during the migration. Once we are sure that the migrated jobs run in the SAP DS 4.3 environment, we will migrate the remaining repositories to the SAP DS environment. Please let us know if we can do this kind of migration of repositories (in chunks)?

Also, do you recommend migrating using ATL files or using Promotion Management since we have 1000 jobs per repository?

Any insights will be helpful !

Regards,

Sharvari

[jmuiruri]

@Sharvari1 yeah, that should work. Promotion Management is only for migrating CMS repository objects like the CMC users, CMC repository List, etc. (see step 6 in my answer above). For Data Services Repository Objects you can use ATL file as shown in step 2,3,4,5 in my answer above..