I removed that parameter at all! It is not working!
Listen, I'm not despered to make the spfile ok, this is a test database. I want to find out what happens.
Oh, and I could not restart the system...
Printable View
I removed that parameter at all! It is not working!
Listen, I'm not despered to make the spfile ok, this is a test database. I want to find out what happens.
Oh, and I could not restart the system...
Since it is a 600-error, it is probably best to open an iTar with Metalink.
Oh, my mistake when I post it, I quoted the wrong file.
Yes, you are right about the slash, unforunately the files that I was told you, from archive does not have log_file_destination at all! And nothing happened.
Anyway, it's solved now, I walked on my heart and I restarted the system. It works fine. Mmmmmmmmmmm!
Probably I will never know what was the problem, maybe a locking problem with the spfile. Win2000 offers me this kind of locking problem at least one time a month...
I do not know why microsoft do not try to solve that problem, I am facing with it since winnt 4.0. We had real serious problems with this a few years ago, when we developped some PowerBuilder applications, and the pbl libraries were shared on a central "repository" (files repository, not db). Then we upgraded to win2000 and the problems happend oftener!
Did you never have problems with "forgotten" locks on files at OS level?
K, from my point of view, this thread could be close.
Glad the problem is solved. I know the frustration about some fiddling issues :-) I still think it was a syntax error in the pfile (the slash, etc) but you might as well be right about the locking stuff.
Yes, I have, by now I hate the word LOCK :-)Quote:
Did you never have problems with "forgotten" locks on files at OS level?
K, from my point of view, this thread could be close.