Row with ibroadlogid of 0 in broadlog tables | Community
Skip to main content
New Member
June 6, 2023
Solved

Row with ibroadlogid of 0 in broadlog tables

  • June 6, 2023
  • 2 replies
  • 1204 views

I've been noticing in the broad logs, tracking logs and exclude logs in our database that we have a single row with broad log id of 0 and all other fields blank.

Our data analytics team was asking why this is the case. Is this something Adobe campaign generates by default for some reason?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Craig_Thonis

Hi Terrence,

 

So an ID of 0 or "zero record" gets automatically created when links are established with other tables. So this would make sense as the broadlog, tracking, and exclusion all have links to other tables.

Please be sure to keep the records. If, for some reason, they do get deleted, the solution below can address it.

 

https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-16945.html?lang=en

 

2 replies

Craig_Thonis
Adobe Employee
Craig_ThonisAdobe EmployeeAccepted solution
Adobe Employee
June 7, 2023

Hi Terrence,

 

So an ID of 0 or "zero record" gets automatically created when links are established with other tables. So this would make sense as the broadlog, tracking, and exclusion all have links to other tables.

Please be sure to keep the records. If, for some reason, they do get deleted, the solution below can address it.

 

https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-16945.html?lang=en

 

LakshmiPravallika
Community Advisor
Community Advisor
June 9, 2023

Hi @terrenceszeto ,

 

It may depend on the database which you are currently using in ACM. In PostgreSQL Database when checked for broadLog and trackingLog and even for other Custom Schemas also, the Primary key having value as "0" do not exist in our Database.

 

If the zero record is required during Upgrades as per your db setup, please put it the same.

 

Regards,

Pravallika.

Adobe Employee
June 9, 2023

Hi @terrence_szeto 

This is expected and you shouldn't remove these records as you might end up in situation where you won't be able to load an entity record because of link to these logs schema containing 0... I also depends on the way links to broadlog and tracking logs are created: 1-1 or 0-1. If a link is created as 1-1 and you've got a 0 in the FK, it will fail to load the record because 0 record won't exist in the referenced entity...

In a way, it's a very classic data modelling principle that allow flexibility without failure

Thanks
Denis