Oracle Chairman and co-founder Larry Ellison isn't buying it. On the company's earnings call in December, Ellison said Amazon "is not moving off of Oracle." He reiterated his point at an August event, saying, "I don't think they can do it."
"They've had 10 years to get off Oracle, and they're still on Oracle," he said. "And it's not going to be easy for them to use their own technology. It's not going to be cost-effective. I mean, it's really, really hard."
Patrick Moorhead, principal analyst at Moor Insights & Strategy, said the incident shows how hard it is for older applications, like those used in Amazon's warehouses, to move off Oracle, which has spent decades working with the world's largest enterprises.
"AWS Aurora is designed for forward-looking applications and Oracle for more legacy applications," he said.
Amazon emphasizes that the problem in this warehouse was completely unrelated to the outages on the Amazon web site on Prime Day, and offered the following statement:
There is a separate internal document from the Amazon Retail team, that CNBC apparently obtained, detailing an issue in a single fulfillment center (out of more than 185 worldwide) that led to the slowing of processing in the fulfillment operations and possibly a slight delay in shipping of products from that facility alone. It is important to point out that there was never an outage at the facility, and the issue only resulted in delaying shipping of about one percent of packages for a short period of time. It's also worth noting that Amazon Aurora did not create a large number of savepoints for the simple reasons that applications create savepoints, and in this instance the application created too many when entering an error loop. This issue was quickly diagnosed and resolved.
Update: This story has been updated to reflect the fact that Amazon creates error reports for incidents of various sizes, not only major incidents. It has also been updated to include Amazon's response.