Are you able to test this in beta?
Unfortunately, I am not able to test in Beta. Sorry.
Also, I suspect that if you put the connection info into tnsnames.ora and use that instead of a direct connect, then there will be no problem.
That's correct, there are no problems using TNS connection. From earlier in the thread:
The issue seems to only occur when using a Direct connection. I do not have the issue when using a TNS connection.
To be clear, the issue does occur with an Oracle 19c client. I understand that the logic currently uses EZConnect syntax regardless of Oracle client and your fix avoids the different Oracle client versions by instead using the full TNS syntax regardless of Oracle client.
Thanks for identifying and correcting.