DSXchange

sohasaid wrote:@chulett, I just want to make use of the whole memory (16 GB) instead of changing the job design.

I honestly don't believe you will have any other choice. We shall see, I suppose.

Ark ark. Why, yes it is.

You would use a UV stage, not ODBC. Or just run the query from the command line via dssh, let me see if I can find an example for you.

Here is one, searching for "dssh" will turn up others.

Same as you would do it for any other dynamic parameter - do something to determine the value and then pass it to the job that needs it. That would typically involve a job (or script) to get the max value and a Sequence to run the two jobs one after the other and pass the value between them. Simples...

Check closer. Lookup failures simply mean you did not get an equality match on the values. Period. So, for whatever reason, your values are not matching. Do a View Data on both the source and lookup source, and click inside the Key fields on both sides. Move your cursor around inside each field. Tha...

Not that I am aware of, there's nothing "dynamic" about those values as far as I know.

I'm going to repeat one last time that, IMHO, concentrating on the transformer and/or hashed file lookup is a mistake. Those kind of errors come from the target, typically Oracle client / driver generated errors and they can be very odd and very subtle, working for 99.9% of what you do in your jobs ...

You reverse the roles, exchange source for target in a job design, that's all I meant.

As noted, the Director shows the number of successful lookups to the hashed file of which you had zero. As also already noted, this is typically a trimming issue, something like "ABC" will not match with "ABC ", for example.

For that, you need to "land" or "stage" your source data, meaning a flat file or staging table, then load from there. That way it becomes static and you can take as long as you like to check whatever needs checking without worrying about what may (or may not) be going on in the t...

Arnd simply corrected your use of a routine attaching to the calling object. That doesn't change the fact that you cannot do what you are attempting to do... which it seems you are still attempting. Or are we just off in testing land?

There's no direct mechanism to do that. Some people use a Universe query to pull out a list of object names for a category and then loop thru them with dsjob but there's no way to do that directly.

Do an explicit conversion of that field using the StringToDecimal() function as one example of a way to do that.

arunkumarmm wrote:Any thoughts on using a ODBC stage to write the target file?

Using the text drivers? No clue how well that would work but might be worth experimenting with. If you give that a try, let us know.

Sorry but my second suggestion isn't valid for your target type. There's nothing in the nature of a sequential file that would cause rejects, I lost track of that and thought we were talking about a database table. Now, you could use a database table as an intermediate staging point, a work table in...