Failed To Connect To Datastage Server With 39202 Error
login 39202 Technote (troubleshooting) Problem(Abstract) Logging into DataStage results in the following error: Failed to connect to host: xxxxx, project: UV (Internal Error (39202)) Resolving the problem There are several possible causes for this error. Go to the $DSHOME directory and run: $. ./dsenv $bin/uvsh If this fails it points to a problem with the engine. If it works correctly and you get the TCL prompt you may have a hung socket. Perform the following steps to cleanup DataStage. Log into server as dsadm or root. Make sure the user has permissions to /tmp and that the partition is not full. From $DSHOME type: $. ./dsenv $bin/smat -t Check that the user has permissions to the location for UVTEMP and UVSPOOL. If you made any changes to ODBC drivers check the permissions under $DSHOME/../branded_odbc. Stop DataStage and check for orphaned processes: $ps -ef|grep phantom $ps -ef|grep dsapi $ps -ef|grep dscs Use kill -9 for any existing processes Check for existing shared memory segment: $ipcs -mop|grep ade (Linux users - use ipcs -m) As root remove any existing segments: $ipcrm -m PID Example: # ipcs -mop |grep ade m 13500432 0xadec7011 --rw-rw-rw- root dstage 0 88240 88100 #ipcrm -m 13500432 Check for hung ports: $netstat -a|grep dsrpc If you get any results in a WAIT state then you need to wait until this it disappears or reboot the server. Depending on the exact state it may clear itself or may never go away. For example a TIME_WAIT is controlled by the ndd parameter tcp_time_wait_interval, which is generally 60s. On Unix/Linux platforms, confirm that the users with login error are a member of group "dstage" or whatever default group was setup at installation time for DataStage files and directories. Use the id command, i.e. "id myuserid" to confirm that dstage is either the default group or in the group list for that user. Start DataStage and Re-connect with DataStage clients. Document information More support for: InfoSphere DataStage Software version: 7.5, 8.0, 8.1 Operating system(s): AIX, HP-UX, Linux, Solaris Reference #: 1413453 Modified
trying to connect with the InfoSphere DataStage Client Technote (troubleshooting) Problem(Abstract) When trying to connect with one of the InfoSphere DataStage clients you receive the error: Failed to connect to host, Internal error 39202 Cause In order to troubleshoot what part of the connection to the project is failing, it is best to turn on Server Side Tracing for the failing project. Server Side Tracing you should where the connection code is failing. Server side tracing can be turned on in 2 places, from the InfoSphere DataStage Administrator and from an DataStage engine prompt. If you can open the DataStage administrator: Click on the Projects Tab, Click http://www-01.ibm.com/support/docview.wss?uid=swg21413453 on the project with the problem and click on Properties. Click the Tracing tab and Check Enable If you can't open the Administrator client, you will need to turn on tracing at the DataStage engine level. Telnet to the DataStage server machine and login as your DataStage admin user cd to the DSEngine directory Unix/Linux: Source the dsenv by typing: . ./dsenv Go into the engine by typing: bin/uvsh Windows: Go into the engine http://www-01.ibm.com/support/docview.wss?uid=swg21431890 by typing: bin\uvsh At the ">" prompt type: LOGTO projectname Where project name is the name of the project with the connection issue. Once in the project type: RESIZE &COMO& 19 TRACE ON Now that tracing is turned on, attempt to open the Designer Client. You should get a warning message that server side tracing has been turned on. Login so that you receive your error message Once you get the error, turn tracing off. From the Administrator, uncheck "Enable". From the Engine prompt type: TRACE OFF When it asks if you want to clear the trace files say No. You can view the trace files in the administrator on the same screen where you turned tracing on. If you cannot get into the Administrator, you can cd into the &COMO& directory in the project and see the trace files in there. The trace files/directories begin with DSRTrace and are all ASCII files Review the log files to find the full error messages corresponding to the connection issue. Document information More support for: InfoSphere DataStage Software version: 7.5.1, 7.5.2, 7.5.3, 8.0.1, 8.1 Operating system(s): AIX, HP-UX, Linux, Solaris, Windows Reference #: 1431890 Modified date: 2010-05-20 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms
internal error:This is an internal error within the DataStage engine. It decodes as "slave failed to give to go-ahead message" which http://pg8873.blogspot.com/2010/07/data-stage-internal-error-39202.html 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 https://datastage4u.wordpress.com/2012/09/12/important-technotes-ibm-infosphere-information-server-8-58-7/ 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 failed to 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 failed to connect created.IBM docs regarding this errorhttp://www-01.ibm.com/support/docview.wss?uid=swg21431890&myns=swgimgmt&mynp=OCSSVSEF&mync=RSolution: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-ppcrestart DS again after changing the path Posted by Pankaj Gautam at 10:37 PM Reactions: Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) tech scribbling archive ► 2016 (1) ► April (1) ► 2015 (6) ► October (1) ► August (1) ► July (2) ► April (1) ► January (1) ► 2014 (14) ► November (4) ► October (1) ► March (4) ► February (2) ► January (3) ► 2013 (4) ► November (2) ► August (1) ► April (1) ► 2012 (12) ► December (1) ► October (2) ► September (4) ► July (1) ► June (1) ► May (2) ► April (1) ► 2011 (9) ► November (1) ► August (2) ► July (1) ► April (1) ► February (4) ▼ 2010 (12) ► November (2) ► October (2) υ
IBM Infosphere Information Server8.5/8.7 Important Technotes -- IBM Infosphere Information Server8.5/8.7 September 12, 2012 ukatru Leave a comment Go to comments Determine PXEngine Version for IBM InfoSphere DataStage Question How do you determine the exact version of DataStage installed based on the PXEngine? Answer Perform the following-directory path may be different based on install location cd /opt/IBM/InformationServer/Server/DataStage/PXEngine/lib and run the following script: for i in * do strings $i | grep \$Version done Example output: Release 8.5 $Version: AIX64 Torrent 2_3 2010/09/20 23:45:58 GMT aixbld05:/builds/IS_8_5_RC_1_T1/PXEngine.src/orch_master/orchestrate//builds/IS_8_5_RC_1 _T1/PXEngine.src/orch_master/Libs/liborchaix64.a root Exp $ Release 7.5.2 $Version: AIX3 Torrent 2_3 2006/03/24 05:00:47 GMT aixbld01:/builds/PXEngine.src/orch_master/orchestrate//builds/PXEngine.src/ orch_master/Libs/liborchaix3.a root Exp $ $Version: AIX3 Torrent 2_3 2007/05/25 18:16:45 GMT aixbld01:/tmp_mnt/apt/aixrelease/patches/px752-102719.752.1/orch_master/ase sybase//tmp_mnt/apt/aixrelease/patches/px752-102719.752.1/orch_master/Libs/liborchasesybaseaix3.a syamalat Exp $ Note that other methods include review of /opt/IBM/InformationServer/Version.xml and /opt/IBM/InformationServer/Server/DataStage/.dsrel file, however, these methods do not provide the in depth information you get from running the script. Datastage server job using Oracle connector errors with DataStage Phantom Aborting with @ABORT.CODE = 3 Problem(Abstract) In a server job that is using the Oracle Connector stage, the following error occurs: DataStage Job xxxx Phantom yyyy Program "JOB.1875607158.DT.1629731972.TRANS1": Line nn, Exception raised in GCI subroutine: Access violation. Attempting to Cleanup after ABORT was raised in stage CopyOfOp_Region_426_Org_Hier_Outbound2..Xfm_Op_Region DataStage Phantom Aborting with @ABORT.CODE = 3 Resolving the problem To resolve the issue: If the Connector stage is used, one will need to do the following when loading the columns: Use Import Table Definitions Use Start Connector Import Wizard to bring in the columns This will ensure that the data type and length are correctly defined. How can I use external C++ code with DataStage as a transformer function (PX Routine) Question How can I use external C++ code with DataStage as a transformer function (Parallel Job Transform Routine - see as PX Routine) Answer PX Routine Tips and Tricks The PX Routine supports two types of external object linking. Object Type: Choose Library or Object. This specifies how the C function is linked in the job. If you ch