DSXchange

So? Any of this help?

I said Pee X, not Tee X.

Hmmm... all you should need is your user in the 'at.allow' and 'cron.allow' files. I don't recall ever having to have an SA worry about permissions on the core files.

One simple 'solution' would be to use an Oracle stage for this, insert it directly. Why futz with a stored procedure just to insert a single record to a table?

If it is meant to be reusable across jobs, put it in a Shared Container.

He was speaking of the PX transformer stage, not the Server object.

Define 'load'. Are there any transformations involved? All inserts? Insert / update / delete?

As noted, I'd probably opt for letting the database perform the aggregation for the second load.

Always four? Stage variables can solve this rather easily if that's the case.

Your 'invalid character' is the #, which means your parameter is not being recognized and evaluated. This is because a parameter cannot resolve another parameter inline.

Not sure how anyone can help with that little information. When something works on its own but not from a Sequence job, the first suspect would be the parameters being passed. Another thing to check is to Reset the aborted job (it does abort, yes?) and see if you get a 'From previous run...' message...

Was it relying on the fact that with a small row count, the first Transformer process will have finished reading the file before the second Transformer gets around to processing the first row? There's really no such phenomena going on. Unless you have row buffering turned on, then a single record w...

Guess they didn't want an acronym you would pronounce as 'Scummy'.

I would imagine it would need to change again before it goes out the door, as SCCS is a well established beastie in its' own right.

Ah... that explains the abbreviated error message, me thinks. I screwed up yesterday and generated several of my own, writing to a hashed file with a null key - those are a wee bit more verbose and obvious as to the source: Job..Stage.Link: ds_uvput() - Write failed for record id '<Missing o...

While waiting (and waiting) for this to post, noticed the forum I had ended up in. Since this really doesn't have anything to do with RTI...

Moderator, please do the needful and move this to the PX forum.

Tanks.

Wow. While I have been involved in generating fixed design jobs based on variable metadata, I can't imagine being able to do this based on the whim of 'different users needs at runtime'. And I don't see how 'user needs' play all that much into the ETL world. Who would these users be? What kind of ne...

Then it sounds like you need to involve your support provider.

ps. The 'datastage job scheduler' *is* cron (and at) on a UNIX server, the Director is just an interface to it.