The code currently takes the URL from the JDBC connection string, splits it on colons and takes the last part to use as the server for a SQL Loader connection.
Depending upon the URL, that will be either the database SID or port/SID.
The only way that seems to work is if there is a TNSNAMES.ORA entry to match the SID to the database instance.
I did set up one database to work ok, but another system that I work on uses the same set of SIDs on each of several servers.
The code for the SQL Plus job runner takes everything in the URL after the "@" sign to use as the server and that would seem more likely to work; also it should cope with a URL of the form server:port/servicename.
The code currently takes the URL from the JDBC connection string, splits it on colons and takes the last part to use as the server for a SQL Loader connection. Depending upon the URL, that will be either the database SID or port/SID. The only way that seems to work is if there is a TNSNAMES.ORA entry to match the SID to the database instance. I did set up one database to work ok, but another system that I work on uses the same set of SIDs on each of several servers. The code for the SQL Plus job runner takes everything in the URL after the "@" sign to use as the server and that would seem more likely to work; also it should cope with a URL of the form server:port/servicename.