error while creating job
Moderators: chulett, rschirm, roy
error while creating job
Error while creating job Error on CREATE.FILE command (creating file "RT_CONFIG8118" as type30.ymkdbfile:cannot create file RT_CONFIG8118yunable to create operating system file "RT_config8118" yxxx processing cannot continueyxxx)
Re: error while creating job
Hi,
Check the permissions on the directory..! Is only happening with this job are are all jobs?
provide more details if you have.
-NB
Check the permissions on the directory..! Is only happening with this job are are all jobs?
provide more details if you have.
-NB
Re: error while creating job
Have you tried using some other filename?
gateleys
gateleys
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Given that this is the 8118th job you've created, and there are six hashed files created per job, you may be hitting an operating system limit "number of subdirectories in a directory". This is 32765 on Solaris. Time to clean up your project, maybe split it into two projects.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I'm almost certain that we have hit "operating system limit "number of subdirectories in a directory". VERSION project directory has exactly 32765
directories and the error while trying to initialize a job was "...unable to create operating system file". The OS is HP-UX though, not Solaris.
However, I need an advise - how to carry on?
I was thinking of creating a completely new VERSION2 project, and use the old one only for promotion of old versions.
Another option mentioned is "split it into two projects". How do I do that?
directories and the error while trying to initialize a job was "...unable to create operating system file". The OS is HP-UX though, not Solaris.
However, I need an advise - how to carry on?
I was thinking of creating a completely new VERSION2 project, and use the old one only for promotion of old versions.
Another option mentioned is "split it into two projects". How do I do that?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Basically select a set of jobs (and any dependent objects such as routines, transforms, data elements, table definitions, etc.) from the old project, export them then import them into the new project. Compile everything to make sure you have not missed any dependent components.
As you get time, delete anything no longer needed from the old project.
As you get time, delete anything no longer needed from the old project.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
I've encountered this limit on AIX before with very large projects and while the real solution is to split the project into multiple ones that are smaller and more manageable (As well as giving better response in the Director) you can resize some of DataStage's files to static hashed, this reduces the number of inodes used by 3 per hashed file (going from 1 dir, 1 hidden, 2 visible files per hashed file to 1 visible file). N.B. this is only a temporary fix.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>