Datastage PX Install Issue

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

Post Reply
Inquisitive
Charter Member
Charter Member
Posts: 88
Joined: Tue Jan 13, 2004 3:07 pm

Datastage PX Install Issue

Post by Inquisitive »

Hi,

I am trying to install Datastage 7.5.2 on RedHat Linux 3.0. I am facing problem where in installation just does not continue and halts at a particular steps in between. I have tried multiple times and every time it halts at this same step.

I am able to provide all required details for the installation including Licesnse Details, Plug In selection,Project name etc, when it starts installing Datastage Server Engine the installation process does not continue and just remains at this step printing '*' and with following message on the screen.

Installing DataStage server engine

[1]+ Stopped sh -c "$unpackdir/dse.load $options >> $dslogfile 2>&1"
****************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************



From the log file I could make out process stops at last step


============================================================
Checking command line options
Thu Jan 4 18:25:20 PST 2007
============================================================

============================================================
Installation started: Thu Jan 4 18:25:20 PST 2007
============================================================

PRODUCT: Ascential DataStage
RELEASE: 7.5.2.9

=================================================================
--------------- W A R N I N G ---------------
=================================================================

Install was unable to detect a previous DataStage server.
By default, this will be treated as a new installation.

Existing DataStage installations, if any, will NOT be upgraded.



=================================================================
--------------- W A R N I N G ---------------
=================================================================

The user 'root' is currently running this install script.

No DataStage administrator has been specified. As a result, the
default DataStage administrator will be set to 'dsadm'.

To specify a DataStage administrator other than the default, you
should exit this script now and re-run the installation using
-admin <user> option on the command line.



============================================================
Checking kernel parameters
Thu Jan 4 18:25:26 PST 2007
============================================================


DataStage server engine location specified by FROM_NOT_FOUND


============================================================
Checking client connections
Thu Jan 4 18:25:26 PST 2007
============================================================


Done.

============================================================
============================================================
Resizing files
Thu Jan 4 18:25:28 PST 2007
============================================================


Done.

============================================================
Unpacking support libraries
Thu Jan 4 18:25:30 PST 2007
============================================================

libdslic.so
39340 blocks

Done.

============================================================
Unpacking summary text and license agreement
Thu Jan 4 18:25:30 PST 2007
============================================================

textfiles/ENU/license.txt
39340 blocks
textfiles/ENU/summary.txt
39340 blocks

Done.

============================================================
Executing setup to obtain installation requirements
Thu Jan 4 18:25:30 PST 2007
============================================================
object/repos/APM.CHECK.FILE.B
object/repos/APM.GET.JOB.DEPENDENTS.B
object/repos/DSAttachODBCDriver.B
object/repos/DSGetODBCLicFile.B
object/repos/DSRGetUVConfigInfo.B
object/repos/DSRMapTbl.B
object/repos/DSRMetaGeta.B
object/repos/DSRUPDATE.B
object/repos/DSR_ADMIN.B
object/repos/DSR_AUDIT.B
object/repos/DSR_BATCH.B
object/repos/DSR_BATCHCTL.B
object/repos/DSR_CATRECS.B
object/repos/DSR_CHECKCONNECTCV.B
object/repos/DSR_CHECKCONNECTSC.B
object/repos/DSR_CHECKCONNECTSTAGE.B
object/repos/DSR_CHECKER.B
object/repos/DSR_CHECKONEROUTINE.B
object/repos/DSR_CHECKUSER.B
object/repos/DSR_CONTAINER.B
object/repos/DSR_CONVERTFUNC.B
object/repos/DSR_CONVERTJOB.B
object/repos/DSR_DOPROJUPGRADE.B
object/repos/DSR_DSN.B
object/repos/DSR_EDIT.B
object/repos/DSR_EXECJOB.B
object/repos/DSR_FILEACCESS.B
object/repos/DSR_GETCONTAINER.B
object/repos/DSR_GETIPCSTAGEPROPS.B
object/repos/DSR_GETJOB.B
object/repos/DSR_GETJOBMETABAG.B
object/repos/DSR_GETLINKMETADATA.B
object/repos/DSR_GETMULTIPARTOBJ.B
object/repos/DSR_GETNAME.B
object/repos/DSR_GETPROP.B
object/repos/DSR_GETRTCONFIG.B
object/repos/DSR_GETSQLTYPES.B
object/repos/DSR_GETSTAGELINKS.B
object/repos/DSR_GETSTAGESOFTYPE.B
object/repos/DSR_GETSTAGETYPES.B
object/repos/DSR_IMPORT.B
object/repos/DSR_IMPPLG.B
object/repos/DSR_IMPTRANS.B
object/repos/DSR_INSTALL.B
object/repos/DSR_JOB.B
object/repos/DSR_LICENSE.B
object/repos/DSR_LOADFILE.B
object/repos/DSR_LOADSTRING.B
object/repos/DSR_LOG.B
object/repos/DSR_MESSAGE.B
object/repos/DSR_NLS.B
object/repos/DSR_PACKAGE.B
object/repos/DSR_PACKINS.B
object/repos/DSR_PARALLEL.B
object/repos/DSR_PLADMIN.B
object/repos/DSR_PLUGIN.B
object/repos/DSR_PLUGIN_DES.B
object/repos/DSR_PROJECT.B
object/repos/DSR_QUICKADD.B
object/repos/DSR_RECORD.B
object/repos/DSR_RELEASE.B
object/repos/DSR_SCHEDULE.B
object/repos/DSR_SCHED_CMD.B
object/repos/DSR_SELECT.B
object/repos/DSR_SQLBUILDER.B
object/repos/DSR_STAGEPROPUSED.B
object/repos/DSR_STAGETYPE.B
object/repos/DSR_STATIC.B
object/repos/DSR_TIMESTAMP.B
object/repos/DSR_TRACE.B
object/repos/DSR_TRACE_CMD.B
object/repos/DSR_UPDATED.B
object/repos/DSR_UPGRADEBATCH.B
object/repos/DSR_UPGRADECONT.B
object/repos/DSR_UPGRADEDSPARAMS.B
object/repos/DSR_UPGRADEJOB.B
object/repos/DSR_UPGRADEPROJ.B
object/repos/DSR_UPGRADEPXCHECK.B
object/repos/DSR_UPGRADEROUT.B
object/repos/DSR_UPGRADETABLE.B
object/repos/DSR_UPGRADETRANS.B
object/repos/DSR_WHEREUSED.B
object/repos/DS_COEXIST.B
object/repos/DS_CONFIGNLS.B
object/repos/DS_CONNECT.B
object/repos/DS_IMPORTDSX.B
object/repos/DS_INSTPACK.B
object/repos/DS_PLADMIN.B
object/repos/DS_REGPLUGIN.B
object/repos/DS_TUNEPROPS.B
object/repos/GetMetaData.B
object/repos/NLS.BUILD.B
39340 blocks


============================================================
Checking for rpc daemon in services file
Thu Jan 4 18:27:14 PST 2007
============================================================

The following entry was found in /etc/services:
dsrpc 31538/tcp # RPCdaemon DSEngine@/home/dsadm/Ascential/DataStage/DSEngine
Done.

============================================================
Clean unishared
Thu Jan 4 18:27:16 PST 2007
============================================================


Fresh Installation
============================================================
Installing and configuring server engine
Thu Jan 4 18:27:18 PST 2007
============================================================

dse.load
13 blocks
DSHOME defined (/home/dsadm/Ascential/DataStage/DSEngine), but directory does not exist.
System info: Linux uhqqpdhetl01 2.4.21-47.ELsmp #1 SMP Wed Jul 5 20:38:41 EDT 2006 i686 i686 i386 GNU/Linux

DataStage Engine 7.5.2.1 Install Options (NewInstall)
Installer root
Administrator dsadm uid=500 gid=200

Command Line Options
Instance tag ade (0xadec7521)
Impersonation mode Enabled
Bypass cpio downloading false
Bypass checksum after download true
Relocate executables false

Bypass checksum after download true
Relocate executables false
Enable autostart script true

Modifiable Options
1) DataStage Engine home directory /home/dsadm/Ascential/DataStage/DSEngine
2) Compile terminfo definitions Yes
3) Media device /tmp/Ascential.media/linux/dbengine
4) Long File Names OFF

Enter a field number to change, q to abort install, or
press <Return> to begin install of DataStage Engine:


Additional Details:

- I am doing root installation.
- Project path and install paths are default
- user dsadm has full access to /tmp/Ascential.media (this is the location from where I am installing)
- Also, I have used same file to install the Datastage 7.5.2 on other Redhat LInux 3.0 servers with identical Env as this one. I did not face any problem with them.

Any solution to above problem or pointers towards the solution would be greatly appreciated.

Below is Entry of the Log file.
Thanks
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

With this stage, was the home directory home/dsadm/Ascential/DataStage/DSEngine been created?
Is seems like waiting for to press Return. Have you tried hitting Return at the last step?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Inquisitive
Charter Member
Charter Member
Posts: 88
Joined: Tue Jan 13, 2004 3:07 pm

Post by Inquisitive »

Yes it creates the directory /home/dsadm/Ascential/DataStage/DSEngine .

I have tried return it does not work.

Then I tried killing the process ( I found PID with ps -ef |grep ade)

Once I killed this process It throws a message do you want to continue instllation? and if I say Yes it will cotinue but again hang in the next step. And it just never completes.
Inquisitive
Charter Member
Charter Member
Posts: 88
Joined: Tue Jan 13, 2004 3:07 pm

Post by Inquisitive »

Hi All,

This issue is resolved after struggling for a week with all different options.

It is resolved after we changed the PS1 command prompt to "$" from default PS1 command prompt.

deault PS1 command prompt had [<hostname> @<username>].

We dont know what exactly was wrong with it. But when we changed PS1 command prompt for both the users it went on fine.

Thanks
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

You mean in the .profile. Thats absurd and really strange. :roll:
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Some time back Ultramundane posted of installation issues with PS1 values that contained a newline. Possibly this problem is related.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I_Server_Whale
Premium Member
Premium Member
Posts: 1255
Joined: Wed Feb 02, 2005 11:54 am
Location: United States of America

Post by I_Server_Whale »

Ray is referring to this POST.
Anything that won't sell, I don't want to invent. Its sale is proof of utility, and utility is success.
Author: Thomas A. Edison 1847-1931, American Inventor, Entrepreneur, Founder of GE
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

As Ray said, "Mega wierd".
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
kumar_s
Charter Member
Charter Member
Posts: 5245
Joined: Thu Jun 16, 2005 11:00 pm

Post by kumar_s »

Can you mark the post as resolved?
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
Post Reply