We are going to save important import in this blog about SAP MaxDB system copy
Reason and Prerequisites
You use MaxDB /liveCache Version 7.5 or higher.
Further FAQ notes about SAP MaxDB/liveCache are available in the SAP Community Network (SCN) at:
https://wiki.scn.sap.com/wiki/x/GkM
Solution
- What is a homogeneous system copy?
We talk about a homogeneous system copy in the following cases: - The target host behaves exactly like the source host as regards byte swapping.
- The version of the target database is the same as or higher than the version of the source database. This requirement applies as of SAP MaxDB Version 7.5.
- What are big endian and little endian? Which endian do I use?
For more information, refer to SAP Note 552464. - Where do I find information about a homogeneous system copy of an SAP MaxDB database?
You can use backup and recovery to perform a homogeneous system copy of an SAP MaxDB database.
For more information about the exact procedure in addition to the installation documentation, refer to SAP Note 129352. - What is a heterogeneous system copy?
We talk about a heterogeneous system copy in the following cases: - The processor on the target host and source host does NOT use the same byte sorting (little endian -> big endian; big endian -> little endian).
- On the source host, a different database system is used than on the target host (for example, Oracle -> SAP MaxDB)
- There may be a heterogeneous SAP liveCache system copy, if neither of the conditions mentioned first applies. In the SAP liveCache environment, you should therefore refer to SAP Note 457425: Homogeneous SAP liveCache Copy.
- Which tool is used to perform a heterogeneous system copy?
In general, you can use the R3load tool for the heterogeneous system copy of an OLTP or BW database.
SAP liveCache and SAP Content Server are exceptions to this rule. - For a heterogeneous system copy of an SAP liveCache database, you cannot copy the data structures of the LCA objects. The SAP liveCache data is stored in the APO system or the SCM system, and the SAP liveCache is reinstalled on the target system. Then the data is reloaded from the APO system or SCM system to the SAP liveCache.
- Since the content server is not included in the SAP ABAP Dictionary, you cannot use R3load to perform a heterogeneous system copy. For the heterogeneous system copy, you can use the SAP MaxDB tool Loader (LOADERCLI).
- Where do I find information about a SAP liveCache system copy?
SAP Note 457425: Homogeneous liveCache copy using backup/restore
SAP Note 632357: Backing up liveCache data for SCM 4.0 or higher
SAP Note 886103: System Landscape Copy for SAP SCM (4.x)
SAP Note 210564: Copying a complete APO system - What do I have to consider after a homogeneous SAP liveCache system copy?
SAP Note 877203: Post steps after the homogeneous liveCache copy using backup/restore
The connection data for the SAP liveCache is stored in the database table DBCON. Since this table is also copied, you must ensure that the connection data is adjusted accordingly for the target system using the liveCache Assistant (transaction LC10).
SAP Note 1015489: Connection problems after system copy - How do I perform a system copy of an SAP Content Server?
SAP Note 962019: System Copy of SAP MaxDB Content Server Database
The homogeneous system copy of an SAP Content Server is performed with backup/recovery (refer to SAP Note 129352). The procedure "Relocation Documents" is described in SAP Note 389366.
The heterogeneous system copy of an SAP Content Server is performed with the SAP Max DB tool Loader and is described in SAP Note 962019. - What do I have to bear in mind for a heterogeneous system copy with R3load?
- Database parameter setting in the SAP MaxDB target system:
Size of the data cache
Ensure that a sufficient size is configured for the data cache. The general rule for productive SAP operation is that the configured data cache size amounts to 1% of the total size of the occupied data area. For the period in which the data is loaded, the cache size must be increased in accordance with the memory that is available on the host.
Database parameter MaxCPUs/MAXCPU
When loading in SAP MaxDB, you must set the database parameter MaxCPUs/MAXCPU to the number of processors in the database server. - Exporting the data
For the export, the data must be unloaded in accordance with the key sequence. For more information, see SAP Note 954268. - Export/import
With split tables, use the parallel export. We recommend that the import is performed sequentially if the records were previously unloaded in the key sequence. - Creating the indexes
Note that the large indexes must not be loaded in parallel. This ensures that several server tasks can be used to create indexes. For detailed information about creating indexes, refer to SAP Note 928037. - Precompiler runtime version
Refer to SAP Note 1043735, if you are using the following precompiler runtime versions:
>= 7.4.03.44 AND < 7.4.03.49
OR
>= 7.5.00.39 AND < 7.5.00.44 - What do I have to consider for the heterogeneous system copy of a BW system?
To load the data without impairing system performance, you must sort the data in accordance with the key sequence when unloading using R3load.
Also read the following notes:
954268 Optimization of exports: Unsorted unloading
777024 BW3.0 und BW3.1 system copy (supplementary note)
771209 NW04: System copy (supplementary note)
888210 NW 7.0 / 7.10: System copy (supplementary note) - Can I use split mirror technology for a system copy?
For more information, refer to SAP Note 371247. - Where can I find more information about system copy?
For more information about system copy, see the SAP Community Network (SCN) under the following links:
HowTo - Creating a clone of a SAP MaxDB database: https://wiki.sdn.sap.com/wiki/x/LB4B
Heterogeneous system copy: http://wiki.scn.sap.com/wiki/x/LDs