↧
Error in FastLoad Script - response (1) by SuSeSi
↧
BTEQ losing header comments of view definitions - forum topic by muthm
Hi,
is there any way to preserve header comments when sending a REPLACE VIEW with BTEQ?
In my scenario, I clone database structures from one system to another. I use BTEQ from a shell or perl scripts to run 'SHOW <object>;' for all objects in the databases, dumping the definitions to .sql files on disk. Then I run those SQL files on the target system, again using BTEQ from shell or perl scripts.
This works fine for making exact one-to-one copies for all kind of objects (functions and procedures are a little bit tricky).
But for views there is a problem: I lose header comments when I send the view definition using BTEQ.
Consider this sample view definition, correctly dumped to a .sql file:
/*
Header comment:
This is a test view.
*/
REPLACE VIEW SampleDB.TestView AS
LOCKING ROW FOR ACCESS
SELECT *
FROM DBC.TablesV;
If I copy the text to SQL Assistant, send it to the database, and then do a SHOW VIEW, I get the expected (and correct) result:
show view SampleDB.TestView;
show view SampleDB.TestView;/*
Header comment:
This is a test view.
*/
REPLACEVIEW SampleDB.TestView AS
LOCKINGROWFORACCESS
SELECT *
FROM DBC.TablesV;
But if I run the sql file with BTEQ, it first nicely tells me that it replaced the view:
/*
Header comment:
This is a test view.
*/
REPLACE VIEW SampleDB.TestView AS
LOCKING ROW FOR ACCESS
SELECT *
FROM DBC.TablesV;
*** View has been replaced.
*** Total elapsed time was 1 second.
But doing a SHOW VIEW in SQL Assistant reveals that the header comments got lost:
show view SampleDB.TestView;
REPLACEVIEW SampleDB.TestView AS
LOCKING ROW FOR ACCESS
SELECT *
FROM DBC.TablesV;
I suppose that BTEQ doesn't include the leading comment in the Teradata request sent to the database system.
Is there a way to tell BTEQ to include the comments?
Or does anyone have an other idea how I can retain the header comments from a scripting environment (i.e. not using SQL Assistant interactively)?
Thanks a lot!
Matthias
Forums:
↧
↧
TPT_INFRA: TPT03586: Warning: the rightmost 63990 characters (bytes) of the values of column Col1 will be truncated on a - forum topic by plentyfish
Hi, can anyone help with this issue. User's job is failing with the following warnings.
TPT_INFRA: TPT03586: Warning: the rightmost 63990 characters (bytes) of the values of column Col1 will be truncated on assignment.
TPT_INFRA: TPT03586: Warning: the rightmost 63985 characters (bytes) of the values of column Col2 will be truncated on assignment.
TPT_INFRA: TPT03586: Warning: the rightmost 63995 characters (bytes) of the values of column Col3 will be truncated on assignment.
TPT_INFRA: TPT03586: Warning: the rightmost 63995 characters (bytes) of the values of column Col4 will be truncated on assignment.
.
.
.
TPT_INFRA: TPT03586: Warning: the rightmost 63997 characters (bytes) of the values of column Col5 will be truncated on assignment.
.Teradata Parallel Transporter FastLoad INMOD Adapter Version 13.10.00.13
Teradata Parallel Transporter Load Operator Version 13.10.00.04
W_O_1_TPT_LOAD_INMOD: private log not specified
W_O_1_TPT_LOAD_INMOD: connecting sessions
W_O_1_TPT_LOAD_INMOD: preparing target table
W_O_1_TPT_LOAD_INMOD: entering Acquisition Phase
W_O_1_TPT_LOAD_INMOD: entering Application Phase
W_O_1_TPT_LOAD_INMOD: Statistics for Target Table: 'TABLE_X'
W_O_1_TPT_LOAD_INMOD: Total Rows Sent To RDBMS: 6264
W_O_1_TPT_LOAD_INMOD: Total Rows Applied: 6264
W_O_1_TPT_LOAD_INMOD: disconnecting sessions
The warnings are on every column of the table and as you can see from table DDL, the cols are very small in terms of length
CREATE SET TABLE TABLE_X ,NO FALLBACK ,
NO BEFORE JOURNAL,
NO AFTER JOURNAL,
CHECKSUM = DEFAULT,
DEFAULT MERGEBLOCKRATIO
(
COL1 CHAR(10) CHARACTER SET LATIN CASESPECIFIC,
COL2 CHAR(15) CHARACTER SET LATIN CASESPECIFIC,
COL3 CHAR(5) CHARACTER SET LATIN CASESPECIFIC,
COL4 CHAR(3) CHARACTER SET LATIN CASESPECIFIC,
COL5 CHAR(1) CHARACTER SET LATIN CASESPECIFIC,
COL6 CHAR(10) CHARACTER SET LATIN CASESPECIFIC,
COL7 CHAR(3) CHARACTER SET LATIN CASESPECIFIC,
COL8 CHAR(6) CHARACTER SET LATIN CASESPECIFIC,
COL9 DATE FORMAT 'YYYY-MM-DD' COMPRESS ,
COL10 CHAR(6) CHARACTER SET LATIN CASESPECIFIC,
COL11 DECIMAL(18,4),
COL12 CHAR(8) CHARACTER SET LATIN CASESPECIFIC,
COL13 DECIMAL(18,4),
COL14 CHAR(8) CHARACTER SET LATIN CASESPECIFIC,
COL15 DECIMAL(18,4),
COL116 CHAR(1) CHARACTER SET LATIN CASESPECIFIC)
PRIMARY INDEX ( COL1 );
Thanks in advance
Forums:
↧
Error in FastLoad Script - response (2) by ThomasNguyen
Also, check your data file, make sure the data records are in FastLoad format and in the endian of the test machine.
↧
Fast Export parallelism - response (1) by ThomasNguyen
The way FastExport works as: Data block contains exported records that DBS server distributes on the sessions. Normally, FastExport gets data blocks on the sessions in the round-robin fashion. Assume there are 4 sessions, FastExport gets data block 1, 2, 3 and 4 on session 1, 2,3 and 4 respectively, then It will get block 5 on session 1, block 6 on session 2, block 7 on session 3 etc…
Thomas
↧
↧
fastload on linux - response (7) by ThomasNguyen
As Dieter mentioned: related to AIX using big-endian while your Linux box is little-endian.
You can do FastExport on Linux box (to obtain the file) as you already did on AIX box, then FastLoad the file, or you can write a program to convert the file from big endian to little endian (you can google search for a such program).
↧
Error in FastLoad Script - response (3) by krishaneesh
From the error it appears that there is an issue with the source file /home.jugal/finsert.txt. The error says that there is a unexpected data format or a control character in an unexpected position.
Also i do not see a SET RECORD command in the script. is it a formatted text or a vartext with the two columns separated by a separator(,| etc..). Inspect the file and verify.
↧
Teradata Parallel Transporter - Session Character Set - response (14) by feinholz
@Santanu84: please do NOT use the attributes ValidUTF8 and ReplaceUTF8Char.
We are not happy with the results we are getting from that feature and we are redesigning it.
@arun_tim1: what version of TPT are you running on z/OS?
↧
Teradata Parallel Transporter - Session Character Set - response (15) by ratchetandclank
@arun_tim1: Does not look like TPT caused the abend, because you can see the return code from the step LOAD_TABLES. Please paste the DC operator log of the execution. If possible, please execute the job setting the TraceLevel attribute to ALL, for DC operator and paste the log.
IDI0044I and IDI0053I should not cause abend. Look at the documentation of these in the IBM website here:
http://pic.dhe.ibm.com/infocenter/pdthelp/v1r1/index.jsp?topic=%2Fcom.ibm.faultanalyzer.doc_7.1%2Fidiugg05493.htm
↧
↧
Teradata Parallel Transporter - Session Character Set - response (16) by feinholz
I think we need to see the entire set of output.
We only have a partial story here.
The job terminated with an error (Job step LOAD_TABLES terminated (status 8) ).
But the part of the output you sent does not show why.
I do see that the Update operator was stopped in the middle of the Acquisition Phase for some reason, which means the error is probably with the DataConnector operator.
↧
Teradata Parallel Transporter - Session Character Set - response (17) by arun_tim1
Hi feinhoz
I am using Teradata Parallel Transporter Version 13.10.00.04.
↧
Teradata Parallel Transporter - Session Character Set - response (19) by arun_tim1
Hi
The following error i got in the DATA CONNECTOR
!WARNING! file 'DD:PTYIN' not processed (errno 129).
EDC5129I No such file or directory.
Setting exit code = 12.
Method PX_Terminate entry: Phase 1
↧
Teradata Parallel Transporter - Session Character Set - response (20) by feinholz
Please send your entire JCL.
What dataset is PTYIN pointed to?
↧
↧
Fast Export parallelism - response (2) by SuSeSi
The number of sessions requested to Database by fexp is assigned to different AMPs. If the resulted data is from a single (or limited AMP) then mostly the sessions assigned to those AMPs will be active most of the time.
↧
Load rows of data from teradata tables to mysql tables - response (1) by SuSeSi
Use TPT (where producer is export operator and consumer is odbc operator)
or
Use OLE DB Access Module (OleLoad) which is WINDOWS only product with a GUI to connect and transfer data.
Check out in Manuals for examples.
↧
Error in FastLoad Script - response (4) by Jugalkishorebhatt1
Hi Guys,
Thanks for the response. Yes. The error is relating to EOF(End of File), which more relates to source input.
This is the 1st time im running fastload script.
Following is the format give in the source file:
1001 1232
I have given it in the format which is used to give in Fast Export using .ACCEPT command.
↧
Teradata Parallel Transporter - Session Character Set - response (21) by mailtodvyag@gmail.com
Does Teradata 13 support TPT ??
↧
↧
Re: Delete Syntax in MLOAD - forum topic by balu_td
Hi,
I need to delete the rows from table in mload script which are not matching in the file.
Tried couples of ways but couldn't succeed.
DELETE FROM Employee WHERE EmpNo <> :EmpNo and EmpName <> :Empname;
UTY0805 RDBMS failure, 3537: A MultiLoad DELETE Statement is Invalid.
DELETE FROM Employee WHERE (EmpNo,EmpName) NOT IN (:EmpNo,:Empname);
UTY0805 RDBMS failure, 3707: Syntax error, expected something like
a 'SELECT' keyword or '(' or a 'NONTEMPORAL' keyword or 'AS' keyword or '('
between '(' and ':'
Please help
Thanks
Balu
Forums:
↧
Teradata Parallel Transporter - Session Character Set - response (22) by feinholz
It is the other way around. :)
The question should be, "Does TPT support Teradata 13?"
The answer is "yes", but it depends on which versions of TPT.
Our client products will support Teradata release "current and 4 back".
This means that TTU 13.0, 13.10, 14.0, 14.10 and 15.0 will support Teradata 13.
↧
Teradata Parallel Transporter - Session Character Set - response (23) by Santanu84
Hi feinholz
Thanks for your reply.
Any further suggestion from you on my case ?
Thanking You
Santanu
↧
Check once if you are using recent version of piom (dataconnector).