Hi,
I am trying to read a Teradata table from the DS parallel job using Teradata Enterprise Stage. Its giving me the following error. Also can't view the data.
TeradataTble: Unrecognized argument: -db_cs
But I could connect thru DS manager to import the metadata definitions.
DataStage Version 7.0
Teradata2 Version 6.1
DataStage Server: Unix.
What is the environment variable to set?. or check it out.
Unable to read Teradata table from DS parallel JOB
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 10
- Joined: Wed Dec 15, 2004 2:19 am
-
- Premium Member
- Posts: 10
- Joined: Wed Dec 15, 2004 2:19 am
Try without APT_TERA params
Try this first:
0.Create a copy of job.
1. Use a user which has write privilages to database being read from.
2. Remove all APT_TERA env variables.
3. use unecrypted password.
4. See if the above works.
If the above works then try using encrypted password.
If both work then go back to orignial job and try with unecrypted password for TERA parameter.
Also at one point I believe but am not sure APT_TERA_SYNC_PASSWORD was actually
APT_TER_SYNC_PASSWORD without the A.
0.Create a copy of job.
1. Use a user which has write privilages to database being read from.
2. Remove all APT_TERA env variables.
3. use unecrypted password.
4. See if the above works.
If the above works then try using encrypted password.
If both work then go back to orignial job and try with unecrypted password for TERA parameter.
Also at one point I believe but am not sure APT_TERA_SYNC_PASSWORD was actually
APT_TER_SYNC_PASSWORD without the A.
-
- Premium Member
- Posts: 10
- Joined: Wed Dec 15, 2004 2:19 am
Is this problem having with all the tables/multiple tables or is it just that one table. Also try re-importing the metadate. Sometimes it so happens that the dba decides to change the column name and hence it will create an error doing the select (view data). My dba did that. That is offcourse, if you have a column in that table that has a name close to db_cs.
Also, i believe that in DS 7.0, you could not view data if you have environment variables defined. Someone correct me if i am wrong.
As far as performance goes, that depends upon a number of factors. Like how many bytes of data in a particular row, what sql functionality (update, insert, upserts, delete first and then insert, etc.) is being performed, are there triggers on that table thats slowing it down, how often you pass a commit, whats the transaction size etc.
Also, i believe that in DS 7.0, you could not view data if you have environment variables defined. Someone correct me if i am wrong.
As far as performance goes, that depends upon a number of factors. Like how many bytes of data in a particular row, what sql functionality (update, insert, upserts, delete first and then insert, etc.) is being performed, are there triggers on that table thats slowing it down, how often you pass a commit, whats the transaction size etc.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.