DSC using JDBC 14.10 despite an upgrade to TTU 16.XX in Teradata

 Problem:

Regardless of TTU 16.10 being installed on BAR Servers (including the DSC Server), DSC Server using JDBC 14.10

 

select distinct ClientJDBCDriverVersion from dbc.logonoff where ClientSystemUserID='dscuser';

ClientJDBCDriverVersion

14.10.00.17

 

select Appid, ClientID,username,clientAddr, count(*)

from PDCRINFO.DBQLogTbl_Hst

where ClientID='DSCUSER'

Group by 1,2,3,4

order by 1,2,3,4;

 

APPID

CLIENTUSER

USERNAME

COUNT(*)

JDBC14.10.00.17;1.7.0_151    

DSCUSER                      

ARCUSER1

376

JDBC14.10.00.17;1.7.0_151    

DSCUSER                      

VIEWPOINT

1

JDBC14.10.00.17;1.7.0_91     

DSCUSER                      

ARCUSER1

9580

 

Environment:

DSC 16.10, DSC 16.20

Cause:

Whenever jobs are started either via the BAR operation portlet or the DSC Command line, a connection is established between DSC server to the target TD DBS system and this connection uses a DSC-builtin JDCB 14.10 driver.

 

Solution:

There is no now problem with the DSC-builtin JDBC 14.10 driver accessing a Teradata 15.x or 16.x System. JIRA DSA-2064 has been opened to build DSC with a newer JDBC driver version.

 

Comments