Oracle reported Ora-07445 error, ugrent! Please help.

[Frank de Vries]

Do you still need help or is it resolved.
Could you otherwise post your pfile here
(init.ora) for both db's

[Ron Gordon]

I am having similar issue on my 8.1.7.2.0 databases. (32bit oracle on 64 bit sun server) According to oracle the fix is to upgrade to 9i. My work around is to monitor the alert.log every 10 minutes. If the ORA-7445 error occurs bounce the database automatically.

[Frank de Vries]

Uugh pretty nasty - you must have patient users :)
How often I have heard this from Oracle that upgrading to the next release would solve something. As if bugs don't exist there ?
Whatever happened to root-cause analysis.

I would check if you have multiple db_writers
and I would start up a db with a minimum
of parameters (almost Vanilla) to see
if your problem persists

From what I understand the error is
triggered sometime after starting a db.

Check the usual suspects unix kernel params such as NPROC, MAXUSERS and all SEM'S*
and SHARED SEGMENT params.
Then I would check IPCS and see if it is aligned (one memory segment for complete SGA)
and that semaphores behave correctly)

Well see how you get on.
good luck

[刘绍江]

Hi, Dear

Thanks for all your kindly support on this case.
Now The problem was fixed. I would like to
explain where the problem is:

In face, everything will cause the ora-07445 error. such as OS patch, ORACLE BUG, APPLICATION BUG, OR CPU, MEMORY.

I am sure that it is not oracle paramter problem as the oracle instance can be run at other node with same parameter configuration.

So we did a test on memory and CPU, de-active one by one, at least, after we deactived the Main CPU(0), The oracle did not report such error.
I monitored the status for several days, it can work well.
But CPU did not report any error at system level.

In a word, One Cpu caused this trouble.
The problem was fixed drastically after Hp replaced the failed CPU.

[刘绍江]

The cpu caused this problem, Please browse my post for detailed information.