Error in SAPinst (problem in import abap)

Hi All,
I'm trying to install SAP ECC6.It run smoothly up to unpack Import ABAP.Then installation stopped showing Error
ERROR 2010-08-08 15:32:27
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2010-08-08 15:32:27
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
The last line in SAPCLUST.log,SAPSSEXC.log,SAPAPPL2.log is
C:\usr\sap\IDS\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
C:\usr\sap\IDS\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20100808153003
Looking forward for a solution to this.
Any Help would be appreciated.
Thanks & regards,
Tejinder Paul

Hi Paul,
Could you paste the out put of logfile
import_monitor.java.log
Regards
Ashok

Similar Messages

Problem in Import Abap phase

Hi Gurus
I am installing ECC6 SR3 in one of the test systems (Windows 2008 R2, 3GB RAM, Core2Duo) . I used 3 R3loads for import Abap. My problem is, out of the total 28 tasks, 27 have finished successfully but SAPAPPL2 is causing problem. Generally R3load will take around 750MB of RAM each during import. All the tasks have finished with this memory. However, as soon as the R3load starts processing SAPAPPL2 task, the RAM consumption by it increases dramatically to 100%, meaning it eats up all the RAM, leaving oracle with less than 3MB to perfrom!!! That is causing import to be too slow to be barely noticed. Can somebody tell me what is happening here?
I have tried increasing SGA for oracle and db writer process but no help. Even the oracle starts with around 250MB, as soon as R3load takes over, it just goes down.
I have tried with latest R3lload too. Nothing helps here. Did somebody see this before?
Thanks
Javed

Dear Javed,
Can you please check the permissions and owner of /usr/sap/trans directory.
Also please take a complete OS restart and try again through sapinst.
I faced this problem and I did these above things and my problem was resolved.
Also provide the error log description.
Regards
Pranay

Create Index error on all jobs of import abap installation phase

Hello,
I'm facing an issue on import abap phase on IDES SAP ERP 2004 installation over SLES 11/MaxDB 7.6.03 build 9.
Logs below are focused on table REPOSRC because it is the first error over installation, the same error appear again and again for the next tables.
We ran the installation again changing the number of parallel processes to 1 job at time but finally nothing change.
sapdb log size : -rw-rw---- 1 sdb sdba 8808038400 Mar 30 23:01 DISKL001
cache_size = 159488
Thanks in advance, Deiby
import_monitor.log
TRACE: 2010-03-29 16:53:00 com.sap.inst.migmon.LoadTask run
Loading of 'REPOSRC' import package is started.
TRACE: 2010-03-29 16:53:00 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'REPOSRC' import package:
/usr/sap/IDS/SYS/exe/run/R3load -ctf I /software/51034985/51034985_2/EXP2/DATA/REPOSRC.STR /tmp/sapinst_instdir/ERP/SYSTEM/ADA/CENTRAL/AS/DDLADA.TPL REPOSRC.TSK ADA -l REPOSRC.log
TRACE: 2010-03-29 16:53:00 com.sap.inst.migmon.LoadTask processPackage
Loading of 'REPOSRC' import package into database:
/usr/sap/IDS/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -nolog -c 10000
ERROR: 2010-03-29 16:53:04 com.sap.inst.migmon.LoadTask run
Loading of 'REPOSRC' import package is interrupted with R3load error.
Process '/usr/sap/IDS/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -nolog -c 10000' exited with return code 2.
For mode details see 'REPOSRC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
REPOSRC.log
/usr/sap/IDS/SYS/exe/run/R3load: START OF LOG: 20100329165300
/usr/sap/IDS/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/IDS/SYS/exe/run/R3load: version R7.00/V1.4
Compiled Jan 23 2008 17:32:58
/usr/sap/IDS/SYS/exe/run/R3load -ctf I /software/51034985/51034985_2/EXP2/DATA/REPOSRC.STR /tmp/sapinst_instdir/ERP/SYSTEM/ADA/CENTRAL/AS/DDLADA.TPL REPOSRC.TSK ADA -l REPOSRC.log
/usr/sap/IDS/SYS/exe/run/R3load: job completed
/usr/sap/IDS/SYS/exe/run/R3load: END OF LOG: 20100329165300
/usr/sap/IDS/SYS/exe/run/R3load: START OF LOG: 20100329165300
/usr/sap/IDS/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/IDS/SYS/exe/run/R3load: version R7.00/V1.4
Compiled Jan 23 2008 17:32:58
/usr/sap/IDS/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -nolog -c 10000
DbSl Trace:   prepare() of C_0000, rc=1, rcSQL=-942 (POS(28) Unknown table name:SVERS)
DbSl Trace: SQL PREPARE on connection 0, rc=-942 (POS(28) Unknown table name:SVERS)
(DB) INFO: connected to DB
(DB) INFO: The MaxDB logwriter is switched off#20100329165300
(DB) INFO: Savepoint on database executed#20100329165300
(DB) INFO: REPOSRC created#20100329165300
(DB) INFO: Savepoint on database executed#20100329165301
(DB) INFO: REPOSRC~0 created#20100329165301
DbSl Trace:   writeLob() of C_0003, rc=1, rcSQL=-10201 (Function sequence error (no data for execution expected))
DbSl Trace: LOB_WRITE on connection 0, rc=-10201 (Function sequence error (no data for execution expected))
(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "REPOSRC"
(SQL error -10201)
error message returned by DbSl:
Function sequence error (no data for execution expected)
(DB) INFO: disconnected from DB
/usr/sap/IDS/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/IDS/SYS/exe/run/R3load: END OF LOG: 20100329165304
/usr/sap/IDS/SYS/exe/run/R3load: START OF LOG: 20100330120734
/usr/sap/IDS/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/IDS/SYS/exe/run/R3load: version R7.00/V1.4
Compiled Jan 23 2008 17:32:58
/usr/sap/IDS/SYS/exe/run/R3load -i REPOSRC.cmd -dbcodepage 4103 -l REPOSRC.log -nolog -c 10000
(DB) INFO: connected to DB
(DB) INFO: The MaxDB logwriter is switched off#20100330120734
(DB) INFO: Savepoint on database executed#20100330120735
(DB) INFO: REPOSRC deleted/truncated#20100330120735
DbSl Trace:   writeLob() of C_0004, rc=1, rcSQL=-10201 (Function sequence error (no data for execution expected))
DbSl Trace: LOB_WRITE on connection 0, rc=-10201 (Function sequence error (no data for execution expected))
(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "REPOSRC"
(SQL error -10201)
error message returned by DbSl:
Function sequence error (no data for execution expected)
DbSl Trace: EXECUTE on connection 0, rc=-1452 (POS(1) Duplicate secondary key)
ERROR : Execute for create index BNK_BATCH_HEADERBA on BNK_BATCH_HEADER failed (dbrc=99).
(SQL error -1452)
error message returned by DbSl:
SQL-Statement: CREATE UNIQUE INDEX "BNK_BATCH_HEADERBA" ON "BNK_BATCH_HEADER" ( "MANDT" , "BATCH_NO" )
/usr/sap/IDS/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/IDS/SYS/exe/run/R3load: END OF LOG: 20100330120739
REPOSRC.TSK
T REPOSRC C ok
P REPOSRC~0 C ok
D REPOSRC I err
Edited by: Deiby Alvez on Mar 31, 2010 10:39 PM

hello friends,
i have a similar error in context of an unicode conversion in phase import with r3load. in logs in file D010TAB.log i see the following output:
DbSl Trace: EXECUTE on connection 0, rc=-7055 (POS(55) Column(s) already indexed:/BI0/E0D_DECU~P)
ERROR : Execute for create index /BI0/E0D_DECU~P on /BI0/E0D_DECU failed (dbrc=99).
(SQL error -7055)
error message returned by DbSl:
SQL-Statement: CREATE INDEX "/BI0/E0D_DECU~P" ON "/BI0/E0D_DECU" ( "KEY_0D_DECUP" , "KEY_0D_DECUT" , "KEY_0D_DECUU" , "KEY_0D_DECU1" , "KEY_0D_DECU2" , "KEY_0D_DECU3" , "KEY_0D_DECU4" , "KEY_0D_DECU5" )
POS(55) Column(s) already indexed:/BI0/E0D_DECU~P
/usr/sap/SPV/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/SPV/SYS/exe/run/R3load: END OF LOG: 20100414185908
45 / 47 are complete in phase import.
For a TEST Case , i have deleted all indices on tables in selection of /BI0/*. I will rerun this procedure. the largest part of indices on tables come from a bw-installation in a seperate client.
best regards,
christoph

(DB) ERROR: db_connect rc = 256 in Import ABAP

I am installing ECC 6.0 SR1 EHP4 Ready in AIX 6.1 db2 9.1.7.
Got following error in step 27 (IMPORT ABAP)
ARNING 2011-03-03 16:42:02.173
 CJSlibModule::writeWarning_impl()
Execution of the command "/usr/sap/WD1/SYS/exe/run/R3load -testconnect" finished with return code 2. Output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
/usr/sap/WD1/SYS/exe/run/R3load: START OF LOG: 20110303164202
/usr/sap/WD1/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
/usr/sap/WD1/SYS/exe/run/R3load: version R7.01/V1.4 [UNICODE]
Compiled Feb 24 2009 21:54:08
/usr/sap/WD1/SYS/exe/run/R3load -testconnect
DbSl Trace: DbSlConnect to 'WD1' as 'sapwd1' failed
(DB) ERROR: db_connect rc = 256
DbSl Trace: DbSlConnect to 'WD1' as 'sapwd1' failed
(DB) ERROR: DbSlErrorMsg rc = 29
/usr/sap/WD1/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/WD1/SYS/exe/run/R3load: END OF LOG: 20110303164202
WARNING[E] 2011-03-03 16:42:02.176
 CJSlibModule::writeError_impl()
Thanks
Amit Barnawal

Hello,
dbms_type
Must be always set to "mss" for SQL Server.
MSSQL_SERVER
Name of the SQL Server instance. E.g. "SQLSERVER" (default
instance on server "SQLSERVER") or "SAPSQL\PRD" (named instance
"PRD" on server "SAPSQL")
MSSQL_DBNAME
Name of the database, usually <SID> in uppercase letters.
MSSQL_SCHEMA
Name of the database schema, usually "dbo" in lowercase letters.
With an MCOD system, the database schema is <sid> in lowercase
letters.
regards,
John Feely

SAPInst mySAP 2005 - Import ABAP Hangs

Hello All,
I am currently trying to install mySAP 2005 IDES on the following:
-> Windows Server 2003
-> MaxDB 7.6
-> 4GB RAM
-> 500 GB Hard Drive
I am finding that during the Import ABAP phase I reach 70 of the 72 and then it seems to hang. I have checked the import log and it is not moving forward at all.
Has anyone else experienced this and resolved it? I thought that maybe the number of database volumes was insufficient and have extended the number from the normal 14 (@13.2 GB each) to 21.
Regards,
Nicholas Wilson

Hi Rajat,
The Import ABAP phase has now completed. Thank you for your attention.
For others reading this thread, the Import ABAP phase takes a very long time (in my case it was the SAPAPPL1_10 import package which took the longest). It may be worth installing on a RAID configuration which will reduce the bottleneck.
I will close this thread.
Regards,
Nicholas.

SAPINST stopped at IMPORT ABAP step

Please help if you can
sapinst showing the following error:
An error occurred while processing option SAP ERP 6.0 EHP4 Ready - Support Release 1 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
in import_monitor_java.log , i get the following:
Loading of 'SAPAPPL0' import package: ERROR
Import Monitor jobs: running 2, waiting 21, completed 4, failed 1, total 28.
Import Monitor jobs: running 3, waiting 20, completed 4, failed 1, total 28.
at the end 26 were imported successfully, 1 with error i.e. SAPAPPL0 and other one is waiting
In SAPAPPL0.log I get the following:
(RFF) ERROR: invalid checksum in data file "/media/sap/install/nw701/51036902/DATA_UNITS/EXPORT_5/DATA/SAPAPPL0.001"
current table was "SMIMPHIO"
(DB) INFO: disconnected from DB
/usr/sap/HRD/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/HRD/SYS/exe/run/R3load: END OF LOG: 20111006080022

Hi,
yes, damaged file definitely.
I think you should copy fully the installation files from DVD/CD (Make sure the installation media is downloaded fully) into local disk, and run the installation locally.
You can compare the checksums (you may use a freeware tool such as 'md5sum')
and compare both checksums from source and targetfile
Regards,
Vincent

Problem class important error while executing Query from favorites

Hi Experts,
1. I have tried execute the query from favorites it is showing the error message. " Problem class important"
In the message text: logs showing error message [Attached the message screenshot].
2. From "Query Designer" Execute [Ctrl+R] gives the error "500 Internal Server Error" [Attached the screenshot]
3. Able to execute the reports from RRMX.
No ST22 dumps. Can any one suggest about...how to rectify the errors.
Thanks in advance...Surya

Need tyo make sure the problem is with the query/workbook are general issue with all workbooks/query.
1. Make sure the base query of work book is still executable. RRMX/RSRT.
2. Execute the work book in Bex/Excel and look for definition of workbook; there might be some thing in the workbook referencing other than base query.
3. If other workbook are also not working? need to check if other users have same issue.?
Hope this will help to narrow the problem.
Gopi

Sapinst error at import abap phase

Hi experts,
i am getting error at import abap phase. please have you look and let me know your inputs
ERROR 2011-08-31 22:55:27.730 [sixxcstepexecute.cpp:937]
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_DB|ind|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|abapload|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|
runMigrationMonitor was executed with status ERROR
( Last error reported by the step:
Execution of the command "/opt/java1.5/bin/java -classpath migmon.jar -showversion -Xmx1024m -d64 com.sap.inst.migmon.imp.ImportMonitor -sapinst"
finished with status TST_ERROR.)
Regards
Srinivas

Dear Srinivas,
I hope this may problem with as follwing
1)This had happened as a particular DVD was not copied properly You should copy it again and started it may be !
2) Please check Snote for Java : 716926 & 1426759
Thanks
Mithun

SAP Ides ECC 6.0 Install: Import ABAP - Package SAPDODS Error - ORA-00903

Experts,
Good Morning!
I'm trying to install SAP IDES ECC 6.0 version on a Windows 2008 R2 Server with Oracle 11g DB (11.2).
System Info: 16GM RAM & 600GB Hdd. Prereqs passed.
I'm getting the following error during the Import ABAP phase (16 of 29) in the sapinst log:
"An error occurred while processing option Enhancement Package 6 for SAP ERP 6.0 > SAP Application Server ABAP > Oracle > Central System > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. "
Here's the dump of import_monitor.java.log
java version "1.4.2_32"
Java(TM) 2 Runtime Environment, Standard Edition (build 4.1.012)
SAP Java Server VM (build 4.1.012 1.6-b03, Oct 21 2011 14:18:45 - 41_REL - optU - windows amd64 - 6 - bas2:161688 (mixed mode))
Import Monitor jobs: running 1, waiting 1, completed 141, failed 0, total 143.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 141, failed 1, total 143.
Here's the dump of import_monitor.log:
INFO: 2014-07-05 13:42:53
Data codepage 4103 is determined using TOC file 'C:\Target\Export1\DATA\D010TAB.TOC' for package 'D010TAB'.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2014-07-05 13:42:53 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
ERROR: 2014-07-05 13:42:54 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is interrupted with R3load error.
Process 'C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error' exited with return code 2.
For mode details see 'SAPDODS.log' file.
Standard error output:
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2014-07-05 13:43:21
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2014-07-05 13:43:21
1 error(s) during processing of packages.
INFO: 2014-07-05 13:43:21
Import Monitor is stopped.
Here's the log of SAPDODS...
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140705134253
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/720_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.4 [UNICODE]
Compiled Aug 16 2011 02:26:36
patchinfo (patches.h): (0.098) DB6: correction for R3load PL 91 on HP-UX and SOLARIS (note 1609719)
process id 1488
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF16
(SQL) INFO: Searching for SQL file SQLFiles.LST
(SQL) INFO: SQLFiles.LST not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/SQLFiles.LST
(SQL) INFO: C:\Target\Export1\DB/SQLFiles.LST not found
(SQL) INFO: Searching for SQL file DODS.SQL
(SQL) INFO: DODS.SQL not found
(SQL) INFO: Searching for SQL file C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: found C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: Trying to open C:\Target\Export1\DB/ORA/DODS.SQL
(SQL) INFO: C:\Target\Export1\DB/ORA/DODS.SQL opened
(DB) ERROR: DDL statement failed
(DROP TABLE "/BI0/APERS_BOD00")
DbSlExecute: rc = 103
(SQL error 942)
error message returned by DbSl:
ORA-00942: table or view does not exist
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: Error 903 in exec_immediate() from oci_execute_stmt(), orpc=0
DbSl Trace: ORA-00903 occurred at SQL stmt (parse error offset=15)
(DB) ERROR: DDL statement failed
( CREATE TABLE [/BI0/APERS_BOD00] ( [TCTUSERNM] nvarchar(000012) NOT NULL , [TCTOBJVERS] nvarchar(000001) NOT NULL , [TCTSYSID] nvarchar(000010) NOT NULL , [TCTQUACT] nvarchar(000001) NOT NULL , [TCTOBJNM] nvarchar(000040) NOT NULL , [TCTTLOGO] nvarchar(000004) NOT NULL , [RECORDMODE] nvarchar(000001) NOT NULL , [TCTTIMSTMP] nvarchar(000014) NOT NULL ) WITH ( DATA_COMPRESSION = PAGE ) )
DbSlExecute: rc = 99
(SQL error 903)
error message returned by DbSl:
ORA-00903: invalid table name
(DB) INFO: disconnected from DB
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140705134254
FYI - A retry does not help. Also tried to search for the error on scn, google but haven't been able to find the right solution.
Can you help?
Regards,
Cobain.

Divyanshu - sorry to ask but can you explain why i need to update r3load and r3trans to resolve this error? Just want to understand why I'm doing a correction so I can learn from the same.
Also, can you clarify the file update process:
For R3load:
a) the r3load used by the command is dated 8/16/2011 (location:C:\usr\sap\AVV\SYS\exe\uc\NTAMD64\...)
b) the r3load i have in my db folder is dated 10/23/2011 (location:C:\Final\Installer\BS7i2011_Installation_Master_\DATA_UNITS\BS2011_IM_WINDOWS_X86_64\ORA\UC\...)
Do i replace (a) with (b)?
For R3trans:
How do I update this file?
- Cobain.

Error in import abap step while importing system copy.

Hi All,
My colleague had taken System copy of development server, few days back. it was completed successfully,
now we want to restore that system copy, as hardware failed. But when we start the import of system copy,
all ABAP jobs are failing in import abap step, Some DDL statement problem. can u pls help wht to do.
I found in some forums, SMIGR_create_DDL report need to be generated prior to taking system copy, but he
didnt taken tht.
OS: Windows 2003
DB: DB2
Pls find sapinst.log
INFO 2009-10-27 10:43:06.890
Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2009-10-27 10:53:37.125
Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
Import Monitor jobs: running 1, waiting 63, completed 0, failed 0, total 64.
Import Monitor jobs: running 2, waiting 62, completed 0, failed 0, total 64.
Import Monitor jobs: running 3, waiting 61, completed 0, failed 0, total 64.
Loading of 'DOKCLU' import package: ERROR
Import Monitor jobs: running 2, waiting 61, completed 0, failed 1, total 64.
Loading of 'D010TAB' import package: ERROR
Import Monitor jobs: running 1, waiting 61, completed 0, failed 2, total 64.
Loading of 'REPOSRC' import package: ERROR
Import Monitor jobs: running 0, waiting 61, completed 0, failed 3, total 64.
Import Monitor jobs: running 1, waiting 60, completed 0, failed 3, total 64.
Import Monitor jobs: running 2, waiting 59, completed 0, failed 3, total 64.
Import Monitor jobs: running 3, waiting 58, completed 0, failed 3, total 64.
Loading of 'DYNPSOURCE' import package: ERROR
Import Monitor jobs: running 2, waiting 58, completed 0, failed 4, total 64.
Loading of 'SAPAPPL1_4' import package: ERROR
Import Monitor jobs: running 1, waiting 58, completed 0, failed 5, total 64.
Loading of 'SAPAPPL2_2' import package: ERROR
Import Monitor jobs: running 0, waiting 58, completed 0, failed 6, total 64.
Import Monitor jobs: running 1, waiting 57, completed 0, failed 6, total 64.
Import Monitor jobs: running 2, waiting 56, completed 0, failed 6, total 64.
Import Monitor jobs: running 3, waiting 55, completed 0, failed 6, total 64.
Loading of 'SAPNTAB' import package: ERROR
Import Monitor jobs: running 2, waiting 55, completed 0, failed 7, total 64.
Loading of 'SAPSSEXC_9' import package: ERROR
Import Monitor jobs: running 1, waiting 55, completed 0, failed 8, total 64.
Loading of 'SAPSSEXC_8' import package: ERROR
Import Monitor jobs: running 0, waiting 55, completed 0, failed 9, total 64.
Import Monitor jobs: running 1, waiting 54, completed 0, failed 9, total 64.
Import Monitor jobs: running 2, waiting 53, completed 0, failed 9, total 64.
Import Monitor jobs: running 3, waiting 52, completed 0, failed 9, total 64.
Loading of 'SAPAPPL2_6' import package: ERROR
Import Monitor jobs: running 2, waiting 52, completed 0, failed 10, total 64.
Loading of 'SAPAPPL1_3' import package: ERROR
Import Monitor jobs: running 1, waiting 52, completed 0, failed 11, total 64.
Loading of 'SAPAPPL2_5' import package: ERROR
Import Monitor jobs: running 0, waiting 52, completed 0, failed 12, total 64.
Import Monitor jobs: running 1, waiting 51, completed 0, failed 12, total 64.
Import Monitor jobs: running 2, waiting 50, completed 0, failed 12, total 64.
Import Monitor jobs: running 3, waiting 49, completed 0, failed 12, total 64.
Loading of 'D010INC' import package: ERROR
Import Monitor jobs: running 2, waiting 49, completed 0, failed 13, total 64.
Loading of 'SAPAPPL1_2' import package: ERROR
Import Monitor jobs: running 1, waiting 49, completed 0, failed 14, total 64.
Loading of 'SAPAPPL1_7' import package: ERROR
Import Monitor jobs: running 0, waiting 49, completed 0, failed 15, total 64.
Import Monitor jobs: running 1, waiting 48, completed 0, failed 15, total 64.
Import Monitor jobs: running 2, waiting 47, completed 0, failed 15, total 64.
Import Monitor jobs: running 3, waiting 46, completed 0, failed 15, total 64.
Loading of 'SAPSSEXC_2' import package: ERROR
Import Monitor jobs: running 2, waiting 46, completed 0, failed 16, total 64.
Loading of 'DYNPLOAD' import package: ERROR
Import Monitor jobs: running 1, waiting 46, completed 0, failed 17, total 64.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 0, waiting 46, completed 0, failed 18, total 64.
Import Monitor jobs: running 1, waiting 45, completed 0, failed 18, total 64.
Import Monitor jobs: running 2, waiting 44, completed 0, failed 18, total 64.
Import Monitor jobs: running 3, waiting 43, completed 0, failed 18, total 64.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 43, completed 0, failed 19, total 64.
Loading of 'SAPAPPL2_14' import package: ERROR
Import Monitor jobs: running 1, waiting 43, completed 0, failed 20, total 64.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 0, waiting 43, completed 0, failed 21, total 64.
Import Monitor jobs: running 1, waiting 42, completed 0, failed 21, total 64.
Import Monitor jobs: running 2, waiting 41, completed 0, failed 21, total 64.
Import Monitor jobs: running 3, waiting 40, completed 0, failed 21, total 64.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 2, waiting 40, completed 0, failed 22, total 64.
Loading of 'SAPSSEXC_4' import package: ERROR
Import Monitor jobs: running 1, waiting 40, completed 0, failed 23, total 64.
Loading of 'SAPAPPL2_10' import package: ERROR
Import Monitor jobs: running 0, waiting 40, completed 0, failed 24, total 64.
Import Monitor jobs: running 1, waiting 39, completed 0, failed 24, total 64.
Import Monitor jobs: running 2, waiting 38, completed 0, failed 24, total 64.
Import Monitor jobs: running 3, waiting 37, completed 0, failed 24, total 64.
Loading of 'SAPSSEXC_7' import package: ERROR
Import Monitor jobs: running 2, waiting 37, completed 0, failed 25, total 64.
Loading of 'SAPAPPL0_7' import package: ERROR
Import Monitor jobs: running 1, waiting 37, completed 0, failed 26, total 64.
Loading of 'SAPAPPL0_1' import package: ERROR
Import Monitor jobs: running 0, waiting 37, completed 0, failed 27, total 64.
Import Monitor jobs: running 1, waiting 36, completed 0, failed 27, total 64.
Import Monitor jobs: running 2, waiting 35, completed 0, failed 27, total 64.
Import Monitor jobs: running 3, waiting 34, completed 0, failed 27, total 64.
Loading of 'SAPAPPL2_7' import package: ERROR
Import Monitor jobs: running 2, waiting 34, completed 0, failed 28, total 64.
Loading of 'SAPAPPL2_4' import package: ERROR
Import Monitor jobs: running 1, waiting 34, completed 0, failed 29, total 64.
Loading of 'SAPAPPL1_6' import package: ERROR
Import Monitor jobs: running 0, waiting 34, completed 0, failed 30, total 64.
Import Monitor jobs: running 1, waiting 33, completed 0, failed 30, total 64.
Import Monitor jobs: running 2, waiting 32, completed 0, failed 30, total 64.
Import Monitor jobs: running 3, waiting 31, completed 0, failed 30, total 64.
Loading of 'SAPAPPL0_3' import package: ERROR
Import Monitor jobs: running 2, waiting 31, completed 0, failed 31, total 64.
Loading of 'SAPCLUST' import package: ERROR
Import Monitor jobs: running 1, waiting 31, completed 0, failed 32, total 64.
Loading of 'SAPAPPL0_8' import package: ERROR
Import Monitor jobs: running 0, waiting 31, completed 0, failed 33, total 64.
Import Monitor jobs: running 1, waiting 30, completed 0, failed 33, total 64.
Import Monitor jobs: running 2, waiting 29, completed 0, failed 33, total 64.
Import Monitor jobs: running 3, waiting 28, completed 0, failed 33, total 64.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 2, waiting 28, completed 0, failed 34, total 64.
Loading of 'ENHOBJCONTRACT' import package: ERROR
Import Monitor jobs: running 1, waiting 28, completed 0, failed 35, total 64.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 0, waiting 28, completed 0, failed 36, total 64.
Import Monitor jobs: running 1, waiting 27, completed 0, failed 36, total 64.
Import Monitor jobs: running 2, waiting 26, completed 0, failed 36, total 64.
Import Monitor jobs: running 3, waiting 25, completed 0, failed 36, total 64.
Loading of 'SAPSSEXC_1' import package: ERROR
Import Monitor jobs: running 2, waiting 25, completed 0, failed 37, total 64.
Loading of 'SAPSSEXC_6' import package: ERROR
Import Monitor jobs: running 1, waiting 25, completed 0, failed 38, total 64.
Loading of 'SAPAPPL2_8' import package: ERROR
Import Monitor jobs: running 0, waiting 25, completed 0, failed 39, total 64.
Import Monitor jobs: running 1, waiting 24, completed 0, failed 39, total 64.
Import Monitor jobs: running 2, waiting 23, completed 0, failed 39, total 64.
Import Monitor jobs: running 3, waiting 22, completed 0, failed 39, total 64.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 0, failed 40, total 64.
Loading of 'SAPAPPL2_1' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 0, failed 41, total 64.
Loading of 'SAPAPPL1_5' import package: ERROR
Import Monitor jobs: running 0, waiting 22, completed 0, failed 42, total 64.
Import Monitor jobs: running 1, waiting 21, completed 0, failed 42, total 64.
Import Monitor jobs: running 2, waiting 20, completed 0, failed 42, total 64.
Import Monitor jobs: running 3, waiting 19, completed 0, failed 42, total 64.
Loading of 'REPOTEXT' import package: ERROR
Import Monitor jobs: running 2, waiting 19, completed 0, failed 43, total 64.
Loading of 'SAPAPPL0_5' import package: ERROR
Import Monitor jobs: running 1, waiting 19, completed 0, failed 44, total 64.
Loading of 'SAPAPPL2_9' import package: ERROR
Import Monitor jobs: running 0, waiting 19, completed 0, failed 45, total 64.
Import Monitor jobs: running 1, waiting 18, completed 0, failed 45, total 64.
Import Monitor jobs: running 2, waiting 17, completed 0, failed 45, total 64.
Import Monitor jobs: running 3, waiting 16, completed 0, failed 45, total 64.
Loading of 'SAPSSEXC_10' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 0, failed 46, total 64.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 1, waiting 16, completed 0, failed 47, total 64.
Loading of 'SAPAPPL0_6' import package: ERROR
Import Monitor jobs: running 0, waiting 16, completed 0, failed 48, total 64.
Import Monitor jobs: running 1, waiting 15, completed 0, failed 48, total 64.
Import Monitor jobs: running 2, waiting 14, completed 0, failed 48, total 64.
Import Monitor jobs: running 3, waiting 13, completed 0, failed 48, total 64.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 13, completed 0, failed 49, total 64.
Loading of 'SAPAPPL0_9' import package: ERROR
Import Monitor jobs: running 1, waiting 13, completed 0, failed 50, total 64.
Loading of 'SAPAPPL2_11' import package: ERROR
Import Monitor jobs: running 0, waiting 13, completed 0, failed 51, total 64.
Import Monitor jobs: running 1, waiting 12, completed 0, failed 51, total 64.
Import Monitor jobs: running 2, waiting 11, completed 0, failed 51, total 64.
Import Monitor jobs: running 3, waiting 10, completed 0, failed 51, total 64.
Loading of 'SAPSPROT' import package: ERROR
Import Monitor jobs: running 2, waiting 10, completed 0, failed 52, total 64.
Loading of 'SAPAPPL2_13' import package: ERROR
Import Monitor jobs: running 1, waiting 10, completed 0, failed 53, total 64.
Loading of 'SAPAPPL2_12' import package: ERROR
Import Monitor jobs: running 0, waiting 10, completed 0, failed 54, total 64.
Import Monitor jobs: running 1, waiting 9, completed 0, failed 54, total 64.
Import Monitor jobs: running 2, waiting 8, completed 0, failed 54, total 64.
Import Monitor jobs: running 3, waiting 7, completed 0, failed 54, total 64.
Loading of 'SAPSLOAD' import package: ERROR
Import Monitor jobs: running 2, waiting 7, completed 0, failed 55, total 64.
Loading of 'SAPSDOCU' import package: ERROR
Import Monitor jobs: running 1, waiting 7, completed 0, failed 56, total 64.
Loading of 'SAPAPPL1_1' import package: ERROR
Import Monitor jobs: running 0, waiting 7, completed 0, failed 57, total 64.
Import Monitor jobs: running 1, waiting 6, completed 0, failed 57, total 64.
Import Monitor jobs: running 2, waiting 5, completed 0, failed 57, total 64.
Import Monitor jobs: running 3, waiting 4, completed 0, failed 57, total 64.
Loading of 'SAPDDIM' import package: ERROR
Import Monitor jobs: running 2, waiting 4, completed 0, failed 58, total 64.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 4, completed 0, failed 59, total 64.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 4, completed 0, failed 60, total 64.
Import Monitor jobs: running 1, waiting 3, completed 0, failed 60, total 64.
Import Monitor jobs: running 2, waiting 2, completed 0, failed 60, total 64.
Import Monitor jobs: running 3, waiting 1, completed 0, failed 60, total 64.
Loading of 'SAPDODS' import package: ERROR
Import Monitor jobs: running 2, waiting 1, completed 0, failed 61, total 64.
Loading of 'SAPUSER1' import package: ERROR
Import Monitor jobs: running 1, waiting 1, completed 0, failed 62, total 64.
Loading of 'SAP0000' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 0, failed 63, total 64.
ERROR 2009-10-27 10:53:37.125
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2009-10-27 10:53:37.140
FCO-00011 The step runMigrationMonitor with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
Thanks.

i checked the DOKCLU log, pls find the log below:
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20091027104307
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Aug 23 2009 23:42:38
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -k 1gage5M50Dp01eqte1]x3Qa5 -l DOKCLU.log -stop_on_error -loadprocedure fast LOAD
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "ATD                                                                                "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SERVER"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 1"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 23 Step 7)"
(DB) ERROR: DDL statement failed
( DROP TABLE "DOKCLU" )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
( CREATE TABLE "DOKCLU" ( "ID" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "OBJECT" SAPDB6CHAR(60) DEFAULT ' ' NOT NULL , "LANGU" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TYP" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "DOKVERSION" SAPDB6FIXCHAR(4) DEFAULT '0000' NOT NULL , "PAGENO" SMALLINT DEFAULT 0 NOT NULL , "TIMESTMP" SAPDB6CHAR(46) DEFAULT ' ' NOT NULL , "PAGELG" SMALLINT DEFAULT 0 NOT NULL , "VARDATA" VARCHAR(3800) FOR BIT DATA ) IN ATD#ES700D INDEX IN ATD#ES700I LONG IN ATD#ES700D )
dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
(DB) INFO: disconnected from DB
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20091027104307
Thanks

DB2 9.7 DFACT.SQL syntax error in Import ABAP phase - System Copy

Hi all. I'm trying a system copy with a source system SAP ECC 6.0 ehp4 based on NW 701 and db2 LUW 9.1 .
As it seems supported by SAP, i'm using db2 LUW 9.7 in target system.
O.S. is Windows 2008.
I got an error in phase "Import ABAP".
Sapinst.log says:
INFO 2010-02-18 10:12:14.337
An error occured and the user decided to retry the current step: "|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
INFO 2010-02-18 10:12:14.509
Switched to user: devadm.
INFO 2010-02-18 10:12:14.572
Creating file C:\Program Files\sapinst_instdir\ERPEhP4\LM\COPY\DB6\SYSTEM\CENTRAL\AS-ABAP\import_monitor.java.log.
INFO 2010-02-18 10:12:14.603
Switched to user: devadm.
INFO 2010-02-18 10:12:14.618
Working directory changed to C:\Program Files\sapinst_instdir\ERPEhP4\LM\COPY\DB6\SYSTEM\CENTRAL\AS-ABAP.
INFO 2010-02-18 10:12:14.618
Output of C:\j2sdk1.4.2_24-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2010-02-18 10:12:44.790
Execution of the command "C:\j2sdk1.4.2_24-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_24-rev"
Java(TM) Platform, Standard Edition for Business (build 1.4.2_24-rev-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_24-rev-b06, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 73, failed 0, total 75.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 73, failed 1, total 75.
WARNING[E] 2010-02-18 10:12:44.790
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2010-02-18 10:12:44.790
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
Looking into import_monitor.java.log i found that the problem is in dfact import.
I've looked into sapdfact.log and i found:
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100218105045
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]
Compiled Jan 28 2010 20:22:25
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error -loadprocedure fast LOAD:COMPRESS_ALL
(DB) INFO: connected to DB
(DB6) INFO: COMPRESS YES is set during table creation.
(DB6) DB2 9.5 automatic dictionary creation does not require an explicit REORG.
(DB6) Compression threshold is ignored.
(GSI) INFO: dbname   = "DEV                                                                                "
(GSI) INFO: vname    = "DB6                             "
(GSI) INFO: hostname = "UNKNOWN                                                         "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SRVSAPDEV"
(GSI) INFO: release = "6.0"
(GSI) INFO: version = "6002 Service Pack 2"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 26 Step 5)"
(DB) ERROR: DDL statement failed with SQL error
( ALTER TABLE "/BI0/E0PPM_VC1" DROP PRIMARY KEY )
(SQL error -539)
error message returned by dsql:
SQL0539N Table or nickname "SAPDEV./BI0/E0PPM_VC1" does not have a "PRIMARY" key. SQLSTATE=42888
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB6) INFO: executing DDL statements for object /BI0/E0PPM_VC1 from external SQL file.
(DB) ERROR: DDL statement failed with SQL error
( CREATE TYPE 2 UNIQUE INDEX "/BI0/E0PPM_VC1~0" ON "/BI0/E0PPM_VC1"   ("KEY_0PPM_VC1T" ,   "KEY_0PPM_VC11" ,   "KEY_0PPM_VC1U" ,   "KEY_0PPM_VC1P" )   USING STOGROUP ___FAI PRIQTY 16   SECQTY 10240 FREEPAGE 0 PCTFREE 0   GBPCACHE CHANGED DEFINE NO   BUFFERPOOL BP3 COPY NO   PIECESIZE 2097152 K CLUSTER NOT PADDED )
(SQL error -7)
error message returned by dsql:
SQL0007N The character "_" following "" )   USING STOGROUP" is not valid. SQLSTATE=42601
(DB) INFO: disconnected from DB
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100218105045
So as you can see it seems that there's some syntax error in dfacl.log. The wrong SQL statement referred by sapdfact.log is
ind: /BI0/E0PPM_VC1~0
sql: CREATE TYPE 2 UNIQUE INDEX "/BI0/E0PPM_VC1~0" ON "/BI0/E0PPM_VC1"
("KEY_0PPM_VC1T" ,
"KEY_0PPM_VC11" ,
"KEY_0PPM_VC1U" ,
"KEY_0PPM_VC1P" )
USING STOGROUP ___FAI PRIQTY 16
SECQTY 10240 FREEPAGE 0 PCTFREE 0
GBPCACHE CHANGED DEFINE NO
BUFFERPOOL BP3 COPY NO
PIECESIZE 2097152 K CLUSTER NOT PADDED ;
|
ALTER TABLE "/BI0/E0PPM_VC1"
ADD PRIMARY KEY ("KEY_0PPM_VC1T",
"KEY_0PPM_VC11",
"KEY_0PPM_VC1U",
"KEY_0PPM_VC1P") ;
Am i missing something?
Data in referred tables (infocubes) isn't really important.
Is there a safe way to proceed?
Thanks in advance.
Regards
Simone Zaffalon

And this is the strange point: my source system is not a BI and my dataclasses .SQL files are not empty.
Me too i would expect that the files should be empty but instead they are full of object definitions.
For example i have APPL0.SQL that contains a list of all tables of ECC system, for example
tab: MAMT
sql:     CREATE TABLE "MAMT"
        ("MANDT" SAPDB6VARCHAR(000003)
        DEFAULT '000' NOT NULL,
        "MATNR" SAPDB6VARCHAR(000018)
        DEFAULT ' ' NOT NULL,
        "SPRAS" SAPDB6VARCHAR(000001)
        DEFAULT ' ' NOT NULL,
        "MEINH" SAPDB6VARCHAR(000003)
        DEFAULT ' ' NOT NULL,
        "MTXID" SAPDB6VARCHAR(000002)
        DEFAULT ' ' NOT NULL,
        "LFDNR" SAPDB6VARCHAR(000002)
        DEFAULT '00' NOT NULL,
        "MAKTM" SAPDB6VARCHAR(000040)
        DEFAULT ' ' NOT NULL)
        IN "&location&"
        INDEX IN "&locationI&"
        LONG IN "&locationL&"
      COMPRESS YES;
      ALTER TABLE "MAMT" LOCKSIZE ROW;
and like this for all others tables.
What would occur if i launch an import with such .SQL files?
(shuld i put this question to another thread or is fine for you to answer on this?)
Thank you again.
Simone Zaffalon

RUNTIME ERROR IMPORT ABAP PHASE IN HETEROGENIOUS SYTEM COPY

Hi All,
We have started heterogenious sytem copy from windows (mssql_ to linux(maxdb).
In import abap phase at the 128th job it ended with an error Here i attach the log of IMPORT_MONITOR.LOG
ERROR : Execute for create index /BI0/F0RSTT_C01~P on /BI0/F0RSTT_C01 failed (dbrc=99).
(SQL error -7055)
error message returned by DbSl:
SQL-Statement: CREATE INDEX "/BI0/F0RSTT_C01~P" ON "/BI0/F0RSTT_C01" ( "KEY_0RSTT_C01P" , "KEY_0RSTT_C01T" , "KEY_0RSTT_C01U" , "KEY_0RSTT_C011" , "KEY_0RSTT_C012" , "KEY_0RSTT_C013" , "KEY_0RSTT_C014" , "KEY_0RSTT_C015" , "KEY_0RSTT_C016" , "KEY_0RSTT_C017" , "KEY_0RSTT_C018" , "KEY_0RSTT_C019" , "KEY_0RSTT_C01A" )
(DB) INFO: disconnected from DB
/usr/sap/DM1/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/DM1/SYS/exe/run/R3load: END OF LOG: 20110417003352
/usr/sap/DM1/SYS/exe/run/R3load: START OF LOG: 20110417004819
/usr/sap/DM1/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/DM1/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Jan 23 2008 17:39:05
/usr/sap/DM1/SYS/exe/run/R3load -i SAPAPPL1_24.cmd -dbcodepage 4103 -k                          -l SAPAPPL1_24.log -nolog -c 10000
(DB) INFO: connected to DB
(DB) INFO: The MaxDB logwriter is switched off#20110417004819
(GSI) INFO: dbname   = "DM1                                                                                "
(GSI) INFO: vname    = "ADABAS D                        "
(GSI) INFO: hostname = "sgmw-s-relse1                                                   "
(GSI) INFO: sysname = "Linux"
(GSI) INFO: nodename = "sgmw-s-relse1"
(GSI) INFO: release = "2.6.32.12-0.7-xen"
(GSI) INFO: version = "#1 SMP 2010-05-20 11:14:20 +0200"
(GSI) INFO: machine = "x86_64"
(DB) ERROR: DDL statement failed
(DROP INDEX "PCL4~XPS" ON "PCL4")
DbSlExecute: rc = 103
(SQL error -4011)
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: EXECUTE on connection 0, rc=-7055 (POS(59) Column(s) already indexed:/BI0/F0RSTT_C01~P)
ERROR : Execute for create index /BI0/F0RSTT_C01~P on /BI0/F0RSTT_C01 failed (dbrc=99).
(SQL error -7055)
error message returned by DbSl:
SQL-Statement: CREATE INDEX "/BI0/F0RSTT_C01~P" ON "/BI0/F0RSTT_C01" ( "KEY_0RSTT_C01P" , "KEY_0RSTT_C01T" , "KEY_0RSTT_C01U" , "KEY_0RSTT_C011" , "KEY_0RSTT_C012" , "KEY_0RSTT_C013" , "KEY_0RSTT_C014" , "KEY_0RSTT_C015" , "KEY_0RSTT_C016" , "KEY_0RSTT_C017" , "KEY_0RSTT_C018" , "KEY_0RSTT_C019" , "KEY_0RSTT_C01A" )
(DB) INFO: disconnected from DB
/usr/sap/DM1/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/DM1/SYS/exe/run/R3load: END OF LOG: 20110417004819
Import Monitor jobs: running 1, waiting 1, completed 128, failed 0, total 130.
Loading of 'SAPAPPL1_24' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 128, failed 1, total 130.
could any one please help me in solving this issue
Thanks!
Vardhan.

\\10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA\ARFCSDATA.TOC
Please check if above said file located under specified path where SAPINST searvhing for it ie at
10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA. if this file dont exist them it may be the case that your export is not proper.
Also check if user from which you have started this SAPINST is able to access
10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA.
Thanks..
Mohit

Error at IMPORT ABAP

Hi,
I am Installing Solution manager 4.0 with Oracle 10.2 as database in AIX 5.3. During the installation Phase at import ABAP stage,i am getting the following error.
WARNING 2007-07-26 12:11:41
 CJSlibModule::writeWarning_impl()
Execution of the command "/usr/java14_64/bin/java -classpath migmon.jar -showver
sion -Xj9 com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs /softwar
e/export/51032524_1/SAP_Solution_M._4.0_SR2_Inst._Export/EXP1:/software/export/5
1032524_2/SAP_Solution_M._4.0_SR2_Inst._Export/EXP2:/software/export/51032524_3/
SAP_Solution_M._4.0_SR2_Inst._Export/EXP3:/software/export/51032524_4/SAP_Soluti
on_M._4.0_SR2_Inst._Export/EXP4 -installDir /tmp/sapinst_instdir/SOLMAN/SYSTEM/O
RA/CENTRAL/AS -orderBy "" -r3loadExe /usr/sap/SOL/SYS/exe/run/R3load -tskFiles y
es -extFiles yes -dbCodepage 4102 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop
onerror" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 2.3)
IBM J9 VM (build 2.3, J2RE 1.4.2 IBM J9 2.3 AIX ppc64-64 j9ap64142-20070322 (JIT
enabled)
J9VM - 20070320_12026_BHdSMr
JIT - 20070223_1804ifx1_r8
GC - 20070227_AA)
Import Monitor jobs: running 1, waiting 17, completed 0, failed 0, total 18.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 0, waiting 17, completed 0, failed 1, total 18.
ERROR 2007-07-26 12:11:41
CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details se
e log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-07-26 12:11:41
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|in
d|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|1
0|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0
|runMigrationMonitor was executed with status ERROR .
System Configuration is
AIX 5.3 & 4GB RAM
Java Version is
java -version
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM AIX 5L for PowerPC (64 bit JVM) build ca
ix64142-20070317 (SR8) (JIT enabled: jitc))
Could u please tell me what could be the solution for this
Regards
SS

Hi,
One of these would solve your problem.
1. When the installation fails, check if DB is running, if not restart the DB services and continue with the installation.
2. It might be due to the fact that the database space allocation was insufficient. The default amount of volumes created by the installer would be low.
3. Also increase the virtual memory (Run the pre install check). Give sufficient virtual memory.
Feel free to revert back.
--Ragu

Installation error phase "import ABAP" - ERP2005 IDES - mssql2005

Hi.
I've problems installing ERP2005 IDES with microsoft sql server 2005 at windows 2003server x64.
I've installed solution manager 4.0 succesfylly at the same host.
I've read about simular problems at this forum (with oracle). But no solutions for me.
Error in phase "Import ABAP":
CJS-30022 Program 'Migration Monitor' exits with error code 103.
For details see log file(s) import_monitor.java.log, import_monitor.log
IMPORT_MONITOR.LOG:
ERROR: 2007-10-05 17:29:12 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is interrupted with R3load error.
Process 'E:\usr\sap\E01\SYS\exe\nuc\NTAMD64\R3load.exe -i SAPSDIC.cmd -dbcodepage 1100 -l SAPSDIC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSDIC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
SAPSDIC.LOG:
(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed>
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: F4UHLP~1 created
In SAPSDIC.tsk I find one error:
D F4UHLP I err
I want to install nonunicode, but I've tried to install unicode with the same result.
I've also recieving this error in a log-file:
sapparam: SAPSYSTEMNAME neither in Profile nor in CommandlineI understand that I manually can set the parameter SAPSYSTEMNAME in control.xml, but I've dont know where and if this is a good solution?
This is what i've been trying without success:
-Uninstalled the instance and deleted inst_dir/erp.
-Environment variable is set like inst_guide describes
-Paging Files is ok
-Access to table F4UHLP is ok
Can anybody help me? Please? I'm desperate.
Kindly regards
Harald Vedvik
Message was edited by:
 Harald Vedvik
Message was edited by:
 Harald Vedvik

Hi again.
I posted my logs in the beginning of this thread, but if you want a more detailed
b]sapinst.log:
WARNING 2007-10-08 13:00:48
Errors when executing sql command: If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.
INFO 2007-10-08 13:00:49
Execute step doGrantServiceRights of component |NW_Onehost|ind|ind|ind|ind|00|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssOsUser|ind|ind|ind|ind|11|2.
INFO 2007-10-08 13:01:27
Output of C:\j2sdk1.4.2_15-x64\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\ERP2005IDES\Export\51032413_1\EXP1;E:\ERP2005IDES\Export\51032413_2\EXP2;E:\ERP2005IDES\Export\51032413_3\EXP3;E:\ERP2005IDES\Export\51032413_4\EXP4;E:\ERP2005IDES\Export\51032413_5\EXP5;E:\ERP2005IDES\Export\51032413_6\EXP6;E:\ERP2005IDES\Export\51032413_6\EXP7;E:\ERP2005IDES\Export\51032413_6\EXP8;E:\ERP2005IDES\Export\51032413_6\EXP9;E:\ERP2005IDES\Export\51032413_6\EXP10;E:\ERP2005IDES\Export\51032413_6\EXP11 -installDir D:\sapinst_instdir -orderBy "" -r3loadExe E:\usr\sap\E01\SYS\exe\nuc\NTAMD64\R3load.exe -tskFiles yes -extFiles no -dbCodepage 1100 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2007-10-08 13:17:59
Execution of the command "C:\j2sdk1.4.2_15-x64\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType MSS -importDirs E:\ERP2005IDES\Export\51032413_1\EXP1;E:\ERP2005IDES\Export\51032413_2\EXP2;E:\ERP2005IDES\Export\51032413_3\EXP3;E:\ERP2005IDES\Export\51032413_4\EXP4;E:\ERP2005IDES\Export\51032413_5\EXP5;E:\ERP2005IDES\Export\51032413_6\EXP6;E:\ERP2005IDES\Export\51032413_6\EXP7;E:\ERP2005IDES\Export\51032413_6\EXP8;E:\ERP2005IDES\Export\51032413_6\EXP9;E:\ERP2005IDES\Export\51032413_6\EXP10;E:\ERP2005IDES\Export\51032413_6\EXP11 -installDir D:\sapinst_instdir -orderBy "" -r3loadExe E:\usr\sap\E01\SYS\exe\nuc\NTAMD64\R3load.exe -tskFiles yes -extFiles no -dbCodepage 1100 -jobNum 3 -monitorTimeout 30 -loadArgs " -loadprocedure fast" -trace all -sapinst" finished with return code 103. Output:
java version "1.4.2_15"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_15-b02, mixed mode)
Import Monitor jobs: running 1, waiting 18, completed 0, failed 0, total 19.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 0, waiting 18, completed 0, failed 1, total 19.
ERROR 2007-10-08 13:17:59
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2007-10-08 13:17:59
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
import_monitor.log:INFO: 2007-10-08 13:01:29
Import Monitor is started.
CONFIG: 2007-10-08 13:01:29
Application options:
dbCodepage=1100
dbType=MSS
extFiles=no
importDirs=E:\ERP2005IDES\Export\51032413_1\EXP1;E:\ERP2005IDES\Export\51032413_2\EXP2;E:\ERP2005IDES\Export\51032413_3\EXP3;E:\ERP2005IDES\Export\51032413_4\EXP4;E:\ERP2005IDES\Export\51032413_5\EXP5;E:\ERP2005IDES\Export\51032413_6\EXP6;E:\ERP2005IDES\Export\51032413_6\EXP7;E:\ERP2005IDES\Export\51032413_6\EXP8;E:\ERP2005IDES\Export\51032413_6\EXP9;E:\ERP2005IDES\Export\51032413_6\EXP10;E:\ERP2005IDES\Export\51032413_6\EXP11
installDir=D:\sapinst_instdir
jobNum=3
loadArgs= -loadprocedure fast
monitorTimeout=30
orderBy=
r3loadExe=E:\usr\sap\E01\SYS\exe\nuc\NTAMD64\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-10-08 13:01:29
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-10-08 13:01:29
List of packages with views: 'SAPVIEW'.
TRACE: 2007-10-08 13:01:29 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'D:\sapinst_instdir\DDLMSS.TPL' template file is started.
INFO: 2007-10-08 13:01:29 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'D:\sapinst_instdir\DDLMSS.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2007-10-08 13:01:29
Data codepage 4103 is determined using TOC file 'E:\ERP2005IDES\Export\51032413_1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.
INFO: 2007-10-08 13:01:32
Version table 'SVERS' is found in STR file 'E:\ERP2005IDES\Export\51032413_4\EXP4\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
INFO: 2007-10-08 13:01:32
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'E:\ERP2005IDES\Export\51032413_4\EXP4\DATA\SAPSDIC.STR' from package 'SAPSDIC'.
TRACE: 2007-10-08 13:01:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2007-10-08 13:01:33 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
E:\usr\sap\E01\SYS\exe\nuc\NTAMD64\R3load.exe -ctf I E:\ERP2005IDES\Export\51032413_4\EXP4\DATA\SAPSDIC.STR D:\sapinst_instdir\DDLMSS.TPL SAPSDIC.TSK MSS -l SAPSDIC.log
TRACE: 2007-10-08 13:01:33 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
E:\usr\sap\E01\SYS\exe\nuc\NTAMD64\R3load.exe -i SAPSDIC.cmd -dbcodepage 1100 -l SAPSDIC.log -loadprocedure fast
ERROR: 2007-10-08 13:17:46 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is interrupted with R3load error.
Process 'E:\usr\sap\E01\SYS\exe\nuc\NTAMD64\R3load.exe -i SAPSDIC.cmd -dbcodepage 1100 -l SAPSDIC.log -loadprocedure fast' exited with return code 2.
For mode details see 'SAPSDIC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2007-10-08 13:17:59
Cannot continue import because not all import packages with data conversion tables are loaded successfully.
WARNING: 2007-10-08 13:17:59
1 error(s) during processing of packages.
INFO: 2007-10-08 13:17:59
Import Monitor is stopped.
Do you need more than alredy posted for sapsdic.log?
SAPSDIC.LOG:
(IMP) INFO: ExeFastLoad failed with <2: BCP Commit failed>
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: F4UHLP~1 created
I dont know if you recive my points? I've been giving you points:)
best regards
Harald

Error in SAP installation in phase 19 of 34 - Import ABAP

Hi SAP Gurus,
Good day all, I'm facing problem when installing SAP ECC 6.0 EHP7 (IDES version). Its stucked in phase 19 of 34 Import ABAP.
Below are the error details:-
ECC Message Box
An error occurred while processing option SAP Business Suite 7i 2013 Support Release 1 > EHP7 for SAP ERP 6.0 ABAP Support Release 1 > Oracle > SAP Systems > Application Server ABAP > Standard System > Standard System( Last error reported by the step: Process call 'D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.). You can now:
Choose Retry
to repeat the current step.
Choose Log Files
to get more information about the error.
Stop the option and continue later.
Log files are written to C:\Program Files/sapinst_instdir/BS2013/BS2013SR1/ERP607SR1/ORA/INSTALL/STD/ABAP.
Below are the logs from R3load.exe:-
sapparam: sapargv(argc, argv) has not been called!
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20141006062234
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/741_REL/src/R3ld/R3load/R3ldmain.c#6 $ SAP
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: version R7.40/V1.8 [UNICODE]
Compiled Nov 23 2013 13:31:32
-------------------- Start of patch information ------------------------
patchinfo (patches.h): (0.009) Support for SUM/ZDM and DMO (note 1778564)
DBSL patchinfo (patches.h): (0.011) DBSL error corrections in 7.41: (4) LOBs (note 1928526)
--------------------- End of patch information -------------------------
process id 4612
DbSl Trace: Connect via SAPUSER not supported for kernel >= 740.
(DB) ERROR: db_connect rc = 256
DbSl Trace: Connect via SAPUSER not supported for kernel >= 740.
(DB) ERROR: DbSlErrorMsg rc = 29
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\ECC\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20141006062234
Looking forward for your reply.
Regards,
Jay
-96-

Hi
I'm afraid you forget selecting the SSFS option during installation and it is the only connection method supported for kernel 7.40
It should be possible to fix this manually and perform all the step to connect using SSFS... but restarting your installation might be faster & easier.
1622837 - Secure connection of AS ABAP to Oracle via SSFS
As of SAP Kernel Release 7.40 (irrespective of the Oracle version), only the secure connection (secure connect) is supported via SSFS.
Regards

Error in SAPinst (problem in import abap)

Similar Messages

Maybe you are looking for