Page 2 of 2
Posted: Mon Dec 14, 2009 7:17 am
by chulett
And?
Changing permissions worked for me
Posted: Thu Apr 08, 2010 3:47 pm
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.
Posted: Thu Apr 08, 2010 4:54 pm
by ray.wurlod
It's probably worth putting the command umask 002 into the $DSHOME/dsenv script, too.