Non-concurrent import sets creating duplicate CMDB Integration Execution (CEX) records - Support and Troubleshooting

Non-concurrent import sets creating duplicate CMDB Integration Execution (CEX) records .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Description Non-concurrent imports are still creating two CMDB Integration Executions every time they run.

The duplicate executions: 1. Have no import set nor concurrent import set 2. Are all stuck in a loading state 3. Appear to be associated with a scheduled import 4. Are created prior to the execution that is associated with an import set.

This does not affect the import itself — data is imported correctly. The issue is limited to tracking and reporting within the CMDB Integration Execution list.

Steps to Reproduce

Did/Could not reproduce oob.

Customer is in Zurich Patch 6 Hot Fix 2 Integration Commons for CMDB to Version: 2.23.2

1. Open the scheduled Data import 2. Click on the "Execute now" , button 3. From the "Executions" related list, open the latest Import Set created and wait until the state go to "Processed" 4. In the Import Set record, check in the related list Import Set Runs" that the status is "completed" 5. Open the "CMDB Integration Executions" list and search for records (filtered by Application). /sn_cmdb_int_util_cmdb_integration_execution_list.do

* 2 records starting at the same time; one is in State Completed, the second is in state Loading. * The Completed execution has a number much lower than the one Loading * The duration calculated for the Completed records is not equal "End Time" minus "Start Time"

Workaround

Duplicate execution records can be safely identified and removed manually using the following filter on the

sn_cmdb_int_util_cmdb_integration_execution table:

query:- state=loading^import_set.number=NULL^concurrent_import_set.number=NULL

Review the results before deleting to confirm they match the pattern described above.

Resolution

A fix is targeted for Integration Commons for CMDB v2.26. The fix ensures that the execution record created at scheduled

import start time is correctly linked to the import set when processing completes, rather than creating a second record.