DSXchange

Which is exactly what I meant - spelled the same, cased the same, yada yada. And the parameter name is obviously wrong just by the fact that they do not allow 'dots' in them... confirmed that today on the off chance I was misremembering that.

I would suggest having it upgraded to at least 9.2.0.5, but I also haven't had any issues with 9.2.0.6 and 9.2.0.8 as well. Earlier than that and they seem to be chock full 'o nuts.

That shouldn't be a problem, we do the same thing here. What's important to find out is the exact version of the 9i client you have installed - it should be four sets of digits, like 9.2.0.8 for example.

I assume you mean DBA not dbx, and you'll check with your Oracle folks, but whatever works.

You don't have a job parameter named "targetfile.txt" defined in the job. And I'm fairly certain parameter names are not allowed to have dots in them, change the name and see if that fixes things.

No, that's not used. I mean the Oracle client on the DataStage server. Forgot to ask - is the Oracle client version on the DataStage server a different version from what is installed on your actual database? Ultimately, unless we manage to fix this, any kind of answer about core dumps will need to c...

My assumption there was that a Sequencer set to 'All' was added to the sequence job, that's what makes it wait for multiple jobs at once. Nothing about doing that should make it go 'haywire'.

Yes, it is compatible. Not saying it will work or that CLOBs are a supported data type, but it *is* compatible. Let us know what happens when you try.

In other words, as already noted, they are identical. Well, except for the schema name parameter which is not anything that would cause a core dump. Core dumps come from bugs in the Oracle client, from what I've seen.

That would be my opinion, yes. I'm sure others here will disagree and I'd be curious to hear their reasoning.

Odd... and I really got nothing, sorry.

Is this a repeatable behaviour with the modified version of the Sequence or was it a one time thing? I'll guess we may have to wait and see.

PhilHibbs wrote:Is it possible that running a job of the same name in another project might confuse the Job Schedule?

Nope. Are you certain the Sequence itself tried to start the job twice? Any chance someone/thing else started it before your Sequence did?

ps. Don't recall ever seeing anything like this.

I assume the OP was asking about XML format versus a 'normal' flat file as a source, not about trying to read XML with a Sequential file stage. Let us know, xyz. Perhaps I'm an old fart, but I find XML an enormous PITA - unnecessarily large, unnecessarily complex, needing to be sucked into memory to...

It should be fine as long as you know the max, I would think. And it doesn't need to be a fixed number, you can filter out any 'shorties' downstream of the pivot.

You can split the second 'combo' field in individual fields and then Pivot. Do you know the maximum number of pipes you could see there?