Hi,
I am facing a problem with exporting the Job Designs and Job Executables in my project. I am unable export the job category wise. For Routines and shared containers etc.. it's working fine. If I try to export the job category wise, it is giving the following error.
"Error calling subroutine: *DataStage*DSR_SELECT (Action=7); check DataStage is set up correctly in project dashbd_sg_int
(Subroutine failed to complete successfully (30107))".
This happens with only one project in the server, for the rest of the projects it's working fine.
If anyone knows something about this, pls revert.
Regards,
Tom.
Unable to Export Job Categories
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 41
- Joined: Fri Jun 04, 2004 5:52 am
- Location: Bangalore
-
- Participant
- Posts: 437
- Joined: Fri Oct 15, 2004 6:13 am
- Location: Pune, India
Cause for this error is..
Hi,
I was also facing similar problem.
Solution is : Re-indexing is to be done for the project. It requires all users to be logged of the Project. The command:
This command can be executed from uvsh or DS Administrator.
Regards,
Kirtikumar.
I was also facing similar problem.
Solution is : Re-indexing is to be done for the project. It requires all users to be logged of the Project. The command:
Code: Select all
DS.REINDEX ALL
Regards,
Kirtikumar.
Regards,
S. Kirtikumar.
S. Kirtikumar.
-
- Premium Member
- Posts: 41
- Joined: Fri Jun 04, 2004 5:52 am
- Location: Bangalore
..it worked...but not before some anxious movements..
Thanks,
Tom
Thanks,
Tom
Last edited by tombastian on Wed Apr 06, 2005 8:37 am, edited 1 time in total.
-
- Participant
- Posts: 64
- Joined: Fri Jul 16, 2004 7:53 am
Tom,
the indices usually only need to be rebuilt after something goes wrong within a project (i.e. system crash or file system full or similar events) or if the pathname to the project has changed. The repository files are all accessed by relative path or name; but the secondary indices contain an absolute path which can wreak havoc when doing a UNIX level rename or copy of a projects {which is why the documentation states that you shouldn't be doing this}. I seem to remember you posting a while ago about problems in the project so this might still have been a remnant of those issues.
the indices usually only need to be rebuilt after something goes wrong within a project (i.e. system crash or file system full or similar events) or if the pathname to the project has changed. The repository files are all accessed by relative path or name; but the secondary indices contain an absolute path which can wreak havoc when doing a UNIX level rename or copy of a projects {which is why the documentation states that you shouldn't be doing this}. I seem to remember you posting a while ago about problems in the project so this might still have been a remnant of those issues.