0 - 7 of 7 tags for teradata 13

Folks - if ANYONE out there wants to join me in getting access to TPN+ membership reply or IM me ( preferably if there, IM in the forum that is ) . I have  been in Terdata world for a long time - technology has now changed drastically from what it used to be during V2R3/5/6 days .

Would anybody know why I would be getting this error with Teradata, and not with Teradata 12?

Conversion from type "DBNull" to type 'Integer' is not valid.



When I tried to install the Teradata ODBC Driver Bit) in the Windows 2008 R2 and tried to run through the QlikView, Iam getting this error "Error: SQL Error:Specified driver could not be loaded due to system error 126: The specified module could not be found. (Teradata, C:\Program Files\Teradata\Client\13.0\ODBC Driver for Teradata\Lib\tdata32.dll)."

I found that the file is available in the specified location. Please clarify whether Teradata ODBC driver 64 bit is compatible with the windows 2008 R2.


I am interested in any comments from users of Teradata regarding Teradata v13 Virtual Storage. Has anyone successfully implemented it in a live environment? an Active EDW? I am interested in real life experience rather than test setups or strictly controlled POC environments (Im a committed cynic!)

The availability of Teradata's geospatial extension package in 2007 brought these location capabilities to Teradata 12, 6.2 and 6.1.  This package is still available as a free download from Teradata and when installed, adds geospatial functionality as a User Defined Type (UDT) along with a library of User Defined Functions (UDFs).  (

In ResUsageSpma and ResUsageSvpr tables our Teradata 13 installation (on SUSE) shows NodeType as UNKNOWN.
Did we miss anything during installation? can we define nodetype ourselves?
As per my understanding, NodeType should be automatically configured by Teradata.