06-12-2012
26,
8
Join Date: Sep 2011
Last Activity: 12 October 2017, 5:24 PM EDT
Location: USA
Posts: 26
Thanks Given: 1
Thanked 8 Times in 7 Posts
"RED state exception" is almost all-ways hardware issue, 99.9%.
Posting more details we may be able to tell what component, but guess is CPU is at fault here. V250 is dual CPU system, can you remove one of them at the time and try to boot as a single CPU system?
---------- Post updated at 09:41 AM ---------- Previous update was at 09:33 AM ----------
From Oracle documentation:
The unexpected reboot could also be due to Red State Exception (RSE) errors. The user needs to verify if the console output has any Red State Exception (RSE) errors. The RSE can be triggered by both Software and/or Hardware, but this condition is most commonly due to a hardware fault (bad DIMM or bad CPU/ L2SRAM). The RSE error and all output are only logged to the system console (ttya or RSC) and usually is reported by one of the CPUs:
ERROR: CPU3 RED State Exception
System State (CPU3 reporting)
If you have active Oracle support, this issue is for them to deal with.
In case the console logs have RSE errors, once again, this is a critical issue where you will need a qualified MOS Support Engineer to assist you, so please contact a qualified engineer at MOS for assistance.: