Duplicate table getting created after CMDB query run.

Shraddha Dube
Tera Contributor

Hi,

 

There is one scenario in which CMDB team created two tables and according to them one is original and one is duplicate with different table name and same label name.

 

according to CMDB team after daily query run, records used to get stored in original table which was created on 22nd May 2022 but now from last 1 month after query run records are getting stored in duplicate table like live data is now storing in duplicate table instead of Original.

 

When we tried to delete duplicate table and ran query, duplicate table again getting created  with same table name and again records are getting stored in that duplicate table.

 

Please help me to understand why duplicate table is getting generated again and again even after delete and how can we resolve this issue so records will get stored again in original table after query run.

 

Thank you in advance!!  

6 REPLIES 6

Mark Manders
Mega Patron

These are created from the Query Builder. You will need to check on the conditions set in there and also check on what changed '1 month' ago. Did someone update it and selected the wrong one?


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Hi @Mark Manders ,

 

As we analyzed, it appears that the 'Run As' field name was changed to another user name as original user is not part of organization anymore, and since then, duplicate tables have started getting created.

 

We need to identify how this change is triggering the duplication and implement a solution to prevent further duplicate table creation

 

Thanks,

Shraddha

Can't you just set the 'run as' as system user and be done with it? Then you will never have this issue again.


Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark

Hi @Mark Manders ,

 

No we can't use set the 'run as' field to system user. We have to set another user name only. Can you please is this existing behavior and if yes how can we resolve this issue as this issue affecting 60+ reports due to changing run as field.

 

Thanks,

Shraddha