Hi All,
I am facing error in delivery sending; Cannot insert duplicate key row in object in neolaneprod.elcbroadlogdcns with unique index id
upon checking i identified this same duplicate broadlog id is present for one the delivery sent in 2013
here elcbroadlogdcns is custom table same as broadlogrcp keep broadlog enteriescan someone please help me with quick resolution for this??
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi Shrutii,
Typically duplicate keys occur when the sequence in the table is close or has run out of available IDs within its 32bit sequence. To address this, there are a few best practices:
1) Ensure that in the Deployment wizard that you are keeping only the minimum required logs (see the purge settings in deployment wizard) as long log retention uses up available IDs.
2) Ensure that the Database Cleanup workflow is running fully as that workflow is in charge of purging logs and old deliveries, etc. noted in step 1.
3) Ensure that tables are using custom sequences versus the out of the box xtkNewID. This was one of the biggest causes of this issue, as in older versions of Campaign the tables all shared the same sequence, meaning that the number of available IDs would run out very quickly.
4) If none of the above works, you can consider deploying negative IDs which effectively doubles the amount of available IDs for any given sequence.
This type of error has been covered multiple times within the forums and in Campaign Support if you need additional details and assistance. See below:
https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-questions/error-duplicate-ke...
Regards,
Craig
Hi @Shrutii ,
Restart your workflow, mostly this error will get fixed.
And, to troubleshoot further, go to Tools > Advanced > Deployment wizard > Next > Purge Data
Check how many days has been specified for delivery logs.
By default it will be 180 days. When it is set to 180 days, 6 months old record will get deleted from cleanup workflow. If the primary key sequence for broad Log schema exhaust, it will again start from beginning. If the delivery log value has been modified in your instance to store delivery logs more than 180 days (Not recommended though...), then you might get this error.
Hi Shrutii,
Typically duplicate keys occur when the sequence in the table is close or has run out of available IDs within its 32bit sequence. To address this, there are a few best practices:
1) Ensure that in the Deployment wizard that you are keeping only the minimum required logs (see the purge settings in deployment wizard) as long log retention uses up available IDs.
2) Ensure that the Database Cleanup workflow is running fully as that workflow is in charge of purging logs and old deliveries, etc. noted in step 1.
3) Ensure that tables are using custom sequences versus the out of the box xtkNewID. This was one of the biggest causes of this issue, as in older versions of Campaign the tables all shared the same sequence, meaning that the number of available IDs would run out very quickly.
4) If none of the above works, you can consider deploying negative IDs which effectively doubles the amount of available IDs for any given sequence.
This type of error has been covered multiple times within the forums and in Campaign Support if you need additional details and assistance. See below:
https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-questions/error-duplicate-ke...
Regards,
Craig
please tell me where and how we can change the sequence
please help to share screenshot if poosible
reaally looking for quick response as this is impacting the prod
Views
Replies
Total Likes
4) If none of the above works, you can consider deploying negative IDs which effectively doubles the amount of available IDs for any given sequence.
how and where we can do this
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies