Amazon's cloud computing division AWS has announced that it has decided to utilize its own databases instead of Oracle's and the company has finally turned off its last Oracle database. AWS has managed to move 75 petabytes of internal data stored on almost 7,500 Oracle databases back to its own service. In a blog post, AWS's Jeff Barr explained that the database migration is now complete after several years of work, saying: "Today I would like to tell you about an internal database migration effort of this type that just wrapped up after several years of work. Over the years we realized that we were spending too much time managing and scaling thousands of legacy Oracle databases. Instead of focusing on high-value differentiated work, our database administrators (DBAs) spent a lot of time simply keeping the lights on while transaction rates climbed and the overall amount of stored data mounted. This included time spent dealing with complex & inefficient hardware provisioning, license management, and many other issues that are now best handled by modern, managed database services."
Database giant Oracle has released a fix for a severe bug in Oracle Database Server on Windows. The Oracle Database Server bug, tagged with the identifier CVE-2018-3110 is about as severe as it possible because it can not only give an attacker "complete control" over the vulnerable 11g, 12c, and new 18c database, but also provides shell access to the Windows server it is running on top of. The bug, which stems from a Java virtual machine component of the database, has a CVSS v3 base score of 9.9 out of 10. Vulnerable versions include Oracle Database Database vulnerability in versions 22.214.171.124 and 126.96.36.199 on Windows. It also affects version 188.8.131.52 on Windows, Linux, and Unix servers, however the latter two were patched in Oracle's planned July update, according to Oracle.