DSXchange

Surely you don't mean the Remove Duplicates stage?

Your previous incarnation of the job you 'stopped' was still running. Or at least the Oracle process associated with it still was. That was what kept the table 'busy'. I've seen that happen - job stops or aborts but the Oracle process lives on. Then you either need to wait for it to finish or have y...

Welcome! :D

Yes, as long as they are declared as Job Parameters, they can be used in your Oracle query. Just enclose the parameter name in hash/pound signs when you use it.

Or you can look into 'Releasing' jobs and using the Package Installer to migrate executables. However, I believe you are doing yourself a great disservice by not including the 'source'. Are you sure that 'not allow access to source code of jobs' doesn't just mean you use a Protected Project or trans...

Hmm, great. Hey Craig, I did'nt know you were a windoze guy too Well, I do run a dual-core AMD box for gaming, and some less-than-well-written ones don't like multiple cores. So you make them work by binding them to a specific processor. You can do it either post-launch as above or using a utility ...

Not even just a UNIX thing, you can do it on yer Winders box.

Three-finger-salute, Processes tab and right-click on any process...

Edited to add: assuming some sort of 'multi-core' setup, you won't see the 'Set affinity...' option with a single core.

Sounds like it could be a bug to me. From what I recall, $PROJDEF worked much the same way in the initial release of that functionality, something they subsequently 'fixed' so a recompile wasn't necessary to pick up changed values.

Perhaps a Support call is in order?

Really? It certainly can be done in a Server job, don't see why that aspect of this would be different in PX. [shrug] It's the exact same 'XML Input' stage in both products, yes? Not a PX specific flavor that I am aware of, so sure seems like you should be able to make that work the same way. Make s...

Right... we all saw your fake sql in the first post.

As noted, any valid SQL will work in DataStage. What precisely is the problem you have when you try to use this in a job?

ray.wurlod wrote:You have omitted "A" for the month.

Dang, missed that.

Looks like output that would normally be in your &PH& directory. Best to call your Support provider and ask them, I would think.

Of course, and something I'd already posted earlier.

You don't "need" a batch job, though one certainly could be used. You could read the file in a Server job, build your table name from the date and then run your other job once per record. Look at the UtilityRunJob routine in the 'sdk\Utility' category, it is what you would use in the transformer. Do...

I don't think so either. Passing them in from outside means they are just strings inside the job, it won't recognize them as valid link and column names.

Be glad to be proven wrong, however.

I have tried passing the stage a file name as specified in the XML source tag but this doesn't work either (job succesful, but empty output). I'll wager you read the XML file just fine with that setup. Stuff in with no stuff out is generally a sign of improper XPath expressions in the XML Input sta...