Skip to Content
Mar 23, 2021 at 08:30 AM


579 Views Last edit Mar 23, 2021 at 08:31 AM 2 rev

Hello all,

we try to upgrade our EHP5 to EHP8 (7.02 -> 7.50).

We get the following error in phase MAIN_INIT/JOB_RDDTAXIT_JOB:


Checks after phase MAIN_INIT/JOB_RDDTAXIT_PRE were negative!

Last error code set:<br>Batchjob 'RDDTAXIT' with id '08565200' is aborted


Unfortunately there are no helpful details in the logs and we can't find a note regarding this.

This is the content of the Job-Dump:

************************** Batch Job Info ***************************

Batch Job Name RDDTAXIT Batch Job ID 08565200 Batch Job Work Process ID 20 Batch Job Host Name xxxxxxx_xxx_00 Batch Job Status A Batch Job Started by User DDIC Batch Job End Date 20210323 Batch Job End Time 085653

************************** Batch Job Log ****************************

20210323 085652 Job started 20210323 085652 Step 001 started (program RDDTAXIT, variant , user ID DDIC) 20210323 085653 Internal session terminated with a runtime error (see ST22) 20210323 085653 Job cancelled

*************************** System Log ******************************

Instance xxxxxxx_xxx_00 Work Process ID 020 Work Process Type BTC Client 000 User Name DDIC Date 23.03.2021 Time 08:56:53

Severity Icon @5C\QVery High Priority@ Message Text Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred

Severity Icon @SR\QInformation@ Message Text > Short dump "210323 085653 xxxxxxx_xxx_00 DDIC " created.

Severity Icon @5C\QVery High Priority@ Message Text Transaction Canceled 00 671 ( SAPSQL_ARRAY_INSERT_DUPREC 20210323085653xxxxxxx_xxx_00 DDIC 000 )

************************** ABAP Dump Content ************************

ABAP Short Dump Header Data --------------------------- Short Dump Category: ABAP Programming Error Runtime Error: SAPSQL_ARRAY_INSERT_DUPREC ABAP Program: PROG RDDTAXIT ABAP Main Program: RDDTAXIT ABAP Package: SAUS_UPG Software Component: SAP_BASIS Application Component: BC-UPG-TLS-TLA Upgrade Tools for ABAP

Where did the dump occur ------------------------ Frame Program: RDDTAXIT ABAP Program: RDDTAXIT ABAP Include: RDDTAXIT Line Number: 386 Additional Info: MAIN

Short text ---------- The ABAP/4 Open SQL array insert results in duplicate database records. records in the data base.

What happened? -------------- Error in the ABAP Application Program

The current ABAP program "RDDTAXIT" had to be terminated because it has come across a statement that unfortunately cannot be executed.

What can you do? ---------------- Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look at and manage termination messages, and you can also keep them for a long time.

Error analysis -------------- An exception occurred that is explained in detail below. The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught in procedure "MAIN" "(FORM)", nor was it propagated by a RAISING clause. Since the caller of the procedure could not have anticipated that the exception would occur, the current program is terminated. The reason for the exception is:If you use an ABAP/4 Open SQL array insert to insert a record in the database and that record already exists with the same key, this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error situation, processing does not terminate, but SY-SUBRC is set to 4.)

How to correct the error ------------------------ Use an ABAP/4 Open SQL array insert only if you are sure that none of the records passed already exists in the database.

If the error occures in a non-modified SAP program, you may be able to find an interim solution in an SAP Note. If you have access to SAP Notes, carry out a search with the following keywords:


If you cannot solve the problem yourself and want to send an error notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File (Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21. Restrict the time interval to 10 minutes before and five minutes after the short dump. Then choose "System->List->Save->Local File (Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP program: The source code of the program In the editor, choose "Utilities->More Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which actions and input led to the error. The exception must either be prevented, caught within proedure "MAIN" "(FORM)", or its possible occurrence must be declared in the RAISING clause of the procedure. To prevent the exception, note the following:

System environment ------------------ SAP Release..... 702 SAP Basis Level. 0022

Application server... "xxxxxxxx" Network address...... "xx.xx.xx.xx" Operating system..... "Linux" Release.............. "4.12.14-122.51-defau" Hardware type........ "x86_64" Character length.... 16 Bits Pointer length....... 64 Bits Work process number.. 20 Shortdump setting.... "full"

Database server... "xxxxxxx" Database type..... "ORACLE" Database name..... "xxx" Database user ID.. "SAPSR3"

Terminal.......... "???"

Char.set.... "C"

SAP kernel....... 722 created (date)... "Jun 7 2020 15:44:10" create on........ "Linux GNU SLES-11 x86_64 cc4.3.4 use-pr190909" Database version. "OCI_112,, V2, default"

Patch level. 1000 Patch text.. "???"

Database............. "ORACLE 10.2.0.*.*, ORACLE 11.2.*.*.*, ORACLE 12.*.*.*.*" SAP database version. 722 Operating system..... "Linux"

Memory consumption Roll.... 1629248 EM...... 0 Heap.... 0 Page.... 24576 MM Used. 1575848 MM Free. 31936

User and Transaction -------------------- Client.............. 000 User................ "DDIC" Language key........ "E" Transaction......... Transaction ID...... "605963E19F446E8FE10000000AF50024"

EPP Whole Context ID.... 36303533334138363630353333413836 EPP Connection ID....... 36303539394634343630353939463434 EPP Caller Counter...... 1

Program............. "RDDTAXIT" Screen.............. "SAPMSSY0 1000" Screen Line......... 6 Debugger Active..... "none"

Information on where terminated ------------------------------- Termination occurred in the ABAP program "RDDTAXIT" - in "MAIN". The main program was "RDDTAXIT".

In the source code you have the termination point in line 386 of the (Include) program "RDDTAXIT". The program "RDDTAXIT" was started as a background job. Job Name....... "RDDTAXIT" Job Initiator.. "DDIC" Job Number..... 08565200 The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in procedure "MAIN" "(FORM)", but it was neither handled locally nor declared in the RAISING clause of its signature.

The procedure is in program "RDDTAXIT"; its source code begins in line 93 of the (Include program "RDDTAXIT".

Internal notes -------------- The termination was triggered in function "ab_HandleRsqlErrors" of the SAP kernel, in line 724 of the module "//bas/722_STACK/src/krn/runt/absapsql.c#3". The internal operation just processed is "SQLS". Internal mode was started at 20210323085652.

Active Calls in SAP Kernel -------------------------- Lines of C Stack in Kernel (Structure Differs on Each Platform) (LinStack+0x33)[0x1634403] (CTrcStack2+0x48)[0x603a20] (_ZL16rabax_CStackSavev+0x91)[0x788f51] (ab_rabax+0x27e0)[0x1786610] (_Z19ab_HandleRsqlErrorsR5Jsqls9RsqlError9CloseMode+0x22d)[0x7b6331] (_ZL15SqlsExecuteCallhR5Jsqls+0xbe5)[0x7b8bee] (_Z8ab_jsqlsv+0x1b1c)[0x7ba746] (_Z8ab_extriv+0x59e)[0x17b96ce] (_Z9ab_xeventPKDs+0x32)[0x17f2d62] (_Z8ab_triggv+0x4c)[0x176a78c] (ab_run+0x10c)[0x179091c] (dynpmcal+0x57b)[0x166ce5b] (dynppai0+0x103)[0x166d683] (dynprctl+0x3fa)[0x167344a] (dynpen00+0x4c1)[0x1662be1] (TskhLoop+0x1437)[0x15d34d7] (ThStart+0x2c2)[0x4b7f17] (DpMain+0x3b3)[0x157ad53] /lib64/[0x7f9c4f239a35]

Any suggestions how we can find more details?
As far as i understand the job tries to insert a value that is already in the DB. But which one?

Kind regards