Java System Copy: Target system installation copying Enterprise Portal (
-------------------------
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 Export/HP-UX: remote export required ( ------------------------- Java: Cleanup Script for KMC 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, youneed to remove the configuration on the target system with the help of acleanup script and then set up a new configuration. The cleanup script is available as an attachment to SAP Note 883859. ------------------------- 25/OCT/05>-------------------------- Java Export/UNIX: Error when trying to write to Solution: Change owner and group of the ------------------------- After the target central instance installation set the Java VM parameters for the J2EE Engine according to SAP Notes 723909 and 831812. ------------------------- When exporting a distributed system, using local export directories, the created exports directories need to be merged, that is copied together. Make sure that the SOURCE.PROPERTIES file is the one created when exporting the Central Instance. Otherwise the import will abort with the following error: FJS-00003 TypeError: sourceProps.get (\(in script NW_Java_OneHost ind ind ind ind, line 11804: ???) FCO-00011 the step InitPrivateContext with step Key |NW_Java_OneHost|ind|ind|ind|ind|0|NW_OneHost_System|ind|ind|ind|ind|1|0 |NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|i nd|ind|ind|3|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|InitPriva teContext was executed with status ERROR Solution: Copy the SOURCE.PROPERTIES from the Central Instance export to the Java export DVD or add the property src.id.host to the SOURCE.PROPERTIES file using the value created by the Central Instance export. ----------------------------------------------------------------------- 2 MaxDB-Specific Procedure ------------------ 23/MAY/06>---------------------------------- Homogeneous MaxDB System Copy: Exporting database statistics During a homogeneous MaxDB system copy, you can export the database statistics and import them into the target system. For exporting the database statistics call the database loader as follows: On Unix: /sapdb/programs/bin/loadercli -d The export of the statistics is performed by: EXTRACT USER STATISTICS OUTSTREAM FILE ' ------------------------ 20/APR/06>--------------------------- System Copy with Target Database MaxDB 7.6 For system copies with target database MaxDB 7.6 check SAP Note 941635 for more information. ----------------------------------------------------------------------- 3 MS SQL Server-Specific Procedure ------------------------ 24/JUL/06>--------------------------- Symptom: A dialog box with the following message appears during an export from a dbo-based system (dbs/mss/schema=dbo or not set): \database ... You can only install an SAP system in a database with no user objects belonging to the system schema dbo.\ The export cannot be continued. Solution: Proceed as follows: 1. Stop SAPinst. 2. Open the file control.xml in the sapinst log directory and look for the following lines: AllowNew: mig ? \ AllowDboObjects: mig ? \ 3. Change these lines to AllowNew: ins ? \ AllowDboObjects: ins ? \ 4. Save the control.xml, restart SAPinst and choose \installation\ ======================================================================== 4 Oracle-Specific Procedure ======================================================================== --------------------CHANGED 14/JUL/2008>------------------------- Error in sapinst_dev.log: (...)runCatprocSql This error occurs while installing oracle patch 10.2.04 only! Error: FCO-00011 The step runCatprocSql with step key NW_Onehost ind ind ind ind 0 0 NW_Onehost_System ind ind ind ind 1 0 NW_CreateDBandLoad ind in ind ind 10 0 NW_CreateDB ind ind ind ind 0 0 NW_OraDBCheck ind ind ind ind 0 0 NW_OraDBMain ind ind ind ind 0 0 NW_OraDBStd ind ind ind ind 3 NW_OraDbBuild ind ind ind ind 5 0 runCatprocSql was executed with status ERROR . Solution: 1. Edit file control.xml in your installation directory as follows: 2. Search for \ 3. Go to \4. Replace \\ 5. Restart sapinst and continue with the installation. ------------------------- BW only: Error during \of BW specific packages SAPDDIM, SAPDFACT, SAPDODS The problem occurs during the export with R3szchk while creating the DBSIZE.XML file. The tablespaces PSAP@SCHEMAID@anything are mapped to PSAP@SCHEMAID@ but in DDLORA.TPL the tablespaces are mapped to BW specific tablespaces. Solution: 6. Get the latest R3szchk from SAP Service Marketplace at: http://service.sap.com/swdc -> Download -> Support Packages and Patches -> Entry by Application Group -> SAP NetWeaver -> SAP NETWEAVER -> SAP NETWEAVER 2004S -> Entry by Component -> Application Server ABAP -> SAP KERNEL 7.00 -> -> ORACLE 7. Restart the export. The DBSIZE. XML will be created also with the BW specific tablespaces. ------------------------- Error during system copy with Oracle-specific procedure During a system copy with the Oracle-specific procedure, the following error may occur: ERROR 2007-01-04 21:48:25 [iaxxejsbas.cpp:178] EJS_ErrorReporter FJS-00003 ReferenceError: row is not defined (in script NW_Java_DB|ind|ind|ind|ind, line 90323: ???) ERROR 2007-01-04 21:48:25