Autonomous Database: What Does That Mean for You?

We’re living in a new age of the database.

Oracle sparked the first revolution, with the relational database.

Now we’re back again with the second revolution. It’s truly—well, revolutionary. And we’re calling the Autonomous Database.

Try Autonomous Transaction Processing—Sign up for the trial

Today we’re here to break it down for you, tell you what it is, and why we think you should care.

Why a Self-Driving Database Is the Future

It’s not just a revolution in databases that’s happening right now. We’re seeing the rise of the cloud, an explosion of data, and true promise for valuable machine learning. Everywhere you turn, you face challenges to the old way of doing things—and dazzling potential for the future.

Here’s what most companies are trying to do:

  • Transform to the modern cloud model
  • Ensure data safety
  • And do more with less

At Oracle, we argue that we’re uniquely positioned to help you through these challenges with our new kind of database, and here’s why.

Oracle has invested literally thousands of engineering years automating and optimizing the database. We’ve introduced and matured many sophisticated automation capabilities from memory management to workload monitoring and tuning—all of which are used in the Autonomous Database. We’ve arguably created an unmatched on-premise database, and that’s precisely what puts us in a unique position as we seek to create the cloud’s best database to help you with all of your new goals.

Here’s our dream: an autonomous, self-driving database that will automatically take care of all database and infrastructure management, as well as monitoring and tuning.

In our vision for the future, this Autonomous Database will:

  • Reduce costs and improve productivity because it automates the mundane tasks of having to provision, patch, and backup databases
  • Free up IT teams to focus on tasks that will bring value to the business
  • Be self-securing to protect itself from both external attacks and any malicious internal users
  • Automatically encrypt all data whether it’s at rest or in flight and automatically apply security updates with no downtime
  • Be self-repairing, and automatically recover from any failure
  • Minimize all kinds of downtime including plan maintenance

Wait a minute though—that’s not a vision for the future.

It’s what’s happening now.

Today, we’re announcing the launch of Autonomous Transaction Processing Cloud Service, which together with the Autonomous Data Warehouse that we released earlier this year, completely changes the way people look at and use a database.

We call this, “The Last Upgrade You’ll Ever Do.”

We are so proud of this. The Autonomous Database is the culmination of that database journey we started over 40 years ago. It brings full automation to every layer of database deployment, from optimization to operations to infrastructure.

In both Autonomous Transaction Processing and the Autonomous Data Warehouse, autonomous intelligence drives infrastructure and database operations for you, while also providing the ability to automatically tune internal database structures to optimize your application workload’s SQL as data changes over time.

We’ve made it easy, so easy.

You can create a highly available, mission-critical database deployment with the click of a button. Define your application schemas, load data using familiar tools, and get started processing your business transactions while leaving the mundane, time-consuming database operations to us.

The Autonomous Database—Optimized by Workload

Right now, there are two workloads we’ve optimized for the Autonomous Database. Of course we don’t plan to stop here. But here’s what we have that’s currently available, ready for you to purchase.

Autonomous Transaction Processing is what we’ve launched today, and we’ve been waiting to show it to you. It’s a database solution we created for general purpose transaction processing and mixed workload applications. Think of it as your database solution for transaction, batch, IoT, and reporting associated with those use cases.

We released the Autonomous Data Warehouse back in March. ADW is best for all analytic workloads. Think of it as your replacement for a data warehouse, data mart or data lake. It’s great for machine learning too.

Both Autonomous Transaction Processing and Autonomous Data Warehouse share the Autonomous Database platform of Oracle Database 18c on our Exadata Cloud infrastructure. The difference is how the services have been optimized within the database.

Here’s the breakdown:

How Can You Deploy the Autonomous Database?

So you know which flavor of the Autonomous Database you want. Or perhaps you know you want both. When it comes to deployment, you can choose between serverless Autonomous Data Warehouse or Autonomous Transaction Processing databases.

Or, very soon, you’ll be able to deploy on dedicated Exadata Cloud Infrastructure for the highest isolation. The complete hardware stack is isolated from other tenants and will provide a unique, fully isolated cloud within the public cloud.

For those who are a fan of Cloud at Customer, don’t worry. We plan to provide this option very soon.

Why Should You Want the Autonomous Database?

We could talk about the benefits of the Autonomous Database endlessly—and we will, in a future article. But here are the top benefits, boiled down as succinctly as we could make it.

The Autonomous Database enables:

  1. More IT innovation for less money
  2. More developer Innovation for less
  3. Fewer security breaches
  4. High availability due to built-in redundancy
  5. Easy upgrade to cloud
  6. Guaranteed lower cost

But don’t just take our word for it:

Don’t forget to take a look at our reviews on Gartner Peer Insights:

“We have also started with the Oracle Autonomous Data Warehouse Cloud and that was exceptionally impressive from start to finish – very easy to use – uploading of data easy and fast and the compression reduced the amount of storage needed 4 times.”

See the full review.

The people who are using Autonomous Database every day, the ones who are able to see how thoroughly it streamlines their work, are already talking about it and what they’re saying is good.

How to Get Started With the Autonomous Database

We can’t wait to show you the Autonomous Database too. And that’s why we’ve put together a free trial experience, so you can see if the Autonomous Database is truly as much of a gamechanger as we say. (Hint: It is)

Here’s what we’re giving you:

3338 hours, 2 TB of Exadata storage—what are you waiting for?

You’ll be able to:

  1. Provision an Autonomous Transaction Processing or Autonomous Data Warehouse instance
  2. Connect SQL Developer to the new database instance
  3. Load data files if needed and go!

You have nothing to lose, right?

Experience a new kind of database with Oracle’s Autonomous Database. Sign up today.

Related:

%1 (%2) %3Data inconsistency detected in table %4 of database %5 (%6,%7).

Details
Product: Exchange
Event ID: 448
Source: ESE
Version: 6.5.0000.0
Message: %1 (%2) %3Data inconsistency detected in table %4 of database %5 (%6,%7).
   
Explanation
ESE Event ID: 448 indicates that there is a corruption or inconsistency in a table in the Jet database.Check the Application log carefully for related events and patterns that may relate to this event. Check the System log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system.
   
User Action
  1. Check the Application log carefully for related events and patterns that may relate to this event. Check the System log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system. If there are any such errors, replace the hardware, update the hardware system files, or repair the file system to prevent any future errors. Do this before proceeding to the next step

  2. If the information store database is running, it is suggested that you ExMerge your data to .pst files, delete the database, create a blank database, and then ExMerge your databases to a blank database.

  3. If the database is running, you may also move all the mailboxes to another store, delete the affected database, create a new database, and then move all the mailboxes back.

  4. If the information store database will not mount, the suggested remedy is to restore from online backup before the errors appear in the Application Log.

  5. If the information store database will not mount and there is no backup, the last resort is to repair the database using Eseutil /p and then repeatedly run Isinteg -fix until there are no longer any fixes reported. Then ExMerge out the data, create a blank store, and ExMerge the data back in.

Related:

() Data inconsistency detected in table of database (,).

Details
Product: Exchange
Event ID: 448
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>Data inconsistency detected in table <name> of database <name> (<value>,<value>).
   
Explanation

ESE event 448 indicates that there is a corruption or inconsistency in a table in the Jet database.

Check the application log carefully for related events and patterns that may relate to this event. Check the system log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system.

   
User Action
  • Check the application log carefully for related events and patterns that may relate to this event. Check the system log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system. If there are any such errors, replace the hardware, update the hardware system files, or repair the file system to prevent any future errors. Do this before proceeding to the next step
  • If the information store database is running, it is suggested that you ExMerge your data to .pst files, delete the database, create a blank database, and then ExMerge your databases to a blank database.
  • If the database is running, you may also move all the mailboxes to another store, delete the affected database, create a new database, and then move all the mailboxes back.
  • If the information store database will not mount, the suggested remedy is to restore from online backup before the errors appear in the application Log.
  • If the information store database will not mount and there is no backup, the last resort is to repair the database using Eseutil /p and then repeatedly run Isinteg -fix until there are no longer any fixes reported. Then ExMerge out the data, create a blank store, and ExMerge the data back in.

Related:

() Internal trace: ()

Details
Product: Exchange
Event ID: 901
Source: ESE
Version: 6.5.6940.0
Component: Microsoft Exchange Extensible Storage Engine
Message: <process name> (<process id>) <storage group name>Internal trace: <file name> (<number>)
   
Explanation

This event indicates an unexpected error that relates to the Jet engine, ESE.dll, or to the Store process, (Store.exe). This is a generic error and the causes are various.

Associated problems seen with this event include a corrupt Exchange store database, but this symptom is not always associated with this event. In some cases, when there has been corruption of a database, an associated ESE Event ID 448 is logged in the application log. This indicates that there is a corruption or inconsistency in a table in the Jet database. In other cases, there has been no actual problem with Jet or the Exchange store and restarting the Exchange store has solved the issue.

   
User Action
  1. Check the application log for associated events, including checking ESE Event ID 448. If there is a question about the Exchange store database, check the integrity of the database using the command “ESEUTIL /G” (without the quotation marks).
  2. If there is an ESE Event ID 448 in the application log, check the log carefully for related events and patterns that could relate to this event. Check the system log carefully for related events and patterns including any errors related to hardware, drives, controllers, or the file system. If there are any such errors, replace the hardware, update the hardware system files, or repair the file system to prevent any future errors. Do this before proceeding to the next step.

    If the Exchange store database is running, it is suggested that you ExMerge your data to .pst files, delete the database, create a blank database, and then ExMerge your databases to a blank database. If the database is running, you can also move all the mailboxes to another store, delete the affected database, create a new database, and then move all the mailboxes back.

    If the Exchange store database will not mount, the suggested remedy is to restore from online backup before the errors appear in the application log.

    If the Exchange store database will not mount and there is no backup, the last resort is to repair the database using Eseutil /p and then repeatedly run Isinteg -fix until there are no longer any fixes reported. Then ExMerge out the data, create a blank store, and ExMerge the data back in.

  3. If the error recurs, consider contacting Microsoft Product Support Services. If the root cause cannot be determined from the application and system logs, a debug session may be necessary to determine the root cause. However, the exact symptom would need to recur to capture the event in a debug session.

Related: