DSXchange

Isn't WADL a description of duck locomotion on land?

There's no Cust_Type_Ind IN ('I', 'N') and no Cust_Type_Ind IS NOT NULL constraint in your SQL query.

Won't be a problem to host.

Now if only I could find the time to put the rest of my website together!

Are you reading from the same table that you're updating? You may be seeing lock contention.

Array size is merely the number of records transmitted at one burst. It should be calculated as the buffer or packet size divided by the estimated record size, rounded down to a whole number (ideally a multiple of two). Number of records per commit (per transaction) is typically a separate property....

There isn't one.

If there is, it's something YOUR developers/designers have implemented. It is they, therefore, who need to do the explaining.

What advice have you had from your official support provider? Have you even asked your official support provider about this issue?

Qantas is having a sale at the moment - if you book before 5th April 2014 you can get a return economy fare to Las Vegas of $1399 (usually just over $2000).

I've seen something similar when connected via Remote Desktop to the client machine. I keep a Director client open, and Alt-Tab to it and back again. My main gripe is that using scroll bars seems to lose focus from all other controls in the Designer client. I do not see this behaviour when directly ...

What count do you get running Test #3 or Test #5 through a non-DataStage client, such as TOAD?

deesh wrote:to solve the issue, do we need to enable the Runtime Column Propagation.

First can you please explain what you believe "the issue" to be?

Welcome aboard. Fault type 11 is an access violation (SIGSEGV). Your application has tried to access a memory location it does not own. There are very many possible causes. Reset (rather than re-compile) your job and view the "from previous run" message that is logged as a result. Share it...

I don't really see this as being a parameter issue. It might be. I have had one experience of a job running in PROD that was passed parameters to the DEV environment, which did not have the capacity to do all the things that were being requested to be done in PROD environment. Took a while to diagn...

Welcome aboard.

What is the row count reported from the Oracle Connector stage (in the job log)?
Are you really selecting from the correct Oracle schema and table in your DataStage job? Double check, then triple check.

How many nodes are there in your parallel execution configuration file?

Look at the "job starting" events in the jobs that are getting aborted, and verify whether parameters are being passed correctly.