Last updated on DECEMBER 19, 2016
Applies to:Oracle Database Appliance Software - Version 22.214.171.124 to 126.96.36.199
Oracle Database Appliance X3-2 - Version All Versions to All Versions [Release All Releases]
Oracle VM - Version 3.2.3 to 3.2.3 [Release OVM32]
Information in this document applies to any platform.
Brief overview of the three types of ODA Virtualized Platform (ODAVP) domains:
Oracle Database Appliance Base Domain (ODA_BASE): A privileged virtual machine domain, specifically for databases, that provides database performance similar to bare metal deployments. A PCI pass-through driver provides ODA_BASE direct access to the shared storage.
Domain 0 (Dom0) and Dom1: In this note we also refer to Dom1 to identify Dom0 on the second ODA node.
Default domain that initiates Oracle Database Appliance Virtualized Platform provisioning processes and hosts virtual machine templates.
Most of the responsibility of hardware detection in an Oracle Database Appliance Virtualized Platform environment is passed to the management domain, referred to as domain zero (or Dom0). On x86-based servers, the Dom0 / (Dom1) kernel is actually a small-footprint Linux kernel with support for a broad array of devices, file systems, and software RAID and volume management. In Oracle Database Appliance Virtualized Platform, Dom0 provides access to much of the system hardware, creating, deleting and controlling guest operating systems, and presenting those guests with a set of common virtual hardware.
Guest Domains (Domain U): Virtual machines that are provisioned to host non-database workloads, such as applications and middleware. Guest operating systems each have their own management domain, called a user domain, abbreviated to "Domain U". These domains are unprivileged domains that have no direct access to the hardware or to the device drivers. Each Domain U starts after Dom0 is running on Oracle Database Appliance Virtualized Platform.
- We see the odarepo1 and odarepo2 repositories on the public nodes and the dom0 dom1 nodes.
- We created new shared repositories to clone new VMs into.
- The shared repositories on the public nodes are there as seen with df -k .
- However, the DOM0/1 nodes show nothing: They should have the IP and /OVS/Repositories/sharedreponame;
- Only the odarepos are displayed.
- We created some VMs which were already cloned into the new shared repos.
- While cloning we noticed that Public node 1 had I/O errors using the df command.
- All the shared repos had the I/O errors.
- We have rebooted the ODA several times and the problem still persists.
- and -
2) on 2.10 +
- and -
3a) New usage
3c) Changed Node name to use Upper or Mixed Case
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms