Problems to connect with an Oracle EBS database when using copy data activity

[rmoraes1987]

Hello folks!

I'm trying to get data from Oracle EBS database. Here's the flow:

- VM Azure connect to a EBS server and access the data with a tnsnames.ora and Oracle client for microsoft tools installed;

- I checked the conn with an dbeaver installed inside the VM and that's okay;

- Now I'm trying to get data inside Fabric using the On-Premise Data Gateway. This app is installed and configured with the same e-mail using in Fabric;

- When I try to get data using dataflow gen2, It reaches the EBS server and database schemas;

- But when I try to get from Simple copy data activities, it just doesn't work, always get error 400.

Can somebody help me with this?

[rmoraes1987]

Hello.

Just to inform that today everything is fine in a miraculous way.

I only switched the VM tô 8GB RAM to deal with the Gateway cluster tô PowerBI service.

[v-mdharahman · Accepted solution]

Hi @rmoraes1987,

Thanks for reaching out to the Microsoft fabric community forum.

Based on what you’ve shared, it sounds like your Oracle connection through the Azure VM and On-Premises Data Gateway is functioning correctly, especially since you’re able to access the data via Dataflow Gen2. That confirms the gateway and Oracle client configuration are set up properly.

However, the issue you're facing with the Simple Copy Data activity returning a 400 error likely points to either the copy activity not routing through the gateway correctly, or a mismatch in connection parameters (like service name vs SID, or credential issues).

Here are a few things to check and try:
* Confirm Linked Service is Gateway-enabled. Go to your Data Pipeline > Copy Data activity > Source, and check the linked service you're using for Oracle. Now open the linked service and make sure “Connect via on-premises data gateway” is enabled, and that it’s selecting the correct gateway installed on your VM.
* Check Connection Type in Linked Service. For Oracle, you may have options like Oracle Database, Oracle using Service Name, or Oracle using SID. If your tnsnames.ora uses a service name, ensure you're using the correct connection type (Service name vs SID) in your linked service. Also confirm the port (usually 1521), host, and service name exactly match what's in tnsnames.ora.
* Review Gateway Logs (Optional). If you have admin access to the gateway VM open On-premises data gateway app, go to Diagnostics, and enable logging. Now re-run the Copy Data activity and then review the logs for specific error messages tied to the 400 response.

I would also take a moment to thank @lbendlin, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.

If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

Best Regards,
Hammad.
Community Support Team

[lbendlin]

Can you confirm that you have done the tnsnames.ora setup on all gateway cluster members?