Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik Open Lakehouse is Now Generally Available! Discover the key highlights and partner resources here.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Netezza Database connection error

I'm attempting to connect to a Netezza server, and gettting an error. I've tried both the tNetezzaInput component, and the tJDBCInput connection, both generate the same error.
The error: when I run a simple job to retrieve data: "A connection error has occurred: Invalid - database name" (full text below)
I know that the underlying connection is good, as it is possible to create a new connection, then do "Import Schema" using both Netezza and JDBC options. The Import Schema correctly retreives various tables.
Any ideas?
Exception in component tNetezzaInput_2
org.netezza.util.PSQLException: A connection error has occurred: Invalid - database name
at org.netezza.core.PgHandshake.handshake(Unknown Source)
at org.netezza.core.PgHandshake.connect(Unknown Source)
at org.netezza.jdbc1.AbstractJdbc1Connection.handshake(Unknown Source)
at org.netezza.jdbc1.AbstractJdbc1Connection.openConnection(Unknown Source)
at org.netezza.Driver.getConnection(Unknown Source)
at org.netezza.Driver.connect(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at testjava.testnetezza_0_1.testnetezza.tNetezzaInput_2Process(testnetezza.java:888)
at testjava.testnetezza_0_1.testnetezza.runJobInTOS(testnetezza.java:1547)
at testjava.testnetezza_0_1.testnetezza.main(testnetezza.java:1459)
Labels (4)
2 Replies
Anonymous
Not applicable
Author

Hello
Can you connect to Netezza in metadata?
Best regards

shong
Anonymous
Not applicable
Author

I am now able to successfully run a simple job to extract and load tables in netezza. I'm not sure what the solution was, I re-created the job from scratch and it now works, in both tNetezzaInput/Output and ODBC components.