Quote:
Originally posted by jrpm
Are you using a variant on 'Startup Parallel' in your command file. It is not directly a factor, except that I have seen that message in the past when starting the second server of a Parallel Server environment but forgetting to tell the server it was coming up in parallel so it could not get it's exclusive locks on some files (the other server already had locks.)
There is another possibility in that I have seen NT, particularly an underpowered box for its current workload, not clear the NT level lock tables on files very quickly. When that is happening, you can either wait 'a while' or bounce the box to clear the OS level locks. (Oracle may be down, but NT hasn't freed the locks yet.)
-------------------------------------------------------------