This is not a big deal, but we have rogue processes that will lock modules and never release them. If I attempt to compile them we end up with exclusive locks (as you should). However the only way to stop the rogue process is to kill it, we do not know what process it is so we kill them all, unfortunately SQL Navigator shows up with the same unix session “command” and it gets killed. Once this happens, navigator will report the session terminated and turn everything red and ask you if you want to reconnect, some times it reconnects, some times it takes my PC to 100% busy and I end up having to end session on it through task manager. As far as I am concerned this is a very unimportant problem, just thought I would report it.
Thanks for the explanation…
We may contemplate this further, when we look into SQL Nav error handling situations.
- Jaime -