What's wrong (spfile)

The path is correct. I could not understand. I did this many times... :(
And it corrupted my spfile, too (before that, I issued the same statement, and because it freezed I killed the sqlplus)...
Look:

SQL> create spfile from pfile='d:\dafne\admin\pfile\initdafne.ora';
create spfile from pfile='d:\dafne\admin\pfile\initdafne.ora'
*
ERROR at line 1:
ORA-00600: internal error code, arguments: [kspsetpao1], [594], [581],[*],
[sessions], [2], [], []

?

Oh, the spfile is not corrupted it is no more...(I looked now...)

[Edited by ovidius on 04-04-2002 at 03:44 AM]

Do the following:

In the pfile, put the directory parameters in quotes. For example: not control_files = (d:\dafne\admin\control_01.ora,
d:\dafne\admin\control_02.ora), but ("d:\dafne\admin\control_01.ora","d:\dafne\admin\control_02.ora"). Then run the create spfile command.

They are already like this, and the problem is IT IS THE SAME PFILE I used last time...
I think is a win2000 locking problem... But I do not know. Look:
the pfile remains locked. If I make a copy, then I used it to make the spfile, the same error is issued, and the new copy remains locked, too!
I already have 4 copies... :(
Oh, the locking problem is that classic one, in win2000, I close everything that accessed the file, I overwrite the rights, and nothing. From my experience, only a restart solve this, but I cannot do this, of course.
What I can't understand is WHY isn't working with fresh copy of the file??? The same error... :(

Are you sure there are no syntax errors in the pfile. Could you post it?

How could it be? It is made by orcale from the spfile... :)))

Look:

Code:

---


*.background_dump_dest='D:\dafne\admin\bdump'
*.compatible='9.0.0'
*.control_files='D:\dafne\control\control01.ctl','D:\dafne\control\control02.ctl','D:\dafne\control\control03.ctl'
*.core_dump_dest='D:\dafne\admin\cdump'
*.cursor_sharing='SIMILAR'
*.db_block_size=4096
*.db_cache_size=25165824
*.db_domain='pps.phoenix'
*.db_name='dafne'
*.fast_start_mttr_target=300
*.instance_name='dafne'
*.java_pool_size='0'
*.large_pool_size='4194304'
*.log_archive_dest='d:\dafne\redo_arch\'
*.log_buffer=8388608
*.open_cursors=300
*.processes=60
*.remote_login_passwordfile='EXCLUSIVE'
*.sessions=66
*.sga_max_size=67108164
*.shared_pool_size=16777216
*.sort_area_size=2097152
*.timed_statistics=TRUE
*.undo_management='AUTO'
*.undo_tablespace='UNDO'
*.user_dump_dest='D:\dafne\admin\udump'

---

Run the create command with this one:

Code:

---


background_dump_dest="D:\dafne\admin\bdump"
compatible=9.0.0
control_files=("D:\dafne\control\control01.ctl","D:\dafne\control\control02.ctl","D:\dafne\control\control03.ctl")
core_dump_dest="D:\dafne\admin\cdump"
cursor_sharing=SIMILAR
db_block_size=4096
db_cache_size=25165824
db_domain=pps.phoenix
db_name=dafne
fast_start_mttr_target=300
instance_name=dafne
java_pool_size=0
large_pool_size=4194304
log_archive_dest="d:\dafne\redo_arch\"
log_buffer=8388608
open_cursors=300
processes=60
remote_login_passwordfile=EXCLUSIVE
sessions=66
sga_max_size=67108164
shared_pool_size=16777216
sort_area_size=2097152
timed_statistics=TRUE
undo_management=AUTO
undo_tablespace=UNDO
user_dump_dest="D:\dafne\admin\udump"

---

SQL> startup mount pfile='d:\dafne\admin\pfile\initdafne.ora';
LRM-00111: no closing quote for value 'D:\dafne\a'
ORA-01078: failure in processing system parameters

It did not like it... :)

Quote:

---

Originally posted by ovidius
SQL> startup mount pfile='d:\dafne\admin\pfile\initdafne.ora';
LRM-00111: no closing quote for value 'D:\dafne\a'
ORA-01078: failure in processing system parameters

It did not like it... :)

---

Replace log_archive_dest="d:\dafne\redo_arch\"

with log_archive_dest="d:\dafne\redo_arch"

The slash is probably the problem.

Oh, I think the slash could not be the problem, as this is exactly the pfile that I was using for this database from the very beggining. The file that I posted is a backup. It surely is the very file that I used tens of times to create spfile from it, and from that spfile I created other pfiles that I modified and then I used it to create brand new databases from scratch, that are working. I'm absolutely dazzled, because this is the last point where I thought I ever find out a problem... I mean, 'create spfile from pfile' ... God!
Let's see, what process exactly does the job, and what it needs for it. Maybe we find out something that part of us didn't know...
So, as far as I know, all that you need is to be connected to an instance, even "idle". And the instance could be in any state, in fact, it does not matter. (Oh, by the way, my instance is healthy, if I do not issue something like %pfile% pr %spfile% it is very happy, but it was started with pfile='...', because now it does not have a spfile anymore...).
So, the pfile is good enough to start open the instance, but is not good enough to create some spfile?
Hey, some guru here, ever meet something like this? Please? Pliiiizzzzz? :D

I forget to tell you, the db is noarchivelog mode.

[Edited by ovidius on 04-04-2002 at 05:21 AM]

Did you try to remove the slash and then run the create spfile command. Try that first.

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.

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.

---

Yes, I have, by now I hate the word LOCK :-)