DSXchange

Wait... does 'ignored the slash' mean 'removed the extra slash' here? It fails with two slashes but works fine with one slash?

Nothing you can do other than get your hands on a version that does support running PX jobs on Windows - and that's 7.5x2 (yes, with an 'x') or anything in the 8 family.

Exactly, simply put the full path to the script in the Input Values field along with any parameters if needed. And you can use job parameters in any portion of that. If needed.

Not really a DataStage problem. Best to work this out with a DBA or whomever does SQL support in your organization, get them to help you work this out. As noted, not only must you select the same number of columns on each 'side' of the union, data types of matched columns must be compatible as well.

In order to install/use the product on UNIX one must first purchase a copy of it for the UNIX of one's desired flavor such as RHAS. Having a Windows license doesn't get you anything you can use on UNIX.

A "double slash" usually isn't a problem. Ignoring that, are you certain the hashed file at that path otherwise exists and is accessible?

That would be when 11g is first officially supported. That's not to say it cannot be accessed successfully with earlier versions. Oracle clients are "forwards compatible" so I'd be surprised if an earlier client, like a 9i or 10g one, couldn't be leveraged here. Best to take these question...

Exactly, more like a snippet of procedural language, something akin to PL/SQL in Oracle.

Sorry for the late response. No need to bring down DataStage and the "2+ days old" criteria was to avoid effecting any running jobs.

First thing to check would be the number of entries in the Project's &PH& "phantom" directory. Large or out of control numbers there could induce a processing lag. If needed, clear out anything 2+ days old and see if that helps.

Clarify something here. Your subject says "Delays between Job Sequences / Calling Next Job" and yet you never mention anything about that in your posts, just mentioning total run time for the sequence of jobs. So... when the overall sequence goes from 12 minutes to 35 minutes for the exact...

That is called 'pivoting' the data, specifically a vertical pivot of rows to columns and of which a search for that phrase would turn up many conversations on the topic.

Ask your DBA or if you have something like Toad (you should if you don't) it can show you. This is typically a PL/SQL error, hence the trigger question.

Longvarchar.

No, there isn't a way to "disable" activities. You can add conditional logic to branch around them if you're going to be doing this on a regular basis, otherwise you've hit on the other two techniques I would have mentioned.