Import Abap Program
Hi All,
i have an ABAP Program which is downloaded from a site and
showing in Internet Explorer.
How to import that ABAP Program into SAP.
rgrds
Sandeep
Hi Sandeep,
Copy the program into Notepad.
And in ABAP Editor, you have anoption to import the data from notepad.
Best Regards,
Ram.
Similar Messages
-
Import data from ABAP program to Excell template file
Hello everyone
I have a such task: In abap program I have fields(screen fields), which I want to import into excell file. I don't want to export into empty file but into ready template .xls. Is there any possibility to match corresponding fields?
I really need to know, I will be gratefully for any suggestions.
GreetingsHi Katarzyna ,
something like
DATA: EXCEL TYPE OLE2_OBJECT.
DATA: BOOKS TYPE OLE2_OBJECT.
DATA: BOOK TYPE OLE2_OBJECT.
DATA: CELL TYPE OLE2_OBJECT.
DATA: FONT TYPE OLE2_OBJECT.
DATA: FILE TYPE OLE2_OBJECT.
CREATE OBJECT EXCEL 'EXCEL.APPLICATION'.
CALL METHOD OF EXCEL 'WORKBOOKS' = FILE.
CALL METHOD OF FILE 'OPEN' EXPORTING #1 = P_FILE
#2 = 1.
CALL METHOD OF EXCEL 'CELLS' = CELL EXPORTING #1 = P_LINE
#2 = P_COLUMN.
SET PROPERTY OF CELL 'VALUE' = P_VALUE.
CALL METHOD OF EXCEL 'QUIT'.
This is just a compilation from a complex program. Do some modularization (i.e. create FORM fill_cell using P_line P_column P_value...)
Hope I did not forget anything. Meanwhile we have much more modern and advanced methods and classes - this one is of 2000 (Release 4.5?).
Regards,
Clemens -
Import issue for ABAP program in Production Server ?
Hi Experts,
I have an ABAP program which gets executed properly in BW Development server but getting the following error when I am trying to execute it in the BW Production while I could activate the program successfully.
Kindly help me to resolve this issue.
Thanks in advance !!!
Regards,
Gokulkumar RDHi Golkul,
Can you debug the program while execute?
I think there is some hardcoding in the program for checkiing the client and then raised a custom message in the program.
Can you share the coding of the prorgam if possible?
Try to check for any messages raised in the program. Also click on the on the message pop up and see the details on the message and let us know.
Thanks
Amit -
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 -
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. -
Import ABAP error in ERP 2005 SR2 IDES installation
Hi Experts
I am trying to install the SAP ERP 2005 SR2 ( OS is 2003 and Database is Oracle 10g )IDES which i downloaded from the SAP market place and got
the following error at the IMPORT ABAP task
INFO 2008-02-20 14:19:37
Output of C:\Program Files\Java\j2re1.4.2_16\bin\java.exe -classpath migmon.jar -showversion
com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "D:\ERP 2005 IDES\51032413_1\EXP1;
D:\ERP 2005 IDES\51032413_2\EXP2;D:\ERP 2005 IDES\51032413_3\EXP3;D:\ERP 2005 IDES\51032413_4\EXP4;
D:\ERP 2005 IDES\51032413_5\EXP5;D:\ERP 2005 IDES\51032413_6\EXP6;D:\ERP 2005 IDES\51032413_6\EXP7;
D:\ERP 2005 IDES\51032413_6\EXP8;D:\ERP 2005 IDES\51032413_6\EXP9;D:\ERP 2005 IDES\51032413_6\EXP10;
D:\ERP 2005 IDES\51032413_6\EXP11" -installDir C:\PROGRA1\SAPINS1\ERP\SYSTEM\ORA\CENTRAL\AS
-orderBy "" -r3loadExe D:\usr\sap\SRD\SYS\exe\nuc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 1100
-jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst is written to the logfile import_monitor.java.log.
WARNING 2008-02-20 14:31:07
Execution of the command "C:\Program Files\Java\j2re1.4.2_16\bin\java.exe -classpath migmon.jar -showversion
com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "D:\ERP 2005 IDES\51032413_1\EXP1;
D:\ERP 2005 IDES\51032413_2\EXP2;D:\ERP 2005 IDES\51032413_3\EXP3;D:\ERP 2005 IDES\51032413_4\EXP4;
D:\ERP 2005 IDES\51032413_5\EXP5;D:\ERP 2005 IDES\51032413_6\EXP6;D:\ERP 2005 IDES\51032413_6\EXP7;
D:\ERP 2005 IDES\51032413_6\EXP8;D:\ERP 2005 IDES\51032413_6\EXP9;D:\ERP 2005 IDES\51032413_6\EXP10;
D:\ERP 2005 IDES\51032413_6\EXP11" -installDir C:\PROGRA1\SAPINS1\ERP\SYSTEM\ORA\CENTRAL\AS
-orderBy "" -r3loadExe D:\usr\sap\SRD\SYS\exe\nuc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 1100
-jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103.
Output: java version "1.4.2_16"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_16-b05)Java HotSpot(TM)
Client VM (build 1.4.2_16-b05, mixed mode)Import Monitor jobs: running 1, waiting 18, completed 0, failed 0, total 19.
Loading of 'SAPSDIC' import package: ERRORImport Monitor jobs: running 0, waiting 18, completed 0, failed 1, total 19.
ERROR 2008-02-20 14:31:07
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2008-02-20 14:31:07
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|NWABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor
was executed with status ERROR .
can anyone help me to fix this error. Installation of ECC 6.0 with SQL SERVER 2005 was done fine.
Thanking you
Regards
MrudulHi Mrudul,
Understood you have downloaded the completed IDES SAP 2005 SR2 package, i have also downloaded it several months ago, but i found the package not full good when i prepare to install it last week, 3 of 35 Exp unpackage CRC32 error(51032413_part15.rar & 51032413_part16.rar & 51032413_part17.rar) when unpackage them, can you do me a favor to share me the 3 rar files? As the original download address have been obsoleted away service.sap.com, i can tell you my FTP site to store them.
51032413_part15.rar & 51032413_part16.rar & 51032413_part17.rar
Or 51032413_3\EXP3\DATA\SAPAPPL1.009 & SAPAPPL1.010
12/17/2006 02:32 AM 1,048,576,000 SAPAPPL1.009
12/17/2006 02:42 AM 954,643,456 SAPAPPL1.010
Tks!
Best rds,
Jeff
msn: [email protected] -
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 ZaffalonAnd 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 -
System copy --- Import issue in Import ABAP phase
HI Team, We are doing migration using system export/import method from win2008/SQL2008 to Win2012/SQL2012 . While doing export there was a problem with table SOFFCONT1 , So we have followed the note 1922094 and changed the size of the package from 1 GB to 2 GB in SOFFCONT1.cmd , After this We have exported the data from the source system using SWPM tool. Now we are importing in to Target system , During the Import ABAP phase we are facing the below issue for same table SOFFCONT1 . Could you please tell us how to fix this issue . Do we need to do same activity for the table while importing also ? =============================================================== H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140712143736 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.6 [UNICODE] Compiled Dec 4 2013 17:25:27 patchinfo (patches.h): (0.138) Abort R3load task if TOC file has not entry for the table (note 1914260) process id 11608 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe -ctf I \\192.168.114.11 \y\Migration\Ghana_Migration_Ecc\\export\ABAP\DATA\SOFFCONT1.STR C:\Program Files\sapinst_instdir\BS2005\ERP60SR3 \LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL SOFFCONT1.TSK MSS -l SOFFCONT1.log H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: job completed H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140712143736 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140712143736 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.6 [UNICODE] Compiled Dec 4 2013 17:25:27 patchinfo (patches.h): (0.138) Abort R3load task if TOC file has not entry for the table (note 1914260) process id 10364 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe -i SOFFCONT1.cmd -dbcodepage 4103 -l SOFFCONT1.log -loadprocedure fast (DB) INFO: connected to DB (GSI) INFO: dbname = "GFGH-SAP- " (GSI) INFO: vname = "MSSQL " (GSI) INFO: hostname = "GFGH-SAP- " (GSI) INFO: sysname = "Windows NT" (GSI) INFO: nodename = "GFGH-SAP-" (GSI) INFO: release = "6.3" (GSI) INFO: version = "9600 " (GSI) INFO: machine = "6x AMD64 Level 21 (Mod 2 Step 0)" (SQL) INFO: Searching for SQL file SQLFiles.LST (SQL) INFO: SQLFiles.LST not found (SQL) INFO: Searching for SQL file \\192.168.114.11 \y\Migration\Ghana_Migration_Ecc\\export\ABAP\DB/SQLFiles.LST (SQL) INFO: \\192.168.114.11 \y\Migration\Ghana_Migration_Ecc\\export\ABAP\DB/SQLFiles.LST not found (SQL) INFO: Searching for SQL file APPL1.SQL (SQL) INFO: APPL1.SQL not found (SQL) INFO: Searching for SQL file \\192.168.114.11 \y\Migration\Ghana_Migration_Ecc\\export\ABAP\DB/MSS/APPL1.SQL (SQL) INFO: \\192.168.114.11 \y\Migration\Ghana_Migration_Ecc\\export\ABAP\DB/MSS/APPL1.SQL not found (DB) INFO: SOFFCONT1 created (DB) INFO: SOFFCONT1~0 created Interface access functions from dynamic library dbmssslib.dll loaded. (IMP) INFO: ExeFastLoad failed with (IMP) ERROR: ExeFastload: rc = 2 (DB) INFO: disconnected from DB H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error (s) H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140712163351 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140712191514 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.6 [UNICODE] Compiled Dec 4 2013 17:25:27 patchinfo (patches.h): (0.138) Abort R3load task if TOC file has not entry for the table (note 1914260) process id 8772 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe -i SOFFCONT1.cmd -dbcodepage 4103 -l SOFFCONT1.log -loadprocedure fast (DB) INFO: connected to DB (GSI) INFO: dbname = "GFGH-SAP- " (GSI) INFO: vname = "MSSQL " (GSI) INFO: hostname = "GFGH-SAP- " (GSI) INFO: sysname = "Windows NT" (GSI) INFO: nodename = "GFGH-SAP-" (GSI) INFO: release = "6.3" (GSI) INFO: version = "9600 " (GSI) INFO: machine = "6x AMD64 Level 21 (Mod 2 Step 0)" (DB) INFO: SOFFCONT1 deleted/truncated Interface access functions from dynamic library dbmssslib.dll loaded. (IMP) INFO: ExeFastLoad failed with (IMP) ERROR: ExeFastload: rc = 2 (DB) INFO: disconnected from DB H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error (s) H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140712193907 Thanks, Pavan 91-991 233 6633HI Team, We are doing migration using system export/import method from win2008/SQL2008 to Win2012/SQL2012 . We have exported the data from the source system using SWPM tool. Now we are importing in to Target system , During the Import ABAP phase we are facing the below issue. Could you please tell us how to fix this issue .If you need any other info please reach me out on 91- 991 233 6633 =============================================================== H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140712143736 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.6 [UNICODE] Compiled Dec 4 2013 17:25:27 patchinfo (patches.h): (0.138) Abort R3load task if TOC file has not entry for the table (note 1914260) process id 11608 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe -ctf I \\192.168.114.11 \y\Migration\Ghana_Migration_Ecc\\export\ABAP\DATA\SOFFCONT1.STR C:\Program Files\sapinst_instdir\BS2005\ERP60SR3 \LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL SOFFCONT1.TSK MSS -l SOFFCONT1.log H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: job completed H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140712143736 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140712143736 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.6 [UNICODE] Compiled Dec 4 2013 17:25:27 patchinfo (patches.h): (0.138) Abort R3load task if TOC file has not entry for the table (note 1914260) process id 10364 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe -i SOFFCONT1.cmd -dbcodepage 4103 -l SOFFCONT1.log -loadprocedure fast (DB) INFO: connected to DB (GSI) INFO: dbname = "GFGH-SAP- " (GSI) INFO: vname = "MSSQL " (GSI) INFO: hostname = "GFGH-SAP- " (GSI) INFO: sysname = "Windows NT" (GSI) INFO: nodename = "GFGH-SAP-" (GSI) INFO: release = "6.3" (GSI) INFO: version = "9600 " (GSI) INFO: machine = "6x AMD64 Level 21 (Mod 2 Step 0)" (SQL) INFO: Searching for SQL file SQLFiles.LST (SQL) INFO: SQLFiles.LST not found (SQL) INFO: Searching for SQL file \\192.168.114.11 \y\Migration\Ghana_Migration_Ecc\\export\ABAP\DB/SQLFiles.LST (SQL) INFO: \\192.168.114.11 \y\Migration\Ghana_Migration_Ecc\\export\ABAP\DB/SQLFiles.LST not found (SQL) INFO: Searching for SQL file APPL1.SQL (SQL) INFO: APPL1.SQL not found (SQL) INFO: Searching for SQL file \\192.168.114.11 \y\Migration\Ghana_Migration_Ecc\\export\ABAP\DB/MSS/APPL1.SQL (SQL) INFO: \\192.168.114.11 \y\Migration\Ghana_Migration_Ecc\\export\ABAP\DB/MSS/APPL1.SQL not found (DB) INFO: SOFFCONT1 created (DB) INFO: SOFFCONT1~0 created Interface access functions from dynamic library dbmssslib.dll loaded. (IMP) INFO: ExeFastLoad failed with (IMP) ERROR: ExeFastload: rc = 2 (DB) INFO: disconnected from DB H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error (s) H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140712163351 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20140712191514 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/721_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: version R7.20/V1.6 [UNICODE] Compiled Dec 4 2013 17:25:27 patchinfo (patches.h): (0.138) Abort R3load task if TOC file has not entry for the table (note 1914260) process id 8772 H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe -i SOFFCONT1.cmd -dbcodepage 4103 -l SOFFCONT1.log -loadprocedure fast (DB) INFO: connected to DB (GSI) INFO: dbname = "GFGH-SAP- " (GSI) INFO: vname = "MSSQL " (GSI) INFO: hostname = "GFGH-SAP- " (GSI) INFO: sysname = "Windows NT" (GSI) INFO: nodename = "GFGH-SAP-" (GSI) INFO: release = "6.3" (GSI) INFO: version = "9600 " (GSI) INFO: machine = "6x AMD64 Level 21 (Mod 2 Step 0)" (DB) INFO: SOFFCONT1 deleted/truncated Interface access functions from dynamic library dbmssslib.dll loaded. (IMP) INFO: ExeFastLoad failed with (IMP) ERROR: ExeFastload: rc = 2 (DB) INFO: disconnected from DB H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error (s) H:\usr\sap\\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20140712193907 Thanks, Pavan 91-991 233 6633
Hi,
This is SAP Business one system administration forum. Please find correct forum and repost above discussion to get quick assistance.
Please close this thread here with helpful answer.
Thanks & Regards,
Nagarajan -
System copy: import abap phase
Hi Guys,
While performing system copy I am facing issue in import abap phase, pasting the log for your reference:
SAPSSEXC_26.log
D:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#13 $ SAP
D:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
Compiled Jul 17 2007 00:40:17
D:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC_26.cmd -dbcodepage 4103 -l SAPSSEXC_26.log -loadprocedure fast
(DB) INFO: connected to DB
(GSI) INFO: dbname = "<SID>SAPDEMO\<SID> "
(GSI) INFO: vname = "MSSQL "
(GSI) INFO: hostname = "SAPDEMO\<SID> "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SAPDEMO"
(GSI) INFO: release = "5.2"
(GSI) INFO: version = "3790 Service Pack 2"
(GSI) INFO: machine = "8x AMD64 Level 6 (Mod 30 Step 5)"
(DB) ERROR: DDL statement failed
(DROP INDEX [TTREEI].[TTREEI~NOD])
DbSlExecute: rc = 103
(SQL error 3701)
error message returned by DbSl:
Cannot drop the index 'TTREEI.TTREEI~NOD', because it does not exist or you do not have permission.
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB) ERROR: DDL statement failed
(CREATE INDEX [TTREEI~NOD] ON [TTREEI] ( [NODE_ID] ) )
DbSlExecute: rc = 99
(SQL error 3621)
error message returned by DbSl:
Warning: Fatal error 824 occurred at Sep 24 2010 12:45AM. Note the error and time, and contact your system administrator.
The statement has been terminated.
(DB) INFO: disconnected from DB
D:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
D:\usr\sap\<SID>\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100924004524
ECC 6.0 SR2
MSSQL2005
Please suggest asap.
Regards,
Mridul GuptaHi,
After moving further I got stuck in Install Java Engine phase
Extracting packed root JAR
ERROR: Error during installation of SDM on D:\usr\sap\W6V\DVEBMGS15\SDM\program
ERROR: Cannot extract D:\usr\sap\W6V\DVEBMGS15\SDM_tmp\pack\packedRoot.jar to D:\usr\sap\W6V\DVEBMGS15\SDM\root: Cannot extract JAR:
Error: Could not extract file origin/com.adobe/PDFManipulation/Adobe Systems/0/705.20060314112518.106587/adobe-PDFManipulation.sda from archive D:/usr/sap/W6V/DVEBMGS15/SDM_tmp/pack/packedRoot.jar
Additional error message is:
invalid entry CRC (expected 0xc596dc9d but got 0xcb9ef375)
Processing error. Return code: 4
Please suggest.
Regards,
Mridul Gupta -
How to create the condition record by ABAP program
Hi Friends,
I want to create/change the condition record of PR00 by ABAP program. It seems that there have no such BAPI/standard function can help on this. Can any one of you point out a way to me?? Thanks in addvance.
Joe GR.Joe,
Check with below FM..
BAPI_PRICES_CONDITIONS.
Check this link:
Re: Sample code for BAPI_PRICES_CONDITIONS
examples....
http://www.4ap.de/abap/bapi_prices_conditions.php
Two useful threads on Same topic
Re: Sample code for BAPI_PRICES_CONDITIONS
Re: Problem with BAPI_PRICES_CONDITIONS
BAPI_PRICES_CONDITIONS
Please check this sample code from other thread.
wtable1-table_no = '306'.
wtable1-applicatio = 'V'.
wtable1-cond_type = 'ZPR0'.
wtable1-operation = '009'.
wtable1-varkey = '13001001USD 000000000050068946'.
wtable1-valid_to = '99991231'.
wtable1-valid_from = '20051101'.
wtable1-cond_no = '$000000001'.
APPEND wtable1 TO table1.
wtable2-operation = '009'.
wtable2-cond_no = '$000000001'.
wtable2-created_by = sy-uname.
wtable2-creat_date = '20051022'.
wtable2-cond_usage = 'A'.
wtable2-table_no = '110'.
wtable2-applicatio = 'V'.
wtable2-cond_type = 'ZPR0'.
wtable2-varkey = '13001001USD 000000000050068946'.
wtable2-valid_from = '20051101'.
wtable2-valid_to = '99991231'.
APPEND wtable2 TO table2.
wtable3-operation = '009'.
wtable3-cond_no = '$000000001'.
wtable3-cond_count = '01'.
wtable3-applicatio = 'V'.
wtable3-cond_type = 'ZPR0'.
wtable3-scaletype = 'A'.
wtable3-scalebasin = 'C'.
wtable3-scale_qty = '1'.
wtable3-cond_p_unt = '1'.
wtable3-cond_unit = 'EA'.
wtable3-calctypcon = 'C'.
wtable3-cond_value = '454'.
wtable3-condcurr = 'USD'.
APPEND wtable3 TO table3.
CALL FUNCTION 'BAPI_PRICES_CONDITIONS'
EXPORTING
PI_initialmode = 'X'
PI_BLOCKNUMBER =
TABLES
ti_bapicondct = table1
ti_bapicondhd = table2
ti_bapicondit = table3
ti_bapicondqs = table4
ti_bapicondvs = table5
to_bapiret2 = table6
to_bapiknumhs = table7
to_mem_initial = table8
EXCEPTIONS
update_error = 1
OTHERS = 2
IF sy-subrc <> 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
READ TABLE table6 WITH KEY type = 'E' TRANSPORTING NO FIELDS.
IF sy-subrc = 0.
loop at table6 into ret.
write: / ret-type, ret-message, ret-id, RET-LOG_NO, RET-LOG_MSG_NO,
RET-MESSAGE_V1, RET-MESSAGE_V2, RET-MESSAGE_V3, RET-MESSAGE_V4,
RET-PARAMETER,RET-ROW,RET-FIELD.
endloop.
ELSE.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
*EXPORTING
WAIT =
IMPORTING
return = ret
ENDIF.
Don't forget to reward if useful.... -
ECC 6.0 Installation fails during Import ABAP Phase
Hi,
I am tryiing to install ECC 6.0 on windows 2003:Oracle and it is failing at phase 17 Import Abap with the following error:
ERROR 2007-11-13 16:04:09
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-11-13 16:04:09
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|9|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 .
here is the import_monitor.java.log file:
ava version "1.4.2_14"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_14-b05)
Java HotSpot(TM) Client VM (build 1.4.2_14-b05, mixed mode)
Import Monitor jobs: running 1, waiting 37, completed 0, failed 0, total 38.
Loading of 'SAPNTAB' import package: OK
Import Monitor jobs: running 0, waiting 37, completed 1, failed 0, total 38.
Import Monitor jobs: running 1, waiting 36, completed 1, failed 0, total 38.
Import Monitor jobs: running 2, waiting 35, completed 1, failed 0, total 38.
Import Monitor jobs: running 3, waiting 34, completed 1, failed 0, total 38.
Loading of 'SAPSSEXC_4' import package: OK
Import Monitor jobs: running 2, waiting 34, completed 2, failed 0, total 38.
Import Monitor jobs: running 3, waiting 33, completed 2, failed 0, total 38.
Loading of 'DOKCLU' import package: OK
Import Monitor jobs: running 2, waiting 33, completed 3, failed 0, total 38.
Import Monitor jobs: running 3, waiting 32, completed 3, failed 0, total 38.
Loading of 'SAPAPPL2_1' import package: OK
Import Monitor jobs: running 2, waiting 32, completed 4, failed 0, total 38.
Import Monitor jobs: running 3, waiting 31, completed 4, failed 0, total 38.
Loading of 'SAPSSEXC_2' import package: OK
Import Monitor jobs: running 2, waiting 31, completed 5, failed 0, total 38.
Import Monitor jobs: running 3, waiting 30, completed 5, failed 0, total 38.
Loading of 'DD03L' import package: OK
Import Monitor jobs: running 2, waiting 30, completed 6, failed 0, total 38.
Import Monitor jobs: running 3, waiting 29, completed 6, failed 0, total 38.
Loading of 'SAPAPPL1_1' import package: OK
Import Monitor jobs: running 2, waiting 29, completed 7, failed 0, total 38.
Import Monitor jobs: running 3, waiting 28, completed 7, failed 0, total 38.
Loading of 'SAPSSEXC_1' import package: OK
Import Monitor jobs: running 2, waiting 28, completed 8, failed 0, total 38.
Import Monitor jobs: running 3, waiting 27, completed 8, failed 0, total 38.
Loading of 'SAPAPPL0_3' import package: OK
Import Monitor jobs: running 2, waiting 27, completed 9, failed 0, total 38.
Import Monitor jobs: running 3, waiting 26, completed 9, failed 0, total 38.
Loading of 'SAPAPPL1_2' import package: OK
Import Monitor jobs: running 2, waiting 26, completed 10, failed 0, total 38.
Loading of 'SAPAPPL2_2' import package: OK
Import Monitor jobs: running 1, waiting 26, completed 11, failed 0, total 38.
Import Monitor jobs: running 2, waiting 25, completed 11, failed 0, total 38.
Import Monitor jobs: running 3, waiting 24, completed 11, failed 0, total 38.
Loading of 'SCPRSVALS' import package: OK
Import Monitor jobs: running 2, waiting 24, completed 12, failed 0, total 38.
Import Monitor jobs: running 3, waiting 23, completed 12, failed 0, total 38.
Loading of 'SAPAPPL0_1' import package: OK
Import Monitor jobs: running 2, waiting 23, completed 13, failed 0, total 38.
Import Monitor jobs: running 3, waiting 22, completed 13, failed 0, total 38.
Loading of 'SAPAPPL2_3' import package: ERROR
Import Monitor jobs: running 2, waiting 22, completed 13, failed 1, total 38.
Loading of 'SAPSSEXC_3' import package: ERROR
Import Monitor jobs: running 1, waiting 22, completed 13, failed 2, total 38.
Import Monitor jobs: running 2, waiting 21, completed 13, failed 2, total 38.
Import Monitor jobs: running 3, waiting 20, completed 13, failed 2, total 38.
Loading of 'SAPSSEXC_5' import package: ERROR
Import Monitor jobs: running 2, waiting 20, completed 13, failed 3, total 38.
Loading of 'SAPAPPL0_2' import package: ERROR
Import Monitor jobs: running 1, waiting 20, completed 13, failed 4, total 38.
Import Monitor jobs: running 2, waiting 19, completed 13, failed 4, total 38.
Import Monitor jobs: running 3, waiting 18, completed 13, failed 4, total 38.
Loading of 'FUPARAREF' import package: ERROR
Import Monitor jobs: running 2, waiting 18, completed 13, failed 5, total 38.
Import Monitor jobs: running 3, waiting 17, completed 13, failed 5, total 38.
Loading of 'TODIR' import package: ERROR
Import Monitor jobs: running 2, waiting 17, completed 13, failed 6, total 38.
Import Monitor jobs: running 3, waiting 16, completed 13, failed 6, total 38.
Loading of 'SAPSDIC' import package: ERROR
Import Monitor jobs: running 2, waiting 16, completed 13, failed 7, total 38.
Import Monitor jobs: running 3, waiting 15, completed 13, failed 7, total 38.
Loading of 'SEOSUBCODF' import package: OK
Import Monitor jobs: running 2, waiting 15, completed 14, failed 7, total 38.
Loading of 'SAPSSRC' import package: ERROR
Import Monitor jobs: running 1, waiting 15, completed 14, failed 8, total 38.
Loading of 'E071K' import package: ERROR
Import Monitor jobs: running 0, waiting 15, completed 14, failed 9, total 38.
Import Monitor jobs: running 1, waiting 14, completed 14, failed 9, total 38.
Import Monitor jobs: running 2, waiting 13, completed 14, failed 9, total 38.
Import Monitor jobs: running 3, waiting 12, completed 14, failed 9, total 38.
Loading of 'SAPSPROT' import package: OK
Import Monitor jobs: running 2, waiting 12, completed 15, failed 9, total 38.
Import Monitor jobs: running 3, waiting 11, completed 15, failed 9, total 38.
Loading of 'SAPPOOL' import package: ERROR
Import Monitor jobs: running 2, waiting 11, completed 15, failed 10, total 38.
Loading of 'SCPRVALS' import package: OK
Import Monitor jobs: running 1, waiting 11, completed 16, failed 10, total 38.
Loading of 'SAPSDOCU' import package: OK
Import Monitor jobs: running 0, waiting 11, completed 17, failed 10, total 38.
Import Monitor jobs: running 1, waiting 10, completed 17, failed 10, total 38.
Import Monitor jobs: running 2, waiting 9, completed 17, failed 10, total 38.
Import Monitor jobs: running 3, waiting 8, completed 17, failed 10, total 38.
Loading of 'SAPSLEXC' import package: ERROR
Import Monitor jobs: running 2, waiting 8, completed 17, failed 11, total 38.
Loading of 'SAPCLUST' import package: OK
Import Monitor jobs: running 1, waiting 8, completed 18, failed 11, total 38.
Import Monitor jobs: running 2, waiting 7, completed 18, failed 11, total 38.
Import Monitor jobs: running 3, waiting 6, completed 18, failed 11, total 38.
Loading of 'SAPAPPL0_4' import package: ERROR
Import Monitor jobs: running 2, waiting 6, completed 18, failed 12, total 38.
Loading of 'SAPUSER' import package: ERROR
Import Monitor jobs: running 1, waiting 6, completed 18, failed 13, total 38.
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 0, waiting 6, completed 19, failed 13, total 38.
Import Monitor jobs: running 1, waiting 5, completed 19, failed 13, total 38.
Import Monitor jobs: running 2, waiting 4, completed 19, failed 13, total 38.
Import Monitor jobs: running 3, waiting 3, completed 19, failed 13, total 38.
Loading of 'SAPDDIM' import package: OK
Import Monitor jobs: running 2, waiting 3, completed 20, failed 13, total 38.
Loading of 'SAPDFACT' import package: OK
Import Monitor jobs: running 1, waiting 3, completed 21, failed 13, total 38.
Loading of 'SAPDODS' import package: OK
Import Monitor jobs: running 0, waiting 3, completed 22, failed 13, total 38.
Import Monitor jobs: running 1, waiting 2, completed 22, failed 13, total 38.
Import Monitor jobs: running 2, waiting 1, completed 22, failed 13, total 38.
Loading of 'SAPUSER1' import package: OK
Import Monitor jobs: running 1, waiting 1, completed 23, failed 13, total 38.
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 24, failed 13, total 38.
here is a copy of import_monitor.log
INFO: 2007-11-13 14:02:09
Import Monitor is started.
CONFIG: 2007-11-13 14:02:09
Application options:
dbCodepage=4103
dbType=ORA
extFiles=yes
importDirs=C:\sapcds\inst_exp\exp1\EXP1;C:\sapcds\inst_exp\exp1\EXP2;C:\sapcds\inst_exp\exp1\EXP3;C:\sapcds\inst_exp\exp1\EXP4;C:\sapcds\inst_exp\exp1\EXP5;C:\sapcds\inst_exp\exp1\EXP6;C:\sapcds\inst_exp\exp2\EXP7;C:\sapcds\inst_exp\exp2\EXP8;C:\sapcds\inst_exp\exp2\EXP9;C:\sapcds\inst_exp\exp2\EXP10;C:\sapcds\inst_exp\exp2\EXP11
installDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS
jobNum=3
loadArgs= -stop_on_error
monitorTimeout=30
orderBy=
r3loadExe=E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2007-11-13 14:02:09
List of packages with table structure: 'SAP0000'.
CONFIG: 2007-11-13 14:02:09
List of packages with views: 'SAPVIEW'.
TRACE: 2007-11-13 14:02:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is started.
INFO: 2007-11-13 14:02:09 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL' template file is successfully completed.
Primary key creation: after load.
Index creation: after load.
INFO: 2007-11-13 14:02:10
Data codepage 1100 is determined using TOC file 'C:\sapcds\inst_exp\exp1\EXP1\DATA\SAPSSEXC_3.TOC' for package 'SAPSSEXC_3'.
INFO: 2007-11-13 14:02:12
Version table 'SVERS' is found in STR file 'C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
INFO: 2007-11-13 14:02:12
Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR' from package 'SAPNTAB'.
TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is started.
TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPNTAB' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP10\DATA\SAPNTAB.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPNTAB.TSK ORA -l SAPNTAB.log
TRACE: 2007-11-13 14:02:12 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPNTAB' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPNTAB.cmd -dbcodepage 4103 -l SAPNTAB.log -stop_on_error
INFO: 2007-11-13 14:13:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPNTAB' import package is successfully completed.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_3' import package is started.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is started.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_4' import package is started.
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_3' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP1\DATA\SAPSSEXC_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_3.TSK ORA -l SAPSSEXC_3.log
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_4' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_4.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_4.TSK ORA -l SAPSSEXC_4.log
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'DOKCLU' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP11\DATA\DOKCLU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" DOKCLU.TSK ORA -l DOKCLU.log
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_3' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_3.cmd -dbcodepage 4103 -l SAPSSEXC_3.log -stop_on_error
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_4' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_4.cmd -dbcodepage 4103 -l SAPSSEXC_4.log -stop_on_error
TRACE: 2007-11-13 14:13:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'DOKCLU' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -l DOKCLU.log -stop_on_error
INFO: 2007-11-13 14:28:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_4' import package is successfully completed.
TRACE: 2007-11-13 14:29:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_2' import package is started.
TRACE: 2007-11-13 14:29:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_2.TSK ORA -l SAPSSEXC_2.log
TRACE: 2007-11-13 14:29:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_2.cmd -dbcodepage 4103 -l SAPSSEXC_2.log -stop_on_error
INFO: 2007-11-13 14:34:56 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is successfully completed.
TRACE: 2007-11-13 14:35:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_1' import package is started.
TRACE: 2007-11-13 14:35:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_1.TSK ORA -l SAPAPPL2_1.log
TRACE: 2007-11-13 14:35:12 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_1.cmd -dbcodepage 4103 -l SAPAPPL2_1.log -stop_on_error
INFO: 2007-11-13 15:02:33 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_1' import package is successfully completed.
TRACE: 2007-11-13 15:02:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_1' import package is started.
TRACE: 2007-11-13 15:02:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL1_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL1_1.TSK ORA -l SAPAPPL1_1.log
TRACE: 2007-11-13 15:02:43 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1_1.cmd -dbcodepage 4103 -l SAPAPPL1_1.log -stop_on_error
INFO: 2007-11-13 15:08:06 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_2' import package is successfully completed.
TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask run
Loading of 'DD03L' import package is started.
TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'DD03L' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP9\DATA\DD03L.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" DD03L.TSK ORA -l DD03L.log
TRACE: 2007-11-13 15:08:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'DD03L' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i DD03L.cmd -dbcodepage 4103 -l DD03L.log -stop_on_error
INFO: 2007-11-13 15:19:29 com.sap.inst.migmon.LoadTask run
Loading of 'DD03L' import package is successfully completed.
TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_1' import package is started.
TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_1.TSK ORA -l SAPSSEXC_1.log
TRACE: 2007-11-13 15:19:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_1.cmd -dbcodepage 4103 -l SAPSSEXC_1.log -stop_on_error
INFO: 2007-11-13 15:22:34 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_1' import package is successfully completed.
TRACE: 2007-11-13 15:22:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_2' import package is started.
TRACE: 2007-11-13 15:22:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_2.TSK ORA -l SAPAPPL2_2.log
TRACE: 2007-11-13 15:22:42 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_2.cmd -dbcodepage 4103 -l SAPAPPL2_2.log -stop_on_error
INFO: 2007-11-13 15:24:18 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_1' import package is successfully completed.
TRACE: 2007-11-13 15:24:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_3' import package is started.
TRACE: 2007-11-13 15:24:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_3' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_3.TSK ORA -l SAPAPPL0_3.log
TRACE: 2007-11-13 15:24:40 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_3' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_3.cmd -dbcodepage 4103 -l SAPAPPL0_3.log -stop_on_error
INFO: 2007-11-13 15:34:21 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_3' import package is successfully completed.
TRACE: 2007-11-13 15:34:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_2' import package is started.
TRACE: 2007-11-13 15:34:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL1_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL1_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL1_2.TSK ORA -l SAPAPPL1_2.log
TRACE: 2007-11-13 15:34:41 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL1_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL1_2.cmd -dbcodepage 4103 -l SAPAPPL1_2.log -stop_on_error
INFO: 2007-11-13 15:45:42 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1_2' import package is successfully completed.
INFO: 2007-11-13 15:46:06 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_2' import package is successfully completed.
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_1' import package is started.
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRSVALS' import package is started.
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_1.TSK ORA -l SAPAPPL0_1.log
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SCPRSVALS' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SCPRSVALS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SCPRSVALS.TSK ORA -l SCPRSVALS.log
TRACE: 2007-11-13 15:46:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SCPRSVALS' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SCPRSVALS.cmd -dbcodepage 4103 -l SCPRSVALS.log -stop_on_error
TRACE: 2007-11-13 15:46:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_1.cmd -dbcodepage 4103 -l SAPAPPL0_1.log -stop_on_error
INFO: 2007-11-13 15:51:35 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRSVALS' import package is successfully completed.
TRACE: 2007-11-13 15:51:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_3' import package is started.
TRACE: 2007-11-13 15:51:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL2_3' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP8\DATA\SAPAPPL2_3.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL2_3.TSK ORA -l SAPAPPL2_3.log
TRACE: 2007-11-13 15:51:41 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL2_3' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_3.cmd -dbcodepage 4103 -l SAPAPPL2_3.log -stop_on_error
INFO: 2007-11-13 15:56:27 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_1' import package is successfully completed.
TRACE: 2007-11-13 15:56:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_2' import package is started.
TRACE: 2007-11-13 15:56:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_2' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_2.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_2.TSK ORA -l SAPAPPL0_2.log
TRACE: 2007-11-13 15:56:43 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_2' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error
ERROR: 2007-11-13 15:56:48 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL2_3' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL2_3.cmd -dbcodepage 4103 -l SAPAPPL2_3.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL2_3.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
ERROR: 2007-11-13 15:56:51 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_3' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_3.cmd -dbcodepage 4103 -l SAPSSEXC_3.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSEXC_3.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
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is started.
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_5' import package is started.
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSEXC_5' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP3\DATA\SAPSSEXC_5.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSEXC_5.TSK ORA -l SAPSSEXC_5.log
TRACE: 2007-11-13 15:57:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDIC' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP9\DATA\SAPSDIC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDIC.TSK ORA -l SAPSDIC.log
TRACE: 2007-11-13 15:57:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC_5' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_5.cmd -dbcodepage 4103 -l SAPSSEXC_5.log -stop_on_error
TRACE: 2007-11-13 15:57:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDIC' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error
ERROR: 2007-11-13 15:57:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC_5' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC_5.cmd -dbcodepage 4103 -l SAPSSEXC_5.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSEXC_5.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
ERROR: 2007-11-13 15:57:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_2' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_2.cmd -dbcodepage 4103 -l SAPAPPL0_2.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL0_2.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
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask run
Loading of 'FUPARAREF' import package is started.
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask run
Loading of 'TODIR' import package is started.
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'FUPARAREF' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\FUPARAREF.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" FUPARAREF.TSK ORA -l FUPARAREF.log
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'TODIR' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\TODIR.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" TODIR.TSK ORA -l TODIR.log
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'TODIR' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error
TRACE: 2007-11-13 15:57:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'FUPARAREF' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i FUPARAREF.cmd -dbcodepage 4103 -l FUPARAREF.log -stop_on_error
ERROR: 2007-11-13 15:57:40 com.sap.inst.migmon.LoadTask run
Loading of 'FUPARAREF' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i FUPARAREF.cmd -dbcodepage 4103 -l FUPARAREF.log -stop_on_error' exited with return code 2.
For mode details see 'FUPARAREF.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
TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is started.
TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSSRC' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSSRC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSSRC.TSK ORA -l SAPSSRC.log
TRACE: 2007-11-13 15:58:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSRC' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error
ERROR: 2007-11-13 15:58:10 com.sap.inst.migmon.LoadTask run
Loading of 'TODIR' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i TODIR.cmd -dbcodepage 4103 -l TODIR.log -stop_on_error' exited with return code 2.
For mode details see 'TODIR.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
TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask run
Loading of 'SEOSUBCODF' import package is started.
TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SEOSUBCODF' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SEOSUBCODF.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SEOSUBCODF.TSK ORA -l SEOSUBCODF.log
TRACE: 2007-11-13 15:58:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SEOSUBCODF' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SEOSUBCODF.cmd -dbcodepage 4103 -l SEOSUBCODF.log -stop_on_error
ERROR: 2007-11-13 15:58:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -stop_on_error' 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
TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask run
Loading of 'E071K' import package is started.
TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'E071K' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\E071K.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" E071K.TSK ORA -l E071K.log
TRACE: 2007-11-13 15:59:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'E071K' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i E071K.cmd -dbcodepage 4103 -l E071K.log -stop_on_error
INFO: 2007-11-13 16:00:13 com.sap.inst.migmon.LoadTask run
Loading of 'SEOSUBCODF' import package is successfully completed.
ERROR: 2007-11-13 16:00:31 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSRC' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSRC.cmd -dbcodepage 4103 -l SAPSSRC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSSRC.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
ERROR: 2007-11-13 16:00:31 com.sap.inst.migmon.LoadTask run
Loading of 'E071K' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i E071K.cmd -dbcodepage 4103 -l E071K.log -stop_on_error' exited with return code 2.
For mode details see 'E071K.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
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is started.
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRVALS' import package is started.
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is started.
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SCPRVALS' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SCPRVALS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SCPRVALS.TSK ORA -l SCPRVALS.log
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPPOOL' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPPOOL.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPPOOL.TSK ORA -l SAPPOOL.log
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSPROT' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP5\DATA\SAPSPROT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSPROT.TSK ORA -l SAPSPROT.log
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SCPRVALS' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SCPRVALS.cmd -dbcodepage 4103 -l SCPRVALS.log -stop_on_error
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPPOOL' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -stop_on_error
TRACE: 2007-11-13 16:00:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSPROT' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSPROT.cmd -dbcodepage 4103 -l SAPSPROT.log -stop_on_error
INFO: 2007-11-13 16:01:20 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSPROT' import package is successfully completed.
TRACE: 2007-11-13 16:01:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is started.
TRACE: 2007-11-13 16:01:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSDOCU' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP4\DATA\SAPSDOCU.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSDOCU.TSK ORA -l SAPSDOCU.log
TRACE: 2007-11-13 16:01:40 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSDOCU' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSDOCU.cmd -dbcodepage 4103 -l SAPSDOCU.log -stop_on_error
ERROR: 2007-11-13 16:01:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPPOOL' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPPOOL.cmd -dbcodepage 4103 -l SAPPOOL.log -stop_on_error' exited with return code 2.
For mode details see 'SAPPOOL.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
INFO: 2007-11-13 16:01:57 com.sap.inst.migmon.LoadTask run
Loading of 'SCPRVALS' import package is successfully completed.
INFO: 2007-11-13 16:02:01 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDOCU' import package is successfully completed.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_4' import package is started.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is started.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is started.
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLEXC' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSLEXC.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLEXC.TSK ORA -l SAPSLEXC.log
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPCLUST' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPCLUST.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPCLUST.TSK ORA -l SAPCLUST.log
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPAPPL0_4' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp2\EXP7\DATA\SAPAPPL0_4.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPAPPL0_4.TSK ORA -l SAPAPPL0_4.log
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLEXC' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error
TRACE: 2007-11-13 16:02:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPCLUST' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -stop_on_error
TRACE: 2007-11-13 16:02:10 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPAPPL0_4' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_4.cmd -dbcodepage 4103 -l SAPAPPL0_4.log -stop_on_error
ERROR: 2007-11-13 16:02:10 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLEXC' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLEXC.cmd -dbcodepage 4103 -l SAPSLEXC.log -stop_on_error' exited with return code 2.
For mode details see 'SAPSLEXC.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
INFO: 2007-11-13 16:02:23 com.sap.inst.migmon.LoadTask run
Loading of 'SAPCLUST' import package is successfully completed.
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is started.
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is started.
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPSLOAD' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPSLOAD.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPSLOAD.TSK ORA -l SAPSLOAD.log
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPUSER.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPUSER.TSK ORA -l SAPUSER.log
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSLOAD' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPSLOAD.cmd -dbcodepage 4103 -l SAPSLOAD.log -stop_on_error
TRACE: 2007-11-13 16:02:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -stop_on_error
ERROR: 2007-11-13 16:02:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL0_4' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPAPPL0_4.cmd -dbcodepage 4103 -l SAPAPPL0_4.log -stop_on_error' exited with return code 2.
For mode details see 'SAPAPPL0_4.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
ERROR: 2007-11-13 16:02:41 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER' import package is interrupted with R3load error.
Process 'E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER.cmd -dbcodepage 4103 -l SAPUSER.log -stop_on_error' exited with return code 2.
For mode details see 'SAPUSER.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
INFO: 2007-11-13 16:02:42 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSLOAD' import package is successfully completed.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is started.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is started.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is started.
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDDIM' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDDIM.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDDIM.TSK ORA -l SAPDDIM.log
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDFACT' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDFACT.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDFACT.TSK ORA -l SAPDFACT.log
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPDODS' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPDODS.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPDODS.TSK ORA -l SAPDODS.log
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDODS' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDODS.cmd -dbcodepage 4103 -l SAPDODS.log -stop_on_error
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDDIM' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDDIM.cmd -dbcodepage 4103 -l SAPDDIM.log -stop_on_error
TRACE: 2007-11-13 16:03:09 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPDFACT' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error
INFO: 2007-11-13 16:03:10 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDDIM' import package is successfully completed.
INFO: 2007-11-13 16:03:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDFACT' import package is successfully completed.
INFO: 2007-11-13 16:03:11 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS' import package is successfully completed.
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is started.
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAP0000.TSK ORA -l SAP0000.log -o D
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAPUSER1' import package:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -ctf I C:\sapcds\inst_exp\exp1\EXP6\DATA\SAPUSER1.STR "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS\DDLORA.TPL" SAPUSER1.TSK ORA -l SAPUSER1.log
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -stop_on_error
TRACE: 2007-11-13 16:03:39 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPUSER1' import package into database:
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe -i SAPUSER1.cmd -dbcodepage 4103 -l SAPUSER1.log -stop_on_error
INFO: 2007-11-13 16:03:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAPUSER1' import package is successfully completed.
INFO: 2007-11-13 16:03:40 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
WARNING: 2007-11-13 16:04:09
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2007-11-13 16:04:09
13 error(s) during processing of packages.
INFO: 2007-11-13 16:04:09
Import Monitor is stopped.
how can i resolve these errors?Hi,
Here are the logs of the jobs that are failing to complete. i am selecting the recommended which is unicode
SAPALLP2_3.log
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE TABLE "TN02Q" ( "MANDT" VARCHAR2(9) DEFAULT '000' NOT NULL , "EINRI" VARCHAR2(12) DEFAULT ' ' NOT NULL , "ANWEN" VARCHAR2(12) DEFAULT ' ' NOT NULL , "PARNA" VARCHAR2(30) DEFAULT ' ' NOT NULL , "PARWE" VARCHAR2(45) DEFAULT ' ' NOT NULL , "COMMT" VARCHAR2(90) DEFAULT ' ' NOT NULL ) TABLESPACE PSAPSR3 STORAGE (INITIAL 16384 NEXT 0000000040K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select /*+ index(idl_sb4$ i_...","Typecheck","kgghtInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155648
SAPSSEXC_3.log
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(DB) INFO: REPOSRC created #20071113141340
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 99, table "REPOSRC"
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select /*+ index(idl_sb4$ i_...","Typecheck","kgghtInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155650
SAPSSEXC_5.log
DbSl Trace: Failed to register client info: orc=604
DbSl Trace: ORA-604 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=0)
(DB) ERROR: DDL statement failed
(CREATE TABLE "TFTIT" ( "SPRAS" VARCHAR2(3) DEFAULT ' ' NOT NULL , "FUNCNAME" VARCHAR2(90) DEFAULT ' ' NOT NULL , "STEXT" VARCHAR2(222) DEFAULT ' ' NOT NULL ) TABLESPACE PSAPSR3700 STORAGE (INITIAL 34164981 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 1
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select name,password,datats#...","Typecheck","kgghtInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155711
SAPAPPL0_2.log
DbSl Trace: ORA-604 occurred when executing SQL statement (parse error offset=41)
(DB) ERROR: DDL statement failed
(CREATE UNIQUE INDEX "ECRM_REPL_KEY~0" ON "ECRM_REPL_KEY" ( "MANDT", "ISUPRODLOG", "OBJNUM" ) TABLESPACE PSAPSR3 STORAGE (INITIAL 16384 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) )
DbSlExecute: rc = 99
(SQL error 604)
error message returned by DbSl:
ORA-00604: error occurred at recursive SQL level 2
ORA-04031: unable to allocate 4108 bytes of shared memory ("shared pool","select con#,obj#,rcon#,enabl...","Typecheck","kgghteInit")
(DB) INFO: disconnected from DB
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: job finished with 1 error(s)
E:\usr\sap\SIL\SYS\exe\uc\NTI386\R3load.exe: END OF LOG: 20071113155711 -
How to find the Web AS Port from ABAP program
Hi
I have an ABAP program which passes an URL for a BSP page to the Alert Framework. While creating the URL I need to find out the Hostname and port number for the Web service for that server. Hostname comes from sy-host but I am not able to find the port number.
Please help...
Thanks in advanceHi,
consider this little code snippet:
data: l_urls type tihttpurls2.
call method cl_http_server=>get_extension_info
EXPORTING
extension_class = 'cl_http_ext_bsp'
IMPORTING
urls = l_urls.
l_urls contains a table of configured ports. maybe that helps.
regards, Ulli -
Reading the XML message from Xi stored in XML format from a abap program.
Hi Gurus,
My requirement here is to read the data that will be coming from Xi from my custom abap program and updating 2 data base tables. The method is after the data mapping is done a class is generated in abap proxy in which a method is available. Inside the method i am writing the code for getting the Xi data stored as a payload message which can be seen in the transaction SXMB_MONI. My code is given below.
***begin code***
method ZII_PAYROLL_HEADER_IN~PAYROLL_HEADER_IN.
**** INSERT IMPLEMENTATION HERE **** ***
data: ln type i.
DATA: i_items TYPE TABLE OF ZPAYLOAD_WRAPPER_EMPLOYEE_REC3.
*DATA: wa_items type ZPAYLOAD_WRAPPER_EMPLOYEE_TAB5.
data: wa_items type ZPAYLOAD_WRAPPER_EMPLOYEE_REC3.
DATA:PERNR TYPE STRING.
*data: it_ZPAYLOAD_WRAPPER16 TYPE ZPAYLOAD_WRAPPER16.
I_ITEMS[] = INPUT-PAYLOAD_WRAPPER-BODY-XMLDOC-PAYROLL_PERIOD_OVERVIEW-EMPLOYEE_RECORD[].
*I_ITEMS = INPUT-payloadWrapper-Body-XMLDOC-PayrollPeriodOverview-EmployeeRecord.
describe table i_items[] lines ln.
endmethod.
**End code***
As per the logic the data stored in the XML message should be avaialble in INPUT-payloadWrapper-Body-XMLDOC-PayrollPeriodOverview-EmployeeRecord which i am assigning to a local internal table in the class.
But in my case there is no data coming in
INPUT-payloadWrapper-Body-XMLDOC-PayrollPeriodOverview-EmployeeRecord.
But i can see the data transffered from XI in the transaction SXMB_MONI->XML message->inbound message->payload.
Is there any way to read the data stored in the XML message in the transaction SXMB_MONI.
Also why the data is not coming in
INPUT-payloadWrapper-Body-XMLDOC-PayrollPeriodOverview-EmployeeRecord inside the class.
If there is any solution for this problem please post it.You can use function module SXMB_GET_MESSAGE_PAYLOAD.
Code snippet:
DATA: ls_mast TYPE sxmspmast,
ls_msgkey TYPE sxmsmkey,
lv_bin_xml TYPE xstring,
lv_str_xml TYPE string.
* select sxmspmast into ls_mast
ls_msgkey-msgid = ls_mast-msgguid.
ls_msgkey-pid = 'RECEIVER'.
CALL FUNCTION 'SXMB_GET_MESSAGE_PAYLOAD'
EXPORTING
im_msgkey = ls_msgkey
im_archive = ' '
im_version = ls_mast-vers
IMPORTING
ex_msg_bytes = lv_bin_xml
EXCEPTIONS
not_authorized = 1
no_message = 2
internal_error = 3
no_payload = 4
OTHERS = 5.
IF sy-subrc EQ 0.
lv_str_xml = cl_soap_moni_helper=>convert_xstring_to_string( xstring_in = lv_bin_xml ).
ENDIF. -
Hi everyone!
Is there a way in ABAP to output XML files? Pls. send code/ function module if any.
From ABAP programs, we are sure that we can output TEXT files, but how about XML files?
The significance of this question is related
Currently we are using XI to interface SAP and AMS, this question for ABAP to produce XML file arose, if for example, the XI server is down and we have to still send data from one system to another. IDocs can also produce XML files, pls confirm. Earlier however, we have preferred XI rather than IDocs to do this. Anyway, any idea regarding this scenario will be greatly appreciated.
Thanks and God bless!
CelesteHi,
Please check this sample codes from other thread.
1. itab --- > xml
xml ---> itab.
2. This program will do both.
(just copy paste in new program)
3.
REPORT abc.
*-------------- DATA
DATA : t001 LIKE TABLE OF t001 WITH HEADER LINE.
DATA : BEGIN OF itab OCCURS 0,
a(100) TYPE c,
END OF itab.
DATA: xml_out TYPE string .
DATA : BEGIN OF upl OCCURS 0,
f(255) TYPE c,
END OF upl.
DATA: xmlupl TYPE string .
******************************* FIRST PHASE
******************************* FIRST PHASE
******************************* FIRST PHASE
*------------------ Fetch Data
SELECT * FROM t001 INTO TABLE t001.
*------------------- XML
CALL TRANSFORMATION ('ID')
SOURCE tab = t001[]
RESULT XML xml_out.
CALL FUNCTION 'SCMS_STRING_TO_FTEXT'
EXPORTING
TEXT = xml_out
* IMPORTING
* LENGTH =
TABLES
FTEXT_TAB = itab.
*-------------- Download
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
filetype = 'BIN'
filename = 'd:xx.xml'
TABLES
data_tab = itab.
******************************* SECOND PHASE
******************************* SECOND PHASE
******************************* SECOND PHASE
BREAK-POINT.
REFRESH t001.
CLEAR t001.
CALL FUNCTION 'GUI_UPLOAD'
EXPORTING
filename = 'D:XX.XML'
filetype = 'BIN'
TABLES
data_tab = upl.
LOOP AT upl.
CONCATENATE xmlupl upl-f INTO xmlupl.
ENDLOOP.
*------------------- XML
CALL TRANSFORMATION ('ID')
SOURCE XML xmlupl
RESULT tab = t001[]
BREAK-POINT.
Regards,
Ferry Lianto
Maybe you are looking for
-
List of soundcards/audio interfaces working under Mac OS 10.6 + Logic 9 ?
hey everybody, I have a Digidesign Digi 002 and the Core Audio drivers for Snow Leopard are not avalaible yet. I am looking to get another soundcard/interface until the Digi 002 drivers are available. What cards/interfaces are compatible with Snow Le
-
Query of queries in a function
I call my report through a command such as the following: <cfquery name="myquery"> select * from somewhere </cfquery> <cfreport template="myreport.cfr" format="flashpaper" overwrite="no" query="#myquery#"> <cfreportparam NAME="commdate" VALUE="#commd
-
Hello, where can i download the updates from Acrobat Pro 9 for Mac? I purchased the software a few years ago and ha dot reinstall it. It was possible for me to download the main program, but i can not find the updates up to version 9.5.5. I would nee
-
Hi, I am new to BDB development. Here i am working on node traversal using XmlValue class. I have some of the queries on traversing the nodes using XmlValue class…. Steps followed for the same are as below… 1. Opening the BDB Environment 2. Loading t
-
Problems with the technical assistance and Warranty in BRAZIL
My English is not the best, but I will do my best. I've bought an Iphone 4 from a telephony company called TIM here in Brazil, and after 15 days the device was not working anymore. I sent it to the technical assistance 32 days ago, and they said yest