Oracle x86 servers indicate and log events and errors in various ways. Depending on the system configuration and software, certain types of errors are captured only temporarily. Therefore, you must observe and record all available information immediately before you attempt any corrective action. Power-on self-test (POST), for instance, accumulates a list of failed components across resets. However, failed component information is cleared after a system reset. Similarly, the state of LEDs in a hung system is lost when the system reboots or resets.
If you encounter any system problems that are not familiar to you, gather as much information as you can before you attempt any remedial actions. The following tasks provide a basic approach to information gathering.
Gather as much error indications and messages as possible from the system.
Review and verify the system operating environment, firmware, and hardware configuration. To accurately analyze error indications and messages, you or an Oracle Service engineer must know the system operating environment and patch revision levels and the specific hardware configuration.
Compare the specifics of your situation to the latest published information about your system. Often, unfamiliar problems you encounter have been seen, diagnosed, and fixed by others. This information might help you avoid the unnecessary expense of replacing parts that are not actually failing.