Modernizing SAP ECC and Content Server: From AS400 to Windows 2019

Recently, I had the opportunity to work on a complex migration project for a customer. This project involved migrating their SAP ECC 6.0 system from DB2/400 on OS400 to a modern Windows 2019 with MaxDB 7.9. Concurrently, we upgraded their Content Server (CS) from SAPDB 7.3 on Windows 2003 to MaxDB 7.6 on Windows 2019. Below, I’ll outline the steps we took to ensure a smooth and successful migration, highlighting some key tasks and strategies critical to the project's success.

Our first major task was to migrate the customer’s SAP ECC 6.0 system from the AS/400 environment to a Windows 2019 server with?MaxDB 7.9. This was a heterogeneous migration, requiring changes to both the operating system and the database platform.

• Preparation and Compatibility Check: We began by ensuring compatibility using the SAP Product Availability Matrix (PAM), confirming that ECC 6.0 was compatible with the latest Windows OS and MaxDB 7.9. This step was critical to avoiding potential issues during the migration process.
• Requesting Migration Key and Creating DDL: A migration key was requested through the SAP Marketplace to facilitate the migration process. We then ran the SMIGR_CREATE_DDL?report on the source system to generate the necessary table structure for MaxDB?database in the target environment.
• Export Preparation and Execution: Preparatory actions were taken to clean up the system and ensure a smooth export. These included deleting temporary tables, setting released jobs to scheduled, locking users, and clearing log tables. We also set up a maintenance license and calculated the required number of parallel jobs for the export. Using SAP's Software Provisioning Manager (SWPM), we exported the source system data and moved the export dumps to the target server for import.
• Import and Post-Import Steps: On the target Windows server, we used SWPM to import the data into MaxDB. Post-import, we applied the necessary licenses, unlocked users, and ran table checkers to verify the import's success. System parameters were adjusted to ensure optimal performance and stability.

2. Content Server Migration: From SAPDB to MaxDB

Alongside the ECC migration, we upgraded the customer’s Content Server from SAPDB 7.3 to MaxDB 7.6, aligning it with their upgraded infrastructure.

• Backup and Restoration Approach: This migration involved a homogeneous move, where a backup from SAPDB 7.3 was restored into MaxDB 7.6 on the new Windows 2019 server. This approach maintained data consistency and integrity.
• Setting Up the Target Environment: CS 7.53 with MaxDB 7.6 was installed on the target system. A new database was created using Database Studio, based on the migration backup. Parameters such as RUNDIRECTORY and DIAG_HISTORY_PATH were configured appropriately to ensure proper data and log storage.
• Database Configuration and Migration: System tables were loaded and a catalog migration was performed, bringing the database to a Unicode state, which was a requirement. The database was then brought to an ONLINE state, and a comprehensive data backup was generated to complete the migration process.

Conclusion

This project successfully migrated the customer’s SAP ECC 6.0 system and Content Server to modern platforms using the latest version of MaxDB. By carefully planning and executing each step, we ensured a seamless transition with minimal disruption, setting a foundation for future scalability and technological advancements. This project highlighted the importance of strategic planning, meticulous execution, and thorough validation in achieving successful system migrations.

?

SNOTEs Referred:

767598 - Available SAP MaxDB documentation

1995794 - Upgrade SAP DB 7.3 to SAP MaxDB 7.6 with Migration to the recent Linux Kernel

129352 - Homogeneous system copy with SAP MaxDB

2143316 - Homogeneous system copy: From SAP DB Version 7.3 with backup/recovery to SAP MaxDB Version 7.6.