Page 1 of 1

Datastage 8.7 Server Installation error in Solaris

Posted: Tue May 28, 2013 7:49 pm
by ragavendradineshdsx
Hi all,

We are trying to install IBM Datastage Server 8.7 version in Solaris 10 machine and we are stuck with the below error:

----------------------------------------------------------------------------------

FAILED: Ensure that user db2inst1 is able to execute a script cleanly. Resolution: IBM InfoSphere Information Server installation program runs script files that include the commands to switch to a user and then run scripts as that user. If the user profile or the profile the user inherits executes commands that return error output or an invalid return code, the installer cannot distinguish between those errors and errors from the install scripts. A common cause of such errors is when there are stty commands in the profile which will fail if there is not a terminal. You should modify the user profile so it does not generate errors when a profile is sourced in a script where there is no terminal.

----------------------------------------------------------------------------------

Please help us out in resolving this road block and to proceed with the Datastage installation.

Posted: Tue May 28, 2013 8:02 pm
by priyadarshikunal
first question will be whether you have created those users in advance or during the installation?

Posted: Tue May 28, 2013 8:20 pm
by ragavendradineshdsx
Hi,

We created all the required users in advance as per Datastage Installation guide.

Posted: Wed May 29, 2013 12:00 am
by ray.wurlod
Did you modify the .profile file for any of these users, or the /etc/profile file?

Posted: Wed May 29, 2013 9:09 am
by ragavendradineshdsx
Hi Ray,

thanks for your reply. We didn't do any chnages in the .profile file. In fact, i do not see any .profile file for these users under the home directory.

Please advice what kind of changes we need to do in .profile file?

Posted: Wed May 29, 2013 4:14 pm
by ray.wurlod
Nothing. That's the point. Read the error message again - there must be nothing in the login process that puts unexpected output onto stdout.

What is the umask setting for db2inst1?

Have you involved your official support provider?