DSXchange

You appear to be using a temporary table (#temp). But DS might interpret that as a parameter with missing #.

Reading the SQL, I do not think it is a temp table but an inline view. So it must just be temp.columnname

Are you having any counter?

You can try skipping (constraint) first 8m rows and try loading the rest.

Check the "Properties" tab and define a new parameter.

First, I will suggest getting the buildop working.

It is possible. Period.

Define a property variable and pass to it.

It is possible. Period.

Define a property variable and pass to it.

Need more information.

Why is the input to appearing in the fashion? That too when it is almost ready to be loaded into fact table !!

You can pass it as its property variables.

You can pass it as its property variables.

Do you have a test area?

I assume the job did finish successfully !!!!????

What about the volume? row size? transaction size?

Monitor the session and SQL from Oracle side.

1.) What if you try to run now with old format of invocation id?
2.) Was the invocation Id prepared from some given set of values?
3.) Was the job/routine preparing invocation id disturbed / corrupted?

Did not read all the mails, so do not know if this has been covered... 1.) How were the jobs scheduled? i.e. via DataStage or external scheduler? 2.) What is the invocation id (prior to failure)? i.e. what format? 3.) What was the invocation id (during failure)? 4.) Were there any invocation sequenc...

Try
without -1

This clearly proves that "thinking alike" is not restricted to wise people.

Why and What do you want to achieve ?