Devart Forums

We reproduced the issue with a different error the second time. We will investigate it and post here about the results as soon as possible.

We have reproduced the issue. However we think that it is the designed behaviour. As we understand, your schema epu_api does not have privileges to access dev03.calculateServiceInputRecord and dev03.calculateServiceInputList. You can perform the following test:
1. Open SQL*Plus and login as epu_api.
2. Perform the following query in SQL*Plus: You will get errors. Even native Oracle tool can't use synonyms if your schema does not have access to end objects.
3. Execute the following query under sys user: 4. Repeat 1-2 steps. Now this query should be executed successfully.
5. Execute the following query under sys user to revoke privileges if needed: As you can see even SQL*Plus can't use epu_api.calculateServiceInputRecord synonym if epu_api does not have privileges to access dev03.calculateServiceInputRecord.

The UUID type is mapped to System.Guid. It is the designed behaviour. And we recommend you to use Guid values instead of string ones and replace code that casts them to strings in your program. If it is not possible or will take a lot of time, we can create a static class with a static property, which will force returning string values from UUID columns. Please post here whether such solution suits you.

chris.pritchard wrote:Note, that after the no data found error from Oracle, if the code is rerun (presumably reusing the same connection object) you will no longer get this error. Instead I get a devart dotconnect error when I assign a value to an OracleObject property. The error seems to indicate something inside the type was not initialised correctly.

We could not reproduce such behaviour. We always get the same error "no data found" for each run. We will investigated the issue further and post here about the results.

We have reproduced the following case:
1. We have three users: user1, user2 and user3.
2. The calculatServiceInputRecord and calculateServiceInputList objects are created in user1.
3. user2 has privileges to access user1 objects. I create 2 synonyms in user2, and your code works successfully.
4. user3 does not have privileges to access user1 objects. I tried to create synonyms via a user3 connection and got the error: "ORA-01031: insufficient privileges". Then I sign in as sys and run the following queries:

create synonym user3.calculateServiceInputList for user1.calculateServiceInputList;
create synonym user3.calculateServiceInputRecord for user1.calculateServiceInputRecord;

And these synonyms are successfully created inside the user3 schema. And when I run your code I got the error: "ORA-01403: no data found".

Looks like your synonyms are created by a user with more privileges than epu_api has. But when you try to use this synonyms under epu_api, you get an error.

Please note, that the second way affects all .NET applications. We added the needed code to SSIS Data Flow Components for Magento. The next public build will works even without adding described entries to the registry.

New build of Devart SSIS Data Flow Components 1.10.979 is available for download now!
It can be downloaded from https://www.devart.com/ssis/download.html or from Devart Account (for users with valid subscription only).
For more information, please refer to viewtopic.php?t=38984

New build of dotConnect for Oracle 9.7.790 is available for download.
It can be downloaded from https://www.devart.com/dotconnect/oracle/download.html (trial version) or from Devart Account (for users with valid subscription only).
For more information, please refer to viewtopic.php?t=38981

We have fixed the bug with reading incorrect timestamp's timezone and offset in the Direct connection mode when the timezone is presented as a string value. We will post here when the corresponding build of dotConnect for Oracle is available for download.

Please specify which type of a project you use. Is it an ASP.NET application or a Web site? Is the result file exe, and is it a service? Do you rebuild your application every day?

If possible create and send us a small test application which can reproduce the issue. And describe the steps that should be done in order to reproduce the issue.

Sorry for the late response. Please specify where your objects and synonyms are located. In which schema (epu_api or dev03) each object and synonym is created. And specify your query that you use in OracleCommand. If it is a stored procedure, then specify the DDL script of this stored procedure.

And specify the C# code with synonyms which reproduces the issue.

We have answered you via e-mail too.

Looks like your Magneto server requires TLS 1.1 or higher. There are 2 ways to force using TLS 1.1 or higher.
I. Add a specific code inside SSIS Data Flow Components for Magento. We will investigate the possibility to force using TLS 1.1 or higher in SSIS Data Flow Components for Magento and post here when we get the results.

II. Add two keys to the registry. After these changes you can use the current version of SSIS Data Flow Components for Magento.
1. Click "Win key + R" and enter regedit. Click Ok: http://prntscr.com/k4onxy
2. Copy and paste "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319" (without quotes) to the path panel and press Enter. http://prntscr.com/k4oow0
3. Right Click the right panel and select New->DWORD (32-bit) Value. http://prntscr.com/k4oqzy
4. Name it SchUseStrongCrypto. http://prntscr.com/k4orkr
5. Double-click this new parameter, set its value to 1, and click Ok. http://prntscr.com/k4osvw
6. Repeat steps 2-5 with the following path on the step 2:"HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319" (without quotes).
7. Restart SQL Server Data Tools.

Is the issue fixed after this?

No, we did not know about the issue before you sent us the test project for reproducing it.

We managed to reproduce the issue with dotConnect for MySQL 8.10.1152 and with your code. However, your code works correctly with the latest 8.13.1402 version of dotConnect for MySQL. Please try using the latest version of dotConnect for MySQL and post here the results.

We have reproduced the issue with the Direct mode. We will investigate it and post here about the results as soon as possible.

You can use the OCI mode as a temporary workaround if this suits your scenario.