Introduction: Oracle hardwareThe problem caused Oracle to suffer. According to the results of a recent survey conducted by the Independent Oracle user organization (IOUG), the accidental interruption of the Oracle database over the past year was mostly caused by hardware faults, this is not caused by hackers.
IOUG (the organization has 265 members, most of which are database administrators, developers, or managers). According to a survey report published in March, despite all-day (round-the-clock) availability requirements continue to grow, but in the last year, there were still seven Oracle Database downtime more than one hour.
According to the report, most accidents are not caused by natural disasters, power outages, or security issues. Accidental database interruptions caused by security incidents account for 1% of the accidental database interruptions. The ratio of accidental database interruptions caused by power outages or natural disasters is 7% and 4%, respectively.
Nearly half of the unexpected interruptions are caused by hardware problems. The number of accidents caused by network, application suite, or database problems accounts for about 1/3. There are many possible causes. For users who encounter both hardware and network problems, their database interruption may take more than 15 hours.
Performance decline is also common: 40% of respondents reported a performance decline at least every two months.
The preceding section describes the impact of Oracle Database hardware faults. We hope that you can manage the Oracle Database hardware to give a green light for your Oracle database operations.