DSXchange

Search the forums here for a portion of your "XML parser" error string, from what I recall it's been discussed before and it's some kind of permissions error.

Hmmm... that drop-down list doesn't show Folder names that I recall. What exact version of DataStage are you running?

Did you try the drag game? I use that pretty much exclusively nowadays, it is so much more convenient.

Drop the 4th column before you get to the Oracle stage. Not a PX'er by any stretch, but couldn't you use a Modify stage for that?

Yup.

Kudos for finding that information on your own, rather than making us explain it for the bajillionth time.

Very good midnight to you. :D No, there's no setting needed for this. Please explain what "I am not able to browse the job" means. Are you saying that your job does not appear in the drop-down list in the Job Activity stage picker object? Make sure you look through the entire list of jobs available ...

That's good to know. I've been under the impression up until now that partially sorted data was as worthwhile as unsorted data - kind of an 'all or nothing' proposition to gain any value from it. Not sure why, never ran any tests one way or the other, just assumed that I guess. So it can still take ...

As noted, many sort options exist, the specific stage is only one such option available. Check the Property Help for the Sort Specification in the stage, it has examples of the syntax needed. Yes, it's a little confusing if you've never used it before, but check the help and give that a shot. Just a...

I don't believe so - isn't that 768? We're not anywhere near that.

I see from the docs that having NLS enabled could change the behaviour of this - for the record, we don't. If that helps. All we do is override the value of $NLS_LANG in the job to AMERICAN_AMERICA.WE8MSWIN1252 if that makes any difference...

And what if the Sequence job itself aborts? The problem remains to be solved regardless of job type.

Ok. Or just this then:


I'd still make sure this bin directory is in your PATH somewhere.

There's nothing to 'enable', you just need to ensure it is in your $PATH. Try setting your environment to the DataStage environment by 'sourcing' dsenv first:


Then run your command again.

That sounds like a bug that should be reported to your Support provider. The behaviour should be the same in that scenario.

The question is "Do staging tables in DW/DM need a Primary Key"? And the short answer is no. They don't fall under the general rule of being "a must for tables in a DW" as to me the staging area / back room "tables" are separate structures outside of the core DW itself.

1) How can i trap the status of the job thru dsjob command. 2) If any job gets aborted then is it necessary to compile the job in the designer before running the dsjob command ? 1) Use the -jobstatus dsjob option as noted. The behaviour of it is well documented. 2) No. It does need to be RESET howe...