DSXchange

Information Analyzer 8.1.2 Currently, Information Analyzer outputs task results, e.g., records that violate a rule, to its own table called IADB. If you want a detail exception report on those errant records using an external application like Oracle BI, you have to export the data out to a flat fil...

We are looking to run a data rule (IA 8.1.2) against a subset of a table, i.e., selected rows based on a condition. For example, we might run the task only against rows whose MATURITY DATE is >= a parameterized date. We're thinking of using Datastage to do the selection (easy enough) but we're wonde...

If it's just a flat file, use the Sequential File stage.

In a Sort stage, turn key change column to True. This key change column stores 1 if the key value of the current row is not equal to the previous row's value or 0 if the key value of the current row is equal to the previous row's value. So whenever the key change column is 1, write to a new file. As...

Just as I thought.

Tab_B left outer join Tab_A on ID

followed by

Transformer, where Tab_B.COL_B is derived from NullToZero(Tab_A.COL_A)

Where the ID matches, Tab_B.COL_B gets the value from Tab_A. Otherwise, it gets zero.

I'm not clear on the mapping, but consider using Oracle left outer join to netezza and NullToZero(value from netezza).

videsh77 wrote:If this sequential file at the end of the job is non-empty, is there any way we can abort the job, so further stream of execution would not progress.

I'm confused by this. If you reach the end of the job wouldn't it be too late to abort it? Unless you're talking about a job sequence?

If I interpret your logic correctly that you want one occurrence of Y's, then use the constraint Flag = 'Y' in Transformer together with either a Sort (no dups) or Dedupe.

AFAIK, switch/case has no equivalent in DS, other than the way priya suggested.

AFAIK, switch/case has no equivalent in DS, other than the way priya suggested.

I understand the OP to mean he only wants one input into a Join stage, which requires two. So to do a self-join, I'm with you...two inputs, but both are the one physical input.

ksk wrote: i want to use only one input stage not two same input stage for example

But a join requires two input streams.

And I take it a change to an existing attribute will not trash others.

Thanks again, gentlemen. You made this a lot clearer.

We might add terms, contacts, policies, others. Page 49 of the v8.1.2 User Guide describes how: Metadata Management.

What's not clear to us yet is how this affects metadata already in MWB, how the two tools work together.

(btw, nice quote)

Thanks, gents. Actually, we want the detail records - not just the report - to be visible outside IA. We plan to use Oracle BI (Answers, Discovers) for reporting. But if we modify or enhance metadata from inside IA, we don't want to clobber what metadata was already created in MWB. Thanks for all th...