DSXchange

Shame? Hardly. I apologize if it came off that way to you, it was more of an attempt to get you to think about what you are posting, to provide enough information so that people can actually help you in a cogent manner rather than have to ask for the details needed to provide that help. It would be ...

No, I would think this could all be done in one job... except for the 'counts in the header' part, that complicates things. Unfortunately, off the top of my head I'm not aware of any trick to insert a record at the front of an existing file without concatenation and the creation of a new file. Not s...

It could be as simple as you or someone else, even using another tool, had a record locked outside the job. When it happens again, your DBA should be able to pinpoint if that is the issue.

Hey Arnd, what is the zero date for julians in Universe? I seem to remember it is old whats-his-name's birthday but can't for the life of me find it. The OP would need to verify their zero date and then offset (as you mentioned) from the internal zero date for this to work.

You don't need "user defined" anything for this, the two links into the one stage will support generated sql just fine. And you certainly won't need the Transaction Size as 1 for this although you do need to be careful with the Array Size if there is any chance you are updating records you...

Again, for the umpteenth time, your design as posted will do exactly that. What are we missing? :? What exact 8.x version are you running, btw? If it is anything other than the latest iteration of 8.1.x.x then suggest you check with your official support provider and see if this is a known bug in yo...

You suppose? You need to find out what those dates translate to before anyone takes more time to guess at the proper solution to automate that.

"keep on running" sounds like a locking problem, have you recruited your DBA to see what is going on in the target table?

The are SAP PACKs available from IBM but I am unclear on the connection mechanism they use. I would assume ODBC for all of them, however.

I was pulling your leg, of course.

So... you've marked this as Resolved but we really didn't come to any true resolution from what I can tell. Can you let us know if you have actually resolved this, please, and what that resolution was?

:!: You cannot have multiple writer processes targeting the same sequential file simulataneuously. That's just "how it works" and has nothing to do with DataStage - it is a restriction of the nature of "sequential" media. If that is what you are doing (and it seems that way) you ...

Yipes, 1? Why do you think you want to set it to that value? And what does this have to do with anything Server related?

How about you tell us what problem you are attempting to fix?

We are obviously missing something or you've left out some critical details - this is dead simple and should work as desired and as (allegedly) designed... unless you are not telling us everything.

As the routine is giving the rowcount as the result it is throwing a warning message(which I have posted) in my previous response. We know that, have addressed that, and have given you the solution for that. If you want to pursue this, make sure you fully describe everything you setup coming out of...

buzzylee wrote:Is there a chance Oracle fixed this issue in 10.2.0.5 version and then introduced this 'bug' again? Somehow I don't believe it

Haven't worked with Oracle much yet, eh?