OCI Database Services : cheatsheet

DB System

  • VM [Virtual Machine] and BM [Bare Metal]
  • Orcale DB version 11.2, 12c, 18c, 19c, 21 c
  • VM is multitenant, servicing multiple tenant on same physical structure and Bare metal is single tenant, dedicated to one
  • Active data guard and RAC is only with Enterprise Edition Extreme Performance
  • Max OCPU in Orcale DB on VM is 24 *2 [ 2 is for RAC] = 48 
  • BM, storage is NOT scalable as NVME is used & max OCPU 52
  • OCPU scaling is available for all DB system however online is only for BM DB System
  • Scaling the OCPU in VM system, require change of shape, requires rebooting,
  • BM.DenseIO2.52 L shape os available for DB version 11.2 and above
  • In VM DB system selected Edition of Oracle can not be changed
  • VM DB system, one can not scale from one node to 2 node DB system , however, can customize the OCPU, DB software version 12 and above
  • Creating a clone requires new ssh key and admin password
  • Full backups can be in Object storage, can be used to restore
  • Oracle recommends a service gateway in VCN with access to object storage for backup
  • Automatic retention default value is 30 days [7,15,30,45,60], automatic backup are deleted on termination
  • 2 Node VM RAC udpates are done in a rolling manner for OCPU scaling or patch deployment
  • Data Guard can be deployed across AD  for HA [High Availbility] and Across Region For DR [Disaster Recovery]
  • Storage Management services is Oracle Grid Infrastructure ASM & LVM, [fast & only for Single Node DB system and for selected version]
  • For a single instance deploy the data guard to make the system availability
  • Data Guard [HA, DR, data protection]
    • It is like stand by replica
    • For VM, second DB system must be available before enabling dataguard
    • Must be same, BM-BM, or VM-VM or 1node-1node or 2node-2node
    • DB version and Edition must be same
    • Network rule should be stateful [ingres and egress allowed]
    • Maximum performance support ASYNC type and Maximum Availability support SYNC transport type
  • ASM offer choice for normal 2 replica, or high 3 replica
  • BM systems are single-node systems and there is no HA without RAC, so data guard is highly recommended for HA, RMAN [backup tool] for high manageability and protection against  data loss, and storage failure  Backups, Golden gate can be configured
  • Single Node VM, out of the box protection is RMAN for backups
  • Prefer ASM over LVM for data guard environment

ExaData Cloud Service

  • Exadata : Ideal DB hardware + DB aware system software + Automation Management
  • Oracle DB as service running on Exadata 
  • Elastic Scaling , Pay per use, Oracle manages Infra, User control automation
  • Base system [not scalable] , X8M Quarter Rack [scalable]
  • MAX 1600 OCPU, 44 TB memory, 96TB PMEM, 1.6PB flash ,3.2 PB service
  • VCN, 2 subnet [clilent subnet, backup subnet] is required,
  • Client subnet require 2 node require 10 IP address [2ip per node, 3 scan ip , 3 reserved], 4 node require 14 ip
  • Backup subnet require 1 ip is required per node
  • Allocate storage for local backup and sparse snapshot can not be changed. Can not be changed the storage option, once the VM cluster is provisioned.
  • Infra maintenance is mandatory, if customer does not setup, oracle will notify at least before two weeks, maximum 180 days from last patch
  • DB server patching and ASM maintenance are done on rolling basis
  • Archived redo logs files are backed up every 30 min
  • Backup with Data guard is done at the primary site
  • Database home is a directory structure at Exadata for Database software binary files

HA Component

Exadata cloud service provide Silver and Gold level  Availability Architecture

  • RMAN backup [for bronze] , 3 identical copies of backup on the primary system
  • RAC  [for silver] save from node failure and ZDM [Zero Downtime Maintenance] and elastic change with no downtime
  • Active data guard for HA [Gold]
    • Site Failure Protection
    • Corruption Prevention
    • Rolling Upgrades
    • Offload Work to standby with read-mostly scale-out

ExaData Cloud@Customer

  • On-premise is same as cloud
  • Can run Exadata Database or Autonomous database as well
  • Multiple VM cluster can be setup on same Exadata

Mysql DB System

  • Mysql Enterprise Edition Only
  • Mysql automatic backup retention 1-35 days, maximum 100 manual backups
  • Once defined automatic backup retention, can‘t be edited 
  • Mysql designed for OLTP, not for OLAP
  • Heatwave removed the requirement to move the database to separate system for OLAP, By Heatwave, one can use the same DB for OLAP. It is in-memory analytics engine.

Orcale NoSQL DB

  • Serverless DB service for dynamic data supporting a different type of nosql DB
    • Document databases
    • Key-value stores
    • Column-oriented databases
    • Graph databases
  • Pay as you use, Read Write Provisioning

Oracle Database Management Service

  • An agent for managing and monitoring Oracle Databases

Oracle Autonomous Database

Automous Serverless

  • Oracle automates and manages everything
  • Elastic, customer chooses size and location
  • Placed on exadata cloud infrastructure in region
  • RAC cluster allows rolling patches and fast failover
  • Designed for common apps or public cloud apps
  • Auto Scaling & Clone support

Autonomous Dedicated

  • Private database cloud running on Exadata, High isolation, Customize operational policies
  • Quarter Rack X7 Exadata
  • 1 Cluster per quarter rack
  • 4 Container databases per cluster
  • No Auto Scaling but Clone support
  • CREATE TABLESPACE & Auto indexing & Documented RTO/RPO

Data Safe

  • This is a cloud service
  • Private endpoint and NSG is required
  • For private ADB, NSG is needed to allow network
  • Data safe need to apply to each PDB in container databases
  • Data Safe can provide a security assessment report
  • Data discovery and Data masking and Activity auditing can be done

Read More,

Leave a Reply

Your email address will not be published. Required fields are marked *