Error setting up internal communications

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

And?
-craig

"You can never have too many knives" -- Logan Nine Fingers
bashbal
Premium Member
Premium Member
Posts: 23
Joined: Mon Mar 01, 2004 12:26 pm
Location: Milwaukee, WI
Contact:

Changing permissions worked for me

Post by bashbal »

I had the same error and found this thread. I'm posting my findings to help the next guy.

We got this error doing column analysis in Information Analyzer. It happend shortly after we changed the credentials in the "Analysis Settings->Analysis Engine".

The new user did not have the same same group as the primary group first user had, so it could not access the RT_SCTEMP directory.

Solution: I changed all of the files to have the dstage group using chgrp command. I also set the SGID bit on all directories to force any new files to belong to the dstage group. From the $DSHOME../Projects directory, do the following:

Code: Select all

find ANALYZERPROJECT -type d -exec chmod g+s {} \;
This assumes that the directories already had group rwx permissions.
Lyle
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

It's probably worth putting the command umask 002 into the $DSHOME/dsenv script, too.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Post Reply