Wednesday, July 28, 2010

Data Stage internal error 39202

While access project thru DataStage Director client, it throws an internal error 39202
Explaination regarding this internal error:

This is an internal error within the DataStage engine. It decodes as "slave failed to give to go-ahead message" which isn't very helpful for a newcomer. It usually means that the agent process that services the connection (dsapi_server) either hasn't started successfully or has failed to respond within a certain period.

This can happen if the DataStage server machine is very busy. You haven't installed DataStage on a PDC or even a BDC by any chance?

Maybe re-booting will remedy the situation. Because you got that far you can be sure that the network connectivity and authentication are all OK.

Read up on how the DataStage RPC mechanism handles requests to connect, and the agent processes (dsapi_server and dsapi_slave) that become involved. Check (using Task Manager on the DataStage server machine) that these processes do actually get created.


IBM docs regarding this error
http://www-01.ibm.com/support/docview.wss?uid=swg21431890&myns=swgimgmt&mynp=OCSSVSEF&mync=R

Solution:
The problem found was in the dsenv file, it had a incorrect LIBPATH
LIBPATH=`dirname $DSHOME`/branded_odbc/lib:`dirname $DSHOME`/DSComponents/lib:`dirname $DSHOME`/DSComponents/bin:$DSHOME/lib:$DSHOME/uvdlls:$ASBHOME/apps/jre/bin:$ASBHOME/apps/jre/bin/classic:$ASBHOME/lib/cpp:$ASBHOME/apps/proxy/cpp/aix-all-ppc_64:/opt/odbc_progres/lib:$LIBPATH

$ASBHOME/apps/proxy/cpp/aix-all-ppc_64
instead of
$ASBHOME/apps/proxy/cpp/aix-all-ppc

restart DS again after changing the path

No comments: