How to clear the "deleted jobs" from repository vi
Moderators: chulett, rschirm, roy
How to clear the "deleted jobs" from repository vi
Hi all,
While I tried to import some jobs in DSManager, it throwed some errors and aborted the import process. But it still shows some new jobs in the repository view. When I tried to delete those jobs, it says there is no such job exist.
I had restarted the server and again checked, but for no use, still it is showing those jobs.
Help me to get rid of these jobs.
Thanks in advance,
Ravin.
While I tried to import some jobs in DSManager, it throwed some errors and aborted the import process. But it still shows some new jobs in the repository view. When I tried to delete those jobs, it says there is no such job exist.
I had restarted the server and again checked, but for no use, still it is showing those jobs.
Help me to get rid of these jobs.
Thanks in advance,
Ravin.
I had this problem in the last project. Sometimes what happens is that if you abort or rename the job and some thing happens(i dont exactly know what), the job in UV remains like a dangling pointer. So you have to go to the UV shell (normally the dsadmin will have access to this dir) and find out those job names and delete them.
Our problem was that we could not see our jobs in the designer. Once i went to the UV shell i noticed that those jobs did not have any category to which they were attached. They only had a job number.
Hope this helps.
Our problem was that we could not see our jobs in the designer. Once i went to the UV shell i noticed that those jobs did not have any category to which they were attached. They only had a job number.
Hope this helps.
I am not seen any "clean up" option in DS Admin client.
If you mean "Clean up resource" which is there in DS Director client, then FYI I had tried that but DS again says that no such job exist.
So I want to know what "clean up" actually means and where that option is present.
Help me.
Thanks in advance,
Ravin
If you mean "Clean up resource" which is there in DS Director client, then FYI I had tried that but DS again says that no such job exist.
So I want to know what "clean up" actually means and where that option is present.
Help me.
Thanks in advance,
Ravin
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Can you check it on a machine that's not using Client Switcher? That is, one on which DataStage 5.x has never been installed.
Can you also report, from its Properties, the exact version of DSAdmin.exe on the system?
Can you also report, from its Properties, the exact version of DSAdmin.exe on the system?
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.
-
- Premium Member
- Posts: 483
- Joined: Thu Jun 12, 2003 4:47 pm
- Location: St. Louis, Missouri USA
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Not sure about "where" it's gone, but I can confirm that it no longer exists at 7.1r1.
The functionality remains, however, via the DS.TOOLS menu on the server. Option 4 (check integrity of job files) will - among other things - track down any orphans and delete them (checking with you first that it is OK to do so).
The full functionality of Cleanup Project is had by using option 2 (rebuild Repository indexes) as well as option 4.
The functionality remains, however, via the DS.TOOLS menu on the server. Option 4 (check integrity of job files) will - among other things - track down any orphans and delete them (checking with you first that it is OK to do so).
The full functionality of Cleanup Project is had by using option 2 (rebuild Repository indexes) as well as option 4.
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.