Open don-torok opened 3 years ago
@MaximMoinat Perhaps white rabbit could accept a full JDBC url, which would override the parameters in the rest of the dialog. That way alternative syntaxes (e.g. oracle) and connection parameters (e.g. modified SSL parameters) can be added as needed.
Hi @don-torok did you get to resolve Oracle thin connection. I have the same issue.
White Rabbit changed the slash before the service name to a colon when it should leave it as a slash and therefore interprets that I am sending the SID and not the Service Name and therefore I cannot connect
@flaquer2 Sorry, this was at customer's site and I do not currently have access to Oracle, nor do I remember if I was able to connect or not.
Hi @don-torok I was able to resolve it thanks to a comment on the forum of Odhsi https://forums.ohdsi.org/t/whiterabbit-oracle-service-name/1691 These are the steps worked for me:
The JDBC connection string syntax for Oracle is different if the last argument is the 'Service Name' vs. the SID.
user/password@//hostname:port/servicename user/password@//hostname:port:sid
I entered hostname:port/servicename White Rabbit failed to connect with the connection string: hostname:port:servicename
White Rabbit changed the slash before the service name to a colon when it should leave it as a slash