DSXchange

Looks like you can't do that. RequestedSessions most probably works in concert with SessionsPerPlayer which must work in concert with the Configuration file. The SessionsPerPlayer default is two. I'll bet you can't request 1 session and try to use the default SessionsPerPlayer default of 2. That's a...

E-case e94953

This "parameter" is an Additional Connection Option comma delimited string within the Property Tree of the Teradata Enterprise Stage. synctimeout=300. Ex: RequestedSessions=8,SessionsPerPlayer=2,synctimeout=300, WORKDB=TEMP,TENACITY=1,SLEEP=5 Using TENACITY and SLEEP require a patch from I...

What is limiting you to only 1-2 Teradata jobs. Any more than that and they fail? What is the failure? What is different between DB2 and Teradata? 1. A DB2 job does not have to be re-partitioned because Datastage is DB2 partition aware. Teradata to DataStage is not. Is it a re-partitioning problem o...

I can't answer your most recent question but we had deadlocks for two reasons; 1. RequestedSession, SeesionsPerplayer was not set therefore they defaulted to RequestedSessions=the number of AMPS, SessionsPerPlayer = 2. This was way, way too high. With 68 sessions simultaneously trying to update the ...

It may be asking a lot to be able to use a Project environment variable in any stage but it is most certainly NOT asking a lot to be able to use them for connectivity to a data source like DB2. If you needed validation that you aren't asking for a lot, you've got it. I completely agree. To me, this ...

"The key is not to bend the spoon with your mind, or join the two tables with no join, but rather to understand that there is no spoon only sporks. "

Use a Look-up stage and define a literal-valued key to join the two tables containing the columns.

Nullable status for all fields is NOT No. At least one: "XXXX" is defined in the database as NULLABLE. Your job column metadata should match the DDL of the database table. The Table will override your job metadata, hence the warning. Further just because you hand code an IF statement doesn...

1. The column definitions in the job do not match the field definitions in the Teradata db table. This is the reason for 1. Converting a nullable source to a non-nullable result; 2. You are using a 2 node configuration file and a 4 AMP Teradata db without specifying RequestedSessions or PlayersPerSe...

If the "insert" XPATH can be defined then it can be parsed from the rest and output as an xml fragment. In your example you could define a column with this XPATH in the description: /msg/insert You will probably need to define it as a repetition element as well which means it will need to ...

If the input link to the Transformer where the warning is coming from is from a Teradata stage then your CHAR (2) is being overriden by the Teradata table definition being accessed by the job from Teradata. Can you confirm that the source table or SQL that contains this column name is NOT defined as...

What? string[max=5] means the field is defined as a VARCHAR (5)!
string[2] means it is defined as CHAR (2). What does the actual Teradata DDL say the field in question is defined as?

You won't find it but you can define it as a User defined env variable. Set it to true.

Intuitively, I believe adding this to the Project and setting it to True along with a NULL Field default of '' (empty) will solve your problem;

APT_IMPEXP_ALLOW_ZERO_LENGTH_FIXED_NULL

I just used root for convenience. The repeating chunks are buried way deep in the overall XML structure.