> a typical freeze is very uncommon for Oracle!
I know. That's what baffles me.
> If a unix system behaves like this it's to 99% hardware and to 90% RAM.
> Even if switching to oracle might indicate a problem with ORACLE.
> Triple check your RAM.
> If possible remove 512MB each at a time and retry.
> I don't believe it has something to do with non-certified SuSE 9.3.
I desperately hope it's not RAM. My last system died due to RAM issues
- it did mean IT was able to upgrade me to a nice shiny new AMD64 though :-)
I've done RAM tests on this computer about a month ago.. let it
memtest86 run over a weekend. No errors. I will drop it into memtest86
again this weekend.
No lockups with any other heavy system loads.
I've done a lot of Google searghing for the ORA-01031
error.. and lots
of people have reported similar problems, but the solutions given
haven't worked in my case.
I'd be happy if I could kill the dB completely and setup a new instance.
Prob is.. the minute I fire up dbca and click on the SID the computer
To unsubscribe, email: suse-oracle-unsubscribe@(protected)
For additional commands, email: suse-oracle-help@(protected)
Please see http://www.suse.com/oracle/ before posting