Home Page for the TeradataForum
 

Archives of the TeradataForum

Message Posted: Tue, 12 Jun 2001 @ 17:36:27 GMT


     
  <Prev Next>  
<<First
<Prev
Next> Last>>  


Subj:   What to do about JDBC Problems
 
From:   Anomy Anom

<-- Anonymously Posted: Tuesday, June 12, 2001 13:24 -- >

I have an ongoing problem with JDBC: I don't have a lot of experience with JDBC and it seems like every problem we discover, I spend a lot of time gathering information, giving it to the GSC and then after a week or two of sending notes back and forth, I'm told to upgrade to the most recent version. Some times the upgrade fixes the problem and other times, it doesn't. If the upgrade doesn't fix the problem, then a lot of time has passed and I'm still at square-one.

I realize that this is pretty typical and will just have to be lived with. The point of this note is to find out what other people do to isolate their JDBC problems. Are there tools that you use? If so, what are they and who makes them? How well do they work? Tracing our applications on the JDBC server (by changing flags in the terajdbc.conf file) is just prohibitive because of the size of the resulting trace logs. What do you do to make tracing more reasonable? What do you do to find JDBC problems?

While I'm at it, what are your experiences with JDBC? How reliable are you finding it? How successful are you at problem isolation and resolution? What kinds of advice can you offer about JDBC? Any help would be appreciated.

TIA



     
  <Prev Next>  
<<First
<Prev
Next> Last>>  
 
 
 
 
 
 
 
 
  
  Top Home Privacy Feedback  
 
 
Copyright for the TeradataForum (TDATA-L), Manta BlueSky    
Copyright 2016 - All Rights Reserved    
Last Modified: 27 Dec 2016