All Forums Tools
tddev1984 9 posts Joined 09/13
05 Jun 2014
TPT load failure - Please suggest

Dear Experts,
We are facing a failure during loading a file into a table using TPT utility. We loaded files a lot of times successfully but this time, its a very huge file (>100 GB) probably causing the issue.
Errror Observed :
FILE_READER: TPT19350 I/O error on file '/dev/aps/file123.dat.
FILE_READER: TPT19417 pmRead failed. Buffer overflow (17)
FILE_READER: TPT19305 Fatal error reading data.
I did some research based on the error codes but couldn't get anything solid to narrow down to the root cause.
Could you please throw some light on what the actual issue could be ?

feinholz 1234 posts Joined 05/08
05 Jun 2014

What is the version of TPT?
What is the platform?
 

--SteveF

tddev1984 9 posts Joined 09/13
25 Jun 2014

Hi , Sorry i was out for a couple of weeks and couldn't respond.
The teradata client version is 13.0.
Platform : AIX
We are calling the TPT in a shell script with parameters.
We loaded 100s of files successfully without any issues till date. I think its the colume of the huge file (>100 GB) thats causing the issue.
 

feinholz 1234 posts Joined 05/08
25 Jun 2014

What exact version of 13.0?
We have released several patches since its GCA version.
And 13.0 is not an officially supported version of TPT, so my first response is for you to update TPT to the latest patch.
Then re-run the job.
If there is still an issue, let me know and we can dig further.
 

--SteveF

siddharth82 1 post Joined 05/09
27 Jun 2014

We are using the TPT version 13.00.00.02 and facing the same issue while loading 320GB file. Immediate help is required here.

feinholz 1234 posts Joined 05/08
27 Jun 2014

Please upgrade to the latest efix version and try again.
If the problem persists, let me know (and let me know what version you used).
 

--SteveF

feinholz 1234 posts Joined 05/08
27 Jun 2014

Please post the script you are using.
Thanks!

--SteveF

tddev1984 9 posts Joined 09/13
30 Jun 2014

Hi Steve, Thanks for your responses.
I have a general question. When loads for smaller files (upto 80-90 GB) are going through successfully using the same scripts and the same version of TPT, it is indicating the the script and version are actually working.  If the framework works for none of the loads we can assume that the version doesn't support the load process.
Could you please share your thoughts on the version/patch impacts only higher volumes?  Also could you please share if addressing bulk volumes was one of the considerations for the efix ?
Thanks much!
 

feinholz 1234 posts Joined 05/08
30 Jun 2014

We fix issues all of the time.
We are currently in development for the 15.10 release.
This means that bug fixes have occurred for 13.0, 13.10, 14.0, 14.10, and 15.0.
When bugs are found in newer releases, we ofte back-ship the fixes to older releases.
It is nearly impossible for me to determine whether any of the 13.0 efixes will take care of the problem you are experiencing.
However, it does not make sense to have you generate traces and logs for us to look at because the code has most likely changed so much between the version you have and the most recent efix.
 
Yes, you are correct that if the load process works on an 80GB file, it should work on a 300GB file. But I have seen stranger things happen.
 
That particular error usually means the row encountered is larger than our block size. On the surface, it does not make much sense, but the file might have a bad row in it and we are having trouble processing it. It is possible that we made changes in one of the efixes to handle it better (not continue, but maybe provide a better error message?
 

--SteveF

WB255000 11 posts Joined 11/09
23 Jul 2014

Hi Experts.
I have a problen which I think is also a version issue.
I detail the problem (I have posted it in other topic too):

TPT 14.10 problems loading data from SQL Server using TPT Wizard

===============================================================================

Recently I made an version upgrade to TTU 14.10 but I'm having some problems that I didn't have in 13.10.
I tried to use the TPT Wizard to create a load Job to retrieve data from "SQL Server", but the Log File says that no rows are exported. That is weird because If I submit the SQL in the source, It returns data.
Do you know if there are some bugs in this version about that?
I copy the TPT JOB and the log, If for some case you need them
 
Script
======
/* 1 */ 
/* 2 */ 
/* 3 */  USING CHARACTER SET UTF8
/* 4 */  DEFINE JOB "Carga_tablas_Paradata"
/* 5 */  (
/* 6 */   DEFINE OPERATOR "W_1_o_Carga_tablas_Paradata"
/* 7 */   TYPE LOAD
/* 8 */   SCHEMA *
/* 9 */   ATTRIBUTES
/* 10 */   (
/* 11 */    VARCHAR "UserName",
/* 12 */    VARCHAR "UserPassword",
/* 13 */    VARCHAR "LogTable",
/* 14 */    VARCHAR "TargetTable",
/* 15 */    INTEGER "BufferSize",
/* 16 */    INTEGER "ErrorLimit",
/* 17 */    INTEGER "MaxSessions",
/* 18 */    INTEGER "MinSessions",
/* 19 */    INTEGER "TenacityHours",
/* 20 */    INTEGER "TenacitySleep",
/* 21 */    VARCHAR "AccountID",
/* 22 */    VARCHAR "DateForm",
/* 23 */    VARCHAR "ErrorTable1",
/* 24 */    VARCHAR "ErrorTable2",
/* 25 */    VARCHAR "NotifyExit",
/* 26 */    VARCHAR "NotifyExitIsDLL",
/* 27 */    VARCHAR "NotifyLevel",
/* 28 */    VARCHAR "NotifyMethod",
/* 29 */    VARCHAR "NotifyString",
/* 30 */    VARCHAR "PauseAcq",
/* 31 */    VARCHAR "PrivateLogName",
/* 32 */    VARCHAR "TdpId",
/* 33 */    VARCHAR "TraceLevel",
/* 34 */    VARCHAR "WorkingDatabase"
/* 35 */   );
/* 36 */ 
/* 37 */   DEFINE SCHEMA "W_0_s_Carga_tablas_Paradata"
/* 38 */   (
/* 39 */    "Lote_id" INTEGER,
/* 40 */    "Lote_descripcion" VARCHAR(100),
/* 41 */    "Lote_Cliente" VARCHAR(20),
/* 42 */    "dedu_fecha_proceso" CHARACTER(23),
/* 43 */    "dedu_cantidad_registros" BIGINT,
/* 44 */    "dedu_veto_total" BIGINT,
/* 45 */    "dedu_cliente_vigente_tot" BIGINT
/* 46 */   );
/* 47 */ 
/* 48 */   DEFINE OPERATOR "W_0_o_Carga_tablas_Paradata"
/* 49 */   TYPE ODBC
/* 50 */   SCHEMA "W_0_s_Carga_tablas_Paradata"
/* 51 */   ATTRIBUTES
/* 52 */   (
/* 53 */    VARCHAR "UserName",
/* 54 */    VARCHAR "UserPassword",
/* 55 */    VARCHAR "SelectStmt",
/* 56 */    VARCHAR "PrivateLogName",
/* 57 */    VARCHAR "DSNName",
/* 58 */    VARCHAR "ConnectString",
/* 59 */    VARCHAR "TruncateData"
/* 60 */   );
/* 61 */ 
/* 62 */   APPLY
/* 63 */    (
/* 64 */     'INSERT INTO P_DW_PROSPECTOS_TEMP_TABLES.mktd_lotes_v1 (Lote_id,Lote_descripcion,Lote_Cliente,dedu_fecha_proc eso,dedu_cantidad_registros,dedu_veto_total,dedu_clien te_vigente_tot) VALUES (:Lote_id,:Lote_descripcion,:Lote_Cliente,: dedu_fecha_proceso,:dedu_cantidad_registros,: dedu_veto_total,:dedu_cliente_vigente_tot);'
/* 65 */    )
/* 66 */   TO OPERATOR
/* 67 */   (
/* 68 */    "W_1_o_Carga_tablas_Paradata"[1]
/* 69 */ 
/* 70 */    ATTRIBUTES
/* 71 */    (
/* 72 */     "UserName" = 'L0607460',
/* 73 */     "UserPassword" = 'XXXXXXXXXX',
/* 74 */     "LogTable" = 'P_DW_PROSPECTOS_TEMP_TABLES.mktd_lotes_v1_log',
/* 75 */     "TargetTable" = 'P_DW_PROSPECTOS_TEMP_TABLES.mktd_lotes_v1',
/* 76 */     "TdpId" = '10.0.xx.xx'
/* 77 */    )
/* 78 */   )
/* 79 */   SELECT * FROM OPERATOR
/* 80 */   (
/* 81 */    "W_0_o_Carga_tablas_Paradata"[1]
/* 82 */ 
/* 83 */    ATTRIBUTES
/* 84 */    (
/* 85 */     "UserName" = 'XXXXXXXXXXXXXX',
/* 86 */     "UserPassword" = 'XXXXXXXXXXXXXX',
/* 87 */     "SelectStmt" = 'SELECT Lote_id,Lote_descripcion,Lote_Cliente,dedu_fecha_proce so,dedu_cantidad_registros,dedu_veto_total,dedu_client e_vigente_tot FROM MKTD_DEDUPLICACION.dbo.Lotes;',
/* 88 */     "DSNName" = 'paradata'
/* 89 */    )
/* 90 */   );
/* 91 */  ); 
 
LOG FILE:
===========
Teradata Parallel Transporter Version 14.10.00.04
Job log: C:\Archivos de programa\Teradata\client\14.10\Teradata Parallel Transporter/logs/LOTE_V1_2-31.out
Job id is LOTE_V1_2-31, running on GAL082262
Teradata Parallel Transporter Load Operator Version 14.10.00.04
W_1_o_Carga_tablas_Paradata: private log not specified
Teradata Parallel Transporter ODBC Operator Version 14.10.00.04
W_0_o_Carga_tablas_Paradata: private log not specified
W_0_o_Carga_tablas_Paradata: connecting sessions
W_0_o_Carga_tablas_Paradata: TPT17176: Info: Message received from ODBC driver:
STATE=01000, CODE=5701,
MSG='[Microsoft][ODBC SQL Server Driver][SQL Server]Changed database context to 'MKTD_DEDUPLICACION'.'
W_0_o_Carga_tablas_Paradata: TPT17176: Info: Message received from ODBC driver:
STATE=01000, CODE=5703,
MSG='[Microsoft][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.'
W_0_o_Carga_tablas_Paradata: TPT17175: Warning: Message received from ODBC driver:
STATE=S1092, CODE=0,
MSG='[Microsoft][ODBC SQL Server Driver]Identificador de opción o atributo no válido'
W_1_o_Carga_tablas_Paradata: connecting sessions
W_1_o_Carga_tablas_Paradata: preparing target table
W_1_o_Carga_tablas_Paradata: entering Acquisition Phase
W_0_o_Carga_tablas_Paradata: sending SELECT request
W_0_o_Carga_tablas_Paradata: data retrieval complete
W_0_o_Carga_tablas_Paradata: Total Rows Exported:  0
W_1_o_Carga_tablas_Paradata: entering Application Phase
W_1_o_Carga_tablas_Paradata: Statistics for Target Table:  'P_DW_PROSPECTOS_TEMP_TABLES.mktd_lotes_v1'
W_1_o_Carga_tablas_Paradata: Total Rows Sent To RDBMS:      0
W_1_o_Carga_tablas_Paradata: Total Rows Applied:            0
W_1_o_Carga_tablas_Paradata: Total Rows in Error Table 1:   0
W_1_o_Carga_tablas_Paradata: Total Rows in Error Table 2:   0
W_1_o_Carga_tablas_Paradata: Total Duplicate Rows:          0
W_0_o_Carga_tablas_Paradata: disconnecting sessions
W_1_o_Carga_tablas_Paradata: disconnecting sessions
W_0_o_Carga_tablas_Paradata: Total processor time used = '0.859375 Second(s)'
W_0_o_Carga_tablas_Paradata: Start : Tue Jul 22 18:28:37 2014
W_0_o_Carga_tablas_Paradata: End   : Tue Jul 22 18:29:00 2014
W_1_o_Carga_tablas_Paradata: Total processor time used = '4.57813 Second(s)'
W_1_o_Carga_tablas_Paradata: Start : Tue Jul 22 18:28:37 2014
W_1_o_Carga_tablas_Paradata: End   : Tue Jul 22 18:29:06 2014
Job step MAIN_STEP terminated (status 4)
Job LOTE_V1_2 completed successfully, but with warning(s).
Job start: Tue Jul 22 18:28:34 2014
Job end:   Tue Jul 22 18:29:06 2014
 
 
Thanks

 

feinholz 1234 posts Joined 05/08
23 Jul 2014

This was a known issue with 64-bit TPT and the Microsoft ODBC driver.
It was fixed in 14.10.00.03.
However, I see that you are using 14.10.00.04, so this is baffling.
I would need you to try the same job with the drivers from DataDirect (TPT is only certified with the drivers from DataDirect).
 

--SteveF

WB255000 11 posts Joined 11/09
24 Jul 2014

Hi.
I tried your suggestion, but It was the same:
===================================================== 
Teradata Parallel Transporter Version 14.10.00.04
Job log: C:\Archivos de programa\Teradata\client\14.10\Teradata Parallel Transporter/logs/Lote_v1_3-34.out
Job id is Lote_v1_3-34, running on GAL082262
Found CheckPoint file: C:/Archivos de programa/Teradata/client/14.10/Teradata Parallel Transporter/tptwizard/objectrepository\\runjobs\Carga_tablas_Paradata\Lote_v1_3\checkpoints\Lote_v1_3LVCP
This is a restart job; it restarts at step MAIN_STEP.
Teradata Parallel Transporter Load Operator Version 14.10.00.04
W_1_o_Carga_tablas_Paradata: private log not specified
Teradata Parallel Transporter ODBC Operator Version 14.10.00.04
W_0_o_Carga_tablas_Paradata: private log not specified
W_0_o_Carga_tablas_Paradata: connecting sessions
W_0_o_Carga_tablas_Paradata: TPT17176: Info: Message received from ODBC driver:
STATE=01000, CODE=5701,
MSG='[Informatica][ODBC SQL Server Driver][SQL Server]Changed database context to 'MKTD_DEDUPLICACION'.'
W_0_o_Carga_tablas_Paradata: TPT17176: Info: Message received from ODBC driver:
STATE=01000, CODE=5703,
MSG='[Informatica][ODBC SQL Server Driver][SQL Server]Changed language setting to us_english.'
W_0_o_Carga_tablas_Paradata: TPT17175: Warning: Message received from ODBC driver:
STATE=S1092, CODE=0,
MSG='[Informatica][ODBC SQL Server Driver]Identificador de opción o atributo no válido'
W_1_o_Carga_tablas_Paradata: connecting sessions
W_1_o_Carga_tablas_Paradata: preparing target table
W_1_o_Carga_tablas_Paradata: entering Acquisition Phase
W_0_o_Carga_tablas_Paradata: sending SELECT request
W_0_o_Carga_tablas_Paradata: data retrieval complete
W_0_o_Carga_tablas_Paradata: Total Rows Exported:  0
W_1_o_Carga_tablas_Paradata: entering Application Phase
W_1_o_Carga_tablas_Paradata: Statistics for Target Table:  'P_DW_PROSPECTOS_TEMP_TABLES.mktd_lotes_v1'
W_1_o_Carga_tablas_Paradata: Total Rows Sent To RDBMS:      0
W_1_o_Carga_tablas_Paradata: Total Rows Applied:            0
W_1_o_Carga_tablas_Paradata: Total Rows in Error Table 1:   0
W_1_o_Carga_tablas_Paradata: Total Rows in Error Table 2:   0
W_1_o_Carga_tablas_Paradata: Total Duplicate Rows:          0
W_1_o_Carga_tablas_Paradata: disconnecting sessions
W_0_o_Carga_tablas_Paradata: disconnecting sessions
W_0_o_Carga_tablas_Paradata: Total processor time used = '0.546875 Second(s)'
W_0_o_Carga_tablas_Paradata: Start : Thu Jul 24 10:15:43 2014
W_0_o_Carga_tablas_Paradata: End   : Thu Jul 24 10:16:05 2014
W_1_o_Carga_tablas_Paradata: Total processor time used = '4.54688 Second(s)'
W_1_o_Carga_tablas_Paradata: Start : Thu Jul 24 10:15:43 2014
W_1_o_Carga_tablas_Paradata: End   : Thu Jul 24 10:16:12 2014
Job step MAIN_STEP terminated (status 4)
Job Lote_v1_3 completed successfully, but with warning(s).
Job start: Thu Jul 24 10:15:38 2014
Job end:   Thu Jul 24 10:16:12 2014
 
 
==================================
 I tried using OLE-Load for creating the TPT Job, which use other operator for connecting to SQL Server and It worked.
 
 

feinholz 1234 posts Joined 05/08
24 Jul 2014

The drivedr indicates it is from "Informatica".
Can you provide some information about that driver?
Is it DataDirect?
Also, when you indicated you used a different operator to connect after using OLE Load to create the job, which operator did you use, and do you know which driver was used in the job?

--SteveF

feinholz 1234 posts Joined 05/08
24 Jul 2014

Ok, just verified with development.
The fix to this problem is in efix #5 (you are running with efix #4).
Please upgrade to 14.10.00.05.
 

--SteveF

WB255000 11 posts Joined 11/09
25 Jul 2014

Hi Feinholz.
Thanks you very much, I'll try using #5 version.
On the Other Hands, I used "DataDirect 6.1 for SQL Server Wire Protocol" this is which appear in my ODBC Drivers List. I suppose Informatica is the driver Provider, if not, I don't know what you meant when you told that I should use DataDirect.

feinholz 1234 posts Joined 05/08
26 Jul 2014

Yes, it is possible that the actual "provider" of the driver is Informatica, even though the drivers themselves are manufactured by DataDirect.
 
I was just trying to make sure because the messages from the driver contained [Informatica] in them, and I needed to make sure they are actually DataDirect drivers.
 
TPT is only certified with drivers from DataDirect.

--SteveF

pyite 9 posts Joined 10/14
30 Oct 2014

Hello, I am receiving the same error when loading using TPT 15.
$LOAD: connecting sessions
$LOAD: preparing target table
$LOAD: entering Acquisition Phase
Job is running in Buffer Mode
Task(APPLY_1[0001]): checkpoint completed, status = Success
Task(SELECT_2[0001]): checkpoint completed, status = Success
ODBC_Operator: sending SELECT request
ODBC_Operator: data retrieval complete
ODBC_Operator: Total Rows Exported:  0
Task(SELECT_2[0001]) ready to checkpoint

Task(SELECT_2[0001]): checkpoint completed, status = Success
Task(APPLY_1[0001]): checkpoint completed, status = Success
Task(SELECT_2[0001]) ready to take the EOD checkpoint

Task(APPLY_1[0001]): checkpoint completed, status = Success
Task(SELECT_2[0001]): checkpoint completed, status = Success
$LOAD: entering Application Phase
$LOAD: Statistics for Target Table:  'DLDPI1DPI_DCFraud.reports'
$LOAD: Total Rows Sent To RDBMS:      0
$LOAD: Total Rows Applied:            0
$LOAD: Total Rows in Error Table 1:   0
$LOAD: Total Rows in Error Table 2:   0
$LOAD: Total Duplicate Rows:          0
TPT_INFRA: TPT02255: Message Buffers Sent/Received = 0, Total Rows Received = 0,
 Total Rows Sent = 0
TPT_INFRA: TPT02255: Message Buffers Sent/Received = 0, Total Rows Received = 0,
 Total Rows Sent = 0
$LOAD: disconnecting sessions
ODBC_Operator: disconnecting sessions
ODBC_Operator: Total processor time used = '0.187201 Second(s)'
ODBC_Operator: Start : Thu Oct 30 13:51:36 2014
ODBC_Operator: End   : Thu Oct 30 13:52:27 2014
$LOAD: Total processor time used = '11.1697 Second(s)'
$LOAD: Start : Thu Oct 30 13:51:35 2014
$LOAD: End   : Thu Oct 30 13:52:34 2014
Job step MAIN_STEP terminated (status 4)
Job pp73577 completed successfully, but with warning(s).
Job start: Thu Oct 30 13:51:31 2014
Job end:   Thu Oct 30 13:52:34 2014
Total available memory:          20000000
Largest allocable area:          20000000
Memory use high water mark:        156280
Free map size:                       1024
Free map use high water mark:          20
Free list use high water mark:          0
Any thoughts?

 

feinholz 1234 posts Joined 05/08
30 Oct 2014

What ODBC driver are you using?
What (exact) TPT version are you running?
The fix to the problem is fixed in 15.00.00.02.
 

--SteveF

pyite 9 posts Joined 10/14
31 Oct 2014

Thanks. Is there a download link to 15.00.00.02? I just downloaded TPT the other day, and it was version 00.
Currently I am using the MS SQL Server driver (trying to get the datadirect driver) -- which I realize is not certified -- however, my understanding is that it should still work, albeit slower.

feinholz 1234 posts Joined 05/08
31 Oct 2014

Talk to your account rep about the download site.
This issue is specific to using the Microsoft SQLServer driver.
(If you had used the DataDirect driver, you would not have seen this problem.)
Thus, even though we do not certify with the MS driver, we will fix issues if they arise.
 

--SteveF

pyite 9 posts Joined 10/14
31 Oct 2014

Thanks Steve, really appreciate it. So just to be clear, despite using the MS driver, the issue is fixed in 02?

feinholz 1234 posts Joined 05/08
31 Oct 2014

Yes.

--SteveF

PAVAN1K 6 posts Joined 09/14
19 Mar 2016

Hi Steve,
I am getting a similar error while loading data from DB2 to Teradata tables. I have odbc db2 dirver 32 bit and my tpt is latest version 15 and it is 32 bit. I am able to create the dsn name for this driver and able to select the data using db2 visualizer(like sql assistant).
Here is the error i am receiving 
"ODBC_Operator: TPT17175: Warning: Message received from ODBC driver:

STATE=S1092, CODE=-99999,

MSG='[IBM][CLI Driver] CLI0133E  Option type out of range. SQLSTATE=S1092'

ODBC_Operator: TPT17128: Error: unable to execute SELECT statement

ODBC_Operator: TPT17101: Fatal error received from ODBC driver:

STATE=42601, CODE=-104,

MSG='[IBM][CLI Driver][DB2] SQL0104N  An unexpected token "," was found followin

g "".  Expected tokens may include:  "<IDENTIFIER>".  SQLSTATE=42601

'" 

 

Could you please suggest me how to resolve this error.

For me, there is a requirement to migrate the db2 data to teradata.

 

Thanks in advance.

Regards,

Pavan

 

Pavan

Fred 1096 posts Joined 08/04
19 Mar 2016

Double-check your SELECT statement syntax, to be sure it is valid for DB2.
 
Note that Teradata does not support use of the IBM driver with the ODBC operator (though it may work). Only the Data Direct ODBC drivers and driver manager are officially supported. Those drivers are packaged with the latest TPT software but you will need to obtain the license key from your Teradata representative.

PAVAN1K 6 posts Joined 09/14
19 Mar 2016

Thanks Fred for the info.
Can we get free data direct odbc driver and driver manager?
I need to test this. I am finding a trail version in the internet. I installed 64 bit. When i trying to connect it is giving again errors like "SG='[DataDirect][ODBC DB2 Wire Protocol driver]Command Not Supported.'". If i correct this again another error is coming.
Is trail version will not work properly. Any idea about this?
 
Thanks
Pavan

Pavan

Fred 1096 posts Joined 08/04
20 Mar 2016

The Teradata-branded Progress DataDirect ODBC drivers are installed with TPT-Base 15.00.00.02 and later eFix (patch) levels and as part of the initial release for 15.10. There is no additional charge to use these drivers, but you must obtain the license key from your Teradata representative. See the 15.10 documentation for more details.
If this is Unix / Linux, check ODBCINST and ODBCINI values. Both the driver manager (specified via ODBCINST) and driver (configured in ODBCINI) must be correct.

feinholz 1234 posts Joined 05/08
21 Mar 2016

A correction to what Fred said above.
DataDirect does not usually provide drivers for the mainframe.
When discussing the DB2 drivers above, no mention was made of the platform.
TPT does work with the DB2 drivers that come with DB2 on z/OS.
Thus, it seems as though the error being reported by the driver is related to a syntax error.

--SteveF

stami27 11 posts Joined 06/09
09 Aug 2016

Hello Steve
We want to upgrade the RDBMS TD 15.10 soon.
Prepared, I have installed the Linux Tools 15.10.01.
...
tdodbc1510-15.10.01.01-1.noarch
tptstream1510-15.10.01.03-1.noarch
tpump1510-15.10.01.02-1.i386
...
My colleagues of the Abinitio development use the  Abinitio version 3.2.5.9.
we have run the Linux TTU's 15.10 in combination with
TD VERSION 15.00.05.12 in use.
Since them, the error in TPT Streamer and Abinitio occurs:
PutBuffer failed.
No record of the load request which found after DBC restart
Type: 1 (0 = TPT err, 1 = DBS err, 2 = CLI err)

With the Linux Tools 15.00 functioning properly
...
tdodbc-15.00.00.03-1.noarch
tptbase1500-15.00.00.04-1.noarch
tptstream1500-15.00.00.04-1.noarch
...

We have opened the Incident RECGWUQ93 (is active, maybe you can see that?),
but other than some trace is little help in sight.
Do you have any idea how to proceed?
Thanks in advance

 

stami27 11 posts Joined 06/09
09 Aug 2016

I forgot to communicate the platform where the TUs are installed:
 cat /proc/version
Linux version 2.6.32-431.11.2.el6.x86_64 (mockbuild@x86-027.build.eng.bos.redhat.com)
(gcc version 4.4.7 20120313 (Red Hat 4.4.7-4) (GCC) ) #1 SMP Mon Mar 3 13:32:45 EST 2014
$

 

feinholz 1234 posts Joined 05/08
09 Aug 2016

What version of TPTAPI have you installed?
What version of CLI?
This sometimes can occur when mismatching components are installed.
 

--SteveF

stami27 11 posts Joined 06/09
09 Aug 2016

This is the complete installation on this machine
$rpm -qa|sort| grep "15.10"
arc1510-15.10.01.01-1.noarch
bteq1510-15.10.01.03-1.i386
cliv21510-15.10.01.04-1.noarch
fastexp1510-15.10.01.03-1.i386
fastld1510-15.10.01.03-1.i386
infinipath-psm-3.0.1-115.1015_open.2.el6.x86_64
jmsaxsmod1510-15.10.01.01-1.noarch
mload1510-15.10.01.05-1.i386
mqaxsmod1510-15.10.01.01-1.noarch
npaxsmod1510-15.10.01.00-1.noarch
piom1510-15.10.01.01-1.noarch
tdicu1510-15.10.01.00-1.noarch
tdodbc1510-15.10.01.01-1.noarch
TeraGSS_linux_x64-15.10.02.04-1.noarch
tptbase1510-15.10.01.03-1.noarch
tptstream1510-15.10.01.03-1.noarch
tpump1510-15.10.01.02-1.i386
$

feinholz 1234 posts Joined 05/08
10 Aug 2016

Since an incident has been opened for this, I will let the GSC handle it for now.
If they need to come to engineering, then I will get involved to help them.
(That message it provided by the DBS when a restart occurs. The job would need to be restarted.)

--SteveF

stami27 11 posts Joined 06/09
11 Aug 2016

Anyway, I thank you.
I have seen, there are some Linux tools with newer version on the Teradata SW Server..
I'll install it first and try again.
GSC recommends in the incident setting environment variable THREADONOFF=1.
That surpised me because in the TD Tools 15.00 it was not set and has nevertheless worked!
 

Apurba93 1 post Joined 08/16
11 Aug 2016

how to invoke command line argument while running mload script in unix system?

Apu

You must sign in to leave a comment.