Page 1 of 1

Unable to Export Job Categories

Posted: Wed Apr 06, 2005 6:51 am
by tombastian
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.

Cause for this error is..

Posted: Wed Apr 06, 2005 7:35 am
by Kirtikumar
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:

Code: Select all

DS.REINDEX ALL
This command can be executed from uvsh or DS Administrator.

Regards,
Kirtikumar.

Posted: Wed Apr 06, 2005 8:07 am
by tombastian
..it worked...but not before some anxious movements..

Thanks,
Tom

Posted: Wed Apr 13, 2005 3:03 am
by sudharsanan
Tom,

"it worked...but not before some anxious movements.. "

what are the anxious movements you did?..

Kriti,

can you throw some inputs on Re-indexing... why this has to be done?.. and what are the advantages and Disadvantages of Re-indexing?..please let us know...

Thanks
Sudharsanan AN

Posted: Wed Apr 13, 2005 3:51 am
by ArndW
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.