Admin Error: OPENSEQ failed on Project

carlosfelipevfs · Post by **carlosfelipevfs** » Wed Jan 28, 2009 7:22 am

Hi,

configuration:

Red Hat linux 64
DataStage 8.0
Oracle 10g R2

Erro

DSR_Parseconfig: OPENSEQ of
/opt/IBM/InformationServer/Server/PXEngine/etc/master_config.apt ELSE
clause, STATUS() = 2

Who can help?

Thanks
Felipe

ray.wurlod · Post by **ray.wurlod** » Wed Jan 28, 2009 7:37 pm

Status 2 is "file not found". Please check the correct spelling and casing of the file name - file names on UNIX are case-sensitive.

carlosfelipevfs · Post by **carlosfelipevfs** » Fri Jan 30, 2009 1:42 pm

Thanks,

IBM Analytics Champion 2009 - 2020 · Post by **asorrell** » Thu Nov 12, 2009 10:30 am

I just got this myself and figured out the solution. This message appears when you open the Administrator on a project and your id doesn't have write access to the PXEngine/etc sub-directory.

I opened the Administrator as dsadm, no error message. Opened the project while logged in as my id (which is authorized as an administrator) - error message. Checked and the access write for the PXEngine/etc sub-directory didn't give the "dstage" group write access.

Do a chmod 775 on that directory and the problem goes away.

Code: Select all

$ pwd
/opt/IBM/InformationServer/Server/PXEngine
$ ls -ld etc
drwxr-xr-x  3 dsadm dstage 2048 Oct 22 17:36 etc
$ chmod 775 etc
$ ls -ld etc
drwxrwxr-x  3 dsadm dstage 2048 Oct 22 17:36 etc

ray.wurlod · Post by **ray.wurlod** » Thu Nov 12, 2009 1:21 pm

That's one of the reasons to install with umask 022.

philds · Post by **philds** » Fri Jan 08, 2010 7:40 pm

Actually, umask 022 is what the installation guide or release notes asks for.

I did follow the instructions:
umask 022
./install -is:tempdir /tmp -console

and get the same error msg for the same reason...
...because umask 022 is actually setting the group read only :
>umask 022
>umask -S
u=rwx,g=rx,o=rx

That's probably still better than having to many directories in
"g+w" but they should either fix the dir as a post-install task or change the client to check that the file is there or the dir is writable before trying to open/create it.

As suggested upper in the thread, chmod g+w on the etc dir got rid of the error message.

ritusethi · Post by **ritusethi** » Fri Jan 22, 2010 12:58 pm

I would like to add that I saw the same error on one of the machines we had configured and changing permissions to the etc directory had nothing to do with the issue .
The issue here was that the path of the parallel files like APT_ORCHHOME was incorrect in the DSParams file and once that was fixed it resolved the issue .

Lesson learnt .. before copying the DSParams file make sure the environments with their paths are the same in source and destination of copy .

Thanks
Ritu Sethi