Error Setting Up Internal Communications Datastage
up internal communications (fifo RT_SCTEMP/jobName.fifo) Technote (troubleshooting) Problem(Abstract) DataStage jobs fail with error message: Message: Error setting up internal communications (fifo RT_SCTEMP/jobName.fifo) Resolving the problem The following error occurs when DataStage is unable to create, delete, read, or write a temporary fifo file for a job to the RT_SCTEMP directory within the project owning the job. Error setting up internal communications (fifo RT_SCTEMP/jobName.fifo) The above error has two primary causes: Unable to process file due to locks. Unable to process file due to file permissions or other file system problems. Virus Scan or backup program interferes with writing fifo files to temp or scratch directories as discussed in technote: DataStage Job intermittently aborts with message "Error setting up internal communications" If the failure is due to locks, then the above error should have additional text at the end or in subsequent message stating the lock status, for example: Error setting up internal communications (fifo RT_SCTEMP/MyTestJob. fifo LOCKED STATUS () -1); file is locked . In that situation, refer to the following technote for instructions on how to clear locks for a job: DataStage user or job unable to get exclusive access to object due to old locks If the issue is not due to locks, then review the following checklist to resolve other common causes for this error: Check the file limits at job runtime, especially if all jobs run under a common userid such as DSADM. You can check the limits used at DataStage job run-time even if you cannot run jobs, by running the command through the DataStage Administrator client. Login to DataStage Administrator Client, select the failing project, click the COMMAND button, and then enter command: sh ulimit -a If the number is under 2048, consider increasing it. On busy systems it may need to be higher. In this situation, you can add command to set the limit to $DSHOME/dsenv script such as: ulimit -n 10240 After making the change you will need to stop and restart DataStage and then perform above test again to ensure new limit is in effect. Check available space on volume containing the RT_SCTEMP directory. If the project containing failing jobs is named "MyProject", then the path to RT_SCTEMP will be similar to: /opt/IBM/InformationServer/Server/Projects/MyProject/RT_SCTEMP Also, when checking disk space (using df command on unix systems) in addition to looking at the free/used dis
process stopped unexpectedly" SOL: needs to kill LoggingAgentSocketImpl Ps -ef | grep LoggingAgentSocketImpl (OR) PS -ef | grep Agent (to http://devipriyadeepak.blogspot.com/2012/11/datastage-common-errors-and-solutions.html check the process id of the above) 2. Warning: A sequential operator cannot preserve the partitioning of input data set on input port 0 SOL: Clear the preserve http://datastagetechguru.blogspot.com/2014/12/datastage-most-common-errorswarnings.html partition flag before Sequential file stages. 3. Warning: A user defined sort operator does not satisfy the requirements. SOL: Check the order of sorting columns and make sure use error setting the same order when use join stage after sort to joing two inputs. 4. Conversion error calling conversion routine timestamp_from_string data may have been lost. xfmJournals,1: Conversion error calling conversion routine decimal_from_string data may have been lost SOL: check for the correct date format or decimal format and also null values in the date or decimal fields before passing to error setting up datastage StringToDate, DateToString,DecimalToString or StringToDecimal functions. 5. To display all the jobs in command line SOL: cd /opt/ibm/InformationServer/Server/DSEngine/bin ./dsjob -ljobs
error: "LoggingAgent.sh process stopped unexpectedly" SOL:needs to kill LoggingAgentSocketImpl Ps -ef |grepLoggingAgentSocketImpl(OR) PS -ef |grep Agent(to check the process id of the above) 2.Warning: A sequential operator cannot preserve the partitioning of input data set on input port 0 SOL:Clear the preserve partition flag before Sequential file stages. 3.Warning: A user defined sort operator does not satisfy the requirements. SOL:Check the order of sorting columns and make sure use the same order when use join stage after sort to joing two inputs. 4.Conversion error calling conversion routine timestamp_from_string data may have been lost. xfmJournals,1: Conversion error calling conversion routine decimal_from_string data may have been lost SOL:check for the correct date format or decimal format and also null values in the date or decimal fields before passing to datastage StringToDate, DateToString,DecimalToString or StringToDecimal functions. 5."Error trying to query dsadm[]. There might be an issue in database server" SOL:Check XMETA connectivity. db2 connect to xmeta (A connection to or activation of database "xmeta" cannot be made because ofBACKUP pending) 6."DSR_ADMIN: Unable to find the new project location" SOL:Template.ini file might be missing in /opt/ibm/InformationServer/Server. Copy the file from another severs. 7."Designer LOCKS UP while trying to open any stage" SOL:Double click on the stage that locks up datastage Press ALT+SPACE Windows menu will popup and select Restore It will show your properties window now Click on "X" to close this window. Now, double click again and try whether properties window appears. 8."Error Setting up internal communications (fifo RT_SCTEMP/job_name.fifo) SOL:Remove the locks and try to run (OR) Restart DSEngine and try to run (OR) Go to /opt/ibm/InformationServer/server/Projects/proj_name/ ls RT_SCT* then rm-fRT_SCTEMP then try to restart it. 9.While attempting to compile job,"failed to invoke GenRunTime using Phantom process helper" RC:/tmp space might be full Job status is incorrect Format problems with projects uvodbc.config file SOL: 1)clean up /tmp directory 2)DS DirectorĂ JOBĂ clear status file 3)confirm uvodbc.config has the following entry/format: [ODBC SOURCES] DBMSTYPE = UNIVERSE Network= TCP/IP Service =uvserver Host =127.0.0.1 10.No jobs or logs showing in IBM DataStage Director Client, however jobs are still accessible from the Designer Client. SOL:SyncProject cmd that is installed with DataStage 8.5 can be run to analyze and recover projects SyncProject -ISFile islogin -project dstage3 dstage5 -Fix 11.CASHOUT_DTL: Invalid property value /Co