Issue when connecting fabric to oracle using pipeline

[SLI]

Hi all 

I have an issue in fabric when I am trying to connect to oracle autonomous using a pipeline 

the goal is to Connect to oracle database , copy data into a lakehouse 

but when we do it i have this message :

Failed to open the Oracle database connection. Network Transport: SSL failure in parsing wallet location Illegal characters in path. ID d’activité: db4fc233-b0d0-456b-95dc-47e3de193990

the gateway that we use works Very good with power bi  (same connection to the same database)

have you an idea about whist i should do?

is there any issue with this kind of connection 

[v-hashadapu · Accepted solution]

Hi @SLI , Thank you for reaching out to the Microsoft Community Forum.

Sorry for the inconvinience. Can you please provide more information, along with error screenshots.

Thank you.

[v-hashadapu · Accepted solution]

Hi @SLI , Thank you for reaching out to the Microsoft Community Forum.

Sorry for the inconvinience. Can you please provide more information, along with error screenshots.

Thank you.

[SLI]

Hi @v-hashadapu yes of course , please find bellow the screen shot of the error 

thanks for your help

[SLI]

Please if you have any update about this topic don't hesitate to answer 

the problem is not resolved yet 

thank you 

[v-hashadapu · Accepted solution]

Hi @SLI , Thank you for reaching out to the Microsoft Community Forum.

Your issue is likely related to an invalid wallet path or Fabric pipeline permissions. Make sure there are no spaces, special characters, or an incorrect directory reference and check if the wallet path may be misconfigured. Also, ensure Fabric’s pipeline have permission to access the wallet location. Test the Connection Outside Fabric, If it fails, the issue is with the wallet itself, not Fabric.

Please refer to the below MS official documentation for more information:

Set up your Oracle database connection

Configure Oracle database in a copy activity

If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
Thank you.

[SLI]

Thank you  @v-hashadapu 

we have created a new gateway based on wallet path without any special characters and now it works

[SLI]

Hello @govind_021 

thank you for your answer 

it is the same answer that i've obtained from copilote 

i need to know if someone has already encountred the same problem

thank you