DSXchange

Those particular objects (job or routine) contains a prohibited literal ASCII value.

Certainly they removed the option to search out orphaned job components, though the verb remains. That must have been my repressed memory, but it's gone now under 7.5. I wonder why it's gone, because log, config, and status corruption seems to be so common. Sometimes importing the job again doesn't...

You can't compare an intra-instance join query with a pl/sql script using cursors. A DS job with 8 OCI lookups is equivalent to a streaming query with 8 cursor lookups. It's not parallel, doesn't cache repeated lookup values, and doesn't use any of the technologies DS Server has built in it for perf...

Methought there was a repair repository files under the DS.TOOLS repair indices processing? Was I drinking heavily at the time?

All PX or can you use a database (Oracle maybe) to faciliate?

Well, how do you know what constitutes a "row" of data, when it begins and ends, what attributes make up a column and meaning, etc? Sounds like you need to crack a few heads. You could invent a Karnac (sp?) stage that figures out the answer without knowing the question. Sounds like a Douglas Adams s...

What's the structure of the binary file, did they tell you how to read it?

Of course, once you're already there to find out the jobs number, you could just run DS.TOOLS and be finished.

To find out a jobs internal number, you must look at internal file DS_JOBS. Search for help on that.

Define "binary". Are you talking about an EBCDIC file? See the CFF stage. Remember, a Server Sequential stage expects to either read a delimited row ending with a line terminator (CR/LF, LF, user-defined) or a fixed width row with optional line terminator (read to line terminator or via set block si...

Use DS.TOOLS to repair the repository. Search the forum to learn how to access it.

If you have rows that repeat and need to be handled as insert-update-update, or even just update-update-update, you need a referenceable target. The hashed file is perfect for this. It's capable of taking new rows and overwriting existing ones. If you don't have to worry about a manipulated row bein...

Rather than directly writing to the database during transformation, you could stage your reference data into a hashed file, then insert and update rows within the hashed file instead of to insert and update links to ODBC. Then, just dump out of the hashed file the new rows and use insert DML, and du...

In a transformer stage, lookup the existing row (either ODBC lookup or for performance pre-stage to hashed file), if not found derive and send to insert only link. If existing row found, use derivation logic to decide (If NOT(ISNULL(reflink.colX)) Then reflink.colX Else inlink.colX) and send to upda...

"Will datastage do the necessary transformation" What does that mean? If you use a user-defined function in a SQL select query DS doesn't know or care. If your function is "doing stuff" such as queries than understand the performance impact that each row in the query set will run that function, whic...