Run-time error SAPSQL_ARRAY_INSERT_DUPREC occurred

Question

When creating a new SyncBo (T51) instance after syncing eventually MI Clients shows the following message:
[20070315 01:28:14:343] E [MI/Sync ] Received exception info code 10 and detailed message "Exception while callSync: The ABAP/4 Open SQL arrayinsert results in duplicate database records. records in the data base."
In sm21 shows message:
AB0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred
AB1 > Short dump "070316 205056 sapnw ELDA " generated
Looking for SAPSQL_ARRAY_INSERT_DUPREC error in SAP Note we found the note 817849 (Runtime error SAPSQL_ARRAY_INSERT_DUPREC occurs during sync).
We have downloaded and applied this note in Backend as note requires and ALL prerequisites of this note. Also we have upgraded to SP19 and Kernel to 155 (part 1 and 2). But problem continues and the client that happened this problem does not work any more, all new SyncBO instances created goes to MEREP_MON as Waiting status.
The dump on duplicate record is happening when the user is synchronizing and when a record is getting inserted to table merep_10100.
The solution /workaround could be to do a client reset for those devicesand test again and see if it is happening, but error returns happening after this.
When this happen SyncBo instance keeps on Waiting status (MEREP_MON). We couldn't understand why this happen suddenly and then no more new SyncBo could be created, all goes to Waiting status. Reprocess (ShiftF5) or start handler (Shift10) does not take any effect.
Best Regards,
Rogério

Answer 1

Hi Ajith
I am getting the same error and below is the error message from ST22. The only change is I am using for MTR application and the sync fails for the 2nd time when synched for patches for the MTR application. As it is generic sync, could you please advice to get rid of the problem.
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
  neither
caught nor passed along using a RAISING clause, in the procedure
  "LOG_INSERT_DB" "(FORM)"
Since the caller of the procedure could not have expected this exception
  to occur, the running program was 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.)
Thanks, Raj