Datastage Error Setting Up Internal Communications File Is Locked
Contents |
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 setting up internal communications (fifo rt_sctemp error occurs when DataStage is unable to create, delete, read, or write a fifo file is locked in datastage temporary fifo file for a job to the RT_SCTEMP directory within the project owning the job. Error setting up internal rt_sctemp in datastage 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
Error Setting Up Internal Communications (fifo . Pipe ) Status() 2
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 containi
might be blocked by a firewall Server is down SOL: Update the host file on client system so that the server hostname can be resolved from client. Make sure http://techbuzzmadhuri.blogspot.com/2013/02/datastage-common-errors-and-solutions-1.html the WebSphere TCP/IP ports are opened by the firewall. Make sure the WebSphere application server is running. (OR) Restart Websphere services. 2. The connection was refused or the RPC daemon is not http://66.34.129.47/viewtopic.php?p=330636&sid=1d7c1858db07590eec3e8d2dd06c0a3e running (81016) RC: The dsprcd process must be running in order to be able to login to DataStage. If you restart DataStage, but the socket used by the dsrpcd (default is 31538) was error setting busy, the dsrpcd will fail to start. The socket may be held by dsapi_slave processes that were still running or recently killed when DataStage was restarted. SOL: Run "ps -ef | grep dsrpcd" to confirm the dsrpcd process is not running. Run "ps -ef | grep dsapi_slave" to check if any dsapi_slave processes exist. If so, kill them. Run "netstat -a | grep dsprc" to error setting up see if any processes have sockets that are ESTABLISHED, FIN_WAIT, or CLOSE_WAIT. These will prevent the dsprcd from starting. The sockets with status FIN_WAIT or CLOSE_WAIT will eventually time out and disappear, allowing you to restart DataStage. Then Restart DSEngine. (if above doesn't work) Needs to reboot the system. 3. To save Datastage logs in notepad or readable format SOL: a) /opt/ibm/InformationServer/server/DSEngine (go to this directory) ./bin/dsjob -logdetail project_name job_name >/home/dsadm/log.txt b) In director client, Project tab Print select print to file option and save it in local directory. 4. "Run time error '457'. This Key is already associated with an element of this collection." SOL: Needs to rebuild repository objects. a) Login to the Administrator client b) Select the project c) Click on Command d) Issue the command ds.tools e) Select option ‘2' f) Keep clicking next until it finishes. g) All objects will be updated. 5. To stop the datastage jobs in linux level SOL: ps -ef | grep dsadm To Check process id and phantom jobs Kill -9 process_id 6. To run datastage jobs from command line SOL: cd /opt/ibm/InformationServer/server/DSEngine ./dsjob -server