- SAP Community
- Products and Technology
- Additional Q&A
- Installation ECC 6.00 failing by Importing ABAP (e...
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Installation ECC 6.00 failing by Importing ABAP (every attempt)
- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 08-06-2016 5:11 PM
Hello experts,
I have trouble by installing an ECC 6.00 EHP 8 om Max DB.
These are the Errors I receive very installrun I try. They are just the same every attempt.
I try to use the "R3load -merge_bck" -> prompt an "parameter" is missing; but whitch?
the "R3load -merge_only SAPSSEXC.TSK works, but doesn´ t help.
-> So may I ask for help?
These are the errors from import monitor (the details of the logs are below):
1)
ERROR: 2016-08-06 14:56:13 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process '/usr/sap/R3A/SYS/exe/uc/linuxx86_64/R3load -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -nolog -c 50000 -force_repeat -para_cnt 96 -decluster' exited with return code 139.
For mode details see 'SAPSSEXC.log' file.
2)
ERROR: 2016-08-06 14:53:54 com.sap.inst.migmon.LoadTask run
Loading of 'DOKCLU' import package is interrupted with R3load error.
Process '/usr/sap/R3A/SYS/exe/uc/linuxx86_64/R3load -i DOKCLU.cmd -dbcodepage 4103 -l DOKCLU.log -nolog -c 50000 -force_repeat -para_cnt 96 -decluster' exited with return code 139.
For mode details see 'DOKCLU.log' file.
3)
Loading of 'SAPCLUST' import package is interrupted with R3load error.
Process '/usr/sap/R3A/SYS/exe/uc/linuxx86_64/R3load -i SAPCLUST.cmd -dbcodepage 4103 -l SAPCLUST.log -nolog -c 50000 -force_repeat -para_cnt 96 -decluster' exited with return code 139.
For mode details see 'SAPCLUST.log' file.
4)
Loading of 'SAPAPPL1' import package is interrupted with R3load error.
Process '/usr/sap/R3A/SYS/exe/uc/linuxx86_64/R3load -i SAPAPPL1.cmd -dbcodepage 4103 -l SAPAPPL1.log -nolog -c 50000 -force_repeat -para_cnt 96 -decluster' exited with return code 2.
For mode details see 'SAPAPPL1.log' file.
The details of the logs:
1) SAPSSEXC.log
-> no error: lines to find.
-> These are the last lines of the log:
(DB) INFO: loading data in table "DDFIELDANNO" with fastloader #20160806145542
(IMP) INFO: starting import for object "DDFIELDANNO" of type "table" #20160806145542
------------------ C-STACK ----------------------
R3load[S](LinStackBacktrace+0x8c)[0x42980d]
R3load[S](LinStack+0x35)[0x65df95]
R3load[S](CTrcStack2+0x4e)[0x4296a1]
R3load[S](SigIGenAction+0x53c)[0x4db50b]
<signal handler called> [0x7fd9736ce870]
libSDBLoader77.so(Loader_PageBuilder::buildKey(unsigned int*&, int&, int&)+0x75)[0x7fd974196135]
libSDBLoader77.so(Loader_PageBuilder::buildRecord()+0x177)[0x7fd974196697]
libSDBLoader77.so(Loader_PageBuilder::AddData(LOADER_Parameter*)+0x42a)[0x7fd974198e2a]
libSDBLoader77.so(Loader_FastloadCommand::Execute()+0x140)[0x7fd974193b60]
R3ldfldsdbsh.so[S](CSdbFastLoader::executeStmt(bool)+0x5a)[0x7fd96fa3481a]
R3ldfldsdbsh.so[S](CSdbFastLoader::executeFastLoader(DBSL_DA*)+0x8a)[0x7fd96fa37d4a]
R3ldfldsdbsh.so[S](adaExeFastload+0x19)[0x7fd96fa33a89]
R3load[S](ExeDBInsert+0x8b)[0x51673b]
R3load[S](import+0x15aa)[0x517dda]
R3load[S](main_r3ldmain+0x1239)[0x5019b9]
libc.so.6[S](__libc_start_main+0xf5)[0x7fd973338b25]
-------------------------------------------------
2) DOKCLU.log
(DB) INFO: connected to DB
(DB) INFO: The MaxDB logwriter is switched off#20160806144833
(DB) INFO: Maxdb Kernel version 7.9.08.023
SQLDBC 7.9.8.023
(DB) INFO: Loading Data with MaxDB Fastloader Api
(DB) INFO: SDBLoader 7.9.8 .
(DCL) INFO: found logical cluster description for DOKCLU in /tmp/1-OrigInstFiles/ECC618/51050708/DATA_UNITS/EXPORT_11/DATA/SAPDOKCLU.STR.logical
(IMP) INFO: starting create for object "DOKCLU" of type "table" #20160806144833
(DB) INFO: DOKCLU created#20160806144833
(DB) INFO: DOKTL created#20160806144833
(IMP) INFO: finished create for object "DOKCLU" of type "table" in 0 sec #20160806144833
(DCL) INFO: found logical cluster description for DOKCLU in /tmp/1-OrigInstFiles/ECC618/51050708/DATA_UNITS/EXPORT_11/DATA/SAPDOKCLU.STR.logical
(IMP) INFO: starting create for object "DOKCLU~0" of type "primary index" #20160806144833
(DB) INFO: DOKCLU~0 created#20160806144833
(DB) INFO: DOKTL~0 created#20160806144833
(IMP) INFO: finished create for object "DOKCLU~0" of type "primary index" in 0 sec #20160806144833
(DCL) INFO: found logical cluster description for DOKCLU in /tmp/1-OrigInstFiles/ECC618/51050708/DATA_UNITS/EXPORT_11/DATA/SAPDOKCLU.STR.logical
(DB) INFO: loading data in table "DOKCLU" with fastloader #20160806144833
(IMP) INFO: starting import for object "DOKCLU" of type "table" #20160806144833
adaExeFastload (executeFastLoader): -25011:Error executing internal SQL statement 'send packet': 'SQL error -8000 = ä•“å™’å‰…ä‰„æ´ çµâ´æ•¢çˆ ç¥æ…´ç‘²æ‘¥'.
(IMP) ERROR: ExeFastload: rc = 2
(DB) INFO: Savepoint on database executed#20160806145354
------------------ C-STACK ----------------------
-> 'SQL error -8000 = ... the funny characters are in the log - line also.
3) SAPCLUST
(IMP) INFO: starting import for object "SFHOA" of type "table" #20160806144838
adaEndFastload (endFastLoader): -25011:Error executing internal SQL statement 'send packet': 'SQL error -8000 = ä•“å™’å‰…ä‰„æ´ çµâ´æ•¢çˆ ç¥æ…´ç‘²æ‘¥'.
(IMP) ERROR: EndFastload: rc = 2
-> 'SQL error -8000 = ... the funny characters are in the log - line also.
4) SAPAPPL1
(IMP) INFO: starting create for object "DEMO_GTT" of type "global temporary table" #20160806145511
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" #20160806145511
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" #20160806145511
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" #20160806145511
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
(IMP) INFO: starting create for object "DF50L" of type "table" #20160806145511
(IMP) INFO: finished create for object "SATC_CI_EX_CHLOG~O" of type "index" in 0 sec #20160806150341
(IMP) INFO: starting create for object "SATC_CI_GTT_CNTC" of type "global temporary table" #20160806150341
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_SATC_CI_GTT_CNTC" ( "$ada_session_id" CHAR (6) BYTE not null default TRANSACTION,"PGMID" VARCHAR2(4) UNICODE DEFAULT ' ' NOT NULL , "OBJ_TYPE" VARCHAR2(4) UNICODE DEFAULT ' ' NOT NULL , "OBJ_NAME" VARCHAR2(40) UNICODE DEFAULT ' ' NOT NULL , "SYSTEM_GROUP" VARCHAR2(10) UNICODE DEFAULT ' ' 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 "SATC_CI_GTT_CNTC~0" of type "primary index" #20160806150341
ERROR exec_ddl_stmt: (DB) ERROR: DDL statement failed
(ALTER TABLE "$TMP_SATC_CI_GTT_CNTC" ADD PRIMARY KEY ( "$ada_session_id","PGMID", "OBJ_TYPE", "OBJ_NAME", "SYSTEM_GROUP" ) )
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
POS(14) Unknown table name:$TMP_SATC_CI_GTT_CNTC
(IMP) INFO: starting create for object "SATC_CI_GTT_OBJ" of type "global temporary table" #20160806150341
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_SATC_CI_GTT_OBJ" ( "$ada_session_id" CHAR (6) BYTE not null default TRANSACTION,"PGMID" VARCHAR2(4) UNICODE DEFAULT ' ' NOT NULL , "OBJ_TYPE" VARCHAR2(4) UNICODE DEFAULT ' ' NOT NULL , "OBJ_NAME" VARCHAR2(40) UNICODE DEFAULT ' ' NOT NULL , "SYSTEM_GROUP" VARCHAR2(10) UNICODE DEFAULT ' ' NOT NULL ) NO FIXED LENGTH COLUMN )
DbSlExecute: rc = 99
(SQL error -5004)
error message returned by DbSl:
POS(88) Missing constant
(IMP) INFO: starting create for object "SATC_CI_GTT_OBJ~0" of type "primary index" #20160806150341
ERROR exec_ddl_stmt: (DB) ERROR: DDL statement failed
(ALTER TABLE "$TMP_SATC_CI_GTT_OBJ" ADD PRIMARY KEY ( "$ada_session_id","PGMID", "OBJ_TYPE", "OBJ_NAME", "SYSTEM_GROUP" ) )
DbSlExecute: rc = 103
(SQL error -942)
error message returned by DbSl:
POS(14) Unknown table name:$TMP_SATC_CI_GTT_OBJ
Accepted Solutions (1)
Accepted Solutions (1)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Update:
After changing the MaxDB Version to 7.9. SP 6 Build 35 the Installation run without Errors.
Well I have to admit that my evaluation of teh cause of the error was not correct.
The solution is: please use the mentioned MaxDB Version Build 35.
Best regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
I can confirm that information.
With patching the database (MaxDB) to the highest available patch level (7.9.08.40) when the error occured we could finish the installation (with some other more or less anoying errors). We also patched R3load which seems to be helpfull with one of the other problems we had after we pacthed the database.
Kind Regards
Answers (5)
Answers (5)
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Good morning,
just an status update.
We tried serveral attempts, but the same results.
I read the announced post (Installation Netweaver 7.5 - Import ABAP issue). I think the MaxDB there is a few minor versions newer than mine (7.9.08.30 vs. 7.9.08.023). But I doubt that the MaxDB cause the error.
I will download the 4 ERP 6.0 EHP 8 files again. Maybe there is a bug in the compressed files, which is the cause of installing faults.
Best regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi,
What is your Database release and patch level ? Did you try updating your database to current available patch level ?
Refer below thread for similar issue:
Installation Netweaver 7.5 - Import ABAP issue | SCN
Thanks
Rajesh Narkhede
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hi!
Could you please give the full name of kernel files you are trying to use?
Also - did you choose option to decluster database tables in SWPM?
Best regards
Bartosz
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Thanks.
I just run into the same issue. I was using kernel:
SAPEXE_201-80000854
SAPEXEDB_201-80000851
After the error I restarted the install and changed kernel to:
SAPEXE_201-80000796
SAPEXEDB_201-80000793
I also selected the option to not decluster database tables (previously was switched to decluster).
In my case it helped. No issues with import abap.
Best regards
Bartosz
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Good morning,
by reading your commends, I think, you suppose that the error is located in the kernel files.
- But isn´t it loading / filling tables before successfully?
The error is like “loading data in table "DOKCLU" “ and may I suggest a kernel error will prevent any loading activity of any tables. - Or get I wrong?
My SWPM 10 runs and the MaxDB also. But the loading or building tables goes wrong. So it may be a mismatch in one of the 11 ECC 6.00 Files?
Best Regards
Claas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Claas,
The error happens while loading data from the Installation Export files. To load the data into the database R3load is used.
You aleady posted extracts from import_monitor.log. In, for instance the DOKCLU.log file we find
(ADA) INFO: Loading data in table "DOKCLU" with fastloader #20160816091649
(IMP) INFO: Starting import for object "DOKCLU" of type "table" #20160816091649
(ADA) INFO: DOKCLU deleted/truncated#20160816091649
(ADA) INFO: DOKTL deleted/truncated#20160816091649
(SDB) ERROR: adaExeFastload (executeFastLoader): -25011:Error executing internal SQL statement 'send packet': 'SQL error -8000 = ä<9><93>å<99><92>å<89><85>ä<89><84>æ´ ç<8d>µâ<81>´æ<95>¢ç<88> ç<8d>¥æ<85>´ç<91>²æ<91>¥'.
(IMP) ERROR: ExeFastload: rc = 2
(IMP) ERROR: ExeFastload: rc = 2
So, it is possible that the Import Data is corrupt. We tried to run the import with different Versions of R3load so, if the error is not still there after various updates/ patches of the kernel components, you might be right and we can exclude the kernel parts as source for the problem.
SWPM is calling kernel components to do the job so SWPM might also not be the problem. Which brings it down to errors in the Import data.
Reagan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Replace the kernel set completely and restart the installation.
Also update the MaxDB database patch level to the latest version.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Hello Benjamin,
my I ask witch kernel files I have to Change?
I use the SWPM 10 files. In the SAP download area there was a link to the kernel files.
In the MaxDB I have to choose between two files U_kernel or N_kernel versions.
To be honest, I don´t know the correct file combination ECC600 + MaxDB on Linux for an initial installation.
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Reagan
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
Dear Reagan,
thank you for the hint. That´s what wetried yesterday.
I stopped SWPM, patched the kernel with the last available versions of SAPEXE, SAPEXEDB, R3trans and R3load.
The behaviour and the result/ error are still the same. For me it looks like a kernel pacth, at least with the at the moment available patches, is not the solution.
Kind Regards
Jan
For disp+work for example it now lokks like this:
./disp+work -V | head -n 30
Tue Aug 16 07:54:39 2016
Loading DB library '/usr/sap/<SID>/SYS/exe/run/dbsdbslib.so' ...
Library '/usr/sap/<SID>/SYS/exe/run/dbsdbslib.so' loaded
Version of '/usr/sap/<SID>/SYS/exe/run/dbsdbslib.so' is "745.04", patchlevel (0.201)
--------------------
disp+work information
--------------------
kernel release 745
kernel make variant 745_REL
DBMS client library MAXDB_798_b31
DBSL shared library version 745.04
compiled on Linux GNU SLES-11 x86_64 cc4.3.4 use-pr160709 for linuxx86_64
compiled for 64 BIT
compilation mode UNICODE
compile time Jul 11 2016 11:13:39
update level 0
patch number 201
source id 0.201
RKS compatibility level 0
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Report Inappropriate Content
- Explore Business Continuity Options for SAP workload using AWS Elastic DisasterRecoveryService (DRS) in Technology Blogs by Members
- Harnessing the Power of SAP HANA Cloud Vector Engine for Context-Aware LLM Architecture in Technology Blogs by SAP
- SAP Datasphere - Space, Data Integration, and Data Modeling Best Practices in Technology Blogs by SAP
- Issues with Property Naming Conventions in Service Consumption Model Leading to Filter Errors in Technology Q&A
- Define a CHECKBOX and CHECKBOX_HOTSPOT In The Same ALV Report in Technology Blogs by Members
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.