Oracle Database Appliance saves time and money by simplifying deployment, maintenance, and support of database solutions for organizations of every size. Oracle Database Appliance hardware models are optimized to run Oracle Database Standard Edition and Enterprise Edition.
Following are the components of an Oracle Database Appliance deployment:
UI (User Interface): A web-based application to administer and manage an appliance. It interacts with the DCS agent application to perform tasks on the appliance.
CLI: Command Line Interface to manage Oracle Database Appliance. It interacts with the DCS agent application to perform tasks on the appliance.
SDK (Software Development Kit): Oracle Database Appliance Java SDK works with the Oracle Database Appliance software to interact with the DCS agent. You can develop custom client application using REST APIs to manage the appliance.
DCS agent: The DCS agent is a REST application that performs various operations on the appliance, such as provisioning, database lifecycle management, backup and recovery, and storage management.
DCS admin: This application performs lifecycle management operations on the DCS agent, DCS controller, ODACLI, and other components.
oakd: This process manages the storage components of Oracle Database Appliance.
odaadmcli: The CLI that manages the storage components.
dcs-controller: The application on which the Browser User Interface (BUI) is deployed.
Oracle HAMI : Oracle High Availability Metadata Infrastructure service providing distributed services required by DCS including locking and synchronizing configuration details in the cluster.
repository: The file system that holds the images and clone files used by both bare metal Oracle Database Appliance system and VM DB system.
MySQL: The metadata store used by DCS agent.
DBs: Oracle Databases managed by Oracle Database Appliance software.
VMs: The KVM guest machines, also known as application VMs that are managed partially by Oracle Database Appliance. The Oracle Database Appliance software manages basic operation of the VM, such as start, stop, create, delete, and failover. Oracle Database Appliance does not manage the applications in the VM.
ACFS: Oracle ACFS file system used for VM storage, Oracle Database homes, and Oracle Database storage.
GI/ASM disk groups: Oracle Grid Infrastructure and ASM disk groups, such as DATA and RECO.
BM CPU Pools: Use the BM CPU pool to ensure that the database on a bare metal host runs exclusively on the CPU lists specified in the CPU pool. All Oracle processes are bound to the CPUs in this CPU pool and run only on these CPUs. The bare metal CPU pool is assigned to the database by updating the init.ora parameter processor_group_name.
VM CPU Pools: Use the VM CPU pools to cage and manage CPU resource allocations to workloads for virtual machines. Workloads are isolated by creating CPU pools and assigning virtual machines to a specific CPU pool. When you pin a virtual machine to a CPU pool, you ensure that the virtual machine uses CPUs in only that CPU pool.
AFD: Oracle ASM Filter Driver, a kernel module that resides in the I/O path of the Oracle ASM disks. Oracle ASM uses the filter driver to validate write I/O requests to Oracle ASM disks.
OS and KVM: This represents the operating system and KVM Hypervisor.
VM dbsystems: The fully-managed KVM DB System. The DB system contains its own DCS agent, MySQL metadata, zookeeper, Oracle Grid Infrastructure, and Oracle Database. There is no Oracle ASM instance on DB system. The DB system repository is an NFS mount from the repository on the bare metal system. Oracle Database software fully automates the creation of the DB system, including the VM, Oracle Grid Infrastructure, and database creation, patching of the system and database, and deletion of the system.
Shared Storage: The HDD and SSD storage are shared by both nodes on an Oracle Database Appliance high-availability model. On an Oracle Database Appliance single-node system, NVME drives provide the storages. These storages are used by Oracle ASM. The shared storages are passed to the VM DB systems using the virt-scsi protocol.