Solved

Teradata Connection

  • 25 August 2023
  • 8 replies
  • 103 views

Userlevel 1
Badge

We are facing issue in connecting to Teradata. On debugging we found the below error. Can someone help?

 

2023-08-25T09:34:58.217+0000    0       [4|Q-Id]        [INFO|Connec] Executed connect:  Error: com.teradata.jdbc.TeraDriver
2023-08-25T09:34:58.218+0000 0 com.teradata.jdbc.TeraDriver
java.lang.ClassNotFoundException
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:476)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:594)
at XcoreXcdata.realdb.gld.loadClass(Unknown Source)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:527)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:315)
at XcoreXteradataX220X8462.fcf.p(Unknown Source)
at XcoreXteradataX220X8462.fcf.o(Unknown Source)
at XcoreXteradataX220X8462.fcf.i(Unknown Source)
at XcoreXteradataX220X8462.prb.aX(Unknown Source)
at XcoreXteradataX220X8462.prb.k(Unknown Source)
at XcoreXteradataX220X8462.prb.j(Unknown Source)
at XcoreXteradataX220X8462.cpb.j(Unknown Source)
at XcoreXteradataX220X8462.epb.a(Unknown Source)
at cdata.jdbc.teradata.TeradataDriver.connect(Unknown Source)
at XcoreXcdata.realdb.zvb.a(Unknown Source)
at XcoreXcdata.realdb.mnd.a(Unknown Source)
at XcoreXcdata.realdb.qkd.a(Unknown Source)
at XcoreXcdata.realdb.mnd.connect(Unknown Source)
at XcoreXcdata.syncX230X8564.fda.connect(Unknown Source)
at XcoreXcdata.syncX230X8564.gda.a(Unknown Source)
at sync.core.QueryExec.a(Unknown Source)
at sync.core.QueryExec.e(Unknown Source)
at rssbus.syncops.CallStackKeeper.TestConnection(Unknown Source)
at rssbus.syncops.TestConnection.exec(Unknown Source)
at XcoreXcdata.syncX230X8564.wna.a(Unknown Source)
at XcoreXcdata.syncX230X8564.wna.a(Unknown Source)
at XcoreXcdata.syncX230X8564.wna.a(Unknown Source)
at XcoreXcdata.syncX230X8564.ila.a(Unknown Source)
at rssbus.src.testConnection_rsb.a(Unknown Source)
at XcoreXcdata.syncX230X8564.epa.Exec(Unknown Source)
at rssbus.src.testConnection_rsb.execRSB(Unknown Source)
at XcoreXcdata.syncX230X8564.pla.execRSB(Unknown Source)
at XcoreXcdata.syncX230X8564.zna.a(Unknown Source)
at XcoreXcdata.syncX230X8564.cna.a(Unknown Source)
at XcoreXcdata.syncX230X8564.cna.a(Unknown Source)
at XcoreXcdata.syncX230X8564.sla.call(Unknown Source)
at XcoreXcdata.syncX230X8564.mia.call(Unknown Source)
at XcoreXcdata.syncX230X8564.mia.call(Unknown Source)
at rssbus.RSBScript.a(Unknown Source)
at rssbus.RSBScript.a(Unknown Source)
at rssbus.RSBScript.service(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:590)
at org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1410)
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:764)
at org.eclipse.jetty.servlet.ServletHandler$ChainEnd.doFilter(ServletHandler.java:1665)
at b.c.doFilter(Unknown Source)
at org.eclipse.jetty.servlet.FilterHolder.doFilter(FilterHolder.java:202)
at org.eclipse.jetty.servlet.ServletHandler$Chain.doFilter(ServletHandler.java:1635)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:527)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:131)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:538)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:223)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1570)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:131)
at org.eclipse.jetty.server.handler.RequestLogHandler.handle(RequestLogHandler.java:46)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)
at org.eclipse.jetty.server.handler.gzip.GzipHandler.handle(GzipHandler.java:822)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)
at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:223)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1385)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:176)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:484)
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1543)
at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:174)
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1307)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:129)
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:122)
at org.eclipse.jetty.server.Server.handle(Server.java:563)
at org.eclipse.jetty.server.HttpChannel.lambda$handle$0(HttpChannel.java:505)
at org.eclipse.jetty.server.HttpChannel.dispatch(HttpChannel.java:762)
at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:497)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:282)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:314)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)
at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.onFillable(SslConnection.java:558)
at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:379)
at org.eclipse.jetty.io.ssl.SslConnection$2.succeeded(SslConnection.java:146)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:100)
at org.eclipse.jetty.io.SelectableChannelEndPoint$1.run(SelectableChannelEndPoint.java:53)
at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.runTask(AdaptiveExecutionStrategy.java:416)
at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.consumeTask(AdaptiveExecutionStrategy.java:385)
at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.tryProduce(AdaptiveExecutionStrategy.java:272)
at org.eclipse.jetty.util.thread.strategy.AdaptiveExecutionStrategy.lambda$new$0(AdaptiveExecutionStrategy.java:140)
at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:411)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:936)
at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:1080)
at java.base/java.lang.Thread.run(Thread.java:829)
2023-08-25T09:34:58.218+0000 0 [4|Q-Id] [INFO|Connec] Failed to open Teradata connection. Version: [22.0.8462.0]. Edition: [JDBC Driver].

 

 

icon

Best answer by PratikV 30 August 2023, 06:40

View original

8 replies

Userlevel 5
Badge +1

Hi @RajasGujarathi 

This requires an in-depth analysis of the issue you are facing and the best way to move forward will be having our Technical support team look at this. Can you please log a Support case here: https://www.cdata.com/support/submit.aspx.

 

From the error, however, it seems that the Jetty Webserver isn’t able to find the classpath of the JDBC driver. With the CData Teradata JDBC Driver, there are some pre-requisites you need that are mentioned here: https://cdn.cdata.com/help/OTJ/jdbc/pg_connectionj.htm#deploying-the-driver.

Can you confirm if you have followed the steps above for deploying the driver?
 

Userlevel 1
Badge

Thanks @Ankit Singh let me go though the above steps once again to ensure that everything is in place., before I raise a support case.

Userlevel 1
Badge

As per the pre-requisite document, I feel that I have all that is needed.

 

 

However, still facing the same issue

 

Have logged a support case with Technical Support. Hope to see a resolution soon. 

Userlevel 1
Badge

Have not heard anything from Technical Support. Hope to connect soon.

Userlevel 2
Badge

Have not heard anything from Technical Support. Hope to connect soon.


Hi @RajasGujarathi ,

I would like to inform you that ,from the Technical Support side , we have tried to mail you , but due to some network restrictions at your end we are not able to process it and the mail gets fire back.

Below is the response which we are trying to send you.
As per your query I could see you are  facing error:  java.lang.ClassNotFoundException while making a test connection for Teradata which could be due to missing of one of the Jar files in the libs folder. In order to make a successful test connection , you would need to add the attached Jar files of Teradata in the libs folder.

Please download and place the respective Jar files in the libs folder `/opt/sync/libs` and then try to test it out and let us know how it goes?
Waiting to hear from you soon.


We need two Teradata jar files in order to create a successful test connection, but based on the screenshot you provided, it appears that only one Jar file is present. I've included the corresponding Jar files in this topic for your convenience. Please let us know how it turns out.​​​​​​​

Userlevel 1
Badge

Thanks will give this a try.

@PratikV meanwhile can you share the error email that you get. This will help us investigate the issue and possibly fix it.

Userlevel 1
Badge

Thanks All, we are now able to make a successful connection with Teradata using the above drivers.

Userlevel 2
Badge

Thanks will give this a try.

@PratikV meanwhile can you share the error email that you get. This will help us investigate the issue and possibly fix it.

@RajasGujarathi ,

Please find the below image for the same.
 


And I am glad the issues is resolved and the driver is working fine as expected.​​​​​​

Reply