cancel
Showing results for 
Search instead for 
Did you mean: 

SAPSQL_ARRAY_INSERT_DUPREC - ABAP runtime error

Former Member
0 Kudos

Dear Experts,

I am getting a abap dump.

Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC

Exception CX_SY_OPEN_SQL_DB

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 "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", 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.

Information on where terminated

(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.)

Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in

"BAL_DB_INTERNAL_NO_UPDATE_TASK". The main program was "SWNCCOLL ".

In the source code you have the termination point in line 64

of the (Include) program "LSBAL_DB_INTERNALU02".

The program "SAPLSBAL_DB_INTERNAL" was started as a background job.

Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"

Job Initiator.. "SAPADMIN"

Job Number..... 16160100

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", but it was neither

handled locally nor declared

in the RAISING clause of its signature.

The procedure is in program "SAPLSBAL_DB_INTERNAL "; its source code begins in

line

1 of the (Include program "LSBAL_DB_INTERNALU02 ".

Please give me your suggestions to sort out this problem

Thanks in advance

Venkat

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Thank you Sebastian Pondi

Former Member
0 Kudos

Check note 196113 it contains the solution to your problem.

Most of the time this issue is due to a mismatch between the last assigned log number in table BALHDR and the one in the number range object.