Skip to Content
avatar image
Former Member

Loading of 'SAPSSEXC' import package is interrupted with R3load error.

Hi Experts,

While installing ERP6.0 EHP5 in DB2 getting error as mentioned below log. Please help

CONFIG: 2011-09-17 16:55:31

Application options:

dbCodepage=4103

dbType=DB6

extFiles=no

importDirs=C:\SAPCD\sanexport\ABAP

installDir=C:\Program Files\sapinst_instdir\ERPEhP5\LM\COPY\DB6\SYSTEM\CENTRAL\AS-ABAP

jobNum=3

loadArgs=-stop_on_error -loadprocedure fast LOAD

migrationKey=1g1gDEM50Dd01eqtdAM11A96

monitorTimeout=30

orderBy=

r3loadExe=D:\usr\sap\HCD\SYS\exe\uc\NTAMD64\R3load.exe

sapinst=

trace=all

tskFiles=yes

CONFIG: 2011-09-17 16:55:31

List of packages with table structure: 'SAP0000'.

CONFIG: 2011-09-17 16:55:31

List of packages with views: 'SAPVIEW'.

TRACE: 2011-09-17 16:55:31 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\ERPEhP5\LM\COPY\DB6\SYSTEM\CENTRAL\AS-ABAP\DDLDB6.TPL' template file is started.

INFO: 2011-09-17 16:55:31 com.sap.inst.migmon.imp.ImportStandardTask preCreate

Parse of 'C:\Program Files\sapinst_instdir\ERPEhP5\LM\COPY\DB6\SYSTEM\CENTRAL\AS-ABAP\DDLDB6.TPL' template file is successfully completed.

Primary key creation: before load.

Index creation: before load.

INFO: 2011-09-17 16:55:32

Data codepage 4102 is determined using TOC file 'C:\SAPCD\sanexport\ABAP\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.

INFO: 2011-09-17 16:55:33

Version table 'SVERS' is found in STR file 'C:\SAPCD\sanexport\ABAP\DATA\SAPSDIC.STR' from package 'SAPSDIC'.

INFO: 2011-09-17 16:55:33

Data conversion tables 'DDNTF,DDNTF_CONV_UC,DDNTT,DDNTT_CONV_UC' are found in STR file 'C:\SAPCD\sanexport\ABAP\DATA\SAPSDIC.STR' from package 'SAPSDIC'.

TRACE: 2011-09-17 16:55:33 com.sap.inst.migmon.LoadTask run

Loading of 'SAPSSEXC' import package is started.

TRACE: 2011-09-17 16:55:33 com.sap.inst.migmon.LoadTask processPackage

Loading of 'SAPSSEXC' import package into database:

D:\usr\sap\HCD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -k 1g1gDEM50Dd01eqtdAM11A96 -l SAPSSEXC.log -stop_on_error -loadprocedure fast LOAD

ERROR: 2011-09-17 18:27:26 com.sap.inst.migmon.LoadTask run

Loading of 'SAPSSEXC' import package is interrupted with R3load error.

Process 'D:\usr\sap\HCD\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -k 1g1gDEM50Dd01eqtdAM11A96 -l SAPSSEXC.log -stop_on_error -loadprocedure fast LOAD' exited with return code 2.

For mode details see 'SAPSSEXC.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: 2011-09-17 18:27:32

Cannot start import of packages with views because not all import packages with tables are loaded successfully.

WARNING: 2011-09-17 18:27:32

1 error(s) during processing of packages.

INFO: 2011-09-17 18:27:32

Import Monitor is stopped.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Sep 18, 2011 at 06:33 PM

    Hi Sudipta,

    Did you check SAPSSEXC.log yet ? May be we can find something specific there.

    And at the same time, I hope you are using latest kernel (modified kernel dvd - latest R3load etc.).

    Note 1480785 - Creating a Modified Windows Kernel DVD

    Thanks

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 19, 2011 at 10:53 AM

    Hi,

    You can try a simple solution...

    1. Just stop SAP Installation.

    2. De-activate DB2 database

    3. Stop DB2

    4. Start DB2

    5. Activate Database

    6. Restart SAP installation with "Continue Old Installation" option.

    Regards.

    Rajesh Narkhede

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      "SQL1224N The database manager is not able to accept new requests, has terminated all requests in progress, or has terminated the specified request because of an error or a forced interrupt. SQLSTATE=55032 "

      you should start by looking what happened to you DB.

      db2diag.log