DSXchange

I could not get this to work because I could not squish the xpath into the description of any column within a schema file. I believe that IF THAT could be done then you might be able to fix up some kind of RCP. Big if. I believed at the time and still believe your best bet would be some kind of cust...

Probably this; Occurred: 8:39:56 AM On date: 5/15/2009 Type: Fatal Event: SEQ_SRC_FILE_E1,0: Filter status 512; (...) But so what? Whenever I get a gazillion warnings, I start at the first one and fix as many as I can before re-running. Some of the more obvious ones might be cascading into others wh...

I believe that is enough detail. As a general comment, You've got tons of Metadata problems. You've got to match your Oracle Stage with the actual DDL in Oracle, including Nullability. One gotcha is function calls; They are reported to DataStage as DECIMAL(38,10). Another is an Oracle NUMBER no prec...

Try using a DS Macro. If the format is acceptable it would be somewhat simpler then the other suggestions.
sample#DSJobStartDate#.txt

This implies you are using a partitioning scheme other than Entire in the Look-up stage. Is this really required?

The SERVER Merge stage takes no input links and outputs a single link. The input to this stage is two flat files that are sourced from within the stage itself.

It seems to me you need to take a step back and think about doing a little research/learning on the tool. This specific problem has been answered in this forum, if not a bazillion then certainly a gazillion times. Do a search man! It is your friend. In the time it takes to ask, you'd have been answe...

Yeah, what he said.
Now, you know you'll have to handle the outliers as special cases.
For example;
1. The very first row in won't match prev but may not have to be written out immediately.
2. The very last row in needs to be triggered to write it out, even if curr matches prev.

This is the last high-jacking of this post, I promise. That is exactly what I am saying. When creating a teradata table in EE, if a PI is not specified, the first column becomes the PI. Primary Index Property Help; Comma-separated list of field names that will become the primary index for tables, if...

With Seinfeld and the swirl as with Teradata Enterprise Stage and the PI; the order can make a significant difference.

I eye-balled the same when DDL-ing a Teradata table in EE. I had the newbie hope my first column would be the P.I. if none was explicit-ized. By bad as the stage Hal2000'd a column of it's own choosing causing major skew and hot ampin' like a Moe foe. I'll circle the wagons to see if the derivations...

The order of the Stage variables is of paramount importance. The number of keys is not. If the order is as you've listed them above then the "IF" stage variable will never detect a key change. The "current" comes first followed by the stage variable that detects the key change an...

I believe so. DSCAPIOP is not your problem.

You'd need an exported copy of the job before and after the change was made. You could diff the two and get close. I don't know the best way to do this in Windows although I have done it with some XML "diff" utilities in the past. This obviously means exporting the job before/after as xml....

The DSCAPIOP problem manifests itself at the stage level. Meaning the job itself and most stages will substitute correctly. I think it would be worth checking to make sure the ODBC stage is correctly substituting as well. To do this I think you need to set the Project Reporting variable OSH_DUMP to ...