Let's see, who's faster: SAP Support or SAP Community ;-)
------------------------------------------------------------------------------------
During the installation step "Import ABAP" I'm getting an DB error " exec_ddl_stmt_ada failed" on around 16 DB tables (SAPAPPL1 and SAPSDIC)
Extract of the relevant log files:
Import_monitor.log
ERROR: 2017-11-19 14:38:47 com.sap.inst.migmon.LoadTask run
Loading of 'SAPAPPL1' import package is interrupted with R3load error.
Process '/tmp/sapinst_instdir/NW752/ADA/INSTALL/STD/ABAP/R3load -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.
…
ERROR: 2017-11-19 14:47:46 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSDIC' import package is interrupted with R3load error.
Process '/tmp/sapinst_instdir/NW752/ADA/INSTALL/STD/ABAP/R3load -i SAPSDIC.cmd -dbcodepage 4103 -l SAPSDIC.log -nolog -c 50000 -force_repeat -para_cnt 2 -decluster' exited with return code 2.
For mode details see 'SAPSDIC.log' file.
SAPAPPL1.log
(IMP) INFO: Starting create for object "DEMO_CHESS_CM_T" of type "global temporary table" #20171119143630
(IMP) ERROR: Task failed with error: (ADA) exec_ddl_stmt_ada failed for 'CREATE GLOBAL TEMPORARY TABLE "DEMO_CHESS_CM_T" ("CLIENT" VARCHAR2(3) UNICODE DEFAULT '000' NOT NULL, "CHESSMAN" VARCHAR2(1) UNICODE DEFAULT ' ' NOT NULL, PRIMARY KEY("CLIENT", "CHESSMAN")) ON COMMIT DELETE ROWS'
(IMP) ERROR: (ADA) DbSlErrorMsg rc = 0 'everything went well'
(IMP) ERROR: (ADA) POS(8) Missing keyword:TABLESPACE,ROLLBACK,PUBLIC,VIEW,USER,TRIGGER,TABLE,SYNONYM,SEQUENCE,SCHEMA,ROLE,PROCEDURE,PACKAGE,INDEX ...
(IMP) ERROR: Finished create for object "DEMO_CHESS_CM_T" of type "global temporary table" with error in 0 sec #20171119143630
The errors for the other failed DB tables look the same.
This used template in DDLADA.TPL seems to be new in 7.52:
cretabtmp: CREATE GLOBAL TEMPORARY TABLE &tab_name&(/{&fld_name& &fld_desc&, /} PRIMARY KEY(/{&key_fld&/-, /}))ON COMMIT DELETE ROWS
Is it possible that this statement doesn't work on MaxDB?
Cheers, Uwe
Add comment