Installation of IBM Datastage 11.3 failed

ArndW · Post by **ArndW** » Mon Jun 06, 2016 5:30 am

I'm curious as to why the instance was changed from "dcd" to the default "ade" in the configuration file - did you specify anything in the installation? Was the engine tier already installed?

The error message refers to the uvregen command failing. This command can be called manually, but it might be best to understand why the instance was changed before manually testing this command and seeing why it returned an error message (most likely due to a syntax error in the UVCONFIG file).

chulett · Post by **chulett** » Mon Jun 06, 2016 5:37 am

Well... it does repeat this several times and seems to me to be something you should be doing:

2016-06-06T12:29:00.697, INFO: Exit Code: 255, Info: The following critical tunable(s) have been changed in uvconfig!
If you wish to apply these changes, shut down DataStage server,
run uvregen and then restart immediately,
OR restore tunable(s) to their original values.

chulett · Post by **chulett** » Mon Jun 06, 2016 9:41 am

I don't recall dsenv living there... logged in as admin, echo $DSHOME and see what it says, if anything.

Teej · Post by **Teej** » Mon Jun 06, 2016 12:54 pm

So you entered the following command:

cd `cat /.dshome`

and does not find dsenv, or ds.setenv?

And this is an UNIX-based platform, not Windows, correct?

didawin · Post by **didawin** » Tue Jun 07, 2016 2:28 am

So both echo $DSHOME and cat /.dshome are not working, here are the return :

[root@XXXX ~]$ echo $DSHOME

[root@XXXX ~]$ cd `cat /.dshome`
cat: /.dshome: No such file or directory

Yes I don't find dsenv or ds.setenv.
Yes it's RedHat V6.5
Also the error show that he dont find the library in XXXX/InformationServer/Server/DSEngine/bin/uv
Isn't it because i should create the dsenv file with the LIBPATH ?

EDIT : I found an example of ds.setenv in :
XXXX/InformationServer/Server/DSEngine/sample/ds.setenv

What should I do ? :/
How can i create the dsenv file which is missing ?

ArndW · Post by **ArndW** » Tue Jun 07, 2016 5:46 am

A missing "dsenv" file signals a serious installation problem to me, as does the missing "/.dshome" file. And the instance change is one I've never seen during an install, either.

Overall I think that a clean installation from scratch might be the quickest and most painless method for you.

Have you contacted your support provider on this issue?

didawin · Post by **didawin** » Tue Jun 07, 2016 5:54 am

Ok I think we will do a clean re-install.

But the services and the engines are installed on the same filesystem (mount FS) but on 2 different servers.
So I have the services on SERVER_1/FS_MOUNTED_DIRECTORY/InformationServer/
I have Oracle 11G on SERVER_2/FS_MOUNTED_DIRECTORY/Oracle/
I tried to install the engine on SERVER_3/FS_MOUNTED_DIRECTORY/InformationServer/

Should I uninstall also the service on the first server ? Or should I just uninstall the engine on the third server and re-install it ?

No I didn't contact the support provider, how to contact them ?

chulett · Post by **chulett** » Tue Jun 07, 2016 6:38 am

First you need to find out who is the Official Support Provider for your company. Ask. It could be the vendor your company used to purchase the product or it could be IBM directly. The 'who' will lead to the 'how'.

didawin · Post by **didawin** » Tue Jun 07, 2016 6:43 am

Ok but just for me to understand,
when should the installation create the dsenv file ? when we install the services or the engine ? or both ?

ArndW · Post by **ArndW** » Tue Jun 07, 2016 7:30 am

The dsenv file is created as part of the engine tier installation.

PaulVL · Post by **PaulVL** » Tue Jun 07, 2016 7:33 am

Did your mount run out of space while installing?
Did / have enough room?

Check the mounts for the product/engine install.

Teej · Post by **Teej** » Tue Jun 07, 2016 11:03 am

Even if you cross-mount to a new server, if you are using the second server as a primary (Conductor) node, you should be including the /.dshome file (by manually creating/duplicating it from the original server, or sharing it from the original server).

Still would not resolve the missing dsenv file. But that should be shared anyway -- so if the original server do not have it, that server's install somehow went bad.

One other advice - you should keep the paths exactly the same on both servers, especially if you want to use this as a HA install, or a MPP install. It is vital for the engine to see the same full path among other requirements.

-T.J.