----- Original Message -----
Sent: Tuesday, January 07, 2003 6:34
PM
Subject: RE: Database/system
Crashing
Well I relocated the background dest files
and I got the following error... that was a great idea!
ORA-00206: error in writing (block 3, #
blocks 1) of controlfile
ORA-00202: controlfile:
'/u04/oradata/ERCS/ora_control2'
ORA-27063: Message 27063 not found;
product=RDBMS; facility=ORA
SVR4 Error: 5: I/O error
Additional
information: -1
Additional information: 2048
error 221 detected in
background process
The SA's think its a data block corruption.
If anyone has any additional information, it will be greatly
appreciated.
At least now I know why the database crashed
to begin with. Now the SA's just have to figure out how to fix
it.
Thanks for all the help!!
Val
I'd agree with Dan. You need to find the root cause of the
crash. If you rebuild to the current state from scratch, the odds are
you'll see the same problem reoccur. Secondly, while NFS mounted
volumes will work, they should always be a last resort as any network,
remote IO load on the server where the NFS mounted volume lives "could"
cause IO corruption and panic the host server. I didn't see the start
of this thread so these are after the thought comments. Maybe they're
helpful.
Regards,
Bill Burke
"The Kinder and Gentler DBA"
www.OracleGuru.com
www.KBMotorsports.biz
Val,
Not having an entry in the
alert log or having trace files is not all that odd. This indicates a hard
crash of the instance, where the background processes were unable to write
to the files. This could be a result of the instance being forcefully
terminated without using the Oracle shutdown process or it could be the
result of the processes being unable to write to the device containing the
log and trace files. Try moving the background_dump_dest to another device
(preferably internally connected to the server).
I would not reinstall the OS
and Oracle unless it can be reasonably determined that the OS is causing
the problem. What are the reasons the SAs say it is the OS? It is a lot of
work to recreate the system and you have no guarantee that this will solve
it. It sounds like a more detailed inspection of all the systems is in
order instead of spinning the 'Wheel Of Blame' to stop on the 'most
likely' suspect. More troubleshooting is called for, not the drastic step
of "wipe it clean and start over"
Dan Fink
Yes there are NFS mounts involved. What you said about
the OS locks on the audit directory makes a lot of sense. My SA's are
back to thinking it's a OS problem because it crashed again with the
database shut down.
The odd thing is that there is nothing written to the
Oracle alert log file nor are there any entries in the trace files. But
when the system is rebooted and I bring the db back up, Oracle knows it
previously crashed and recovers itself. That's in the alert log file.
Its like the system is losing its pointers or something. I suggested
reinstalling the OS and Oracle then put my database back and see if that
helps. Are there huge risks with this scenario?
Another odd thing that the SA's can't figure out is
there are no entries in the message file nor can they get a dump file to
determine why the system crashed. There is nothing. It crashed over the
weekend with no activity and they got some sort of i-nodes error.
Thanks for all your replies. Any ideas are helpful and I
will relay them to our SA's...
Val
