Hi, Our daily batch job aborted today with a message:
Resource temporarily unavailable.
The daily job has been running for a year and this message is received first time today.
Found a related link on this topic
http://www-01.ibm.com/support/docview.w ... wg21645480
Indicates the cause to be "insufficient user limits for number of processes or file handles, on UNIX/Linux systems, or problems with the job monitor processing for a job.
Using ulimit -u command found file handles and processes are limited to 4096.
1) Does that mean the number of processes are going beyond 4096 hence causing the abort?
2) Do we need to increase the processes as said in the site?
Job aborted with 'Resource temporarily unavailable'
Moderators: chulett, rschirm, roy
Job aborted with 'Resource temporarily unavailable'
Rumu
IT Consultant
IT Consultant
-
- Participant
- Posts: 103
- Joined: Tue Jan 06, 2015 4:30 am
You dont need to edit the dsenv
Depends which operating system you have.
For RHEL, you can edit /etc/security/limits.conf
dsadm soft nproc 10000
dsadm hard nproc 10000
After doing this, logout, relogin as dsadm (or whatever user you use for datastage)
Execute the shell command:
ulimit -a
check if new values are propagated
Depends which operating system you have.
For RHEL, you can edit /etc/security/limits.conf
dsadm soft nproc 10000
dsadm hard nproc 10000
After doing this, logout, relogin as dsadm (or whatever user you use for datastage)
Execute the shell command:
ulimit -a
check if new values are propagated