DSXchange

There are no "common compilation errors" and the basic job import/export process hasn't changed. Any kind of "what's new" information will be in the documentation. You may want to search ITToolbox (or whatever it is called nowadays) for Vincent McBurney's blog postings on the sub...

It's not a "key" in any sense of the word, that's just the field you use to mark the "repetition element" in the XML. Try timeStamp and see what happens.

That would come with the 8.1 software - what used to be called the the 'Installation and Upgrade Guide' is now the Planning, Installation, and Configuration Guide.

Depends on what you mean by 'node' from a database standpoint. Just make sure your sorting is appropriate for the partitioning you are doing in the job and you should be fine regardless of the 'nodes/partitions' of your database.

If you do the sorting in the database and you want to ensure it doesn't get sorted again after that, add an explicit Sort stage and set the option there to "Don't Sort, Already Sorted". Or, from what I understand, you could do "1b" instead but the former technique will be a littl...

It should, as long as you use one or the other. The -jobstatus option gives you 1,2,3 (etc) which match the internal numbers DataStage uses whereas the -wait should be zero or some kind of non-zero return as you've noted. If that's not happening, it may be an 8.x issue and one you should raise with ...

In a way, that doesn't really matter. The Sequence ran the process and that was all it was tasked to do and it was able to do it. The same could apply to Job Activities or any other stage in the Sequence... unless the Sequence itself has a problem, it's going to report back that it ran just fine. So...

You need the Sequence itself to fail or at least log a warning when there are issues with the processes it runs and there are many ways to accomplish that. There are compiler options in the Job Properties tab, for instance, or the Terminator stage to name a couple of things.

You really need to work with your official support vendor for this. The 8.x release complicated situations like this by storing that kind of information in two places and while we could possibly help with any synchronization issues with the legacy repository, the addition of XMETA and what may or ma...

So... what would you consider an 'invalid' varchar?

So an ODBC issue, it seems. Was your DBA able to help with it at all?

Fails how? Without any details there's no way to give you a cogent answer. There's no 'limit' that I'm aware of but that answer may change depending on the nature of your problem.

Also meant to ask but forgot - do you have an Oracle client installed on the DataStage server? That's the primary requirement, after that it is all about the configuration.

What have you done to configure DataStage for Oracle? I would guess that "fresh" here is a synonym for "nothing".

What you'd need to do is spelled out in the Installation and Upgrade Guide and a couple of other documents, from what I recall.

I'm just going to repeat what I said in your other post on this subject.

chulett wrote:As noted, you haven't stated what it is you actually need help with nor asked a question. All you've done is state your task. Please try again.