Hi,
I want to connect to Terdata from my .net application using .net ODBC provider. I have installed the TeraData ODBC adapter. But I am not able to connect. Please help is thata anything I am missing here?
Regards,
Lakesh

Hi All,
Can someone help me to find the solution for below issue? Thanks!
When ever new business users are created, they are provided with initial password which they need to reset the first time they login to Teradata.
In one of our project, business users are accessing Teradata using Tableau desktop and there is no option for them to reset the initial password unless they install teradata tool like SQLA.
So, is there any possibility to have some “light” tools which can be easily installed and can be used for resetting the password in Teradata or any other way to handle this issue, please inform.
 
Regards,
Srini.

Hi I'm new to using Studio Express. I'm wondering what I would need to download and how to configure a basic sample data conneciton within Studio Express.
 
Any help is greatly appreciated! Thank you.

Hi,
we have a jdbc data source configured in sap netweaver java server,which connects to Teradata(13.10.07.28). the jdbc driver version is 15.00.00.20.
we have an ejb consuming that data source.
the java server is running on windows.

private Connection getConnection() throws SQLException {
		Connection conn = _dataSource.getConnection();
		for (int i = 0; i < 3; i++) {

			try {
				if (!conn.isValid(30)) {
					conn = _dataSource.getConnection();
					Statement st=conn.createStatement();// this line throws the error
					st.close();
					st=null;
				} else {
					_location.infoT("get the connection at "+i+" try.");
					break;
				}
			} catch (Exception e) {
				_location.traceThrowableT(Severity.ERROR, "", e);
			}

		}

		return conn;
	}

the problem is this methd always return me the dead connection if it is the first time to run the code. it gives valid connection if you run it immediately after the failure and afterwards. if you haven't accessed it for a while, you will get the issue if u run it again and you get valid connection if u run it after the failuer.
in my code  i am checking the connection is dead or live, but it doesn't help.
If you write following code, the loop never ends until server restart(because of out of memory) for the first time run.

While(!conn.isValid(30)){

conn = _dataSource.getConnection();

}

[EXCEPTION]
 java.sql.SQLException: [Teradata JDBC Driver] [TeraJDBC 15.00.00.20] [Error 1095] [SQLState HY000] Cannot call a method on closed connection 
at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:94) 
at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:64) 
at com.teradata.jdbc.jdbc_4.TDSession.createStatement(TDSession.java:1339) 
at com.teradata.jdbc.jdbc_4.TDSession.createStatement(TDSession.java:645) 
at com.teradata.jdbc.jdbc_4.TDSession.createStatement(TDSession.java:1380) 
at com.sap.sql.jdbc.vendor.VendorConnectionHandle.createStatement(VendorConnectionHandle.java:79) 
at com.sap.engine.services.dbpool.cci.ConnectionHandle.createStatement(ConnectionHandle.java:97) 

any advice will be appreciated.
Thanks
Jun

Hi!
I have on SQL2008 server linked server Teradada. I select from this linked server and for many tables is ok, but
when I select some tables I see error:
OLE DB provider "MCDASQL" for linked server "TD" returned message "Multiple-step OLE DB operation generated errors. Chek each OLE DB status value, if available. No Work was done.
MSG 7311, Level 16, state 2, Line 1
Cannot obtain the schema rowset "DBSCHMA_INDEXES" for OLE DB provider "MSDASQL" for linked server "TD". The provider support the interface, ut returns a failure code it is used.
Example
select * from TD.."001_SM_TABLE"."PAYNAME_ALL_FCT_NO" -- is executed ok and returns rows,
but if
select * from TD.."001_SM_TABLE"."PAYNAME_GR_FCT" - is return error :(
When I select rows use Teradata SQL Asisstant both table is OK and I seee all rows
Please help if You have any ideas
 
 

Hi,

I was able to connect to aster DB via java application using the jdbc:ncluster connection string. Is there a way to use connection pool in my Java code for this aster database connection?
 
Thanks

Hi All,
I am trying to connect my Teradata server through JDBC Driver in java to my Web Application. I am using the following Connection String:
String connectionString ="jdbc:teradata://DatabaseServerName/DATABASE=xxx,DBS_PORT=1025,USER=xxxx,PASSWORD=xxxxx";
I am getting the following error:
com.teradata.jdbc.jdbc_4.util.JDBCException: [Teradata JDBC Driver] [TeraJDBC 13.00.00.07] [Error 1032] [SQLState HY000] Single Sign-On NOT supported for Mechanism TD2.
    at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:91)
    at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:66)
    at com.teradata.jdbc.jdbc.GenericTeraEncrypt.initEncrypt(GenericTeraEncrypt.java:221)
    at com.teradata.jdbc.jdbc.GenericTeraEncrypt.<init>(GenericTeraEncrypt.java:135)
    at com.teradata.jdbc.jdbc.GenericAssignState.action(GenericAssignState.java:82)
    at com.teradata.jdbc.jdbc.GenericLogonController.run(GenericLogonController.java:120)
    at com.teradata.jdbc.jdbc_4.TDSession.<init>(TDSession.java:199)
    at com.teradata.jdbc.jdbc_3.ifjdbc_4.TeraLocalConnection.<init>(TeraLocalConnection.java:95)
    at com.teradata.jdbc.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:54)
    at com.teradata.jdbc.TeraDriver.doConnect(TeraDriver.java:217)
    at com.teradata.jdbc.TeraDriver.connect(TeraDriver.java:150)
    at java.sql.DriverManager.getConnection(DriverManager.java:664)
    at java.sql.DriverManager.getConnection(DriverManager.java:270)
I tried to solve this issue by adding LOGMECH=td2 in the connection string. Since my teradata server is implemented using the TD2 Log On Mechanism, But still i am facing the same issue.
Can anyone Please help me to solve this issue.
Thank you

Where is the README file for the ODBC Driver Suite 15.00.04 for Windows?
I looked in the zip file but there is no README file. Should there be one?

When do I want to use each of these? If I have a source OLEDB system and am continually moving data from there to Teradata via scheduled SQL jobs on the Teradata side, I like that OLEDB Access supports FASTLOAD functionality. Are there limitations to OLEDB access module that would prevent me from using it?
Thanks!

We have OBIEE Linux platform and recently one of our applications have hogging thread alerts with below error message:
 
[nQSError: 16001] ODBC error state: S1000 code: -3156 message: [Teradata][ODBC Teradata Driver][Teradata Database] Request aborted by TDWM. Exception criteria exceeded
 
Can someone please tell us what this message means?...

[nQSError: 16001] ODBC error state: 08S01 code: 4 message: [Teradata] [Unix system error] 4 Unable to get catalog string
can someone please let us know what that message means?

Hi,
I'm on a windows 7 in 32 bits and I use Eclipse IDE for Java EE developper and I install Birt framework manually.
 
I want to use a datasource connected with a teradata database.

So I try some way.
 
At first I try to connect with ODBC with the driver "sun.jdbc.odbc.JdbcOdbcDriver (v2.1)" but that didn't work. So after I search a specific driver for teradata, I find the "com.teradata.jdbc.TeraDriver (v13.10)",
That don't work either.
We use a Teradata v14.00 that doesn't matters ? Or we need a driver more recent ?
 
At last I try to install the Teradata Eclipse plugins to connect with a teradata database with the JDBC database for query builder. We try all the way (we think) in this method but nothing work, we have ever the same error "
 
com.teradata.jdbc.jdbc_4.util.JDBCException: [Teradata JDBC Driver] [TeraJDBC 13.10.00.36] [Error 1277] [SQLState 08S01] Login timeout for Connection to 93.95.17.13 Wed Apr 15 09:56:47 CEST 2015 socket orig=93.95.17.13 cid=30f69c sess=0 java.net.SocketTimeoutException: Connect timed out at java.net.SocksSocketImpl.readSocksReply(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF$ConnectThread.run(TDNetworkIOIF.java:968)

at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:93)

at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeDriverJDBCException(ErrorFactory.java:68)

at com.teradata.jdbc.jdbc_4.util.ErrorFactory.makeIoJDBCException(ErrorFactory.java:206)

at com.teradata.jdbc.jdbc_4.util.ErrorAnalyzer.analyzeIoError(ErrorAnalyzer.java:61)

at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.createSocketConnection(TDNetworkIOIF.java:137)

at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF.(TDNetworkIOIF.java:116)

at com.teradata.jdbc.jdbc_4.TDSession.getIO(TDSession.java:580)

at com.teradata.jdbc.jdbc.GenericLogonController.run(GenericLogonController.java:95)

at com.teradata.jdbc.jdbc_4.TDSession.(TDSession.java:209)

at com.teradata.jdbc.jdk6.JDK6_SQL_Connection.(JDK6_SQL_Connection.java:30)

at com.teradata.jdbc.jdk6.JDK6ConnectionFactory.constructConnection(JDK6ConnectionFactory.java:22)

at com.teradata.jdbc.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:130)

at com.teradata.jdbc.jdbc.ConnectionFactory.createConnection(ConnectionFactory.java:120)

at com.teradata.jdbc.TeraDriver.doConnect(TeraDriver.java:220)

at com.teradata.jdbc.TeraDriver.connect(TeraDriver.java:153)

at com.teradata.datatools.dtp.connectivity.db.teradata.TeradataJDBCConnection.makeConnection(TeradataJDBCConnection.java:276)

at com.teradata.datatools.dtp.connectivity.db.teradata.TeradataJDBCConnection.createConnection(TeradataJDBCConnection.java:121)

at org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(DriverConnectionBase.java:105)

at org.eclipse.datatools.connectivity.DriverConnectionBase.open(DriverConnectionBase.java:54)

at org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.open(JDBCConnection.java:96)

at com.teradata.datatools.dtp.connectivity.db.teradata.TeradataPingFactory.createConnection(TeradataPingFactory.java:36)

at org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(ConnectionFactoryProvider.java:83)

at org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(ConnectionProfile.java:359)

at org.eclipse.datatools.connectivity.ui.PingJob.createTestConnection(PingJob.java:76)

at org.eclipse.datatools.connectivity.ui.PingJob.run(PingJob.java:59)

at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Caused by: java.net.SocketTimeoutException: Connect timed out

at java.net.SocksSocketImpl.readSocksReply(Unknown Source)

at java.net.SocksSocketImpl.connect(Unknown Source)

at java.net.Socket.connect(Unknown Source)

at com.teradata.jdbc.jdbc_4.io.TDNetworkIOIF$ConnectThread.run(TDNetworkIOIF.java:968)
 
"
 
I try to enter a random server to see if we had a difference. Instead of "login time out" we have "login faillure".
 
I try also to open the command-line interface and write "ping <server database>" and that work, 0 lost.
We try to open the database with Teradata SQL Assistant and that work to.  
 
It's just the creation of a datasource with birt which don't work. Anybody can help please ?

I saw we can modify the time for Login_timeout in the web.xlm file in WEB-INF folder, but I don't find the variable "login_timeout" I try so to writte something like that
 
<context-param>
  <param-name>LOGIN_TIMEOUT</param-name>
  <param-value>900</param-value>
 </context-param>
 
But after that we can't restart eclipse.
 
Thanks if someone have any solution.

Hi All,
one of my customer sent me a query generate by JDBC driver 15.00.00.20 to get some metadata. the execution of the query is not performant. I analyse the query and find that the where condition on databasename and tablename are write with LIKE (below I report only the where condition part of the query):
    WHERE t.TableKind IN ('O','T','V')
        AND  t.DatabaseName (NOT CASESPECIFIC) LIKE TRIM(TRAILING   FROM 'Q_TC0_KPE_KPI') (NOT CASESPECIFIC)
        AND  t.TableName (NOT CASESPECIFIC) LIKE TRIM(TRAILING    FROM 'RET_ABBINAMENTO_CAMPO') (NOT CASESPECIFIC)
   
With this where condition TERADATA optimization generate not a good plan even if we define the correspondant stats on where condition columns (as you know, if we use like TD cannot use the stats information).
I change the quey simply substituing the LIKE operator with = (equal) operator:
    WHERE t.TableKind IN ('O','T','V')
        AND  t.DatabaseName (NOT CASESPECIFIC) = TRIM(TRAILING   FROM 'Q_TC0_KPE_KPI') (NOT CASESPECIFIC)
        AND  t.TableName (NOT CASESPECIFIC) = TRIM(TRAILING    FROM 'RET_ABBINAMENTO_CAMPO') (NOT CASESPECIFIC)
In this way I can run the query with a very short elapsed (with the original version the query never end because in the plan we have a product join between 2 big spool !).
Is there a way to modify the query generate by JDBC driver ?
Why the driver use LIKE instead of '=' ?
thank you very match.
 

For Teradata Aster, we can use SQL-H to pull data from Hadoop to Aster.
After some searching, I am still not able to find any documentation (syntax details, etc.).
Does anyone have a link to official TD doc?
 
thanks

Hello,
I'm new to the forum.
I am trying to connect to Teradata Database via Teradata ODBC in Excel 2013 (32 bit).
When I click on the Teradata DSN I keep on getting the following message : [Teradata][ODBC Teradata Driver] Not enough information to log on
The same DSN works fine if I use it to connect to Teradata via SQL Assistant.
Has anyone ran across this issue and a recommended fix ?
THanks,
Faizal

Hi All,
Trying to connect to Teradata by using Eclipse Kepler. By testing connection I am getting the msg that ping succeeded. Once I proceed with connection  I am getting the following error msg - "Error creating SQL Model Connection connection to TeraS. (Error: com.teradata.datatools.dao.TeradataCatalogDAO cannot be cast to com.teradata.datatools.dao.CatalogDAO)
com.teradata.datatools.dao.TeradataCatalogDAO cannot be cast to com.teradata.datatools.dao.CatalogDAO"
Teradata version 14
 

Hello,  I am using a Data Virtualization tool, Teiid Designer, to create a teradata "source model" which is fetching metadata for each table I select for the model.  This connectivity is supported using JDBC connection URL  "jdbc:teradata://database/tmode=ANSI".  I have tried the Teradata 13 and 15 JDBC drivers with associated jar files and registered class:  terajdbc4.jar, tdgssconfig.jar, com.teradata.jdbc.TeraDriver. 
The issue we are having is that we are experiencing a >30 sec wait/processing time between each selection and we have many many selections potentially.  This step should only fetch table metadata, not running table data query.  For db2 jdbc connection and import of table metadata, there is zero wait for us so I am wondering if anyone has any ideas on how to tune the teradata jdbc connection so the process is faster.
Any help would be appreciated.

Hello all,
I have an intersting dilema. We need to create some UDFs which call a C program. This C program will perform some processing on the incoming data and then perform a lookup into a Teradata table. The data will come back and the UDF will in turn go back to the SQL and then perform the same function for the next row.
My concern is that as this is processing for each row, opening and closing the database connection to get a lookup value is going to be very slow. Is there any way this UDF can keep a connection open?
select my_udf_c_call(first_name) from my_multi_million_row_table
In the SQL above, the udf is called my_udf_c_call. The column "first_name" from the table "my_multi_million_row_table" is passed into the C code. This C code in turns does some processing in C, but then also need to make a call to Teradata to pull back some information. Is there any way to keep the db connection open as the 2nd, 3rd, and subsequent rows are processed?
Regards, Jim
 

Please help.  Vhari, you helped me on this in the past and I'm hoping you can help here as well.
 
I've actually got this working last year, however we have moved to a new server , new version of perl, and now I'm having trouble getting the DBD::ODBC module installed.  I've done the exact same steps as before, with the exception this time of being root.  So, I've installed the latest Teradata package and set the environmental variables:
 
ODBCHOME - /opt/teradata/client/14.10/odbc_64
ODBCINI - /opt/teradata/client/ODBC_64/odbc.ini
 
I then update the Makefile.PL file:
 
                $myodbc = 'intersolve'
                                  if !$myodbc && -f "$odbchome/include/qeodbc.h";
As follows:
                 $myodbc = 'intersolve'
                                  if !$myodbc && -f "$odbchome/include/sqlunx.h";
Move the updated lines before this line:
                 if (!$myodbc && ($opt_x || $ENV{PERL_DBD_ODBC_PREFER_UNIXODBC})) {
                        ($myodbc, $odbclibdir) = find_unixodbc($odbchome);
                 } else {
 
 
In addition, replace the following block:
                 print {$sqlhfh} qq{#include <qeodbc.h>\n};
                                  if (-f "$odbcincdir/sql.h") {
                                                   print "You seem to have the official header files.\n";
                                                   $opts{INC} .= " -I$odbcincdir";
                                                   print {$sqlhfh} qq{#include <sql.h>\n#include <sqltypes.h>\n#include <sqlext.h>\n};
With this update:
                 $opts{DEFINE} = "";
                 if (-f "$odbchome/include/sql.h"){
                                  print "You seem to have the official header files.\n";
                                  $opts{INC} .= " -I$odbchome/include";
                                  $opts{LIBS} = "-L$odbclibdir -lodbc";
                                  print {$sqlhfh} qq{#include <sql.h>\n#include <sqltypes.h>\n#include <sqlext.h>\n#include <sqlucode.h>\n};    
 
Then I run the Makefile.PL
 

# perl Makefile.PL

**********

        Remember to actually *READ* the README file!

        And re-read it if you have any problems.

**********

OSNAME: linux

LANG: en_US (LANG=en_US)

ODBCHOME: /opt/teradata/client/14.10/odbc_64

LD_LIBRARY_PATH: /opt/teradata/client/14.00/odbc_64/lib:/opt/teradata/client/14.00/odbc_64/lib64:/opt/teradata/teragss/linux-x8664/14.00.03.02/lib:/opt/teradata/client/14.00/lib:/opt/teradata/client/14.00/tbuild/lib:/usr/lib:/usr/lib64

DBROOT:

WINDIR:

II_SYSTEM:

Perl: 5.010001

ExtUtils::MakeMaker: 6.55_02

Command line options:

  u! = undef

  w! = undef

  e! = undef

  g! = 0

  x! = undef

  o=s =

You are using a Perl configured with threading enabled.

Please read the warnings in DBI about this.

You should also be aware that on non-Windows platforms ODBC drivers come

in two forms, thread-safe and non-thread-safe drivers and you may need

to make sure you are using the right one.

Press return to continue...

Looking for odbc_config in : /opt/teradata/client/ODBC_64

Looking for odbc_config at /opt/teradata/client/ODBC_64/bin/odbc_config

Looking for odbc_config in (PATH) /sbin:/bin:/usr/sbin:/usr/bin

  odbc_config not found

Looking for iodbc-config in PATH /sbin:/bin:/usr/sbin:/usr/bin

  iodbc_config not found

odbc_config not found - ok, there are other things I can do

Still trying to guess ODBCHOME - looking for headers now

  trying /opt/teradata/client/ODBC_64/include

  Found sql.h, sqlext.h, sqltypes.h in /opt/teradata/client/ODBC_64/include

Using ODBCHOME /opt/teradata/client/ODBC_64

This looks like a intersolve type of driver manager.

You seem to have the official header files.

Using DBI 1.633 (for perl 5.010001 on x86_64-linux-thread-multi) installed in /usr/local/lib64/perl5/auto/DBI/

Using DBI 1.633 (for perl 5.010001 on x86_64-linux-thread-multi) installed in /usr/local/lib64/perl5/auto/DBI/

Writing Makefile for DBD::ODBC

The DBD::ODBC tests will use these values for the database connection:

    DBI_DSN=dbi:ODBC:mydsn     e.g. dbi:ODBC:demo

    DBI_USER=username

    DBI_PASS=password

And Now the Make and Make Test

# make

Skip blib/lib/DBD/ODBC.pm (unchanged)

gcc -c   -I. -I/opt/teradata/client/14.10/odbc_64/include -I/usr/local/lib64/perl5/auto/DBI -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic   -DVERSION=\"1.48\" -DXS_VERSION=\"1.48\" -fPIC "-I/usr/lib64/perl5/CORE"  ConvertUTF.c

gcc -c   -I. -I/opt/teradata/client/14.10/odbc_64/include -I/usr/local/lib64/perl5/auto/DBI -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic   -DVERSION=\"1.48\" -DXS_VERSION=\"1.48\" -fPIC "-I/usr/lib64/perl5/CORE"  ODBC.c

./ODBC.xsi: In function 'XS_DBD__ODBC__db__login':

./ODBC.xsi:96: warning: unused variable 'p'

./ODBC.xsi:95: warning: unused variable 'u'

ODBC.c: In function 'XS_DBD__ODBC__st_odbc_rows':

ODBC.c:1321: warning: unused variable 'targ'

ODBC.c:1320: warning: unused variable 'RETVAL'

ODBC.xs: In function 'XS_DBD__ODBC__st_odbc_getdiagrec':

ODBC.xs:60: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'SQLCHAR *'

ODBC.xs:62: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'SQLCHAR *'

ODBC.xs: In function 'XS_DBD__ODBC__st_odbc_getdiagfield':

ODBC.xs:125: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'SQLCHAR *'

ODBC.xs: In function 'XS_DBD__ODBC__db_odbc_getdiagrec':

ODBC.xs:289: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'SQLCHAR *'

ODBC.xs:291: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'SQLCHAR *'

ODBC.xs: In function 'XS_DBD__ODBC__db_odbc_getdiagfield':

ODBC.xs:355: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'SQLCHAR *'

ODBC.xs: In function 'XS_DBD__ODBC__dr_data_sources':

ODBC.xs:511: warning: pointer targets in passing argument 1 of 'strcpy' differ in signedness

/usr/include/bits/string3.h:103: note: expected 'char * __restrict__' but argument is of type 'UCHAR *'

ODBC.xs:531: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'UCHAR *'

gcc -c   -I. -I/opt/teradata/client/14.10/odbc_64/include -I/usr/local/lib64/perl5/auto/DBI -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic   -DVERSION=\"1.48\" -DXS_VERSION=\"1.48\" -fPIC "-I/usr/lib64/perl5/CORE"  dbdimp.c

dbdimp.c: In function 'odbc_db_login6':

dbdimp.c:1029: warning: pointer targets in passing argument 3 of 'SQLDriverConnect' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1803: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1029: warning: pointer targets in passing argument 5 of 'SQLDriverConnect' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1803: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1136: warning: pointer targets in passing argument 2 of 'SQLConnect' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:639: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1136: warning: pointer targets in passing argument 4 of 'SQLConnect' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:639: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1136: warning: pointer targets in passing argument 6 of 'SQLConnect' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:639: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c: In function 'dbd_error2':

dbdimp.c:1335: warning: pointer targets in passing argument 1 of 'strcpy' differ in signedness

/usr/include/bits/string3.h:103: note: expected 'char * __restrict__' but argument is of type 'SQLCHAR *'

dbdimp.c:1336: warning: pointer targets in passing argument 1 of 'strcpy' differ in signedness

/usr/include/bits/string3.h:103: note: expected 'char * __restrict__' but argument is of type 'SQLCHAR *'

dbdimp.c:1373: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'SQLCHAR *'

dbdimp.c:1374: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'SQLCHAR *'

dbdimp.c:1396: warning: pointer targets in passing argument 1 of 'strcat' differ in signedness

/usr/include/bits/string3.h:142: note: expected 'char * __restrict__' but argument is of type 'SQLCHAR *'

dbdimp.c:1397: warning: pointer targets in passing argument 1 of 'strcat' differ in signedness

/usr/include/bits/string3.h:142: note: expected 'char * __restrict__' but argument is of type 'SQLCHAR *'

dbdimp.c:1397: warning: pointer targets in passing argument 2 of 'strcat' differ in signedness

/usr/include/bits/string3.h:142: note: expected 'const char * __restrict__' but argument is of type 'SQLCHAR *'

dbdimp.c:1398: warning: pointer targets in passing argument 1 of 'strcat' differ in signedness

/usr/include/bits/string3.h:142: note: expected 'char * __restrict__' but argument is of type 'SQLCHAR *'

dbdimp.c:1400: warning: pointer targets in passing argument 5 of 'imp_xxh->com.std.dbistate->set_err_char' differ in signedness

dbdimp.c:1400: note: expected 'const char *' but argument is of type 'SQLCHAR *'

dbdimp.c:1400: warning: pointer targets in passing argument 6 of 'imp_xxh->com.std.dbistate->set_err_char' differ in signedness

dbdimp.c:1400: note: expected 'const char *' but argument is of type 'SQLCHAR *'

dbdimp.c:1403: warning: pointer targets in passing argument 5 of 'imp_xxh->com.std.dbistate->set_err_char' differ in signedness

dbdimp.c:1403: note: expected 'const char *' but argument is of type 'SQLCHAR *'

dbdimp.c:1403: warning: pointer targets in passing argument 6 of 'imp_xxh->com.std.dbistate->set_err_char' differ in signedness

dbdimp.c:1403: note: expected 'const char *' but argument is of type 'SQLCHAR *'

dbdimp.c: In function 'odbc_st_tables':

dbdimp.c:1759: warning: pointer targets in passing argument 2 of 'SQLTables' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:834: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1759: warning: pointer targets in passing argument 4 of 'SQLTables' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:834: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1759: warning: pointer targets in passing argument 6 of 'SQLTables' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:834: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1759: warning: pointer targets in passing argument 8 of 'SQLTables' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:834: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c: In function 'odbc_st_primary_keys':

dbdimp.c:1885: warning: pointer targets in passing argument 2 of 'SQLPrimaryKeys' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1998: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1885: warning: pointer targets in passing argument 4 of 'SQLPrimaryKeys' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1998: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1885: warning: pointer targets in passing argument 6 of 'SQLPrimaryKeys' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1998: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c: In function 'dbd_st_statistics':

dbdimp.c:1957: warning: pointer targets in passing argument 2 of 'SQLStatistics' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:828: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1957: warning: pointer targets in passing argument 4 of 'SQLStatistics' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:828: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:1957: warning: pointer targets in passing argument 6 of 'SQLStatistics' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:828: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c: In function 'odbc_st_prepare_sv':

dbdimp.c:2160: warning: pointer targets in passing argument 2 of 'SQLPrepare' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:768: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c: In function 'odbc_st_execute':

dbdimp.c:2863: warning: pointer targets in passing argument 2 of 'SQLExecDirect' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:674: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:2921: warning: pointer targets in assignment differ in signedness

dbdimp.c: In function 'rebind_param':

dbdimp.c:3994: warning: pointer targets in assignment differ in signedness

dbdimp.c:4000: warning: pointer targets in assignment differ in signedness

dbdimp.c: In function 'odbc_db_STORE_attrib':

dbdimp.c:4969: warning: pointer targets in passing argument 6 of 'SQLGetDiagRec' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:733: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c: In function 'odbc_st_FETCH_attrib':

dbdimp.c:5342: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'UCHAR *'

dbdimp.c:5386: warning: pointer targets in passing argument 2 of 'SQLGetCursorName' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:706: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c: In function 'odbc_get_special_columns':

dbdimp.c:5758: warning: pointer targets in passing argument 3 of 'SQLSpecialColumns' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:821: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:5758: warning: pointer targets in passing argument 5 of 'SQLSpecialColumns' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:821: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:5758: warning: pointer targets in passing argument 7 of 'SQLSpecialColumns' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:821: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c: In function 'odbc_get_foreign_keys':

dbdimp.c:5828: warning: pointer targets in passing argument 2 of 'SQLForeignKeys' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1963: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:5828: warning: pointer targets in passing argument 4 of 'SQLForeignKeys' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1963: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:5828: warning: pointer targets in passing argument 6 of 'SQLForeignKeys' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1963: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:5828: warning: pointer targets in passing argument 8 of 'SQLForeignKeys' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1963: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:5828: warning: pointer targets in passing argument 10 of 'SQLForeignKeys' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1963: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:5828: warning: pointer targets in passing argument 12 of 'SQLForeignKeys' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sqlext.h:1963: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c: In function 'odbc_col_attributes':

dbdimp.c:6121: warning: pointer targets in passing argument 1 of 'strlen' differ in signedness

/usr/include/string.h:399: note: expected 'const char *' but argument is of type 'unsigned char *'

dbdimp.c:6121: warning: pointer targets in passing argument 2 of 'Perl_newSVpv' differ in signedness

/usr/lib64/perl5/CORE/proto.h:2210: note: expected 'const char *' but argument is of type 'unsigned char *'

dbdimp.c: In function 'odbc_db_columns':

dbdimp.c:6320: warning: pointer targets in passing argument 2 of 'SQLColumns' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:632: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:6320: warning: pointer targets in passing argument 4 of 'SQLColumns' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:632: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:6320: warning: pointer targets in passing argument 6 of 'SQLColumns' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:632: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:6320: warning: pointer targets in passing argument 8 of 'SQLColumns' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:632: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c: In function 'get_row_diag':

dbdimp.c:7473: warning: pointer targets in passing argument 4 of 'SQLGetDiagRec' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:733: note: expected 'SQLCHAR *' but argument is of type 'char *'

dbdimp.c:7473: warning: pointer targets in passing argument 6 of 'SQLGetDiagRec' differ in signedness

/opt/teradata/client/14.10/odbc_64/include/sql.h:733: note: expected 'SQLCHAR *' but argument is of type 'char *'

gcc -c   -I. -I/opt/teradata/client/14.10/odbc_64/include -I/usr/local/lib64/perl5/auto/DBI -D_REENTRANT -D_GNU_SOURCE -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic   -DVERSION=\"1.48\" -DXS_VERSION=\"1.48\" -fPIC "-I/usr/lib64/perl5/CORE"  unicode_helper.c

Running Mkbootstrap for DBD::ODBC ()

chmod 644 ODBC.bs

rm -f blib/arch/auto/DBD/ODBC/ODBC.so

gcc  -shared -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic ConvertUTF.o ODBC.o dbdimp.o unicode_helper.o  -o blib/arch/auto/DBD/ODBC/ODBC.so     \

           -L/opt/teradata/client/14.10/odbc_64/lib -lodbc      \

chmod 755 blib/arch/auto/DBD/ODBC/ODBC.so

cp ODBC.bs blib/arch/auto/DBD/ODBC/ODBC.bs

chmod 644 blib/arch/auto/DBD/ODBC/ODBC.bs

Manifying blib/man3/DBD::ODBC.3pm

# make test

PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM""-e""test_harness(0, 'blib/lib', 'blib/arch')" t/*.t

t/01base.t ................... ok

t/02simple.t ................. Failed 63/65 subtests

t/03dbatt.t .................. Failed 27/29 subtests

t/05meth.t ................... Failed 12/13 subtests

t/07bind.t ................... Failed 24/25 subtests

t/08bind2.t .................. Failed 3/5 subtests

t/09multi.t .................. Failed 4/7 subtests

t/10handler.t ................ Failed 9/10 subtests

t/12blob.t ................... Failed 23/24 subtests

t/20SqlServer.t .............. Failed 66/67 subtests

t/30Oracle.t ................. Failed 3/4 subtests

t/40UnicodeRoundTrip.t ....... Failed 61/61 subtests

t/41Unicode.t ................ Failed 55/55 subtests

t/45_unicode_varchar.t ....... No subtests run

t/50_odbc_utf8_on.t .......... Failed 3/3 subtests

t/70execute_array_dbi.t ...... #

#

# NOTE: This tests execute_array and execute_for_fetch using DBI's version and not the native DBD::ODBC execute_for_fetch. It should work as it is using nothing special in DBD::ODBC other than the normal methods.

t/70execute_array_dbi.t ...... No subtests run

t/70execute_array_native.t ... No subtests run

t/80_odbc_diags.t ............ No subtests run

t/82_table_info.t ............ No subtests run

t/87_odbc_lob_read.t ......... No subtests run

t/90_trace_flags.t ........... No subtests run

t/odbc_describe_parameter.t .. Failed 16/17 subtests

t/pod-coverage.t ............. ok

t/pod.t ...................... ok

t/rt_38977.t ................. Failed 13/14 subtests

t/rt_39841.t ................. Failed 27/28 subtests

t/rt_39897.t ................. Failed 5/6 subtests

t/rt_43384.t ................. Failed 7/8 subtests

t/rt_46597.t ................. Failed 5/6 subtests

t/rt_50852.t ................. Failed 4/5 subtests

t/rt_57957.t ................. Failed 7/8 subtests

t/rt_59621.t ................. Failed 10/11 subtests

t/rt_61370.t ................. All 1 subtests passed

t/rt_62033.t ................. All 1 subtests passed

t/rt_63550.t ................. All 1 subtests passed

t/rt_78838.t ................. All 1 subtests passed

t/rt_79190.t ................. All 1 subtests passed

t/rt_79397.t ................. All 1 subtests passed

t/rt_81911.t ................. All 1 subtests passed

t/rt_null_nvarchar.t ......... Failed 8/8 subtests

t/sql_type_cast.t ............ Failed 15/16 subtests

Test Summary Report

-------------------

t/02simple.t               (Wstat: 139 Tests: 2 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 65 tests but ran 2.

t/03dbatt.t                (Wstat: 139 Tests: 2 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 29 tests but ran 2.

t/05meth.t                 (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 13 tests but ran 1.

t/07bind.t                 (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 25 tests but ran 1.

t/08bind2.t                (Wstat: 139 Tests: 2 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 5 tests but ran 2.

t/09multi.t                (Wstat: 139 Tests: 3 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 7 tests but ran 3.

t/10handler.t              (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 10 tests but ran 1.

t/12blob.t                 (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 24 tests but ran 1.

t/20SqlServer.t            (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 67 tests but ran 1.

t/30Oracle.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 4 tests but ran 1.

t/40UnicodeRoundTrip.t     (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 61 tests but ran 0.

t/41Unicode.t              (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 55 tests but ran 0.

t/45_unicode_varchar.t     (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/50_odbc_utf8_on.t        (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 3 tests but ran 0.

t/70execute_array_dbi.t    (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/70execute_array_native.t (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/80_odbc_diags.t          (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/82_table_info.t          (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/87_odbc_lob_read.t       (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/90_trace_flags.t         (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/odbc_describe_parameter.t (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 17 tests but ran 1.

t/rt_38977.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 14 tests but ran 1.

t/rt_39841.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 28 tests but ran 1.

t/rt_39897.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 6 tests but ran 1.

t/rt_43384.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 8 tests but ran 1.

t/rt_46597.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 6 tests but ran 1.

t/rt_50852.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 5 tests but ran 1.

t/rt_57957.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 8 tests but ran 1.

t/rt_59621.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 11 tests but ran 1.

t/rt_61370.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/rt_62033.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/rt_63550.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/rt_78838.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/rt_79190.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/rt_79397.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/rt_81911.t               (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: No plan found in TAP output

t/rt_null_nvarchar.t       (Wstat: 139 Tests: 0 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 8 tests but ran 0.

t/sql_type_cast.t          (Wstat: 139 Tests: 1 Failed: 0)

  Non-zero wait status: 139

  Parse errors: Bad plan.  You planned 16 tests but ran 1.

Files=41, Tests=43, 34 wallclock secs ( 0.19 usr  0.11 sys +  4.44 cusr  0.96 csys =  5.70 CPU)

Result: FAIL

Failed 38/41 test programs. 0/43 subtests failed.

make: *** [test_dynamic] Error 255

Any ideas what is going wrong here?  

unable to connect to Teradata server from ssis

Hi All ,
I m trying to connect to TERADATA server from ssis using .Net Providers\.Net data provider for TERADATA.
After giving the server name and credentials i m getting the below error.
 
 
Test connection failed because of an error in initializing the provider.[.Net data provider for teradata][100002] can not create the connection wiyhin the time specified.
 
I have googled a lot but did not find any correct solution.I m struggling from last 2 days.
Could you please help me in this.
Thanks in Advance.
 
GTREDDY