can you share how you’re filling the connection fields (especially connection string / service name format)? it would help narrow this down further.
error usually means the TCP connection was opened but then closed by the server or interrupted on the network side.
Since you mentioned your Node.js script only works when explicitly calling initOracleClient(), that may still be needed depending on how Oracle libraries are installed, but the current error suggests the connection is reaching the server and then being closed, which points more to configuration or network rather than the client library itself.
Hello,
Thank you for all this information, it’s very clear.
However, I don’t think it’s a network issue.
In fact, since n8n version 2.1.2, I haven’t had the problem. However, it is present in 2.7.4.
Have there been any significant changes during this period?
Thank you.
From what I researched in the updates between versions, the oracledb driver changed its behavior. See if one of these three options can help you: run in Docker with OIC explicitly configured, or create a Node.js microservice with oracledb.initOracleClient() exposing the API and consuming it via Node HTTP request, or go back to the version that worked
Thank you for your solutions!
Can’t the n8n team revert to what was done in previous versions so that the connector works under the same conditions?
Thank you!
They must be seeing this for sure.
I’m really happy to hear this helped
If this solution solved the issue for you, please consider leaving a like or marking the reply as the solution ( it helps others find the answer more easily and also supports community contributors.)
