Insert into emp values
(:FNAME ,.......
Above Sample Code from TPT works fine. I want to convert null values in flatfile to blank while loading
insert into emp values ( COALESCE(:Fname,''),.... -- Throws ERROR
insert into emp Values ( case when :Fname is null then '' else :Fname End,... --Throws ERROR\Can Any one Help Me how to convert ?
Thanks.
i don't enable the conneciton filter, but somehow almost databases can't list in Data Source Explorer. but all databases can be listed in when I open Database Cache Properties setting window.
Did anybody come across this issue?
Greetings Experts,
We use Informatica to load data from SAP BW to Teradata staging layer and could see a job not dropping the ET table (some records exist with error code 6705) during Mload operation (upsert) and succeeds. During the next run of the job, it fails in its first phase of Mload as it couldn't create the ET table which already exists.
How to identify the source records (for which we don't have access to) that have violated and landed into ET table? (The source data is landed into Informatica server through the flat file, data is kept in pipe in Informatica which is deleted once the job is completed)
If Teradata has database_link like Oracle, we could have accessed the source data of SAP BW right from Teradata and could have troubleshooted the issue. Can you explain why Teradata implicitly doesn't support db link (I guess). I have gone through the following link and couldn't find a implicit db_link support (for external source systems like SAP, oracle,...) rather than through external tools.
http://forums.teradata.com/forum/database/teradata-dblink
One option is to find all the distinct values on the column which is recorded in ET table of Teradata from the source SAP BW system and identify the records missing in source which may be a tedious task or
use a flat file in Informatica rather than pipe so that we could read the file.
Are there any provision to find the missing records right from Teradata?
I just upgraded to 14.10 software from 13.10. Some parameter has been changed, all jobs were working fine.
Now any user except TDWM will get bad user account or password error.
All profiles are set the same as before. What am I forgetting?
RGlass
What is the error?
Hi all,
I am building an SSIS package in SQL Server BIDS 2008 version to pull data from Teradata and dump to SQL Server.
1. I am able to connect to Teradata sucessfully as Source.
2. Connection to SQL Server as Destination is also good.
2. When I am running the package I am getting the error
********* ERROR *******
[Teradata Source [173]] Error: The Teradata TPT registry key cannot be opened. Verify that the TPT API 12.0 or 13.0 Edition 2 (13.0.0.2) for
Windows x86 is installed properly.
Deatils :
Windows 7
Teradata 14.0 version.
Microsoft® Connectors v1.2 for Oracle and Teradata
SQL Server BIDS 2008 to create SSIS.
When I am checking my control panel -> Programs and Feature -> (have)
1. Teradata Parallel Transport Base 14.0
2. Teradata Parallel Transport Stream 14.0
on my Machine TPT is
HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Client\14.00\Teradata Parallel Transporter Base
HKEY_LOCAL_MACHINE\SOFTWARE\Teradata\Client\14.00\Teradata Parallel Transporter Stream
then why it is looking for TPT API 12.0 or 13.0 Edition 2 (13.0.0.2)
How to solve this issue.
Please help.
Abhay Nautiyal
The FastLoad protocol (used by FastLoad and the TPT Load operator) does not support that syntax in the INSERT statement.
Try the TPT Update operator for that type of operation.
Thank You feinholz and Glass for response . http://stackoverflow.com/questions/20554841/convert-null-to-blank-tpt-fast-load/ dnoeth had helped me.
When you state this:
"I have been able to run the very same tpt script locally from my windows machine that has a TPT version 14.00 as well."
Does that mean the job ran successfully?
I have never heard of a situation where TPT could cause a system reboot, or affect all remote network connectivity.
Hi,
I'm getting the following error when launching a TPT job from the command line -
"Teradata Parallel Transporter Version 13.10.00.07
TPT_INFRA: TPT04013: Error: opening temporary job script output file: "No such file or directory" (2).
Job script compilation failed.
Job terminated with status 12."
The user id does have write access to the checkpoint and logs folder as specified in the twbcfg.ini File. Any suggestions?
Thanks,
Sebastian
In TPT13.10, while processing the script we create some temporary files in the current working directory.
Please make sure the user has the proper access rights to that directory.
Yes, the job runs successfully from a Windows and a Linux machine. For some reason the very same script when run on UNIX AIX causes a system crash. There is an upgrade of the OS in progress, I hope teh crash goes away after that.
Hi,
Can you please try the following:
Run you BIDS as administrator and then give it a test, I am sure this will solve the issue.
The second thing you can is to go to Environment variables, and check TPT settings in path variable, there might be two entries for TPT. remove one and it will be working fine.
You can see the following blog:
http://developer.teradata.com/connectivity/articles/logging-on-teradata-database-sessions-via-bteq
And the update has fixed the problem :)
Is there any standard File Extension recommended by Teradata for its tool Scripts like bteq, fastexport, fastload, mload, tpump, tpt, JobVariables?
any suggestion for better naming standard for different scripts that distinguishes itself from other?
Also, I am finding most of the sample scripts in Teradata Documentation are in .txt files and of course all scripts are plain-text,, So, is that a standard to use .txt for all TD scripts?
The job is being launched from the /home/<user> directory of the <user> itself. Not sure if the following helps - I had set up a twbcfg.ini file in the /home/<user> directory and was able to run jobs successfully with the logs and checkpoints being written into subdirectories within the /home/<user> directory . However I noticed that commands like twbstat and tlogview were not working. So I got rid of the twbcfg.ini file from the /home/<user> directory.
Thanks for the reply
1. I ran BIDS as Administrator, still the same issue.
2. I am not very clear about second thing, are you talking about registry ? or somewhere esle ?
is "Microsoft® Connectors v1.2 for Oracle and Teradata " works with Teradata 14.0 ?
I am not able to understand, if I have installed Teradata 14.0 why it is searching for TPT API 12.0 or 13.0 ?
Thanks in advance
Abhay
I think I am getting your problem, You need to go to the Computer properties, go to advanced proprties, go to environment variables, and within system variables go to the Path variable. copy its value part to notepad and check entries for the TPT. there must be more than one entries. retain only single version entry you want to use and delete others. Or remove the older version entries. I believe the older version entries are listed before the new version in path variable, so system goes to search for that version.
Make a copy of this Path variable string before making any changes :)
Hope it will solve your issue.
Hi,
Which tool you are talking about?
If you are talking about studio, then the following link might help you:
http://forums.teradata.com/forum/database/why-i-do-not-see-all-the-databases-in-teradata-studio