DSXchange

Right, we've all noted that fact by now. I'm looking for a clarification to the statement that the job actually runs fine with this issue only being seen when doing a View Data from the stage...

Errr... ok.

qutesanju wrote:reran the job with modification in the job

What modification?

You should never "select *" rather than list all of the column names, I would wager the columns are different in prod... although you haven't told us what your "failure" is.

All of that would be documented in the new release itself or on IBM's website.

All of that would be documented in the new release itself or on IBM's website.

If you are running your jobs via dsjob then you have full control over that via the -warning option. Otherwise, what 8.x release are you on?

I don't recall a 7.4 release but anywho... it's pretty simple. If your question is specific to Server jobs then it goes in the Server forum. Questions specific to PX jobs go in the Enterprise / Parallel forum. If it is something relevant to all versions, like installations or configuration questions...

That "in the same job" part would be possible in a Server job but I'm not sure you can in a Parallel one... hmmm...

You seem to be firmly in IBM's hands at this point... no clue why it would be doing anything of the sort.

Involve your DBA as that is a database issue from what I've read. One example here. Other examples are out there.

OK... how would one generate a "sequence number" with the new transformer looping? Forgive me but not getting the how of that.

I changed the subject of your post to state the proper issue.

Let's go back to a statement you made in passing... Did you not say the job runs fine and this issue occurs only when you try to View Data from the OCI stage? If so then you seem to be firmly in Bugville and should be contacting your official support provider. The only other thing I might suggest is...

Agreed, but there isn't one hence my answer.