I've seen that happen if you are not alone in the Project. Are there any other users or processes accessing that Project? You may need to kill off any 'leftovers' from other folks and try it again.
-craig
"You can never have too many knives" -- Logan Nine Fingers
[quote="chulett"]I've seen that happen if you are not alone in the Project. Are there [b]any[/b] other users or processes accessing that Project? You may need to kill off any 'leftovers' from other folks and try it again.[/quote]
Hi,
I am alone in the project.
i logged as Administrator.
i restarted the system,but still arise same problem.
but i am sure this happened after executing DS.REindex ALL from Administrator command button...
It happens this way when any of the DataStage Jobs are open in Designer during the REINDEXing process. Make sure that none of the jobs are opened (locked status) before executing this command. You can execute this command once again after making sure that none of the jobs are on locked state.
[quote="tombastian"]It happens this way when any of the DataStage Jobs are open in Designer during the REINDEXing process. Make sure that none of the jobs are opened (locked status) before executing this command. You can execute this command once again after making sure that none of the jobs are on locked state.[/quote]
yes,i done in the same way as u said.
i restarted the system and stop/start all datastage services online.
but still same problem.
have you tried using DS.REINDEX ALL in Command?
I wonder why i cant see any jobs,after using REINDEX..
Exactly. As I tried to say earlier on, all it takes is one stray connection or lock to have a REINDEX make a Project look empty. Been there, done that.
Try again. Use LIST.READU to ensure there are no stray locks on your objects in the repository before you do so and UNLOCK any that still remain. A search of the forum will turn up syntax and examples of using both.
-craig
"You can never have too many knives" -- Logan Nine Fingers
