AutoScaling in Databases

 

AutoScaling in Databases

Autoscaling is about increasing the number of nodes (instances – computers – servers) in OCI, increasing an instance pool. 

AutoScaling Features 

• Use performance metrics and their configured thresholds to decide whether or not to scale a pool;
• When the metrics exceed the threshold, scale-out will occur, that is, the number of instances in the pool will increase;
• If your application is behind a Load Balancer, it is able to “attach” the new instance to the Load Balancer(s) also configured in OCI;
• The AutoScaling configuration can be based on metrics (as mentioned above) or on schedule, where you need to create policies informing when the pool will increase and when the pool will decrease;
• The instance pool must, obligatorily, use an Instance Configuration, guaranteeing standardization in the creation of instances, always using the same configurations.

Well, having said that, the AutoScaling of the Autonomous Database is quite different, but with the common objective of increasing the computational capacity of the resource that will be used, in this case, the Autonomous Database.

Some features about AutoScaling of Autonomous Database:

• Allows you to use up to three times the amount of OCPUs originally allocated. The originally allocated amount is called the base number of OCPUs;
• If the workload increases, autoscaling will increase the number of OCPU cores at that time;
• If the workload decreases, autoscaling will decrease the number of CPU cores at that time;
• You will be billed for the average OCPUs used per hour;
• It is enabled by default and can be enabled or disabled at any time;
• The status of AutoScaling (whether it is enabled or not) can be seen on the Autonomous details page;
• The base number of OCPUs allocated to an Autonomous is always guaranteed. For Autonomous running on dedicated Exadata infrastructure, the maximum number of colors available to a database depends on the number of colors available on the Exadata infrastructure, and is further limited by the number of free colors that are not in use by autoscaling other banks of data to meet high workload demands.

More details about the maximum amount of available OCPUs can be seen here: 

CPU Scaling Oracle Autonomous Database

Oracle Cloud provides a set of data management services built on self-driving Oracle Autonomous Database technology to deliver automated patching, upgrades, and tuning, including performing all routine database maintenance tasks while the system is running, without human intervention.

When you create an Autonomous Database, you can deploy it to one of two kinds of Exadata infrastructure:

• Shared, a simple and elastic choice. Oracle autonomously operates all aspects of the database life cycle from database placement to backup and updates.
• Dedicated on Public Cloud, a private cloud in public cloud choice. A completely dedicated compute, storage, network and database service for only a single tenant, providing for the highest levels of security isolation and governance.
• Dedicated on Cloud@Customer, Autonomous Database on dedicated infrastructure running on on Exadata Database Machine system in your data center, together with the networking configuration that connects it to Oracle Cloud.

Compute Models in Autonomous Database

 

Compute Models in Autonomous Database

Autonomous Database offers two compute models when you create or clone an instance:

• ECPU:

  While provisioning a new database or cloning an existing database:

  • The CPU count defaults to 2 ECPUs.
  • For databases that need 2 or more ECPUs, you must specify the number of assigned as an even integer. For example, you cannot assign 3 ECPUs to a database. The next available number of ECPUs above 2 is 4.
  • An ECPU is an abstracted measure of compute resources. ECPUs are based on the number of cores elastically allocated from the shared pool of Exadata database servers and storage servers.

  
  

  OCPU: 
• While provisioning a new database, cloning an existing database:

  • The CPU count defaults to 1 OCPU.
  • For databases that need more that 1 OCPU, you must specify the number of assigned OCPUs as an integer. For example, you cannot assign 3.5 OCPUs to a database. The next available number of OCPUs above 3 is 4.

• An OCPU is a physical measure of compute resources. OCPUs are based on the physical core of a processor with hyper-threading enabled.

Autonomous Database

 

Autonomous Database (Points)

Oracle Autonomous Database

 

Oracle Autonomous Database

 

Completed Database Automation

• ·        Provisioning
• ·        Scale-up and Scale-out
• ·         Tuning
• ·         Security and Patching
• ·         Fault Tolerance

 

Uses Machine Learning plus advanced and Proven Technologies.

• ·         RAC
• ·         Dataguard
• ·         Database Vault
• ·         Parallel SQL
• ·         In-Memory
• ·         Multitenant

 

Mission Critical, Simple, Low Risk, Low Cost

DEPLOYMENT OPTIONS

·         SHARED Exadata Infrastructure (Get Results Fast)

·         Dedicated Exadata Infrastructure (Rethink IT) -exclusive Hardware

Autonomous Database: SHARED Infrastructure

Primary Goals (Benefits)

Easy :-

• ·         Oracle Automates and Manages Everything.
• ·         Deployment, life cycle, software updates etc.
• ·         Customer simply chooses database compute, storage, and region.

Elastic:-

• ·         Low Minimum Size – 1 OCPU
• ·         Low Minimum time commitment – 1 hour
• ·         Automatically scales Online for true pay-per use

 

Autonomous Database: - Dedicated Infrastructure

Primary Goals (Benefits)

Provides your own Database cloud running on dedicated Exadata Infrastructure

Runs all your databases- any size, scale, or criticality.

Customizable Isolation

·         Isolates workloads using separate Exadata Machines, Virtual Machines or Container Databases.

Customizable Operational Policies

·         Control provisioning, updates, availability, and density.

Oracle Autonomous Database -What and How ?

 

1.      Provision à Rapidly and easily creates Mission-critical databases.

-         Creates Exadata (cloud Infrastructure)

-         RAC (scale-out databases)

-         Active Data Guard standby

2.      Secure -> Protects data from all external and internal threats

-         Apply security updates online,

-         Prevents admin snooping with DB Vault

-         Encrypts all data.

3.      Manage – Automates all Infrastructure and all database Maintenance

-         Patches all software online

-         Tunes settings

-         Performs all OS and SYSDBA operations

-         Diagnoses errors

4.      Protect- Recoers froms any failure without downtime

-         Autmates backup,restore,application transparent failover within cluster or to remote standby.

5.      Secure – Scales online for highest performance and lowest cost

-         Instant,automatic,online scaling of compute and storage enables true pay-per-use

-         Optimize -Optimally runs workloads without human direction.

-         Automatically optimizes,data formats ,indexes, parallelism and plans for each workload.

6.      Optimize – Optimally runs workloads without human direction

Automatically optimizes,data formats,indexes,parallelism and plans for each workload

 

 

 

Autonomous Database Dedicated -Primary Benefits

Dedicated Network Architecture

Autonomous Database -Cloud @customer Primary Benefits

Autonomous DB feature Comparison

Managing and maintaining Autonomous Database

Connecting to Autonomous Database

 

 

Autonomous Database – REST APIs

Autonomous Database -Using OCI-CLI

Autonomous Database -Using OCI-CLI Requirements

 

Autonomous Database -Auto-Index Creation is Inherently Better

Automatic Indexing

Oracle Data Safe

Security Zones of control

Autonomous Database Tools (Development Environment)

 

 

OPTIONS AND CONSIDERATIONS FOR MIGRATING TO ADB’s

Migration to Autonomous Database

Autonomous Migration Methods Overview

Autonomouns :- Database Migration Service