Skip to main content
Solved

Execution log warning column already exists


Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+4

Hi all,

For one of my current client's we are rectrieving a warning while syncing the odx. The task is completed and we can transfer the data. but the warning is a bit odd.

We already tried to remove the folder from the data lake and try a full load. but this didn't fix the warning. Anyone any ideas?

Best answer by Christian Hauggaard

Hi @Bernarddb @daniel this issue has been fixed now, please see

  • 19429: Removed unnecessary warnings in the ODX when synchronizing OLE DB based data sources

in the product update:

 

View original
Did this topic help you find an answer to your question?

9 replies

Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi @Bernarddb 

Which data source are you using? Does the data source table/view have an Id column? Was this Id column at some point deleted and re-added?


Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+4
  • Author
  • TimeXtender Xpert
  • 53 replies
  • August 3, 2023

We are using a ADO data Source. with an SqLClient data provider. The table indeed has a the id field. As far as we are aware the supplier didn't change anything in the view. 


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

@Bernarddb  Which version of TimeXtender are you using?

Can you please share a screenshot of your data source settings similar to below?

Have you set up any primary keys or incremental load rules on the data source?


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Also could you please try to create a new data source and see if you get the same issue? If so can you please also test with the TimeXtender SQL data source?


Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+4
  • Author
  • TimeXtender Xpert
  • 53 replies
  • August 10, 2023

hereby the screenshot. Sorry for the slow reply 

We also tried it with the different connectors but still got the same result


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

@Bernarddb Thanks for the screenshot, can you please share the create statement for the view and create statement for the table which the view is based on in the source database? 


Bernarddb
TimeXtender Xpert
Forum|alt.badge.img+4
  • Author
  • TimeXtender Xpert
  • 53 replies
  • August 17, 2023

We don't have those script's since we are only supplied the table and view. But not the create statements. So i'm guessing we just have to live with the completed with warnings. Since it doesn't impact the transfer.


daniel
TimeXtender Xpert
Forum|alt.badge.img+7
  • TimeXtender Xpert
  • 188 replies
  • August 17, 2023

@Christian Hauggaard , I'm interesed in the reason why TX throughs an 'Warning'. What is the definition or ‘business rule’ for TX to get this warning?


Christian Hauggaard
Community Manager
Forum|alt.badge.img+5

Hi @Bernarddb @daniel this issue has been fixed now, please see

  • 19429: Removed unnecessary warnings in the ODX when synchronizing OLE DB based data sources

in the product update:

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings