Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Installation Netweaver 7.5 - Import ABAP issue

Hi,

i try to install an SAP Netweaver 7.5 as distributed System to use it as SAP Gateway.

Application Server:

Win 2012 R2 x64

8GB RAM

CPU: 2

Database Server:

MaxDb 7.9

Win 2012 R2 x64

8GB RAM

CPU: 2

Software Provisioning Manager

Version 03 / 2016

After installing the central instance i got an Error by installation auf the database instance. The installation step "Import ABAP" aborted because two of import jobs failed.

Things i've tried to fix this issue:

  • Update SAP Kernel Files from SWDC (including R3Load etc.)
  • Redownload the Installation Export
  • Run the Installation of Database Instance with a new Installation Option

But there is still this error. I have also tried to install SAP ECC 6.0 EHP 8 based on Netweaver 7.5. I got the same Error at Import ABAP Step.

IMPORT_MONITOR.LOG

ERROR: 2016-04-08 11:22:46 com.sap.inst.migmon.LoadTask run

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

Process '\\sap-ae1\sapmnt\EG1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -nolog -c 50000 -force_repeat -para_cnt 2 -decluster' exited with return code -1.073.741.819.

For mode details see 'SAPSSEXC.log' file.

ERROR: 2016-04-08 11:24:29 com.sap.inst.migmon.LoadTask run

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

Process '\\sap-ae1\sapmnt\EG1\SYS\exe\uc\NTAMD64\R3load.exe -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -nolog -c 50000 -force_repeat -para_cnt 2 -decluster' exited with return code 2.

For mode details see 'SAPAPPL1.log' file.

SAPAPPL1.LOG

DbSl Trace:   execute(), rc=1, rcSQL=-5004

DbSl Trace: EXECUTE on connection 0, rc=-5004

ERROR exec_ddl_stmt: (DB) ERROR: DDL statement failed

(CREATE TABLE "$TMP_DEMO_GTT" ( "$ada_session_id" CHAR (6) BYTE not null default TRANSACTION,"ID" VARCHAR2(1) UNICODE DEFAULT ' ' NOT NULL , "COL" NUMBER(10) DEFAULT 0 NOT NULL  ) NO FIXED LENGTH COLUMN )

DbSlExecute: rc = 99

  (SQL error -5004)

  error message returned by DbSl:

POS(81) Missing constant

(IMP) INFO: starting create for object "DEMO_GTT~0" of type "primary index" #20160408112337

ERROR exec_ddl_stmt: (DB) ERROR: DDL statement failed

(ALTER TABLE "$TMP_DEMO_GTT" ADD PRIMARY KEY ( "$ada_session_id","ID" ) )

DbSlExecute: rc = 103

  (SQL error -942)

  error message returned by DbSl:

POS(14) Unknown table name:$TMP_DEMO_GTT

(IMP) INFO: starting create for object "DEMO_SFLIGHT_AGG" of type "global temporary table" #20160408112337

DbSl Trace:   execute(), rc=1, rcSQL=-5004

DbSl Trace: EXECUTE on connection 0, rc=-5004

ERROR exec_ddl_stmt: (DB) ERROR: DDL statement failed

(CREATE TABLE "$TMP_DEMO_SFLIGHT_AGG" ( "$ada_session_id" CHAR (6) BYTE not null default TRANSACTION,"MANDT" VARCHAR2(3) UNICODE DEFAULT '000' NOT NULL , "CARRID" VARCHAR2(3) UNICODE DEFAULT ' ' NOT NULL , "CONNID" VARCHAR2(4) UNICODE DEFAULT '0000' NOT NULL , "FLDATE" VARCHAR2(8) UNICODE DEFAULT '00000000' NOT NULL , "SEATSOCC" NUMBER(10) DEFAULT 0 NOT NULL  ) NO FIXED LENGTH COLUMN )

DbSlExecute: rc = 99

  (SQL error -5004)

  error message returned by DbSl:

POS(89) Missing constant

(IMP) INFO: starting create for object "DEMO_SFLIGHT_AGG~0" of type "primary index" #20160408112337

ERROR exec_ddl_stmt: (DB) ERROR: DDL statement failed

(ALTER TABLE "$TMP_DEMO_SFLIGHT_AGG" ADD PRIMARY KEY ( "$ada_session_id","MANDT", "CARRID", "CONNID", "FLDATE" ) )

DbSlExecute: rc = 103

  (SQL error -942)

  error message returned by DbSl:

POS(14) Unknown table name:$TMP_DEMO_SFLIGHT_AGG

SAPSSEXC.LOG

Last Lines of Log. There is no Error Statement in this LogFile.

(DB) INFO: DDFIELDANNO~0 created#20160408112245

(IMP) INFO: finished create for object "DDFIELDANNO~0" of type "primary index" in 0 sec #20160408112245

(DB) INFO: loading data in table "DDFIELDANNO" with fastloader #20160408112245

(IMP) INFO: starting import for object "DDFIELDANNO" of type "table" #20160408112245

Former Member
replied

Hi Martin,

I deleted the other (incomplete) discussion, I hope this was okay.

Concerning this issue, you could try to apply the latest 7.9 SAP MaxDB version (7.9.08.30 or higher) and continue with the import afterwards, as it seems that there has been an issue in older versions that has lead to a similar behavior in other cases.

Best regards,

Boris

0 View this answer in context
Not what you were looking for? View more on this topic or Ask a question