FCO-00011 The step checkForLoadType with step key
|NW_Java_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|9|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_OraDBCheck|ind|ind|ind|ind|0|0|checkForLoadType was executed with status ERROR.
Solution:
Edit the control.xml in the installation directory:
Search for \false;\
-------------------------
Error in step createTempLicense with step key.
The error depends on a wrong DDLORA.TPL and the wrong DDLORA.TPL depends on a PSAPUNDO entry intaora or iaora on the source system.
Solution: Before you start with the database installation on the target system, modify DDLORA.TPL on the export folder /
loc: USER2 PSAPUNDO 0000 APPL0 PSAP@SCHEMAID@ 0000 APPL1 .....
change to loc: APPL0 PSAP@SCHEMAID@ 0000 APPL1 .....
When you already ran into this error, you need to modify the keydb.xml so that all steps are restarted beginning with the step \or start from the beginning.
-------------------------
Windows Oracle: In chapter \the Control File Structure\of the system copy guide for the database specific system copy procedure, add the following information as Step 1: 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 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
Then continue with the other steps in the procedure.
-------------------------
Unable to assign default tablespace to user: SAPSR3
SAPinst cannot convert the old tablespace layout in DBSIZE.XML to the new tablespace layout. The tablespace mapping was not running. SOLUTION:
1. Change the old DBSIZE.XML to a new DBSIZE.XML and restart the installation from the beginning.
You get an example of a right DBSIZE.XML from an export DVD under the folder
========================================================================
5 IBM DB2 for Linux, UNIX, and Windows-Specific Procedure
========================================================================
----------------------
The following applies for an ABAP system or the ABAP part of an ABAP+Java system:
To adhere to the SAP standard naming conventions for tablespaces, we recommend that you consider renaming the tablespaces after the
installation to reflect the new system name. To do so so, enter the following command: db2 rename tablespace
Example:
db2 rename tablespace
If you use the deferred table creation function, you also have to execute the following command for each renamed tablespace using the db6util tool:
db6util -rtvt
For more information, see SAP Note 1227165.
Caution:
Make sure that you use an up-to-date version of the db6util tool. You require at least a version that supports the option -rtvt. To check the command options of the db6util tool, enter the following command: db6util -h
-------------------------
After performing a homogeneous system copy, the DBADM privilege on the database is missing for the user
Execute the following commando as user db2
-------------------------
?
Homogenous System Copy - Export of your SAP System:
If you use DB2 V9. 1 and you want to export your SAP system, proceed as follows:
To avoid severe performance problems with R3szch during the export of your SAP System,download latest R3szch and dbdb6slib from service marketand apply both to your SAP system.
For lib_dbslt, at least patch level 86 is required.
========================================================================
6 IBM DB2 for i5/OS-Specific Procedure
========================================================================
-------------------------
Heterogenous Java system copy to i5/OS: wrong imported JVM parameters
When importing a Java system from other platform to IBM System i and DB2 for i5/OS, the JVM parameters are not set to optimum values. This may cause the engine not to come up or not to perform as expected. Follow SAP note 717376 and update the JVM properties using the configtool. Pay special attention to the Java heap size, Java extension directory and the removal of \
-----------------------------------------------------------------------
7 IBM DB2 UDB for OS/390, z/OS-Specific Procedure
-------------------------
zLinux: Export of Java only system: Execution of the command \-mchkc\
Symptom: When performing an export of a Java only system on zLinux, you get an error message like the following: ERROR 2008-03-07 10:42:52.241
CJSlibModule::writeError_impl()
MUT-03010 Execution of the command \status TST_ERROR.
ERROR 2008-03-07 10:42:52.243
CJSlibModule::writeError_impl()
MUT-03010 Execution of the command \status TST_ERROR.
ERROR 2008-03-07 10:42:52.291 [sixxcstepexecute.cpp:951]
FCO-00011 The step setInstanceValues2 with step key rapidconfig ind indind ind 0 0 NW_GetCI ind ind ind ind 1 0 NW_getDBIn fo ind ind ind ind 20 NW_DB2_DBParameters ind ind ind ind 1 0 setInstanceValues2 was executed with status ERROR ( Last error reported by the step :Execution of the command \
Solution:
Proceed as described in SAP Note 1151952.
-------------------------
--
Export of j2ee System fails after thin client implementation.
Sympton: Your receive the following error message on export:
SCHWERWIEGEND: DB Error during export of J2EE_CONFIGENTRY
08.05.2008 11:48:50 com.sap.inst.jload.Jload printSQLException SCHWERWIEGEND: Message: [ibm][db2][jcc][10152][10176] Ung黮tige Position
1 oder L鋘ge 0.
08.05.2008 11:48:50 com.sap.inst.jload.Jload printSQLException SCHWERWIEGEND: SQLState: null
08.05.2008 11:48:50 com.sap.inst.jload.Jload printSQLException
Solution: Update you jcc driver, version V9.1 FP5 Special Build 20232 (see SAP Note 81737).
-----------------------------------------------------------------------
8 Windows-specific Topics
------------------ 30/MAY/06>--------------------------------- Due to a bug in JDK version 1.4.2_11, the export with jload suffers from serious performance problems. We recommended to wait for the next JDK version before performing an export from a host that is running on a Windows X86_64 server. ------------------ 04/APR/06>---------------------------------- Environment variable SAPSYSTEMNAME to be checked Before starting the export, make sure that the environment variable SAPSYSTEMNAME is set correctly in the environment of SIDADM: SAPSYSTEMNAME=SID Header Data ??R elease Status:??Re lease Status:??Release Status:Release Status:??Released on:??Released on:Released on:28.10.2008 14:42:43??Priority:??Priority:Priority:????Category:??Category:Cate gory:????Primary Component:BC-INS-MIG ??Secondary Components:??Primary Component:BC-INS-MIG ??Secondary Components:Primary Component:BC-INS-MIG ??Secondary Componen ts:BC-INS-MIG ??Secondary Components:??Secondary Components:Secondary Components:BC-INS ??Affected Releases Affected Releases Software Component SAP_APPL SAP_BASIS Release 600 71 From To And Release Release subsequent 600 600 710 710 Related Notes 1238351 - Hom./Het.System Copy SAP NW 7.0 incl. Enhancement Package 1 1177833 - DB6 specific R3szchk patches overview 1170069 - Text lines are returned twice when reading text files > 2 GB 1119611 - Width of table pools in a system copy