Expand my Community achievements bar.

Submissions are now open for the 2026 Adobe Experience Maker Awards

DB Cleanup Workflow Failing Due to Audit Log Error in ACC v7

Avatar

Level 1

Hi there,

I'm facing an issue with my db cleanup workflow—it keeps failing. In the audit log, I'm seeing the following error:

"There is more than one open type URL in the database ('NmsTrackingUrl' table). Most likely the problem comes from an improperly migrated database."

Has anyone encountered this before or know a possible solution?

Regards, Navin

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

2 Replies

Avatar

Employee Advisor

Hi Navin, 

So the way to track this down (if you are hosting your database and marketing server) is to run the following query. If Adobe is hosting your servers, submit a ticket to them to do the same: 

 

SELECT *

FROM NmsTrackingUrl

WHERE (iType = 2)

 

This should produce your Open-type URLs. There should only be 1 open in your system, which is the reason for the error. 

 

From there, identify the problematic URL (most likely the newest URL created) and delete it with a statement similar to the one below:

Delete FROM NmsTrackingUrl

WHERE (iType = 2)

AND itrackingurlid=[replace with ID];

 

Then restart your DB Cleanup workflow. That should correct the issue.

 

Regards,

Craig

Avatar

Level 4

Hi @NavinBamane ,

If you control the database (self-hosted):

Connect to your Campaign database directly

Run the following SQL to identify problematic entries:

SELECT * FROM NmsTrackingUrl WHERE iType = 2;
You should see more than one row—there should be only one, decide which record to keep.

Usually, the oldest or the one with the lowest itrackingurlid should be retained.

Delete the extra entries:

DELETE FROM NmsTrackingUrl WHERE iType = 2 AND itrackingurlid = [ID-to-delete];

Restart the database cleanup workflow in Adobe Campaign Classic.

 

If you are on the Adobe Cloud (managed by Adobe):

You cannot make DB changes directly.

Raise a support ticket and ask Adobe support to perform this cleanup for you, referencing the exact error.

 

Regards,

Abhinav