Solution : https://service.sap.com/sap/support/notes/962019 (SAP Service marketplace login required)
Summary :
For copying a MaxDB Content Server database to another host, a homogeneous system copy using backup/recovery is advised if the source and target systems are compatible in terms of database version and processor byte sorting. Compatibility specifics are detailed in SAP Notes 129352 and 552464 and in the SAP MaxDB documentation. Additionally, a homogeneous system copy is executable when transitioning from LINUX 32-bit to LINUX X86_64 as outlined in Note 129352. In cases where homogeneous copying is unfeasible, a heterogeneous copy using the database loader tool (loadercli) is recommended, adhering to specific _UNICODE settings (build 7.6.05 build 11 or higher). This entails confirming the loader version and ensuring binary compatibility throughout the export/import process. Proper execution mandates the same loader for both procedures, preferring the loader from the target system for version consistency.
Key words :
grundwissen -> konzepte des datenbanksystems -> verwaltung -> replikation und high-availability -> datenbankkopie -> kompatible prozessorarchitekturen für datenbankkopien english, high availability -> database copy -> compatible processor architecture, check data execute check data, create user sapr3 password sap dba, import user data instream file ', export user data outstream file ', loader command export/import tables, loader command export/import user, cat'data instream file ', cat'data outstream file '
Related Notes :
| 1171018 | -1013 = Too many order columns during export |
| 1014782 | FAQ: MaxDB system copy |
| 744774 | Migrating the database catalog to Unicode |
| 129352 | Homogeneous system copy with MaxDB (SAP DB) |