07/NOV/06>----------------------------
Heterogeneous BW system copy: Missing P indexes
Follow the instructions as described in SAP Note 996263.
------------------------ 26/OCT/06>---------------------------- The name of the export directory that you specify during the export must not end with /DATA. Otherwise SAPinst cannot find ------------------------ 04/AUG/06>---------------------------- ABAP/HET: Enter Migration Key When installing the target system's database instance during a heterogeneous system copy, you either have to choose parameter mode 'Custom' or have to check the dialog 'SAP System > Database Import' on the summary screen and then revise this dialog. Only then appears the dialog screen where you can enter the migration key, which is required for a heterogenous system copy. If you forget to revise this dialog setting during the dialog phase, SAPinst will abort in the processing phase when checking the migration key and will ask you for a valid migration key. ------------------------ 27/JUN/06>---------------------------- The Template Installer may not be used after a system copy because it has not been tested under such condition and may break the system. In case you access the Template Installer after the system copy nevertheless, you would notice that it still displays the old SID and host name that the system had before the copy. This information is fetched from a file that has been created by installation that is not updated by the system copy process. This has no adverse effects, because it is used only by the Template Installer, which must not be executed under this condition anyway. ------------------ 12/MAY/06>---------------------------------- System copy export with incorrect SP level If you perform a system copy export with a service pack level that is not the latest service pack level released by SAP for the Java stack, see SAP Note 937362 for more information. ------------------------- 09/MAY/06>--------------------------- ABAP import fails with 'invalid migration key' The ABAP import aborts when checking the migration key. In the logfile test_MIGKEY.log the following error message appears: ERROR: invalid migration key Prerequisites: The source system has already installed a new, digitally signed SAP license. You can check this by calling transaction SLICENSE: The license is only displayed when you click on the 'New Licenses' button. Solution: Use the following migration key (valid until 31/DEC/08): 1G5fdEM50TMIrBzjt6TE5Pae ------------------------- Configuration needs to be edited after the target system installation (< SPS9) After the target system installation proceed as follows: 1. Start the GUI ConfigTool 2. Select File -> Configuration Editor 3. Switch to edit mode 4. SPS9 and lower: Open Configurations -> cluster_data -> Propertysheet instance.properties.IDXXXXX and edit the following properties: ? ? instance.en.host (new value SCS host) instance.en.port (new value enqueue server port, default value is 32 instance.system.id (new value CI instance number) ? ------------------------- J2EE Engine does not start after target system installation Solution: The J2EE Engine needs to be started manually after the target system has been installed and the follow-up acitivities have been performed. In order to start the J2EE Engine of a copied Add-In system, the whole instance must be restarted. ------------------------- Fix import of NetWeaver 2004s SPS06 and higher for AMD64, AS/400 with respect to the Java parameter settings ------------------------- Doublestack export DB2 on Unix: Export Preparation with modified control.xml from SAP Marketplace. If you want to perform a systemcopy with DB2 UDB source database on Unix using parallelly export/import feature by choosing SAP NetWeaver 2004s/Business Suite Application 2005 --> Lifecycle Management --> System Copy --> IBM DB2 UDB for UNIX and Windows --> Source System --> Central/Distributed/HA System --> Based on AS-ABAP and AS-Java--> Export Preparation You have to download the control.xml from SAP Service Marketplace. You can find patch PrepExpDB6NW04S at http://service.sap.com/swdc Support Packages and Patches SAP KERNEL 7.00 32/64-BIT _ PrepExpDB6NW04S patch #1 To run SAPinst with the new control.xml: Copy the Installation Master CD local and replace on CD: Or start SAPinst, choose the 'Export Preparation' option, abort after the first dialog, replace the control.xml in the installation directory and restart teh SAPinst. Choose the 'Export Preparation' option again and choose 'Continue old installation' on the next dialog. ------------------------- System copy import fails during 'unpackSDMKITJAR' Symptom: Target system import fails during the unpackSDMKITJAR with such error : ' Bug in some Java virtual machine implementations cause problems when getting the uncompressed size of big zip archive entries. The problem depends on the actual Java virtual machine implementation. Solution: See SAP Note 904245. ------------------------- During DB import with jload GZIPInputStream throws an IOException complaining (falsely) about a corrupt GZIP trailer. Reason: The system contains at least one large table whose export generates more than 2 GB of uncompressed data. Compression with GZIPOutputStream will not lead to an error but the GZIP trailer written to the end of the output stream will not be interpreted correctly by GZIPInputStream. Workaround: Until the problem will be fixed in the JDKs use a jload from SP 6 (or higher) which implements a workaround. If your system is still on SP 5 or lower contact the hotline to check if and how tools from SP 6 might be used nevertheless. ------------------------- Java Export: error in SDM call createsdmkitjar Symptom: The export aborts in step packSDMKitJar (Export Java Central Instance) with the following error message: Warning: Warning during command execution: No location information available for software component 'SAP-JEECOR'/'sap.com'/'SAP AG'/ '1000.7.00.4.1.20050921171700'. Cannot pack this archive. Missing archives may lead to errors after the packed SDM installation has been extracted later. Info: This SDM installation has been packed to /sapdb/EXP/JAVA/SDM/SDMKIT.JAR To unpack this installation again, extract /sapdb/EXP/JAVA/SDM/SDMKIT. JAR and invoke the SDM command install with parameter extractpackedinst=true Solution: Stop sapinst. Then restart sapinst with the additional parameter 'SAPINST_SKIP_ERRORSTEP=true'. ------------------------- Java System Copy: Frequent Restart of J2EE Engine on Target Host Symptom: After a system copy the J2EE engine frequently restarts on the target system when running with a HP or SUN JDK. Solution: Enlarge the parameters PermSize and MaxPermSize. The values depend on the number and complexity of your deployed applications. If the source JDK was an HP or SUN JDK as well, use the values from the source system. For more information, see SAP Note 723909. ------------------------- If after the system copy, the KM icons are not displayed and services do not start up, you need to adapt the path to the shared KM configuration folder. On each machine in a cluster: 1. Log on to the portal 2. Choose System Administration -> System Configuration -> Knowledge Management -> Content Management -> Repository Managers -> File System Repository 3. Select the etc repository and choose Edit. 4. Set the parameter for Root directory appropriately for your operating system: UNIX: /sapmnt/< SID>/global/config/cm/etc Windows: // 5. To ensure that the correct path is preserved during an upgrade, also enter the path (without etc) in the cm.properties file. The file is located on the machine of the central instance under: o UNIX: Change the value of the parameter System.SharedFolder to: /sapmnt/ WINDOWS: Change the value of the parameter System.SharedFolder to: // o 6. Restart the J2EE engine to activate the settings. -------------------------