DSXchange

:idea: I added the code tags you were missing around your lovely ASCII art, see how much better that looks? Without them the forum software removes all whitespace from your posting and it would go back to looking like this: Oracle1--->Transformer1---------->Lookup1-----------------> Transformer2----...

prasad v wrote:Yes craig, If there are no matching records in the target table. we get rows in the source.

That's one of the things the lookup stage is for.

PATH=$DSHOME/bin:$APT_ORCHHOME/bin:$APT_ORCHHOME/etc:$PATH:$ORACLE_HOME/bin This statement takes your current PATH and puts three directories onto the front of it and one on the back - your Oracle 11g home bin, which explains how the second one got there. You need to look elsewhere to see where PAT...

Can you clarify what you meant by "I find PATH environment variable is trying to read from 2 different databases"? The path is just an ordered list of directories to search, it doesn't "read" anything. If you are concerned about two entries in the PATH, it will use the first one ...

Clarify what you mean by "no records to update in the target table". Ray went with "no records in the source" but I'm wondering if you mean you send an update to the target and it updates zero records?

We'll be here.

Yah, I would suspect a bug here and suggest you contact your official support provider.

Modify stage.

1. Typically, one would include the Invocation ID as part of the name. 2. Since you'll need to set the job to "Append" for the remaining two invocations to work properly, that means you'll need to do something before job to delete any existing version of the output file. Append will happil...

If so, then you would have seen you may need to roll your own as noted here, yes? That 'MS' function doesn't show up until the 8.x version from what I recall.

This means exactly what it says - after the job fails and you restart it, the checkpoint rerun must be restarted with the same parameters in place that the failed run used.

What flavor of UNIX? Have you tried an exact search here for 'microseconds'? I know it has been discussed here in the past and from what I recall, not all operating systems support current time down to that level.

ponzio wrote:

ray.wurlod wrote:you can tune the size of the memory table used by the Aggregator stage. ...

I don't know where I can specify this info ...
Exixts this possibility in DataStage Server ?

Under the covers from the command line via dssh and the DS.TOOLS menu.

If you sort your data for the aggregator, make sure - 1) the sort matches your grouping and 2) you note the sort order in the Aggregator. You must do both for it to help at all.

Is this a problem with just one specific job or all jobs?