Hi, I have just started using TPT and was loading one empty table from one environment to another. It was taking longer than usual so I killed the job using 'Kill job' option on TPT screen. However, if I select on that empty table I was loading into, it gives me error like 'Operation not allowed - table is being loaded'. Not sure how do I release that. Any suggestions ? Thanks.
Hi All,
I am trying to load extended ASCII data (below is sample data) using TPT script, load is failing with "TPT10508: RDBMS error 6706: The string contains an untranslatable character." error, I have tried using CHARACTER SET UTF8, LATIN1_A0, LATIN1252_3A0 and LATIN1251_0A but failed with same error message.
Cool™ Start
Expect with ASCII, using CHARACTER SET ASCII I was able to load successfully but data looks garbage "Coolâ„¢ Start", does anybody have idea or know what is the correct character set to load extended ascii data or TPT doesn't support ascii data.
$ tbuild -f tbuild_tpt.txt
Teradata Parallel Transporter Version 13.00.00.00
Execution Plan generation started.
Execution Plan generation successfully completed.
Job log: /opt/teradata/client/13.0/tbuild/logs/srimitta-9.out
Job id is dsadm-9, running on ABC
Teradata Parallel Transporter SQL DDL Operator Version 13.00.00.00
DDL_OPERATOR: private log not specified
DDL_OPERATOR: connecting sessions
DDL_OPERATOR: sending SQL requests
DDL_OPERATOR: TPT10508: RDBMS error 6706: The string contains an untranslatable character.
DDL_OPERATOR: disconnecting sessions
DDL_OPERATOR: Total processor time used = '0.03 Second(s)'
DDL_OPERATOR: Start : Sun Jun 9 15:17:08 2013
DDL_OPERATOR: End : Sun Jun 9 15:17:09 2013
Job step MAIN_STEP terminated (status 12)
Job dsadm terminated (status 12)
Thanks
Srini
Control characters in Unix file from BTEQ script.Moreover,control characters are common in the file
I have the below data in the table KVB
empno,ename,gender
1,BHARATH,M
2,VENKAT,M
3,RADHA,F
#!/bin/ksh
bteq<<EOFInsSel
`cat /opt/idw/pr/common/cmd/idwpass`
.export data file=sha.txt
.set quiet on
.set width 1500
.set seperator '|'
select ename,empno,gender from kvb;
.EXPORT RESET
.logoff
.exit
My output looks like the below one with control characters and empno is missing
^N^@^G^@BHARATH^B^@^@^@M
^M^@^F^@VENKAT^A^@^@^@M
^L^@^E^@RADHA^C^@^@^@F
Regards
KVB
Hi all,
I'm currently testing TTU 14.00 and experienced an issue when using tdload to move a table (5.3b rows, 600gb) from one system to another. Unfortunately, I'm not sure if the table load actually completed (log indicate it did but only applied 965m rows) as another user dropped/recreated the table and restarted the job. The UV, ET and LOG tables were deleted by the job. I was able to catch the table size before it was dropped and it was much smaller than expected so looks like it probably took the 965m rows.
Anyone have any idea what my issue may be here? Thanks.
Teradata Load Utility Version 14.00.00.09
executed via (initial run didn't include a checkpoint interval but one was included when it was restarted):
tdload -j myjob.var
myjob.var source:
SourceTdpId = 'sys1', SourceWorkingDatabase = 'test', SourceTable = 'spr', SourceUserName = 'testuser', SourceUserPassword = 'xxxxxxxx', TargetTdpId = 'sys2', TargetWorkingDatabase = 'test', TargetTable = 'spr', TargetUserName = 'testuser', TargetUserPassword = 'xxxxxxxx', TargetMaxSessions = 16, TargetMinSessions = 8
Job error output:
LOAD: RDBMS Warning: 6813 Numeric overflow in internal counters. The number of rows returned is actual number of rows returned, modulo 2^32.
$LOAD: Statistics for Target Table: 'spr'
$LOAD: Total Rows Sent To RDBMS: 5259745852
$LOAD: Total Rows Applied: 964778556
$LOAD: Total Rows in Error Table 1: 0
$LOAD: Total Rows in Error Table 2: 0
$LOAD: Total Duplicate Rows: Unknown due to RDBMS 6813 warning code
$LOAD: disconnecting sessions
$EXPORT: disconnecting sessions
Hi there,
I have heard about some kind of teradata tools like CS Ram and Pakdisk? (Paddisk or sth) which are pretty handfull and I cand find any informaton about them.
It was tools to check node/amp data schredding level and to table degeneration check.
I wanted to check it and/or even fix it if there are some tools to it.
Can you help and point some good documentations or knowlage sources?
Regards!
Hi,
I am building an TPT which is doing fast load(LOAD operator) to a NAV_REP table.
I am using export operator to export the data . Now I have two sql statements. one statement is doing calculation based on year and second statement is doing calculation based on month.
I want to pass a variable like CALC = 'M' or CALC = 'Y' and based on that variable, I want to choose the SQL statement in EXPORT . If I pass CALC = M then EXPORT operator should choose SQL statement 1 which is doing calculation based on Month and if CALC = Y then EXPORT operator should choose SQL statement 2 which is doing calculation based on Year.
KIndly note that both the SQLS have exactly same format of out put so there is no need to different schema.(I am using TD 13.10 ).
How can I do that?
Thanks and Regards,
Ram
Hello,
When I submit a request for the TTU - Windows installation package, I receive a link for the 32-bit version. Does anyone know how I can get the 64- bit version?
Thank you,
Rafael H.
hi,
Please help me for below script.
clear;
sessions 10;
tenacity 4;
sleep 20;
DATEFORM ANSIDATE;
show version;
.LOGON 127.0.0.1/TDUSER, TDUSER
DROP TABLE tduser.M1;
DROP TABLE TDUSER.ERR1;
DROP TABLE TDUSER.ERR2;
CREATE SET TABLE tduser.M1
(
MANUFACTURER_ID INTEGER,
MANUFACTURER_NAME VARCHAR(10),
MANFACTURE_CODE VARCHAR(3)
)
UNIQUE PRIMARY INDEX ( MANUFACTURER_ID );
SET RECORD VARTEXT "|";
DEFINE
MANUFACTURER_ID (varchar(2)),
MANUFACTURER_NAME (varchar(10)),
MANFACTURE_CODE (varchar(3)),
FILE = C:\Documents and Settings\code.txt;
SHOW;
BEGIN LOADING TDUSER.M1 ERRORFILES TDUSER.ERR1, TDUSER.ERR2;
INSERT INTO TDUSER.M1 VALUES (:MANUFACTURER_ID,:MANUFACTURER_NAME,:MANFACTURE_CODE);
checkpoint 1000;
.indicators
END LOADING;
logoff;
attaching log....
===================================================================
= =
= FASTLOAD UTILITY VERSION 13.00.00.004 =
= PLATFORM WIN32 =
= =
===================================================================
===================================================================
= =
= Copyright 1984-2009, Teradata Corporation. =
= ALL RIGHTS RESERVED. =
= =
===================================================================
**** 22:46:10 Processing starting at: Sat Jun 15 22:46:10 2013
0001 clear;
**** 22:46:10 Warning: All previous column and file definitions cleared
0002 sessions 10;
**** 22:46:10 FDL4866 SESSIONS command accepted
0003 tenacity 4;
**** 22:46:10 Tenacity Enabled: 4 hour(s)
0004 sleep 20;
**** 22:46:10 Sleep Minutes Set: 20 minute(s)
0005 DATEFORM ANSIDATE;
**** 22:46:10 Date/Time Format set to ANSIDATE
**** 22:46:10 Command completed successfully
0006 show version;
FastLoad Version 13.00.00.004 for Win 32 running Windows Sockets
FastLoad : 13.00.00.08
FastCmds : 13.00.00.11
FastIO : 13.00.00.02
FastMBCS : 13.00.00.02
FastNtfy : 13.00.00.00
FastPars : 13.00.00.06
FastSQL : 13.00.00.16
FastUtil : 13.00.00.04
Standalone Data Connector : 13.00.00.001
PMPROCS : 13.00.00.01
PMRWFMT : 13.00.00.03
PMTRCE : 13.00.00.01
PMMM : 13.00.00.01
PMHEXDMP : 13.00.00.01
PMUNXDSK : 13.00.00.01
ICUVER : TDICU, 13.00.00.01
CLIV2 : 13.00.00.25
MTDP : 13.00.00.15
MOSIos : 13.00.00.05
MOSIDEP : 13.00.00.02
OSENCRYPT : N/A
OSERR : 13.00.00.00
FastLoad linking date: Mar 16 2009
===================================================================
= =
= Logon/Connection =
= =
===================================================================
0007 .LOGON 127.0.0.1/TDUSER,
**** 22:46:10 Teradata Database Release: 13.00.00.12
**** 22:46:10 Teradata Database Version: 13.00.00.12
**** 22:46:10 Current CLI or RDBMS allows maximum row size: 64K
**** 22:46:10 Character set for this job: ASCII
**** 22:46:11 Number of FastLoad sessions requested = 10
**** 22:46:11 Number of FastLoad sessions connected = 2
**** 22:46:11 FDL4808 LOGON successful
0008 DROP TABLE tduser.M1;
**** 22:46:11 Command completed successfully
0009 DROP TABLE TDUSER.ERR1;
**** 22:46:11 Command completed successfully
0010 DROP TABLE TDUSER.ERR2;
**** 22:46:11 Command completed successfully
0011 CREATE SET TABLE tduser.M1
(
MANUFACTURER_ID INTEGER,
MANUFACTURER_NAME VARCHAR(10),
MANFACTURE_CODE VARCHAR(3)
)
UNIQUE PRIMARY INDEX ( MANUFACTURER_ID );
**** 22:46:11 Command completed successfully
0012 SET RECORD VARTEXT "|";
**** 22:46:11 Now set to read 'Variable-Length Text' records
**** 22:46:11 Delimiter character(s) is set to '|'
**** 22:46:11 Command completed successfully
0013 DEFINE
MANUFACTURER_ID (varchar(2)),
MANUFACTURER_NAME (varchar(10)),
MANFACTURE_CODE (varchar(3)),
FILE = C:\Documents and Settings\code.txt;
**** 22:46:11 FDL4803 DEFINE statement processed
0014 SHOW;
FILE = C:\Documents and Settings\code.txt
MANUFACTURER_ID OFFSET = 0 LEN = 2 VARCHAR
MANUFACTURER_NAME OFFSET = 4 LEN = 10 VARCHAR
MANFACTURE_CODE OFFSET = 16 LEN = 3 VARCHAR
TOTAL RECORD LENGTH = 21
0015 BEGIN LOADING TDUSER.M1 ERRORFILES TDUSER.ERR1, TDUSER.ERR2;
**** 22:46:11 Number of AMPs available: 2
**** 22:46:11 BEGIN LOADING COMPLETE
===================================================================
= =
= Insert Phase =
= =
===================================================================
0016 INSERT INTO TDUSER.M1 VALUES (:MANUFACTURER_ID,:MANUFACTURER_NAME,:MANFACTU
RE_CODE);
**** 22:46:11 Number of recs/msg: 3213
**** 22:46:11 Starting to send to RDBMS with record 1
**** 22:46:11 I/O Error on File Read: 35, Text: EOF encountered before
end of record
===================================================================
= =
= Logoff/Disconnect =
= =
===================================================================
**** 22:46:11 Logging off all sessions
**** 22:46:12 Total processor time used = '0.234375 Seconds'
. Start : Sat Jun 15 22:46:10 2013
. End : Sat Jun 15 22:46:12 2013
. Highest return code encountered = '12'.
**** 22:46:12 FastLoad Paused
my data file .....++++++++>
|1|max|d|
|2|rock|a|
|3|doc|b|
please advise where I'm wrong
clear;
sessions 10;
tenacity 4;
sleep 20;
DATEFORM ANSIDATE;\
show version;
.LOGON 127.0.0.1/TDUSER, TDUSER
DROP TABLE tduser.M1;
DROP TABLE TDUSER.ERR1;
DROP TABLE TDUSER.ERR2;
CREATE SET TABLE tduser.M1
(
MANUFACTURER_ID INTEGER,
MANUFACTURER_NAME VARCHAR(10),
MANFACTURE_CODE VARCHAR(3)
)
UNIQUE PRIMARY INDEX ( MANUFACTURER_ID );
SET RECORD VARTEXT "|";
DEFINE
MANUFACTURER_ID (varchar(2)),
MANUFACTURER_NAME (varchar(10)),
MANFACTURE_CODE (varchar(3))
FILE = C:\Documents and Settings\code.txt;
SHOW;
BEGIN LOADING TDUSER.M1 ERRORFILES TDUSER.ERR1, TDUSER.ERR2;
.CHECKPOINT 1000;
.INDICATORS;
INSERT INTO TDUSER.M1 VALUES (:MANUFACTURER_ID,:MANUFACTURER_NAME,:MANFACTURE_CODE) ;
END LOADING;
logoff;
log.......................++++++++++++++++++++
===================================================================
= =
= FASTLOAD UTILITY VERSION 13.00.00.004 =
= PLATFORM WIN32 =
= =
===================================================================
===================================================================
= =
= Copyright 1984-2009, Teradata Corporation. =
= ALL RIGHTS RESERVED. =
= =
===================================================================
**** 00:45:36 Processing starting at: Sun Jun 16 00:45:36 2013
0001 clear;
**** 00:45:36 Warning: All previous column and file definitions cleared
0002 sessions 10;
**** 00:45:36 FDL4866 SESSIONS command accepted
0003 tenacity 4;
**** 00:45:36 Tenacity Enabled: 4 hour(s)
0004 sleep 20;
**** 00:45:36 Sleep Minutes Set: 20 minute(s)
0005 DATEFORM ANSIDATE;\
**** 00:45:36 Date/Time Format set to ANSIDATE
**** 00:45:36 Command completed successfully
0006 show version;
FastLoad Version 13.00.00.004 for Win 32 running Windows Sockets
FastLoad : 13.00.00.08
FastCmds : 13.00.00.11
FastIO : 13.00.00.02
FastMBCS : 13.00.00.02
FastNtfy : 13.00.00.00
FastPars : 13.00.00.06
FastSQL : 13.00.00.16
FastUtil : 13.00.00.04
Standalone Data Connector : 13.00.00.001
PMPROCS : 13.00.00.01
PMRWFMT : 13.00.00.03
PMTRCE : 13.00.00.01
PMMM : 13.00.00.01
PMHEXDMP : 13.00.00.01
PMUNXDSK : 13.00.00.01
ICUVER : TDICU, 13.00.00.01
CLIV2 : 13.00.00.25
MTDP : 13.00.00.15
MOSIos : 13.00.00.05
MOSIDEP : 13.00.00.02
OSENCRYPT : N/A
OSERR : 13.00.00.00
FastLoad linking date: Mar 16 2009
===================================================================
= =
= Logon/Connection =
= =
===================================================================
0007 .LOGON 127.0.0.1/TDUSER,
**** 00:45:36 Teradata Database Release: 13.00.00.12
**** 00:45:36 Teradata Database Version: 13.00.00.12
**** 00:45:36 Current CLI or RDBMS allows maximum row size: 64K
**** 00:45:36 Character set for this job: ASCII
**** 00:45:37 Number of FastLoad sessions requested = 10
**** 00:45:37 Number of FastLoad sessions connected = 2
**** 00:45:37 FDL4808 LOGON successful
0008 DROP TABLE tduser.M1;
**** 00:45:37 Command completed successfully
0009 DROP TABLE TDUSER.ERR1;
**** 00:45:37 RDBMS error 3807: Object 'TDUSER.ERR1' does not exist.
0010 DROP TABLE TDUSER.ERR2;
**** 00:45:37 RDBMS error 3807: Object 'TDUSER.ERR2' does not exist.
0011 CREATE SET TABLE tduser.M1
(
MANUFACTURER_ID INTEGER,
MANUFACTURER_NAME VARCHAR(10),
MANFACTURE_CODE VARCHAR(3)
)
UNIQUE PRIMARY INDEX ( MANUFACTURER_ID );
**** 00:45:37 Command completed successfully
0012 SET RECORD VARTEXT "|";
**** 00:45:37 Now set to read 'Variable-Length Text' records
**** 00:45:37 Delimiter character(s) is set to '|'
**** 00:45:37 Command completed successfully
0013 DEFINE
MANUFACTURER_ID (varchar(2)),
MANUFACTURER_NAME (varchar(10)),
MANFACTURE_CODE (varchar(3))
FILE = C:\Documents and Settings\code.txt;
**** 00:45:37 FDL4803 DEFINE statement processed
0014 SHOW;
FILE = C:\Documents and Settings\code.txt
MANUFACTURER_ID OFFSET = 0 LEN = 2 VARCHAR
MANUFACTURER_NAME OFFSET = 4 LEN = 10 VARCHAR
MANFACTURE_CODE OFFSET = 16 LEN = 3 VARCHAR
TOTAL RECORD LENGTH = 21
0015 BEGIN LOADING TDUSER.M1 ERRORFILES TDUSER.ERR1, TDUSER.ERR2;
**** 00:45:37 Number of AMPs available: 2
**** 00:45:37 BEGIN LOADING COMPLETE
0016 .CHECKPOINT 1000;
**** 00:45:37 FDL4800 Invalid FastLoad statement
0017 .INDICATORS;
**** 00:45:37 FDL4800 Invalid FastLoad statement
===================================================================
= =
= Insert Phase =
= =
===================================================================
0018 INSERT INTO TDUSER.M1 VALUES (:MANUFACTURER_ID,:MANUFACTURER_NAME,:MANFACTU
RE_CODE) ;
**** 00:45:38 Number of recs/msg: 3213
**** 00:45:38 Starting to send to RDBMS with record 1
**** 00:45:38 Sending row 3
**** 00:45:38 Finished sending rows to the RDBMS
===================================================================
= =
= End Loading Phase =
= =
===================================================================
0019 END LOADING;
**** 00:45:38 END LOADING COMPLETE
Total Records Read = 3
Total Error Table 1 = 0 ---- Table has been dropped
Total Error Table 2 = 0 ---- Table has been dropped
Total Inserts Applied = 3
Total Duplicate Rows = 0
Start: Sun Jun 16 00:45:38 2013
End : Sun Jun 16 00:45:38 2013
0020 logoff;
===================================================================
= =
= Logoff/Disconnect =
= =
===================================================================
**** 00:45:38 Logging off all sessions
**** 00:45:39 Total processor time used = '0.234375 Seconds'
. Start : Sun Jun 16 00:45:36 2013
. End : Sun Jun 16 00:45:39 2013
. Highest return code encountered = '8'.
**** 00:45:39 FDL4818 FastLoad Terminated
clear;
sessions 10;
tenacity 4;
sleep 20;
DATEFORM ANSIDATE;\
show version;
.LOGON 127.0.0.1/TDUSER, TDUSER
DROP TABLE tduser.M1;
DROP TABLE TDUSER.ERR1;
DROP TABLE TDUSER.ERR2;
CREATE SET TABLE tduser.M1
(
MANUFACTURER_ID INTEGER,
MANUFACTURER_NAME VARCHAR(10),
MANFACTURE_CODE VARCHAR(3)
)
UNIQUE PRIMARY INDEX ( MANUFACTURER_ID );
SET RECORD VARTEXT "|";
DEFINE
delim0 (varchar(1)),
MANUFACTURER_ID (varchar(2)),
delim1 (varchar(1)),
MANUFACTURER_NAME (varchar(10)),
delim2 (varchar(1)),
MANFACTURE_CODE (varchar(3)),
delim3 (varchar(1)),
newlinechar (varchar(1))
FILE = C:\Documents and Settings\code.txt;
SHOW;
BEGIN LOADING TDUSER.M1 ERRORFILES TDUSER.ERR1, TDUSER.ERR2;
.CHECKPOINT 1000;
.INDICATORS;
INSERT INTO TDUSER.M1 VALUES (:MANUFACTURER_ID,:MANUFACTURER_NAME,:MANFACTURE_CODE) ;
END LOADING;
logoff;
LOG+++++++++++++++++++++++++++
===================================================================
= =
= FASTLOAD UTILITY VERSION 13.00.00.004 =
= PLATFORM WIN32 =
= =
===================================================================
===================================================================
= =
= Copyright 1984-2009, Teradata Corporation. =
= ALL RIGHTS RESERVED. =
= =
===================================================================
**** 00:51:07 Processing starting at: Sun Jun 16 00:51:07 2013
0001 clear;
**** 00:51:07 Warning: All previous column and file definitions cleared
0002 sessions 10;
**** 00:51:07 FDL4866 SESSIONS command accepted
0003 tenacity 4;
**** 00:51:07 Tenacity Enabled: 4 hour(s)
0004 sleep 20;
**** 00:51:07 Sleep Minutes Set: 20 minute(s)
0005 DATEFORM ANSIDATE;\
**** 00:51:07 Date/Time Format set to ANSIDATE
**** 00:51:07 Command completed successfully
0006 show version;
FastLoad Version 13.00.00.004 for Win 32 running Windows Sockets
FastLoad : 13.00.00.08
FastCmds : 13.00.00.11
FastIO : 13.00.00.02
FastMBCS : 13.00.00.02
FastNtfy : 13.00.00.00
FastPars : 13.00.00.06
FastSQL : 13.00.00.16
FastUtil : 13.00.00.04
Standalone Data Connector : 13.00.00.001
PMPROCS : 13.00.00.01
PMRWFMT : 13.00.00.03
PMTRCE : 13.00.00.01
PMMM : 13.00.00.01
PMHEXDMP : 13.00.00.01
PMUNXDSK : 13.00.00.01
ICUVER : TDICU, 13.00.00.01
CLIV2 : 13.00.00.25
MTDP : 13.00.00.15
MOSIos : 13.00.00.05
MOSIDEP : 13.00.00.02
OSENCRYPT : N/A
OSERR : 13.00.00.00
FastLoad linking date: Mar 16 2009
===================================================================
= =
= Logon/Connection =
= =
===================================================================
0007 .LOGON 127.0.0.1/TDUSER,
**** 00:51:07 Teradata Database Release: 13.00.00.12
**** 00:51:07 Teradata Database Version: 13.00.00.12
**** 00:51:07 Current CLI or RDBMS allows maximum row size: 64K
**** 00:51:07 Character set for this job: ASCII
**** 00:51:08 Number of FastLoad sessions requested = 10
**** 00:51:08 Number of FastLoad sessions connected = 2
**** 00:51:08 FDL4808 LOGON successful
0008 DROP TABLE tduser.M1;
**** 00:51:08 Command completed successfully
0009 DROP TABLE TDUSER.ERR1;
**** 00:51:08 RDBMS error 3807: Object 'TDUSER.ERR1' does not exist.
0010 DROP TABLE TDUSER.ERR2;
**** 00:51:08 RDBMS error 3807: Object 'TDUSER.ERR2' does not exist.
0011 CREATE SET TABLE tduser.M1
(
MANUFACTURER_ID INTEGER,
MANUFACTURER_NAME VARCHAR(10),
MANFACTURE_CODE VARCHAR(3)
)
UNIQUE PRIMARY INDEX ( MANUFACTURER_ID );
**** 00:51:08 Command completed successfully
0012 SET RECORD VARTEXT "|";
**** 00:51:08 Now set to read 'Variable-Length Text' records
**** 00:51:08 Delimiter character(s) is set to '|'
**** 00:51:08 Command completed successfully
0013 DEFINE
delim0 (varchar(1)),
MANUFACTURER_ID (varchar(2)),
delim1 (varchar(1)),
MANUFACTURER_NAME (varchar(10)),
delim2 (varchar(1)),
MANFACTURE_CODE (varchar(3)),
delim3 (varchar(1)),
newlinechar (varchar(1))
FILE = C:\Documents and Settings\code.txt;
**** 00:51:08 FDL4803 DEFINE statement processed
0014 SHOW;
FILE = C:\Documents and Settings\code.txt
DELIM0 OFFSET = 0 LEN = 1 VARCHAR
MANUFACTURER_ID OFFSET = 3 LEN = 2 VARCHAR
DELIM1 OFFSET = 7 LEN = 1 VARCHAR
MANUFACTURER_NAME OFFSET = 10 LEN = 10 VARCHAR
DELIM2 OFFSET = 22 LEN = 1 VARCHAR
MANFACTURE_CODE OFFSET = 25 LEN = 3 VARCHAR
DELIM3 OFFSET = 30 LEN = 1 VARCHAR
NEWLINECHAR OFFSET = 33 LEN = 1 VARCHAR
TOTAL RECORD LENGTH = 36
0015 BEGIN LOADING TDUSER.M1 ERRORFILES TDUSER.ERR1, TDUSER.ERR2;
**** 00:51:08 Number of AMPs available: 2
**** 00:51:08 BEGIN LOADING COMPLETE
0016 .CHECKPOINT 1000;
**** 00:51:08 FDL4800 Invalid FastLoad statement
0017 .INDICATORS;
**** 00:51:08 FDL4800 Invalid FastLoad statement
===================================================================
= =
= Insert Phase =
= =
===================================================================
0018 INSERT INTO TDUSER.M1 VALUES (:MANUFACTURER_ID,:MANUFACTURER_NAME,:MANFACTU
RE_CODE) ;
**** 00:51:08 Number of recs/msg: 2570
**** 00:51:08 Starting to send to RDBMS with record 1
**** 00:51:08 Field too large in vartext data record: 1, field:
MANUFACTURER_ID
===================================================================
= =
= Logoff/Disconnect =
= =
===================================================================
**** 00:51:08 Logging off all sessions
**** 00:51:11 Total processor time used = '0.296875 Seconds'
. Start : Sun Jun 16 00:51:07 2013
. End : Sun Jun 16 00:51:11 2013
. Highest return code encountered = '12'.
**** 00:51:11 FastLoad Paused
DATA file++++++++++
1|mayank|ab
22|deepak|xy
10|father|jj
also advise please when to use default option of unformatted and formatted if using normal text file in personal computer.
what is format when we use xcel to keep data for loading.
regards,
Mayank
We are in the process of converting some load script to TPT. In our script , there are some help and show commands are there. How can i migrate the script to TPT.Currently it is running using bteq.
Below sq1l statement, we would like to run thru TPT.
HELP STATS Database.tablename ;
Hi,
I am using BTEQ 13.10.00.04 for WIN32. My primary use of this is to test scripts prior to promotion to a mainframe system which has a chracter line limit of 80.
I have used .SET WIDTH 80 to force the character limit, but if I submit SQL and a line goes over the 80 chars rather than truncating the line it puts a line return in at the 80th character which is great to stop any errors occuring but... if I want the errors to happen is there anyway to force BTEQWIN to truncate?
Thanks
Dan
Is there a way, within a TPT module, to accept in OS environment variables?
I am aware of the global variable file (good for all modules) and the local variable file (good for a particular module), but I need to get variables passed in for a specific execution of a module (i.e. the parms values will change with each execution).
I would also like to have a generic script to invoke various TPT modules (so the -u option would change).
Multiload used to have an ACCEPT capability, but I'm not finding such flexibility with TPT. Right now, we are generating TPT modules from templates, and using awk to replace the variables that we need.
Any/all help appreciated.
Hello Everyone,
I've been learning TPT and have been given various scenarios to execute; specifically ones that deal with the FAST LOAD protocol. There is one scenario that I am having issues trying to figure out, which is as follows:
TARGET TABLE has N columns.
FLAT FILE SOURCE has variable columns for every row (always between N and N-2). Tried to declare columns as NULL in insert statement but since every row may have diff number of columns that does not work.
Any pointers to get me thinking in the right direction would be greatly appreciated? Is this a scenario for using INMODS?
Thanks
I have one column in the table defined as AAA1 decimal(9,2)
sample data:
011069125.71
While doing fastload its throwing an error limit exceeded because its more than 9 numbers. My aim is to define the fastload file to remove the bad data from the table and to load remaining datas without causing any abend.
Is it possible??
Good Morning Experts,
As part of migration, a not null column has been added to a target table in Teradata and the mapping (Informatica 9.1) that uses this target table has been updated to include the newly added column. But strangely the job has failed with the error 'cannot insert NULL value into NOT NULL column'. On further checking, we have found that the control file hasn't generated the newly added column and its value in the insert statement even though the target table (and source table) is updated with the newly added column in the mapping. Should we configure some kind of settings to take them in control file?
There was one more failure on another table on which the PI has been changed (previously - 1 column, now 3 columns). Informatica generated the control file with the same script as in the case of previous run without any changes to PI (I presume) with having new PI columns in the UPDATE script and hence the job has failed as the PI columns cannot be updated in MLOAD. What is the basis for the Informatica in generating the Control file?
Thank you for your time on this.
The article "Teradata Parallel Transporter Supports Quoted VARTEXT in TTU14.00" has a passing comment that there is a possibility to change TPT handling of zero-length strings:
"The user can specify how empty data values are to be handled:
When I import a delimited file using TPT, I get NULLs in a table in place of zero-length strings in a file. I searched through TPT documentation, but did not find any switch, or parameter to modify that behavior. Has anyone managed to successfully do that?
Thank you
I'm Trying to load data from a file into a volatile table. Following my FastLoad Job Script:
sessions 2; errlimit 25; logon xxxx/yyyy,zzzz; CREATE VOLATILE TABLE yyyy.vt_employee ( EmpNo SMALLINT, Name VARCHAR(12)) UNIQUE PRIMARY INDEX( EmpNo ) ON COMMIT PRESERVE ROWS; set record unformatted; define delim0(char(1)), EmpNo(char(9)), delim1(char(1)), Name(char(12)), delim2(char(1)), newlinechar(char(1)) file=insert.input; show; begin loading yyyy.vt_employee errorfiles error_1, error_2; insert into yyyy.vt_employee( :EmpNo, :Name, ); end loading; logoff;
When I run the script, I receive the message "RDBMS error 5341: Volatile table 'vt_employee' not allowed in statement"
Does that mean that it is not allowed at all to use FastLoad with volatile tables? Or is there another problem in my code? When the script runs, I receive the output "CREATE VOLATILE TABLE yyyy.vt_employee ... Command completed successfully". But if I try to show the created table in the Teradata SQL assistant, I get the message that this table doesn't exist. Is it the case that, after the script finished, the volatile table gets destroyed?
In tpt 13.00 we dont have any default Tenacity, the job waited util it gets the load slots, but in 13.10 the job is taking up some default Tenacity as 6 mins for 4 hrs as result the job is failing after waiting for 4 hours.. We can increase the value by defining the attribute TenacityHours, TenacitySleep in the tpt script.. but we need to touch nearly 2000+ scripts to include this variable. Can this Tenacity be increased by anyother way, i mean through TSAM or any database settings?