Page 1 of 1

Error while running Datastage jobs thru UNIX console

Posted: Tue Sep 18, 2007 12:07 pm
by ratuldey
Hi,

I tried to run my 11 datastage job sequences thru a UNIX shell from the console. This sequence would in turn fire the datastage jobs within it.

But the job run failed and I recovered the following error messages from the Error file in UNIX:-

The errors read like -

ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[144]: 13199 Killed
ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[145]: 13200 Killed
ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[146]: 13201 Killed
ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[147]: 13202 Killed
ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[148]: 13203 Killed
ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[149]: 13204 Killed
ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[150]: 13205 Killed
ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[151]: 13206 Killed
ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[152]: 13207 Killed
ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[153]: 13208 Killed
ld.so.1: dsjob: fatal: libvmdsapi.so: open failed: No such file or directory
/data/etl03/mis2/plcw/bin/run_plcsloss.sh[154]: 13209 Killed

Posted: Tue Sep 18, 2007 12:19 pm
by DeepakCorning
Search for "libvmdsapi.so: open failed: No such file or directory " in the forum.

http://dsxchange.com/viewtopic.php?t=98 ... 8c51d26a33

how does . ./dsenv help in this case??

Posted: Tue Sep 18, 2007 1:48 pm
by ratuldey
Hi this is the contents of the 'dsenv' file under the location -
$DSHOME -
/usr/Ascential/DataStage/DSEngine

--------------------------------------------------------------------------------------
set +u

if [ -z "$DSHOME" ] && [ -f "/.dshome" ]
then
DSHOME=`cat /.dshome`
export DSHOME
fi

if [ -z "$DSHOME" ]
then
DSHOME=/usr/Ascential/DataStage/DSEngine; export DSHOME
fi

if [ -z "$APT_ORCHHOME" ]
then
APT_ORCHHOME=; export APT_ORCHHOME
fi

if [ -z "$UDTHOME" ]
then
UDTHOME=/usr/Ascential/DataStage/ud41; export UDTHOME
UDTBIN=/usr/Ascential/DataStage/ud41/bin; export UDTBIN
fi

if [ -n "$DSHOME" ] && [ -d "$DSHOME" ]
then
ODBCINI=$DSHOME/.odbc.ini; export ODBCINI
HOME=${HOME:-/}; export HOME

#LANG="<langdef>";export LANG
#LC_ALL="<langdef>";export LC_ALL
#LC_CTYPE="<langdef>";export LC_CTYPE
#LC_COLLATE="<langdef>";export LC_COLLATE
#LC_MONETARY="<langdef>";export LC_MONETARY
#LC_NUMERIC="<langdef>";export LC_NUMERIC
#LC_TIME="<langdef>";export LC_TIME
#LC_MESSAGES="<langdef>"; export LC_MESSAGES

LD_LIBRARY_PATH=$DSHOME/java/jre/lib/sparc/client:$DSHOME/java/jre/lib/sparc:`dirname $DSHOME`/branded_odbc/lib:$DSHOME/lib:
$DSHOME/uvdlls:$LD_LIBRARY_PATH
export LD_LIBRARY_PATH
fi

# Setup Oracle/SQLPlus

ORACLE_HOME=/opt/oracle/product/10.1.0/client_1
export ORACLE_HOME

ORACLE_SID=PLDWQ
export ORACLE_SID

LD_LIBRARY_PATH=${ORACLE_HOME}/lib32:${LD_LIBRARY_PATH}
export LD_LIBRARY_PATH

PATH=${ORACLE_HOME}/bin:${PATH}
export PATH
--------------------------------------------------------------------------------------


How does the command . ./dsenv help me here??
How does this set the relevant paths for the DSJOBS??

Posted: Tue Sep 18, 2007 4:39 pm
by ray.wurlod
By adding directories to your command search list and your shared library search list, and setting certain required environment variables such as ORACLE_BIN. The dsenv script is executed by all DataStage processes but, as an interactive (non-DataStage) process you must executed it explicitly.