DSXchange

No more ridiculous than DataStage jobs that just run Stored Procedures.

And post your exact 7.x version of DataStage.

The patch allows certain stage properties to be accessed, before that they cannot even be 'opened' once SP2 is installed. AFAIK, that is all that it corrects. This really is a separate issue, however, installing the patch certainly couldn't hurt.

Sure. I made the assumption that the types are matching and it's not something really basic like that.

velagapudi_k wrote:Pls Correct me if I am wrong. Till now I assumed 7.5.2 is same as 7.5x2.
Is it not?

Nope, hence my comment. 7.5x2 is a magical release and the only Windows version (so far) that will actually run PX jobs on Windows.

It may look ok when testing, but it really isn't which is why you get the error. This is typically because of @FM characters in the returned value. Without knowing exactly what you are doing, a couple of suggestions: 1) Either take only the first element of the dynamic array by putting '<1>' at the ...

Those functions don't work for Sequence jobs.

I don't believe this is available in 6.x but in 7.x you have Activity Variables so you wouldn't need to hard-code everything. StageName.$JobName springs to mind.

Well worth upgrading, btw.

velagapudi_k wrote:Even we are using 7.5.2 and I dindt have any problems.

They are using 7.5x2 - different version. Open a case with Support, see what they have to say.

If you have 10g the DBMS_LOB package comes in very handy.

DSguru2B wrote:A little correction, array size is not the commit level but how many rows are passed in a single go. An array size of 1 sends 50 rows i think.

A little correction to your little correction. An array size of 1 sends 1 row, hence the name.

Are you planning on using ODBC? Or OCI? If the latter, then it's a matter of configuring DataStage for Oracle and it's documented in the Install and Upgrade Guide and the Plug-In Configuration Guide.

You really shouldn't be posting this same problem in multiple forums. And I really shouldn't be answering you here, but... The more you talk about this, the less sense it makes. In my case as there are chances that at some point the sequential file is missing and job at activity C [as mentioned earl...

Welcome aboard Ernie.

I want to start the job from jobactivity A for each successfull run and not from the point where it manually aborted due to a comparison abortion in joc called at activity C. I believe meant 'unsuccessful'. So... again... you always want it to start from A, regardless of what happened on the previo...

Timeouts and the dreaded -14 error trying to start jobs are signs of a resource constrained system...