Upgrading TeraData from 16.2 to 17.2

, , ,
1

10.7 used and JDBC_10.3_Fix20 level:

Backend system is updating teradata database from 16.2 to 17.2 version and we need to implement same on webMethods application end.

The IS is 10.7 version and we have downloaded 17.2 tools and utilities from teradata website. We have simple replaced the terajdbc4.jar file with the exist file and restarted our server.

The connections are working fine with old jar files but with new jar file it’s throwing below error.

“[ART.118.5042] Adapter Runtime (Connection): Unable to enable connection resource CE_NS_TERADATA_Connection:TERADATA_Connection_01_NoTx.
[ART.118.5036] Adapter Runtime (Connection): Unable to configure connection manager.
[ADA.1.200] The JDBC DataSource class “com.ncr.teradata.TeraDataSource” cannot be located.
com.ncr.teradata.TeraDataSource”

Apart from this we have tdgssconfig.jar file also in /webMethods/product/release107/IS_LDG_5201/IntegrationServer/lib/jars path.

Can anyone support to understand if we are missing any thing here.

Thanks

2

Hi @Rohit_Dabas,

Perhaps can you give a try by placing the new Jar File in the Custom Folder too and see if any difference.

image
image1291×373 13.8 KB

3

Hi Rohit,

preferrably such jars should be located under under IntegrationServer/instances/packages/WmJDBCAdapter/code/jars, as long as they are not required for the JDBC Pools in IS Admin configuration.

Please check with any tool, which is aware of zip format, if the newer jar file has a new directory structure (which is the namespace of the classes) and adopt your configuration accordingly when this is the case.

Regards,
Holger

4

Hi Holger,

Thank you for your response, I placed the new jar file in suggested location but it didn’t work. With 16.2 jar it’s working by placing in the path I shared above.

Thanks

5

Hi Kailash,

Thank you for your response, I placed the new jar file in suggested location but it didn’t work. With 16.2 jar it’s working by placing in the path I shared above.

Thanks

6

Hi Rohit,

as already assumed above, the newer driver has a different namespacing for its classes.
Please try the “com.teradata.jdbc.TeraConnectionPoolDataSource” instead of “com.ncr.teradata.TeraDataSource”.

Refer to the following links for further informations:
Main Documentation page for Teradata JDBC Driver
Teradata JDBC Driver Users Guide
How to use the Teradata JDBC Driver with WebSphere 9.0 (serves as a sample here where the new DataSource class name is mentioned)

Which JVM version is your IS 10.7 running on (see About-page)?
Latest version of TeraData Driver is version 20, which requires at least JVM 8, while it is no longer compatible with JVM 7. See Overview section in the first mentioned link above.

Remember, that with TeraData driver version 17.x the tdgssconfig jar is no longer needed and should be removed from the classpath.

Regards,
Holger

2 Likes
7

Hi Holger,

Thank you for information, connection got enabled after updating the class path.
We checked for DB version with query “SELECT * FROM dbc.dbcinfo;”.

It still giving 16.20.53.39 which is older version. The database team already confirmed that DB is upgraded to 17.2 and we have added new jars in server but version is still display as older one.

Thanks

1 Like
8

Hi Rohit,

the version mismatch usually should not be a problem as long as the db version and the driver version are quite compatible cross wise. Only caveat would be that the connections are limited to the feature set both understand, bot not those ones which either the newer db version or the newer driver version would provide.
See Release Notes for further informations.

Regards,
Holger

9

Hi Holger,

Thank you for your support, the connection is enabled after change the source class name.

Thanks

1 Like