Skip to main content
To homepage To homepage

Hi,

We've updatet our Data Integration version from 6766.1 to 6963.1. Which means we had to update our outdated providers. So we followed the steps mentioned in this post Change data source provider | Community (timextender.com).

This results in an error when we try to full load changed data source. It keeps giving is the error: “The schema …. already exists on the SQL storage and cannot be used”

 

Which actually means we can’t update our providers/ data sources. We have to create new ones en have to map all our tables in de odx. 

Anyone else facing this problem and have a solution for this?

Hi ​@r.miltenburg 

This is a bug, due to a restriction that two data sources cannot have the same short name. That is not what you are doing as you want to continue to use the same name of course. We apologize for the inconvenience caused by this issue, and we have made an internal case for this to ensure it gets addressed.

Unfortunately I do not see any workarounds besides what you already suggested. Once a short name is set you can’t change it, so you can’t rename it to the original name after creating it as a new one.

I think I had that issue a few times, though I am not sure it was for the same reason, and managed to resolve it by simply manually deleting all tables with that schema in the ODX and the schema itself. 

Then everything ran just fine after I did this

Hi ​@r.miltenburg 

Are you able to send the complete error message to me in a private message or through our support@timextender.com email.

I think I had that issue a few times, though I am not sure it was for the same reason, and managed to resolve it by simply manually deleting all tables with that schema in the ODX and the schema itself. 

Then everything ran just fine after I did this

 

I did the same, problem we had after deploy and executing the tables in the ODX, it didn't recognize the tables, so we still had to remap.

Hi ​@r.miltenburg 

The error means that another data source with the short name (the unique name) "ALG CSV BI" existed in the past and they deployed/executed data into the storage. Then they deleted that data source and created a new one with the same name. Now the SQL schema for the previous data source still exist, possibly with tables in the SQL storage. To avoid the new data source will override those tables, the execution of the new data source has been blocked.

Alternative, they might run two different Ingest on the same SQL storage database and both ingest have a data source with the short name "ALG CSV BI".

They could manually delete the schema "ALG CSV BI" or create a new data source with another short name, but I think they should investigate if one of the above is what has happened.

Does this seem like a thing you could try on your end.

Hi ​@Thomas Lind ,

 

Deleting the schema manually in SSMS also means I have to delete the tables linked to this schema manaully, which means I sttill have to map my tables in the ODX.

The error means that another data source with the short name (the unique name) "ALG CSV BI" existed in the past and they deployed/executed data into the storage. Then they deleted that data source and created a new one with the same name

For the record, we didn't delete the data source before we synced and full loaded the changed provider. 

So unfortunately still not a good alternative for this then just remapping.

Hi ​@r.miltenburg 

I have made an internal ticket for this.

Hi ​@r.miltenburg 

We will have a fix for the schema issue in the next release.

Reply


Terms and ConditionsCookie settings