Solution : https://service.sap.com/sap/support/notes/338372 (SAP Service marketplace login required)
Summary :
The SAP Note addresses issues with the migration key not working during system setups from Release 4.5B onwards. It is required to verify that the migration key was generated using correct source and target system data, which can be found in the respective system's log files, such as SAPAPPL1.log and Migkey.log. The note emphasizes the importance of using the same R/3 release for both the source and target systems' R3load tools. It also notes the sensitivity to case in versions 4.5B and 4.6B, and suggests immediate OSS messaging if the key fails, providing logs and installation numbers. Additionally, potential mismatches with database versions like ADABAS in MaxDB are discussed.
Key words :
//bas/46d/src/ins/r3load/r3load, 6c sr2 installation package, ms sql 2000 tools cd, required target system data, r3load=rel\r3load, 6d akk' cd, os/db combinations, upper/lower case, 6d installations tools, aforementioned log files
Related Notes :
| 1519000 | ERROR: invalid migration key |
| 813964 | Migration Key Wrong - Release 4.7 and Web AS 6.x |
| 715701 | Migration to SAP DB/MaxDB |
| 333097 | INST: 4.6C / 4.6C SR R/3 on UNIX/Oracle - Het. System Copy |
| 316353 | INST: 4.6D SAP Basis - Heterogeneous System Copy |
| 179150 | INST: 4.6B R/3 Inst. - Heterogeneous System Copy |
| 143059 | INST: 4.5B R/3 Inst. - Heterogeneous System Copy |