Skip to main content
To homepage To homepage

We have an issue with an Oracle data source, having a different “Owner” between the acceptance and production environments.

We're on TimeXtender 20.10.51 using Business Units.

The Oracle data source is configured using a global database. On acceptance it looks like this:

When the data source is added on acceptance, objects are read as accpOwner.tableName.

The production global database properties look like this, with a different owner:

However, on production TimeXtender expects the same owner that was configured in acceptance:

And these selected tables don't exist in the production database, because they exist as prodOwner.tableName.

This means that the tables cannot be found in the data source, and consequently cannot be executed. When syncing data source on prod all tables are dropped from the business unit, losing mappings to DSA, and no production tables are selected.

One solution I can think of is to add ACCP and PROD tables in both environments, and use an environment variable to compensate, but this seems unnecessarily laborious. What would be the best way to make this work?

Hi @MartinMemelink 

I don’t think you are able to have two different Owners for each environment.

I would just only use PROD and then possibly add rules to select only specific data for ACCP, but that is probably as laborious as having two versions.

Hi @MartinMemelink 

I don’t think you are able to have two different Owners for each environment.

I would just only use PROD and then possibly add rules to select only specific data for ACCP, but that is probably as laborious as having two versions.

Thanks for your reply Thomas, we would prefer to have production data in our acceptance environment too. However the client is very anxious about mixing environments because acceptance tests have to be performed every time the source system is updated.

We've opted to load PROD and ACCP in the BU on both environments and use data selection rules with an environment variable.

Hi @MartinMemelink 

OK that will work. This is specifically an issue due to how the Oracle data source operates. The tables all get a schema equal to the owner, if it just got a dbo or similar it wouldn’t give any issues.

We use the providers made by Oracle or Microsoft in the setup and they make them behave this way.

I got this old project where I have many ways of connecting to oracle. I downloaded the ODAC package to get the providers and then I used it in a specific Any Source ADO.Net data source. I used the OLE DB one. I also used our own provider which automatically chooses one of these providers.

As you can see, no matter what option I use it always uses the OWNER as the schema name.

So there really is not other way to achieve this.

Hi @MartinMemelink 

Can you add a response that you feel is the Best Answer to this?

Reply


Terms and ConditionsCookie settings