Book Image

Oracle Autonomous Database in Enterprise Architecture

By : Bal Mukund Sharma, Krishnakumar KM, Rashmi Panda
Book Image

Oracle Autonomous Database in Enterprise Architecture

By: Bal Mukund Sharma, Krishnakumar KM, Rashmi Panda

Overview of this book

Oracle Autonomous Database (ADB) is built on the world’s fastest Oracle Database Platform, Exadata, and is delivered on Oracle Cloud Infrastructure (OCI), customer data center (ExaCC), and Oracle Dedicated Region Cloud. This book is a fast-paced, hands-on introduction to the most important aspects of OCI Autonomous Databases. You'll get to grips with concepts needed for designing disaster recovery using standby database deployment for Autonomous Databases. As you progress, you'll understand how you can take advantage of automatic backup and restore. The concluding chapters will cover topics such as the security aspects of databases to help you learn about managing Autonomous Databases, along with exploring the features of Autonomous Database security such as Data Safe and customer-managed keys for Vaults. By the end of this Oracle book, you’ll be able to build and deploy an Autonomous Database in OCI, migrate databases to ADB, comfortably set up additional high-availability features such as Autonomous Data Guard, and understand end-to-end operations with ADBs.
Table of Contents (13 chapters)
1
Part 1 – Understanding Autonomous Database in OCI
4
Part 2 – Migration and High Availability with Autonomous Database
9
Part 3 – Security and Compliance with Autonomous Database

Answers

  1. The available infrastructure options are shared Exadata infrastructure and dedicated Exadata infrastructure.
  2. A shared infrastructure deployment provides easy-to-provision Autonomous Databases where multiple tenants can share an Exadata Cloud infrastructure. With dedicated deployment, you can consider it your own reserved Exadata infrastructure in OCI, which provides more flexibility and control than shared options.
  3. All standard connectivity methods, such as JDBC, SQL* Net, or any SQL client tools such as SQL Developer, are used for connectivity.
  4. ADB is a fully managed service from Oracle. You don’t have access to the OS; additionally, not all DBEE administrative features are available. You should look at the Oracle documentation, as features might change over time.
  5. Up to 60 days (7, 15, 30, and 60 days).
  6. OCI support both BYOL and a License Included model for provisioning.
  7. Yes, you can seamlessly scale beyond 16 OCPUs, although one of the requirements enforced by Oracle is to have a RAC license for scaling beyond 16 OCPUs in a BYOL scenario.
  8. You need at least one OCPU to provision ADB, although upon provisioning, you can shut down the instance and database OCPU billing will stop. Keep in mind that you will be responsible for storage as long as the service instance exists.
  9. Yes, Oracle Enterprise Manager 13.3, along with EM DB plugin bundle patch 13.32.0.190731 can be used. Keep in mind that only ATP-D databases are supported by EM at moment.
  10. Yes, ADB supports XML DB features with certain restrictions.
  11. Dedicated shape options include a quarter rack, half rack, and full rack. Underlying hardware could be one of Exadata X7, X8, X8M, or X9M shapes.
  12. Shape options include a base rack, quarter rack, half rack, and full rack. Underlying hardware could be one of Exadata X7, X8, X8M, or X9M shapes.
  13. No.