JDBC EZConnect URL: Invalid number format for port number when specifying Protocol - oracle

When specifying a JDBC EZConnect URL to include the Protocol, for example:
jdbc:oracle:thin:#tcps://example1.com:1522/my_service_name
jdbc:oracle:thin:#tcp://example1.com:1522/my_service_name
I am getting the error "Status : Failure - Test Failed: IO Error: Invalid number format for port number"
I am following the example page XXX of the Oracle 19c JDBC Developers Guide (http://ora-srv.wlv.ac.uk/oracle19c_doc/jjdbc/jdbc-developers-guide.pdf)
Does anyone have any input into why this error is occurring ?
Thanks
Andrew

Related

Teradata Oracle Wire Protocol ODBC connection test error, specified driver could not be loaded

I am trying to test my ODBC connection in Teradata on UNIX using adhoc file.
teradata/client/17.10/odbc_64/samples/C/adhoc
when trying to connect to Oracle DSN, I get following error
adhoc: (SQL Diagnostics) STATE=IM003, CODE=0, MSG=[DataDirect][ODBC lib] Specifi ed driver could not be loaded
No driver entry found under the DSN :
I have the entries in
odbc.ini as
[BIC_DEV_ORA_TW]
Description=Teradata 8.0 Oracle Wire Protocol
Driver=/opt/teradata/client/17.10/tbuild/odbc/lib64/_Tora28.so
AlternateServers=
ApplicationUsingThreads=1
AccountingInfo=
Action=
ApplicationName=
ArraySize=60000
AuthenticationMethod=1
BulkBinaryThreshold=32
BulkCharacterThreshold=-1
BulkLoadBatchSize=1024
BulkLoadFieldDelimiter=
BulkLoadRecordDelimiter=
CachedCursorLimit=32
CachedDescLimit=0
CatalogIncludesSynonyms=1
CatalogOptions=0
ClientHostName=
ClientID=
ClientUser=
ConnectionReset=0
ConnectionRetryCount=0
ConnectionRetryDelay=3

Greenplum connector giving hostname resolution error in ibm Datas stage

GreenPlum Connection error:
Greenplum_Connector_1,0: The following SQL statement failed: INSERT INTO GPCC_ET_20200903233319813_84175_0 select * from table .
The statement reported the following reason: [SQLCODE=HY000][Native=56,966,976] [IBM(DataDirect OEM)][ODBC Greenplum Wire Protocol driver][Greenplum]ERROR: could not translate host name "hostname_of_machine", port "8001" to address: Name or service not known (cdbutil.c:819)
(seg5 192.168.111.240:6005 pid=38339) (cdbdisp.c:254)(File cdbdisp.c; Line 254; Routine cdbdisp_finishCommand; )
(CC_GPCommon::checkThreadStatusThrow, file CC_GPCommon.cpp, line 808)
As Jon mentioned, "hostname_of_machine" needs to be updated to the real hostname

pyodbc Driver keyword syntax error

My conn_str that is passed into pyodbc.connect(conn_str) is:
conn_str = str("DRIVER={{ODBC Driver 13 for SQL Server}};" +
"server=...;database=...;" + "APP=Entity Mapping
Lookup;UID=svc_infra_jobs;PWD=...").
The =... next to server and database actually contain names, that is not the problem here.
When i try to do: temp = pyodbc.connect(conn_str), I get the error:
pyodbc.Error: ('IM012', '[IM012] [Microsoft][ODBC Driver Manager]
DRIVER keyword syntax error (0) (SQLDriverConnect)')
I have no idea what is wrong with my DRIVER keyword.
I know this is old but figured out that for some driver managers the DSN name length can't exceed 32 characters.
https://community.microstrategy.com/s/article/KB44110-quot-Data-source-name-is-longer-than-32-characters-quot?language=en_US

What's the meaning of: "java.sql.SQLRecoverableException: I/O-Error: Unknown host specified" if TNS-alias specified

Using Oracle JDBC driver with TNS-alias instead of host:port:SID a'la
jdbc:oracle:thin:#TNS_ALIAS
you may get this error message
java.sql.SQLRecoverableException: I/O-Error: Unknown host specified
while calling
java.sql.DriverManager.getConnection
But there is no problem with the hostname specified by TNS-alias.
Sadly this error message does not point to the real reason:
The error occurs if driver cannot find the tnsnames.ora config file.
Solution
You have to ensure that system-property "oracle.net.tns_admin" is set before connecting and points to the directory containing the tnsnames.ora.

[Microsoft][Hardy] (34) Error from server: SSL_connect: wrong version number

Unable to test the HiveODBC driver's System DSN .
The error shown is

Resources