DSXchange

No worries, that probably wasn't the best choice of words. Debating, discussing... whatever, just get on in there and give it a whirl.

nivas wrote:I need to join to a hash file like follows.

You can't. A hashed join is an equi-join, period. Search the forums for 'range lookup' (or perhaps 'ranged lookup') to find various conversations on this topic and what your alternatives are.

Actually, you are truncating the table over and over again, and all that you see there in the end is the last record loaded.

The problem is when the retrieve the nextval this is the same value por a group of records, 5 records or 10 records, is different from each execution Not really sure what this means. If you mean your first call to 'nextval' gets you 5 (for example) and the second is 105 rather than 6, that's a func...

Actually, they are 'user defined'. And you, the user, need to define them in your environment. Rather than argue, suggest you just give it a try.

You import them via the Manager and then load that resulting metadata in the WS Transformer stage.

No, that's true with a Transform but not a Routine. The overhead of the call is negligible but I wouldn't necessarily use one unless it was essential or you wanted a reusable/shared object.

So... you've got records with no field delimiters but not all fields are fully populated? Who comes up with crap formats like this? I don't see how you would do something like this outside of a C or C++ program. Or, I guess, a BASIC routine that does the same, but I imagine that would be... slower. ...

Just... type them in as User Defined variables.

swathi Singamareddygari wrote:

ray.wurlod wrote:There is no job parameter named ACT_L00_TRG in the job called jobname. ...

i am using that parameter in the job

No, you're not or it would be working. And no, you don't need a dollar sign, just the right parameter name.

The job needs to Abort to automatically perform a rollback to the last commit point. For an 'all or nothing' load you'd need to be able to specify that there be no intermediate commits but only the single one at the end. Others will have to answer if/how you can arrange that in PX. Set the intervals...

Define what you mean and include an excellent example so we don't go chasing the wild gooses.

The Filter has problems with wildcards sometimes. Plus you don't do redirection there, but rather the stage reads std out of the filter command. If you want to stick with your command as written, simply put it as a 'before job' ExecSH command and then use the resulting file in the Sequential File st...

WHERE PLT_FROM<=:1 AND PLT_TO>=:2 Means you have two Key fields. The lookup is done where PLT_FROM is less than or equal to the first Key value and PLT_TO is greater than or equal to the second Key value. If you want to stick with the OCI lookup, ensure that query is as well tuned as possible. Or, ...

That simply means you don't have a parameter named "ACT_L00_TRG" in that job. Check the spelling, including the case.