JDBC Driver Class Name
JDBC connection port for Netezza is 5480. Read more on the different ports of
Netezza from here
4. Enable the Sqoop connectivity
in the JDBC connection by changing the value of attribute ‘Use Sqoop
Connector’ from ‘None’ to ‘Sqoop v1.x’.
5. In the ‘Additional
Sqoop arguments’ section of the connection, enter the following:
Note: It is not required to
enter the JDBC URL again in the ‘Additional Sqoop Arguments’ attribute.
During the job execution, URL entered earlier in the ‘Connection String’
section would be re-used.
steps could be repeated for any relational sources having JDBC driver based
connectivity, by providing the appropriate ‘Driver Class Name’ and ‘JDBC URL’
the jar files, including the Netezza driver, when placed under
‘$INFA_HOME/externaljdbcjars’ location, would be transferred to the Hadoop data
nodes using ‘infa_rpm.tar’ file. As an additional step, ensure to restart
the Informatica Domain so that the jar would get picked up and the test
connection could be successful.
in case of ‘Developer Client’, for connectivity, the jar should be kept under
‘%INFA_CLIENT_HOME%\externaljdbcjars’ location. Say for 10.2.2, the default
location would be ‘C:\Informatica\10.2.2\clients\externaljdbcjars’.
What can we do to improve this information (2000 or fewer characters)