To ensure a smooth migration process, it is recommended to prepare for the SAP OS/DB Migration Check analysis session well in advance. This analysis session should be performed on the productive SAP system (referred to as the source system) before the final migration takes place.
Migration test runs are conducted iteratively to determine the optimal configuration for the target system. While a single test run may be sufficient in some cases, it is possible that multiple repeated runs are necessary to fine-tune the migration process. It's important to note that the same project procedure applies to both the OS migration and the DB migration.
It's crucial to emphasize that these analysis sessions and test runs are conducted in the production environment for the sole purpose of checking requirements and ensuring a successful migration. No actual changes are made to the production system during this phase.
Test and final migrations are mandatory for productive SAP systems, while other systems like development, test, or quality assurance systems are typically less critical in terms of downtime. If the initial test run of these systems yields satisfactory results, an additional migration run (final migration) is not required.
The SAP OS/DB Migration Check Analysis Session is performed on the production migration source system and the SAP OS/DB Migration Check Verification Session runs on the migrated production system after the final migration.
If a table exists on the DB but not in the ABAP Dictionary, the table will not be exported if no valid run-time object exists. Run the R3LDCTL standalone to generate the *.STR files in order to check whether the table is included or not. If it is not included, investigate whether the table is required or can be recreated on the target.
If a table exists in the ABAP Dictionary but not on the DB, the export of this object will fail. To solve this issue, you can create the object on the DB, or to skip the export error. The table will be created on the target system.
To ensure safety and enable easy troubleshooting, it is recommended to use separate hardware for OS/DB migration on a productive SAP system, allowing for fallback to the old system in case of major issues.
SAP OS/DB Migration Check Service request : A request needs to be submitted to Customer Interaction Center with the following information : Name of the OS/DB migration certified person who will perform the migration ,Description of the productive source system(s) , Description of the productive target system(s) (following needs to be added SAP System Release , DB Type , DB version , DB size , OS Type and Version , Unicode Version ), Target date for test and final migration of the productive system(s), Plan date for SAP OS/DB Migration Check Analysis Session delivery , Plan date for SAP OS/DB Migration Verification Session delivery.
In the SAP OS/DB Migration Check following things are taken care of :
Perform an SAP OS/DB Migration Check Analysis as soon as the migration project is approved.
Check the production system for migration readiness.
Review and adjust SAP system and database parameters at the target.
Analyze performance in the Source SAP system and the database.
Provide recommendations for the migration target system.
Focus on platform or database-specific aspects during the analysis session.
Conduct the analysis on the productive SAP system considering the target migration environment.
Document the migration check results in detail and is shared with the customer through the SAP Service Marketplace.
Recommendations for the migration target system are included in the analysis results.
Conduct checks for both ABAP and JAVA-based SAP system components.
In the SAP OS/DB Migration Check Verification following things are taken care of :
Wait for 4 weeks after the final migration for SAP OS/DB Migration Check verification, as sufficient data needs to be collected for a comprehensive performance analysis.
Ensure that the previous production system remains accessible during this period.
Analyze SAP system and database logs to identify any potential issues or anomalies.
Evaluate response times of critical transactions to gauge system performance.
Identify and address performance bottlenecks in both the SAP system and database.
Optimize SAP system and database parameters for improved efficiency.
Conduct checks for both ABAP and JAVA-based SAP systems to ensure proper functionality and compatibility.