DSXchange

Have an SA or someone with root access kill it. You should also check for shared memory segments related to your instance tag.

FYI - you cannot have two installations of DataStage on one machine with the same instance tag.

It *should be* or *is*? I'd suggest you double-check, as from what I recall I could download either version for HP-UX.

I didn't mention it because of concerns about db connections, but rather because I've seen the Oracle client cause a core dump just like that. And all kinds of jobs can work just fine and then that special one comes along that triggers some obscure bug in their code and blammo. And it always be repo...

Hmmm... that one should be ok, or at least it has been in my experience on HP-UX. I was worried it was one of the earlier ones, like 9.2.0.1 for example. Out of curiousity, does that match your 9i database version?

You'll probably need to involve your official support provider on this one.

ArndW wrote:On sites with multiple DS instances there won't be a /.dshome file. I would prefer to stick with the simple, time-proven method that Ray suggested, "System(32)".

Ah. Thanks.

However, curious about the 'because of permissions problems' statement.

There's more going on than just the format of the date, it seems. Is this a PA-RISC or Itanium machine? I assume you pulled down the proper version of DataStage, yes?

Ok, would have guessed that. What Oracle client version are you using? One of the known buggy ones, I'd wager.

That one is specific to XP's Service Pack 2 and not being able to open stages. There is yet another patch to address Designer crashing in Sequence jobs.

What database?

What DataStage version and O/S? My dsenv file uses that cat command to set $DSHOME, how is it done in yours?

All you are missing is the warning in the log when there are reject rows. Is that really something you believe you need? An after job routine could check for records down the final combined link and log a warning when it's greater than zero to replace that functionality. Open a case with your offic...

I was going to make the same request, then noticed that bmsq is not the thread starter. Marking will have to wait.

Nice find.

Please mark the thread as Resolved.

Lots of people do this. Some will build hooks into each job 'after job' to leverage a standard routine and others will have separate jobs to farm these same stats from every job's log. Being new to DataStage, some of this may seem a little daunting but don't let that throw you off. One of the great ...