SAP Basis Tech Supports

Symptom

***********************************************************************
* Homogeneous and Heterogeneous System Copy
* for SAP Systems based on SAP Web Application Server 6.40
*
* This SAP Note applies to SAP systems based on
* SAP Web Application Server Java 6.40 SR1.
*
* This comprises: SAP NetWeaver ‘04 SR1
*
* You find the current version of the Java system copy guide on
* SAP Service Marketplace at:
* http://service.sap.com/instguidesNW04 –> Installation –> SAP Web AS
* –> SAP Web AS 6.40 SR1 and Related Documentation
* –> Homogeneous and Heterogeneous System Copy
* –> Homogeneous and Heterogeneous System Copy for SAP Systems based on
* SAP Web AS Java 6.40 SR1
***********************************************************************

Other terms

migration, J2EE Engine, SAP Web AS, SAP Web AS Java

Reason and Prerequisites

Problems discovered after publication of the documentation.
Note:
As of September 2006 a new version of the Installation Master DVD is available.
The DVD “6.20/6.40 Installation Master (Edition Sept. 2006)” provides the following new features:
it includes available installer and system copy functions for installations based on SAP Web AS 6.40it replaces existing Installation Master DVDs and fixes known bugsit does n o t contain new product content
If you use the DVD “6.20/6.40 Installation Master (Edition Sept. 2006)”, read SAP Note 971645 (6.40 Patch Collection Hom./Het.System Copy Java) instead of this SAP Note.
SAP Note 971645 describes the new features of the “6.20/6.40 Installation Master (Edition Sept. 2006)” DVD.

Solution

Sections of this note are:
1 Released components
2 Restrictions
3 Generating and requesting migration key
4 All Software Components and Databases
5 Software Components: SAP KW
6 Software Components: SAP EP
7 Software Components: SAP ERP / SAP CRM Java Components
8 Software Components: SAP KMC
9 Software Components: SAP XI
10 Database-specific information

Table of contents
=================

Date Section Description
———————————————————————–
30/JUN/09 4 DB6: Error for a Unicode databse>
30/NOV/07 4 Java Migration Toolkit unable to start
20/DEC/06 4 XI: Follow-Up Activities: Maintain server settings for XI profile connection before changing the exchange profile
16/NOV/06 4 XI: Follow-Up Activities: Integration Server
26/OCT/06 4 Export directory must not end with /DATA
17/OCT/06 4 SPS18: SDM installation fails
24/AUG/06 10 Oracle 10.2 for products based on SAP Web AS 6.40 – backward release
17/AUG/06 9 XI: Archive old messages to reduce export time
01/AUG/06 4 Export fails, when using the installation master
DVD for NW 2004s
13/JUL/06 10 Win Oracle: Upgrade information
27/JUN/06 4 Template Installer may not be used after a system copy
12/MAY/06 4 System copy export with incorrect SP level
04/MAY/06 4 Configuration needs to be edited after the target
system installation ( 28/APR/06 4 Database Export: The step findSoftwareComponents
aborts
06/MAR/06 9 Additional parameters in the Exchange Profile to be
checked
21/DEC/05 4 Java Export/HP-UX: remote export required ( 08/DEC/05 4 z/Linux: Target System Installation fails in step
CreateMigrationPropertyFiles
08/DEC/05 4 Database Export fails due to trailing blanks in
table UME_STRINGS
08/DEC/05 4 Visual Administrator: No default connection after
target system installation
05/DEC/05 4 HET (SP13 and SP14): Remove entries from table
BC_SCVERSION
05/DEC/05 4 Missing files on Installation Master for HP IA64 /
MaxDB)
30/NOV/05 9 Prerequisites for XI System Copy
30/NOV/05 4 Java system copy: corrupt GZIP trailer
02/NOV/05 4 Java export MaxDB: Output columns too long
27/OCT/05 8 Cleanup script for content exchange
24/OCT/05 6 EP SP12: no system copy possible
21/OCT/05 4 Java System Copy for High Availability Systems
20/OCT/05 8 section 8 added
10/AUG/05 4 EP: Heterogeneous system copy with target DB4
03/AUG/05 4 Java System Copy/Export
22/JUL/05 4 J2EE Cluster gets restarted during export ...
22/JUL/05 4 J2EE Engine does not start after installation ...
08/JUL/05 6 SP11 and higher: missing version_id.txt
18/MAY/05 4 Visual Admin lost default connection after import
04/APR/05 4 Changing JVM parameters after system copy
21/MAR/05 4 Errors in SDM logs after successful import
16/MAR/05 4 IBM JDK on zLinux: Import fails
15/MAR/05 7 XCM configuration files have not been copied
18/FEB/05 6 SP10 Portal:Web Dynpro:URL redirected to old server
28/JAN/05 5 Configure the IKS after the system copy
09/NOV/04 4 Use different SID, instance name, hostname for
target system on the same host
29/OCT/04 4 SP9: SDM installation fails when migrating from
Windows to UNIX

Sections of this note that are marked withHETonly apply to
heterogeneous system copies.
Sections of this note that are marked withHOMonly apply to
homogeneous system copies.

=======================================================================
1 Released Components
=======================================================================

The listing below provides an overview of the Java components which have been released already for system copy.
If you try to perform the system copy for a component that has not yet been released, you will receive a warning message informing you that the copy procedure might fail for this component.
CAUTION: In any case the java engine has to be on SP09 or above!

NetWeaver '04 SR1 SP09:

The following Java components can be copied:
Adobe Document Services 1.0BW Universal Data Integration 3.50BI Meta Model Repository 3.50EP Content Management Collaboration 6.0_640EP Portal Platform 6.0_640Knowledge Warehouse - Internet Knowledge Servlet 1.0XI 3.0 SPS14 - Exchange Infrastructure 3.0JDI SP15 - Java Development Infrastructure

mySAP ERP 2004 SR1 Java Components:

The following Java Components can be copied:
SAP XSS (Employee Self-Services) 5.0SAP Biller Direct (BD) 3.0SAP Internet Sales (ISA in mySAP ERP (ISA ERP) 4.0Internet Pricing & Configurator Web Application (IPC-WAC) 4.0Learning Solution # Course Content Player (LSO-CP) 3.0

mySAP CRM 4.0 SR1 Java Components:

The following Java Components can be copied:
CRM IC Web Client (ICW) 4.0_640CRM Internet Customer Self-Service (ICSS) 4.0_640SAP Internet Sales Web Applications 4.0_640 (ISA for CRM)MapBox (MBX) 4.0_640CRM Software Agent Framework (SAF) 4.0_6.40CRM Broadcast Messaging (BCM) 4.0_640CRM Intelligence Connector (INTCON) 4.0_640CRM Interaction Center Workforce Management Application Services (IC WFM AS) 4.0_640Internet Pricing & Configurator Web Applications (IPC-WAC) 4.0_640.

mySAP SRM 4.0 SR1 Java Components:

The following Java Components can be copied:
Live Auction 2.0

=======================================================================
2 Restrictions
=======================================================================

The system copy is performed by SAPinst using the Jload tool and applies to all operating systems and all databases.
For restrictions which apply to the system copy see SAP Note 711093.

=======================================================================
3 Requesting the migration key
=======================================================================

You have to proceed as follows to generate and to request your migration key for a heterogeneous Java system copy:
1. You start SAPinst on your source system as described in section "Running SAPinst on “2. You choose installation option: Migration – Database Export3. On the screen “Java System > Database Export” you choose a directory for the export file and select option “Prepare Migration Key Request”4. Choose “next” and make the requested entries on the following screens5. Result: The file SOURCE.PROPERTIES has been created.
This file contains the required data for requesting your migration key. No database export has been done!6. You attach the following informations to the customer message you created for the request for the pilot project:a) SOURCE.PROPERTIES fileb) Target OS (for example UNIX/LINUX_32 , NT/I386)c) Target DB (for exmaple ORA, MSS)
Note: Use the naming concention of the folders on the SAP Installation Master DVD

=======================================================================
4 All Databases and Software Components

=======================================================================
———————–—————————–
DB6: Error
Problem:
MUT-02041 Error occurred, first error is:
Solution:
1. Copy the installation DVD to disk.2. Go to the following directory:
\IM_WINDOWS_X86_64\SAPINST\NT\AMD64\PATCOL640\WEBAS630\DB6\COPY\PD3. In the product.xml file, search for “UNICODE” and set the value fromfalse to true.


< ![CDATA[UNICODE]]>



< ![CDATA[false]]> << change the value to true


4. Start the system copy from the copied DVD.

—————————————————-
If the error
CJS-20068 Error when running the J2EE Migration Toolkit.SOLUTION: See output of logfile / /runJmt.log: ‘An exception was thrown during the migration: null’.
occurs during the installation of the target system, you need to apply
SAP Note 1119190.
The error is fixed with SPS > 21

—————————————————-
XI – Follow-Up Activities:
Maintain the server settings for the Exchange Infrastructure profile connectionbeforeyou make changes to the exchange profile parameters.
—————————————————-
XI: Follow-Up Activities:
Integration Server:
Maintaining Prefix Numbers for Workflow and Organizational Management
Run transaction SWF_XI_CUSTOMIZING, select Maintain Definition Environment –> Maintain Prefix Numbers, and choose Perform Automatic Workflow Customizing (F9).

—————————————————-
The name of the export directory that you specify during the exportmust not end with /DATA.
Otherwise SAPinst cannot find .SQL files that may be located in the export directory /DB/.
————————
SPS 18: SDM installation fails
The target system installation aborts with the following error:
Calling SDM autoinstall returned 2
ERROR 2006-10-02 16:15:22
CJSlibModule::writeError_impl()
MUT-01014 Call of SDM API autoinstall ends with error code 2. Log file
/tmp/sapinst_instdir/NW04/COPY/IMPORT/ADDIN/COPYADDIN/ONE_HOST/SDMautoi
nstall.log
…
Installed SDM on /usr/sap/XS1/DVEBMGS63/SDM/program with warnings
For the following components the filesystem location is unknown:
software component ‘SAP_JTECHS’/’sap.com’/'SAP AG’/'1000.6.40.9.0.200411
9045630”/’0′
Solution: Skip this step by either
editing keydb.xml and replacing [ERROR] by [OK]
or
restarting SAPinst providing as additional argument
SAPINST_SKIP_ERRORSTEP=true

This problem will be fixed with SP 19.
—————————————————-
Export fails, when using the installation master DVD for NW 2004s
Exporting an NW’04 system with the installation master for NW 2004s
fails with the following error:
ERROR 2006-08-01 11:02:53
FCO-00011 The step getUsageTypes with step key |NW_Export|ind|ind|ind|
|ind|0|0|NW_Java_Export_Dialog|ind|ind|ind|ind|5|0|getUsageTypes was exe
cuted with status ERROR .
In UTL.java.log you find:
Exception in thread “main” java.lang.NoClassDefFoundError: com/sap/engin
e/offline/OfflineToolStart
Solution:
Use the installation master DVD for NW’04 for copying NW’04.
—————————————————-
The Template Installer must not be used after a system copy because it has not been tested under such condition and may break the system.
In case you accessed 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.
—————————————————-
If you perform a system copy export with a service pack level of SP13 or higher, but not the latest service pack level released by SAP for the Java stack, see SAP Note 937362 for more information BEFORE starting the export.
————————-—————————
Configuration needs to be edited after the target system installation ( After the target system installation proceed as follows:

5. Start the GUI ConfigTool6. Select File -> Configuration Editor7. Switch to edit mode8. SPS17 and lower: Open Configurations -> cluster_data -> Propertysheet instance.properties.IDXXXXX and edit the following properties if existing:instance.en.host (new value SCS host)instance.en.port (new value enqueue server port, default value is 32instance.system.id (new value CI instance number)

————————-—————————
Database Export: The step findSoftwareComponents aborts
During the dialog phase of the Database Export the following error occurs:
The step findSoftwareComponents with step key J2EE_SystemCopy_Export|ind|ind|ind|WebAS|640|0|findSoftwareComponents was executed with status ERROR.
SAPinst tries to access the URL http://:/sap/monitoring/SystemInfoServlet
The usually is 500. You may check this location in a Web browser.

If the password of the administrator user of the J2EE Engine is expired you get the following error:
ERROR 2006-02-23 18:41:06 [iaxxejsbas.cpp:170]
EJS_ErrorReporter
FJS-00003 TypeError: db. get() has no properties (in script InstallationScript_29, line 15003: ???)

Login as the J2EE administrator user and change the password. Use the GUI ConfigTool and update the secure store setting admin/password/ to the new password.

If the user is locked or the entry admin/password/ in the secure store holds an outdated password the following error can be found:
‘com.sap.ins.j2ee. UrlReader’ ‘http://lw103447:51400/sap/monitoring/SystemInfoServlet’ ‘‘ ‘XXXXXX’” finished with return code 2. Output: com.sap.ins.j2ee.UrlReader: Error connecting to http://:/sap/monitoring/SystemInfoServlet. The provided user data might be incorrect or user might be locked.

Unlock the user (e.g. transaction SU01 or SAP note 669848) and ensure that the user’s password stored in the secure store is correct (Use the GUI ConfigTool and check/update the secure store setting admin/password/).

If you use an HTTP port other then the default value above, proceed as follows:If you use the archive JSC13*.sar with patchlevel 5 or higher, either restart the export with the additional command line option J2EE_ENGINE_URL=http://: or export the environment variable J2EE_ENGINE_URL as http://: and restart the exportIf you do not use the archive JSC13*.sar with patchlevel 5 or higher, start the GUI ConfigTool and edit the secure store. Temporarily set admin/port/ to +4, persist the change selecting File -> Apply. You should revert this change when the input phase of the Database Export has finished. Note: You do not need to restart the cluster when performing these changes!If the page is redirected to the HTTPS protocol, use the archive JSC13*.sar with patchlevel 5 or higher, and either restart the export with the additional command line option J2EE_ENGINE_URL=https:// or export the environment variable J2EE_ENGINE_URL as https:// and restart the export. Make sure that the necessary certificates have been imported both for the server and the JDK.

————————-—————————
Java Export/HP-UX: remote export required ( If you want to export your J2EE engine from a HP-UX database host, continue as described in note 884452.
-------------------------————————–
z/Linux: Target System Installation fails in step
CreateMigrationPropertyFiles
Symptom: The target system installation fails with the error:
FJS-00003 TypeError: fmgt.getNode(tmp + “/” + files[i]) has no properti
es (in script InstallationScript_1, line 8969: ???)
ERROR 2005-11-30 10:25:50
FCO-00011 The step CreateMigrationPropertyFiles with step key
J2EE_SystemCopy_OneHost|ind|ind|ind|WebAS|640|0|J2EE_SystemCopy|ind|ind|
ind|ind|ind|0|J2EE_EngineEnterpriseDialogs|ind|ind|ind|WebAS||630|0|J2EE
_Engine|ind|ind|ind|J2EE_Engine|630|0|J2EE_SERVER_CORE|ind|ind|ind|ind|i
nd|0|RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|ind|0|CrateMigrationProper
tyFiles executed with status ERROR.
Solution: This error is uncritical, simply skip this step by either
editing keydb.xml and replacing [ERROR] by [OK]
or
restarting SAPinst providing as additional argument
SAPINST_SKIP_ERRORSTEP=true

Fixed with an update of the System Copy, see SAP Note 868098.
————————-————————–
Database Export fails due to trailing blanks in table UME_STRINGS
Solution: If the source system is SP 14 or higher, proceed according to
SAP note 818947. If it is SP 13 or lower open an OSS message on
BC-JAS-SEC-UME.
————————-————————–
Visual Administrator: No default connection after target system
installation
Symptom: Starting the Visual Administrator after the target system
installation, no default connection is displayed
Solution:logon as adm and edit
/usr/sap///j2ee/admin/adminCFG.properties and replace the
following lines (XX is the number of the central instance):
LOGIN_PORT=5XX04
LOGIN_HTTP_PORT=5XX05
LOGIN_SSL_PORT=5XX0106
create file /usr/sap///j2ee/admin/cfg/adminCFG.properties
and add the following lines:
connection.0.UserName=
connection.0.LoadBalancing=manual
connection.0.TransportLayer=Default
connection.0.DisplayName=Default
connection.0.Port=81
connection.0.HostName=
connection.0.DisplayIndex=0
connection.0.LookupMethod=message_server
Fixed with an update of the System Copy, see SAP Note 868098.

————————-————————–
Heterogeneous System Copy, SP13 and SP14:
Remove all records in table BC_SCVERSION before you start an export of the DB content.
Use the database administration tools of your specific database.

————————-————————–
Missing files on Installation Master for HP IA64 / MaxDB (CDs 51031148,
51030719, 51030762, 51030843, 51031122)
Symptom: On HP IA64 / MaxDB you get the error
WARNING There are parse errors in control.xml: line 3, 24:
error unable to retrieve external entity ‘control.dtd’
Workaround:
Copy the installation master and copy the DTD files from (e.g.)
SAPINST/UNIX/HPIA64/NW04SR1/WEBAS/COPY/ORA to
SAPINST/UNIX/HPIA64/NW04SR1/WEBAS/COPY/ADA and start the installation
from the copied installation master.Copy the DTD files from (e.g.)
SAPINST/UNIX/HPIA64/NW04SR1/WEBAS/COPY/ORA to the installation
directory, restart SAPinst and select ‘Continue Old Installation’.

————————-————————–
Java system copy: corrupt GZIP trailer
Symptom: 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 15 (or higher) which implements a workaround. If your system
is still on SP 14 or lower contact the hotline to check if and how
tools from SP 15 might be used nevertheless.
————————-————————–
Java export MaxDB: Output columns too long
Symptom:
During the export of MaxDB database content using Jload an error like the following appears:
ERROR 2005-09-24 14:23:17 [iaxxgenimp.cpp:653]
showDialog() FCO-00011 The step exportJ2EEDatabase with step
key
NW_Export ind ind ind ind 0 0 NW_Java_Export_Dialog ind ind ind ind 4 0
NW_JAVA_Export_DB ind ind ind ind 3 0 exportJ2EEDatabase was executed
with status ERROR .
You find an error like the following in the jload.log
24.09.05 14:23:16 com.sap.inst.jload.Jload printSQLException
SEVERE: Message: [-2003] (at 8): Output columns too long
Solution:
Apply SAP Note 883533.

————————-—————–
Java System Copy for High Availability Systems
In order to use the catalog for High Availability proceed as follows:
9. Copy the Installation Master DVD10. Create the directory /SAPINST///NW04SR1/WEBAS/COPY//HA11. Copy /SAPINST///NW04SR1/WEBAS/JAVA//HA/product.xml to the created directory12. Delete /SAPINST///NW04SR1/WEBAS/COPY//product.xml
Note: With these modifications it is not possible to use the
product_cp.catalog file anymore.

————————————————–
EP: Heterogeneous system copy with target DB4
If you want to migrate your portal from any database platform to IBM DB2 UDB for iSeries, you have to apply note 868979 in your source system before starting the export.

———————–————————–
Java System Copy/Export
Before starting the export steps on the central instance of the source system, make sure, that you have at least the same amount of disk space available in
\\SAPLOC\\\SDM\program (Windows) or /usr/sap///SDM/program (Unix)
as is used in
\\SAPLOC\\\SDM\root\origin (Windows) or /usr/sap///SDM/root/origin (Unix).
During the export some archives will be written to the program subdirectories and SAPinst will abort if there is not enough space.

————————————————–
J2EE Cluster gets restarted during export of a NetWeaver 04 Add-In system
When exporting a NetWeaver 04 Add-In the J2EE instances are restarted by the R/3 dispatchers after having been stopped by SAPinst.
Solution:
Stop the cluster manually, that is shut down all instances, when the SAPinst summary screen is being displayed or after having confirmed the summary screen.
————————————————–
J2EE Engine does not start after target system installation
Solution:
The J2EE Engine needs to be started manually after the target system installation 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.

————————-—————————
Visual Admin lost default connection after import
Symptom:
You have finished the import on the target system. When you try to start the Visual Administrator of the J2EE Engine from /usr/sap///j2ee/admin with ./go, you get the connect dialog box without ‘Default’ connection in it.
Solution:
Apply related SAP Note 739969.

————————-—————————
Changing JVM parameters after system copy
If you want to change JVM parameters after system copy using the visual Config Tool, you need to apply SAP Note 831812.

————————-—————————
Errors in SDM logs after sucessful import

Symptom:

You get an error message in callSdmViaSapinst like:
*********************************************************************
Mar 10, 2005 3:19:41 PM Error: SAP_MSS: Location of software component
‘SAP_MSS’/’sap.com’/'MAIN_xss04VAL_C’/'1000.100.0.5.0.20041207125637′
unknown.
Mar 10, 2005 3:19:41 PM Error: SAP_MSS: system component version store
not updated.
************************************************************************

Solution:

You can ignore these error messages. See also SAP Note 828978.
————————-—————————
IBM JDK on zLinux: Import fails
Symptom:
Import fails with an error message like this:
************************************************************************
09.03.2005 15:46:18 com.sap.inst.jload.Jload main
INFO: Jload -sec J52,jdbc/pool/J52,F:
\usr\sap\J52\SYS\global/security/data/SecStore.properties,F:
\usr\sap\J52\SYS\global/security/data/SecStore.key -dataDir F:
/export\JDMP -job D:\Program
Files\sapinst_instdir\NW04SR1\WEBAS_COPY\CENTRAL\ONE_HOST/IMPORT.XML
-log D:\Program
Files\sapinst_instdir\NW04SR1\WEBAS_COPY\CENTRAL\ONE_HOST/jload.log
09.03.2005 15:46:20 com.sap.inst.jload.db.DBConnection
connectViaSecureStore
INFO: connected to J52 on jdbc/pool/J52
09.03.2005 15:46:20 com.sap.inst.jload.JobStatus readStatus
INFO: status file IMPORT.sta doesn’t exist – no restart
09.03.2005 15:46:20 com.sap.inst.jload.Jload dbImport
INFO: trying to create table BC_COMPVERS
09.03.2005 15:46:20 com.sap.inst.jload.Jload logStackTrace
SCHWERWIEGEND: java.lang.ArrayIndexOutOfBoundsException
#at java.util.zip.CRC32.update(CRC32.java:51)
#at com.sap.inst.jload.io.DataFile.getNextEntry(DataFile.java:349)
#at com.sap.inst.jload.io.DataFile.findDataEntry(DataFile.java:
388)
#at com.sap.inst.jload.db.DBTable.create(DBTable.java:77)
#at com.sap.inst.jload.Jload.dbImport(Jload.java:276)
#at com.sap.inst.jload.Jload.executeJob(Jload.java:395)
#at com.sap.inst.jload.Jload.main(Jload.java:551)
09.03.2005 15:46:20 com.sap.inst.jload.db.DBConnection disconnect
INFO: disconnected
************************************************************************
Background:
The reason is on the export side: IBM JDK on zLinux damages the export
dump file.
Solution:
Apply related SAP Note 746299.

————————-—————————
Use different SID or instance number for target system on the same host:
Symptom:
You did first the export. Afterwards you uninstalled the J2EE Engine andinstalled the new system on the same host and with the same ID and instance number.
You get an error message like:
“Error while migrating controller
com.sap.sdt.mc.systemcopy.ClusterIDSwitchingController.
Reason:
A configuration with the path “cluster_data/instance.properties.ID14366″ already exists.
Solution:
Use a different system ID or instance number.

————————-—————————
SP9: SDM installation fails when migrating from Windows to UNIX
For more information see SAP note 755132.
As a workaround, you might want to fix the sdmrepository.sdc in the SDMKIT.JAR file on the Java export before installing the target system.
Otherwise you will run into the following error:
“Now, adjust substitution parameters and SDM configuration properly. After that, deploy all components with unknown filesystem location.
Probably, these components have been excluded by request when packing the SDM installation. Finally, redeploy all filesystem SDAs using the SDM command deploy with parameter softwaretype=FS Executed, but finished with warning(s). Return code: 2
TRACE [iaxxejsbas.hpp:270]
EJS_Base::dispatchFunctionCall()
JS Callback has thrown std::ESAPinstJSError: sdmmod.
errorCallingSdmCommandAp
TRACE [iaxxcwalker.cpp:301]”
Workaround:
1. Stop SAPinst2. Repair SDM repository according to SAP note 755132.3. Edit keydb.xml and set the status of step CALL_AUTO_INSTALL from ERROR to OK or restart SAPinst with the property SAPINST_SKIP_ERRORSTEP=true4. Restart SAPinst

This problem has been fixed with SP10.

=======================================================================
5 Software Components: SAP KW
=======================================================================

————————-————————–
Configure the IKS after the system copy
After the system copy, you have to configure the IKS to connect to the new ABAP backend as described in section “Post installation – Configuration on the SAP IKS” in the documentation “Installation Guide SAP Knowledge Warehouse 7.0″ on SAP Service Marketplace at: http://service.sap.com/instguidesNW04 –> Installation –> SAP KW –> Installation Guide – SAP Knowledge Warehouse.

=======================================================================
6 Software Components: SAP EP
=======================================================================

————————-—————————
EP SP12: no system copy possible
An EP system of SP12 cannot be copied. You can either copy an EP system on SP11, or you have to upgrade to SP13 or above and use the new archives provided on the SAP service market place as described in the latest version of the Java System Copy guide.
————————-—————————
SP11 and higher: missing version_id.txt
Portal system copy fails when running it on a system after applying SP Stack 11 or higher because the version_id.txt is missing in /usr/sap///j2ee/portal_misc/versions. If this problem occurs, you should copy the version_id.txt from the right folder as described in related SAP Note 847491.
————————-————————— SP10 Portal:Web Dynpro:URL redirected to old server If this problem occurs, you need to delete all entries in the PRT Cache table in the database as described in related SAP Note 798876.

=======================================================================
7 Software Components: SAP ERP / SAP CRM Java Components
=======================================================================

————————-—————————
XCM configuration files have not been copied
Symptom:
You have performed a system copy of a SAP Web AS 6.40 SRJava system with applications that have been configured with the XCM Administrator, for example SAP CRM 4.0 SR1 Java Applications, Biller Direct. After the system copy, the XCM settings are not available on the target system.
Procedure:
The XCM files are located in the subfolder xcm in sys.global.dir. You need to use the operation system commands to copy this directory and its contents from the sys.global.dir of the source system to the target system as described in SAP Note 827177.

=======================================================================
8 Software Components: SAP KMC
=======================================================================

————————-————————–

Cleanup Script for Content Exchange

If content exchange is configured on the source system, the same configuration exists on the target system after the system copy. However, in most cases, it does not makes sense to have the same configuration on both the source and target system. For this reason, you need to remove the configuration on the target system with the help of a cleanup script and then set up a new configuration. The cleanup script is available as an attachment to SAP Note 883859.
———————————————————————–

General KMC aspect: Filesystem related repositories

KMC in source system might have various filesystem related repository managers configured. FSDB, DBFS or pure FS are supported modi for storage, access and handling of resources within repository managers. Aspects for choosing particular persistence mode are diversified, see also e.g. note 605246. The most popular idea is to connect existing fileserver landscapes to CM. Therefore the common nature is to have ‘remote’ FS configured outside the portal server/s, storing huge amount of data.
The configuration is done in CM configuration framework (e.g. network path, RM), corresponding configuration files are stored in DB and included in the system copy. If the CM configuration is using definitions like ’servername\share’ for localroot and the mount definition in network path, the copied config enables repository manager in target system as well. This in fact depends on the defined users / if these still work on another host, different domain. Local folder definitions won’t work.

Scope of the system copy tool

According to the nature of FS related repositories the copying of any content of referenced FS is not intented and can not be in the scope of the system copy.
If using Filesystem related repositories be sure to have a project specific concept how to handle existing configuration in the target system during preperation phase. Therefore before copying an analysis of the current configuration should be done in this context.
To review target system should be a post copy step. After copying, the component monitor should be used to identify not running repositories.
There are at least three options how to handle FS destinations:
Copy shared folder to other location and configure connection accordingly. This procedure has a limitation: By copying content to other FS location the metadata will change (date), hence the synchronizer will identify them to be new and remove corresponding metadata in DB. ‘Live’ properties in CM like last read, modified by won’t be available any more in target system.Use the original locations, adjust configuration if required.Create new FS destinations if data is not relevant for copied system.

a) Other options to transfer Repository content incl. Metadata
The ‘Portal Drive’ could be used to restore original state / content of repositories. See e.g.:

b) Synchronizer FS <-> DB
What happens to metadata in DB if FS not available ? – The Synchronizer for FSDB persistence checks if defined localroot is accessible, if FS is not accessible at all no corresponding metadata in DB will be removed.

c) Concurrent access to relevant data on FS
Be aware if having several system running with identical CM configuration then identical FS are being used. This could endanger the content on the FS – something critical if productive content.
Concurrent access should be avoided in general as this can lead to inconsistencies.

d) ‘etc’ repository manager
The only default Filesystem repository manager of CM ‘etc’ is covered by the system copy tool as this is a essential system folder of CM.

=======================================================================
9 Software Components: SAP XI
=======================================================================

————————-————————–
After messages have been processed sucessfully, they are kept in the database for a certain period of time. The data volume of these messages significantly influences the time for export/import. Therefore we strongly recommend to reduce the amount of data by archiving or deleting messages before starting the export.
For further information, see the SAP Library at help.sap.com/nw04 -> SAP NetWeaver -> SAP NetWeaver Technical Operations Manual -> Additional Administration of SAP NetWeaver Components -> SAP Exchange Infrastructure -> Monitoring of SAP Exchange Infrastructure -> Data Archiving

————————-————————–
The pre-requisites for copying a XI system are:
XI 3.0 SPS 14SWC ‘XITOOL’: patch level 1 or higher (available on Service Market Place)

After the system copy process is completed please follow the instructions for follow-up activities as described in this guide in section “Configuration Steps for SAP Exchange Infrastructure (XI)”.
————————-—————————
Section 5.2.2.4.3 gives an overview of parameters in the Exchange Profile that are to be checked. Additionally, check the following parameters:
com.sap.aii.connect.directory.rmiportcom.sap.aii.connect.repository.rmiportcom.sap.aii.connect.integrationserver.httpportcom.sap.aii.connect.integrationserver.httpsport

=======================================================================
10 Database-Specific Information
=======================================================================

————————-————————–
Oracle 10.2 for products based on SAP Web AS 6.40 – backward release
A installation with Oracle 10.2 is possible with the SAP versions described in SAP Note 940794.
Exporting the source system:
Your source system runs with oracle 10.2 but there is no new installation master DVD for your release. The export should be performed with one of the available installation master DVDs of your installed product.
Installing the target system:
A direct installation or a system copy with Oracle 10.2 is only possible with the current SAP versions on the relevant kernel versions. Older versions must first be installed or copied with Oracle 9.20 and then the database is upgraded afterwards. A direct installation with oracle 10.2 is only possible with the versions described in SAP Note 940794.
————————-————————–
Windows Oracle:In chapter “Generating the Control File Structure” of the system copy guide for the database specific system copy procedure, add the following information as Step 1:
If you want to migrate your database from 32-bit to 64-bit or vice versa, add the following lines at the bottom of the control.sql file for Oracle 9.2 or Oracle 10.2:

Oracle 9.2: shutdown immediate
startup restrict
spool utlirp.log
@?/rdbms/admin/utlirp.sql
spool off
alter system disable restricted session
Oracle 10.2 shutdown immediate
startup upgrade
spool utlirp.log
@?/rdbms/admin/utlirp.sql
spool off
Shutdown immediate
Startup
Spool utlrp.log
@?/rdbms/admin/utlrp.sql
Spool off
exit
Continue with the other steps in the procedure.