exadata cloud@customer configuration and administration ......2020/12/08 · charan chaudary...
TRANSCRIPT
Oracle® ExadataExadata Cloud@Customer Configuration andAdministration Guide
Release 19F18226-31February 2021
Oracle Exadata Exadata Cloud@Customer Configuration and Administration Guide, Release 19
F18226-31
Copyright © 2008, 2021, Oracle and/or its affiliates.
Primary Author: Nirmal Kumar
Contributors: Mark Bauer, Rhonda Day, Douglas Williams, Michael Fitch, Peter Fusek, Neil Hebert, TerenceBuencamino, Raj Ojha, Behkam Aminzadeh, Ashutosh Chetal, Rachna Thusoo, Kris Bhanushali, AlexanderPrince Mathew, Bob Thome, Tushar Pandit, Manish Shah, Vira Goorah, Somnath Lahiri, Pablo SainzAlbanez, Saravanan Sabapathy, Charan Chaudary Lekkalapudi, Lakshmi Sneha Kandukuri, Nayana Vishwa,Namratha Mandya Subramanya, Boming Zhang, Vedika Joshi, Abhilash Gudasi, Santosh Uttam Bobade,Ankit Mahale, Nithin Kovoor, Ranganath Srirangapatna Ramachandra, Manini Chattopadhyay, Sheila Ray
This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it onbehalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,any programs embedded, installed or activated on delivered hardware, and modifications of such programs)and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Governmentend users are "commercial computer software" or "commercial computer software documentation" pursuantto the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works,and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programsembedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oraclecomputer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in thelicense contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloudservices are defined by the applicable contract for such services. No other rights are granted to the U.S.Government.
This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks oftheir respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks areused under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registeredtrademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will notbe responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
What’s New in Oracle Exadata Cloud@Customer Gen2
What’s New in Oracle Exadata Cloud@Customer xvi
What’s New in ADB-D on Oracle Exadata Cloud@Customer xix
1 Introduction to Oracle Exadata Cloud@Customer
About Oracle Exadata Cloud@Customer 1-1
Per-Second Billing for OCPU Usage 1-2
Per-Second Billing for Autonomous Database OCPU Usage 1-2
System Configuration Options for Oracle Exadata Cloud@Customer 1-3
Oracle Exadata Cloud@Customer X8M-2 System Specifications 1-3
Oracle Exadata Cloud@Customer X8-2 System Specifications 1-4
Oracle Exadata Cloud@Customer X7-2 System Specifications 1-4
Plan Your Configuration Settings on Storage 1-5
About Storage Configuration for Oracle Exadata Cloud@Customer 1-5
Allocation of Storage Space Options on Oracle Exadata Storage Servers 1-6
Allocation Proportions for DATA, RECO and SPARSE Disk Groups 1-7
Moving to Oracle Cloud Using Zero Downtime Migration 1-7
2 Preparing for Exadata Cloud@Customer
Site Requirements for Oracle Exadata Cloud@Customer 2-1
Space Requirements for Oracle Exadata Cloud@Customer 2-2
Weight of Oracle Exadata Cloud X8 Racks 2-2
Receiving, Unpacking, and Access for Oracle Exadata Cloud@Customer Racks 2-2
Flooring for Oracle Exadata Cloud@Customer Racks 2-3
Electrical Power for Oracle Exadata Cloud@Customer Racks 2-3
Temperature and Humidity Ranges for Oracle Exadata Cloud@Customer 2-5
Ventilation for Oracle Exadata Cloud@Customer Racks 2-6
Network Requirements for Oracle Exadata Cloud@Customer 2-7
Network Requirements for Oracle Exadata Cloud@Customer 2-7
Data Center Network Services for Exadata Cloud@Customer 2-8
IP Addresses and Subnets for Exadata Cloud@Customer 2-9
iii
Uplinks for Exadata Cloud@Customer 2-10
Network Cabling for Exadata Cloud@Customer 2-11
Checklists for Exadata Cloud@Customer Deployments 2-11
System Components Checklist for Exadata Cloud@Customer 2-12
Data Center Room Checklist for Exadata Cloud@Customer 2-12
Data Center Environment Checklist for Oracle Exadata Cloud@Customer 2-12
Access Route Checklist for Oracle Exadata Cloud@Customer 2-13
Facility Power Checklist for Oracle Exadata Cloud@Customer 2-13
Safety Checklist for Oracle Exadata Cloud@Customer 2-14
Logistics Checklist for Exadata Cloud@Customer 2-14
Network Configuration Checklist for Oracle Exadata Cloud@Customer 2-15
Reracking Checklist for Oracle Exadata Cloud@Customer 2-16
3 Provisioning Exadata Cloud@Customer Systems
About Provisioning Oracle Exadata Cloud@Customer Systems 3-1
Required IAM Policy for Provisioning Servers 3-2
Prerequisites for Provisioning Oracle Exadata Cloud@Customer Servers 3-3
Using the Console to Provision Oracle Exadata Cloud@Customer 3-3
Using the Console to Create Infrastructure 3-4
Using the Console to Edit Oracle Exadata Cloud@Customer Infrastructure 3-7
Using the Console to Download a File Containing Configuration Data 3-10
Using the Console to Activate Exadata Cloud@Customer Infrastructure 3-10
Using the Console to Check the Status of Exadata Cloud@CustomerInfrastructure 3-11
Using the Console to Move Exadata Cloud@Customer Infrastructure 3-11
Using the Console to Delete Exadata Cloud@Customer Infrastructure 3-12
Managing Infrastructure Maintenance Contacts 3-13
View Primary Maintenance Contact 3-13
Add Secondary Contacts 3-14
Edit Maintenance Contacts 3-14
Promote a Secondary Contact to Primary 3-14
Remove a Secondary Contact 3-15
Using the API for Oracle Exadata Cloud@Customer 3-15
4 Managing VM Clusters on Exadata Cloud@Customer
About Managing VM Clusters on Exadata Cloud@Customer 4-1
Required IAM Policy for Managing VM Clusters 4-2
Prerequisites for VM Clusters on Exadata Cloud@Customer 4-2
Using the Console for VM Clusters on Exadata Cloud@Customer 4-3
Using the Console to Create a VM Cluster Network 4-4
iv
Using the Console to Edit a VM Cluster Network 4-6
Using the Console to Download a File Containing the VM Cluster NetworkConfiguration Details 4-8
Using the Console to Validate a VM Cluster Network 4-8
Using the Console to Terminate a VM Cluster Network 4-9
Using the Console to Create a VM Cluster 4-9
Using the Console to Scale the Resources on a VM Cluster 4-12
Using the Console to Stop, Start, or Reboot a VM Cluster Compute Node 4-14
Using the Console to Check the Status of a VM Cluster Compute Node 4-14
Using the Console to Update the License Type on a VM Cluster 4-15
Using the Console to Move a VM Cluster to Another Compartment 4-15
Using the Console to Terminate a VM cluster 4-16
Using the API for VM Clusters on Exadata Cloud@Customer 4-16
Introduction to Scale Up or Scale Down Operations 4-17
Scaling Up or Scaling Down the VM Cluster Resources 4-17
Calculating the Minimum Required Memory 4-18
Calculating the ASM Storage 4-19
Estimating How Much Local Storage You Can Provision to Your VMs 4-20
Scaling Local Storage Down 4-22
5 Managing Backup Destinations for Exadata Cloud@Customer
About Managing Backup Destinations for Exadata Cloud@Customer 5-1
Required IAM Policy for Backup Destinations 5-2
Prerequisites for Backup Destinations for Exadata Cloud@Customer 5-3
Using the Console for Backup Destinations for Exadata Cloud@Customer 5-3
Using the Console to Create a Backup Destination 5-4
Using the Console to Edit a Backup Destination 5-5
Using the Console to Move a Backup Destination to Another Compartment 5-6
Using the Console to Terminate a Backup Destination 5-7
Using the API for Backup Destinations for Exadata Cloud@Customer 5-7
6 Creating Oracle Database Homes on an Exadata Cloud@CustomerSystem
About Creating Oracle Database Homes on an Exadata Cloud@Customer System 6-1
Required IAM Policy for Creating Oracle Database Homes 6-2
Using the Console to Create Oracle Database Home on Exadata Cloud@Customer 6-2
Using the API for Creating Oracle Database Home on Exadata Cloud@Customer 6-3
v
7 Managing Oracle Database Homes on Exadata Cloud@CustomerSystems
About Managing Oracle Database Homes on Exadata Cloud@Customer Systems 7-1
Required IAM Policy for Managing Oracle Database Homes 7-2
Using the Console for Oracle Database Home on Exadata Cloud@Customer 7-2
Using the Console to View Information About an Oracle Database Home 7-2
Using the Console to Delete an Oracle Database Home 7-3
Differences Between Managing Resources with dbaascli and the Database API 7-3
Using the API for Managing Oracle Database Home on Exadata Cloud@Customer 7-4
8 Managing Oracle Databases on Oracle Exadata Cloud@Customer
Prerequisites and Limitations for Creating and Managing Oracle Databases onOracle Exadata Cloud@Customer 8-1
Oracle Database Releases Supported by Oracle Exadata Cloud@Customer 8-2
About Provisioning and Configuring Oracle Databases on Oracle ExadataCloud@Customer 8-2
Required IAM Policy for Managing Oracle Databases on Oracle ExadataCloud@Customer 8-3
Using the Console to Manage Databases on Oracle Exadata Cloud@Customer 8-4
Using the Console to Create a Database 8-4
Using the Console to Move a Database to Another Database Home 8-7
Using the Console to Terminate a Database 8-8
Using the API to Manage Database Components 8-8
9 Using Oracle Data Guard with Exadata Cloud@Customer
About Using Oracle Data Guard with Exadata Cloud@Customer 9-1
Required IAM Policy for Managing Oracle Data Guard Associations on OracleExadata Cloud@Customer 9-2
Prerequisites for Using Oracle Data Guard with Exadata Cloud@Customer 9-2
Compute Nodes 9-3
Password 9-3
Working with Data Guard 9-3
Switchover 9-4
Failover 9-4
Reinstate 9-4
Using the Console to Manage Oracle Data Guard Associations 9-4
Using the Console to Enable Data Guard on an Exadata Cloud@CustomerSystem 9-5
Using the Console To Perform a Database Switchover 9-6
Using the Console To Perform a Database Failover 9-6
vi
Using the Console To Reinstate a Database 9-7
Using the Console To Terminate a Data Guard Association on an ExadataCloud@Customer System 9-8
Using the API To Manage Data Guard Associations on an ExadataCloud@Customer System 9-8
10
Managing Database Backup and Recovery on Oracle ExadataCloud@Customer
About Managing Backup Destinations for Oracle Exadata Cloud@Customer 10-1
Required IAM Policy for Backup and Recovery 10-3
Using the Console to Manage Backup and Recovery 10-3
Viewing a List of Available Backups with the Console 10-4
Editing Backup Settings with the Console 10-4
Restoring a Database with the Console 10-6
Use the API to Manage Database Backup and Recovery 10-7
11
Connecting to an Exadata Cloud@Customer System
Connecting to a Compute Node with SSH 11-1
Prerequisites for Connecting to an Exadata Cloud@Customer System 11-1
Connecting to a Compute Node from a Microsoft Windows System Using PuTTY 11-2
Accessing a Database After You Connect to the Compute Node 11-3
Connecting from a Unix-Style System 11-4
Connecting to a Database with Oracle Net Services 11-5
Using Oracle Net Services to Connect to a Database 11-5
Prerequisites for Connecting to a Database with Oracle Net Services 11-6
Connecting to a Database Using SCAN 11-6
Connecting to a Database Using a Connect Descriptor that References Allof the SCAN VIPs 11-6
Connecting to a Database Use a Connect Descriptor that References aCustom SCAN Name 11-7
Connecting to a Database Using a Node Listener 11-8
12
Maintaining an Exadata Cloud@Customer System
User-Managed Maintenance Updates 12-1
Oracle Managed Exadata Cloud@Customer Infrastructure Maintenance Updates 12-1
Overview of the Infrastructure Patching Process 12-1
Scheduling Oracle-Managed Infrastructure Updates 12-2
Set the Automatic Maintenance Schedule for Exadata Cloud@CustomerInfrastructure 12-3
vii
View or Edit the Time of the Next Scheduled Maintenance for ExadataCloud@Customer Infrastructure 12-4
View the Maintenance History of Exadata Cloud@Customer Infrastructure 12-4
Monitoring Patching Operations Using Lifecycle State Information 12-5
Receive Notifications about Your Infrastructure Maintenance Updates 12-5
Infrastructure Maintenance Contacts 12-6
13
Patching an Exadata Cloud@Customer System
Required IAM Policy for Patching an Exadata Cloud@Customer System 13-1
About Patching VM Clusters and Database Homes 13-2
Prerequisites for Patching an Exadata Cloud@Customer System 13-3
Using the Console for Patching an Exadata Cloud@Customer System 13-3
Using the Console to Perform a Patch Operation on a VM Cluster 13-3
Using the Console to Perform a Patch Operation on a Database Home 13-4
Using the Console to View Patch History 13-5
Using the Console to View the Patch History of a VM Cluster 13-5
Using the Console to View the Patch History of a Database Home 13-5
Using the Console to Move a Database to Another Home 13-6
Using the API for Patching an Exadata Cloud@Customer System 13-7
14
Patching and Updating an Exadata Cloud@Customer SystemManually
Managing VM Clusters on Exadata Cloud@Customer 14-1
Administering Software Images 14-2
Viewing Information About Downloaded Software Images 14-3
Viewing Information About Available Software Images 14-4
Downloading a Software Image 14-4
Activating a Software Image 14-5
Deleting a Software Image 14-6
Managing Oracle Database and Oracle Grid Infrastructure Patches 14-7
About the dbaascli Utility 14-8
List Available Patches 14-8
Check Prerequisites Before Applying a Patch 14-8
Apply a Patch 14-10
List Applied Patches 14-11
Roll Back a Patch 14-12
Manually Patching Oracle Database and Oracle Grid Infrastructure Software 14-13
Updating the Compute Node Operating System 14-14
Preparing for an Operating System Update 14-14
viii
Updating the Operating System on All Compute Nodes of an Oracle ExadataCloud@Customer System 14-15
Installing Additional Operating System Packages 14-22
Cloud Tooling Updates 14-23
Checking the Installed Cloud Tooling Release for Updates 14-23
Updating the Cloud Tooling Release 14-24
15
Using Enterprise Manager Express and Database Control onExadata Cloud@Customer
About Accessing Enterprise Manager Database Express 15-1
Setting the Port for EM Express to Manage a PDB (Oracle Database 12.1 Only) 15-2
Accessing Enterprise Manager Database Express 15-2
Accessing Enterprise Manager 11g Database Control 15-3
16
Oracle Exadata Cloud@Customer Deployment Assistant
Using Oracle Exadata Cloud@Customer Deployment Assistant 16-1
Accessing Oracle Exadata Cloud@Customer Deployment Assistant 16-2
Step 1: Pre-Installation 16-2
Step 2: Onsite Installation 16-3
Step 3: Post-Installation 16-3
17
Using the dbaascli Utility on Exadata Cloud@Customer
About Using the dbaascli Utility on Exadata Cloud@Customer 17-3
dbaascli database bounce 17-4
dbaascli database changepassword 17-5
dbaascli cpuscale get_status 17-5
dbaascli cpuscale update 17-5
dbaascli database move 17-6
dbaascli database start 17-6
dbaascli database status 17-7
dbaascli database stop 17-7
dbaascli database update 17-7
dbaascli dbhome info 17-8
dbaascli dbhome purge 17-9
dbaascli dbimage list 17-9
dbaascli listener bounce 17-10
dbaascli listener start 17-10
dbaascli listener status 17-10
dbaascli listener stop 17-11
ix
dbaascli patch db apply 17-11
dbaascli patch db list 17-13
dbaascli patch db prereq 17-13
dbaascli patch db switchback 17-14
dbaascli patch tools apply 17-15
dbaascli patch tools list 17-15
dbaascli pdb checkdb 17-16
dbaascli pdb checknode 17-16
dbaascli pdb checkpdb 17-17
dbaascli pdb close 17-17
dbaascli pdb connect_info 17-18
dbaascli pdb connect_string 17-18
dbaascli pdb create 17-19
dbaascli pdb delete 17-19
dbaascli pdb info 17-20
dbaascli pdb local_clone 17-20
dbaascli pdb open 17-21
dbaascli pdb remote_clone 17-21
dbaascli pdb rename 17-22
dbaascli pdb resize 17-22
dbaascli tde rotate masterkey 17-23
dbaascli tde status 17-23
18
Monitoring and Managing Exadata Storage Servers with ExaCLI
About the ExaCLI Command 18-1
Exadata Storage Server Username and Password 18-1
ExaCLI Command 18-2
Connecting to a Storage Server with ExaCLI 18-8
19
Policy Details for Exadata Cloud@Customer
About Resource-Types 19-1
Resource-Types for Exadata Cloud@Customer 19-2
Supported Variables 19-2
Details for Verb + Resource-Type Combinations 19-2
Database-Family Resource Types 19-4
exadata-infrastructures 19-4
vmcluster-networks 19-5
vmclusters 19-6
backup-destinations 19-7
x
db-nodes 19-8
db-homes 19-9
databases 19-9
backups 19-10
autonomous-vmclusters 19-11
autonomous-container-databases 19-12
autonomous-databases 19-13
data-guard-association 19-13
key-stores 19-14
autonomousContainerDatabaseDataguardAssociations 19-15
AutonomousDatabaseDataguardAssociation 19-16
Permissions Required for Each API Operation 19-17
20
Oracle Exadata Cloud@Customer Events
Exadata Infrastructure Event Types 20-1
VM Cluster Network Event Types 20-4
VM Cluster Event Types 20-5
Backup Destination Event Types 20-7
Database Node Event Types (Cloud@Customer) 20-8
Database Home Event Types (Cloud@Customer) 20-9
Database Event Types (Cloud@Customer) 20-10
Database and Grid Infrastructure Patching Event Types 20-11
Autonomous VM Cluster Event Types 20-14
Autonomous Container Database Event Types 20-18
Autonomous Database Event Types 20-19
Data Guard Event Types 20-20
Autonomous Database Autonomous Data Guard Event Types 20-23
Key Store Event Types 20-27
Exadata Cloud@Customer Infrastructure Patching Event Types 20-28
21
Troubleshooting Exadata Cloud@Customer Systems
Patching Failures on Exadata Cloud@Customer Systems 21-1
Determining the Problem 21-1
Troubleshooting and Diagnosis 21-2
Host Issues 21-2
Oracle Grid Infrastructure Issues 21-3
Oracle Databases Issues 21-5
Oracle Cloud Tooling Issues 21-7
Obtaining Further Assistance 21-7
xi
Collecting Cloud Tooling Logs 21-7
Collecting Configuration Tools Logs 21-8
Collecting Oracle Diagnostics 21-8
Failed Patch Modifies the Home Name in oraInventory with the Suffix "_PIP" 21-9
Database is Down While Performing Downgrade to Release 11.2 or 12.1 21-9
After Database Upgrade, the Standby Database Remains in Mounted State inOracle Data Guard Configurations 21-10
Primary Database Fails to Downgrade to 18c in Oracle Data Guard Configurations 21-10
Patching Primary and Standby Databases Configured with Oracle Data Guard Fails 21-11
22
Introduction to Autonomous Database on ExadataCloud@Customer
Database System Architecture Overview 22-1
Resource Types 22-1
Deployment Order 22-2
User Roles 22-2
Available Exadata Infrastructure Hardware Shapes 22-3
Oracle Exadata Cloud@Customer X8M-2 System Specifications 22-4
Access Control Lists (ACLs) for Autonomous Databases on ExadataCloud@Customer 22-4
23
Managing Autonomous Exadata VM Clusters
Create an Autonomous Exadata VM Cluster 23-1
View a List of Autonomous Exadata VM Clusters 23-2
View Details of an Autonomous Exadata VM Cluster 23-2
Change the License Type on an Autonomous VM Cluster 23-3
Move an Autonomous Exadata VM Cluster to Another Compartment 23-3
Terminate an Autonomous Exadata VM Cluster 23-3
Using the API to Manage Autonomous Exadata VM Clusters 23-4
24
Managing Encryption Keys on External Devices
About Oracle Key Vault 24-1
Overview of Key Store 24-2
Required IAM Policy for Managing OKV on Oracle Exadata Cloud@Customer 24-2
Tagging Resources 24-3
Moving Resources to a Different Compartment 24-3
Setting Up Your Exadata Cloud@Customer to Work With Oracle Key Vault 24-3
Step 1: Create a Vault in OCI Vault Service and Add a Secret to the Vault toStore OKV REST Administrator Password 24-4
xii
Step 2: Create a Dynamic Group and a Policy Statement for Key Store toAccess Secret in OCI Vault 24-4
Step 3: Create a Dynamic Group and a Policy Statement for ExadataInfrastructure to Key Store 24-5
Step 4: Create a Policy Statement for Database Service to Use Secret from OCIVault Service 24-6
Step 5: Create Key Store 24-6
Managing Your Key Store 24-7
View Key Store Details 24-7
Edit Key Store Details 24-8
Move a Key Store to Another Compartment 24-8
Delete a Key Store 24-8
View Key Store Associated Autonomous Container Database Details 24-8
Using the API to Manage Key Store 24-9
25
Managing Autonomous Container Databases
Create an Autonomous Container Database 25-1
View a List of Autonomous Container Databases 25-3
View the List of Autonomous Container Databases in an Autonomous ExadataVM Cluster 25-3
View the List of Autonomous Container Databases in a Compartment 25-4
View Details of an Autonomous Container Database 25-4
Rotate CDB Encryption Key 25-4
Change the Backup Retention Policy of an Autonomous Container Database 25-5
Change the Maintenance Schedule of an Autonomous Container Database 25-6
Restart an Autonomous Container Database 25-6
Move an Autonomous Container Database to Another Compartment 25-7
Terminate an Autonomous Container Database 25-7
Using the API to Manage Autonomous Container Databases 25-8
26
Managing Autonomous Databases
Create an Autonomous Database 26-1
Manage Access Control List of an Autonomous Database 26-3
View a List of Autonomous Databases 26-4
View Details of an Autonomous Database 26-5
Rotate ADB Encryption Key 26-5
Set the Password of an Autonomous Database's ADMIN User 26-6
Scale the CPU Core Count or Storage of an Autonomous Database 26-6
Enable or Disable Auto Scaling for an Autonomous Database 26-7
Move an Autonomous Database to Another Compartment 26-7
xiii
Stop or Start an Autonomous Database 26-8
Restart an Autonomous Database 26-9
Back Up an Autonomous Database Manually 26-9
Restore an Autonomous Database 26-10
Restore from a Backup 26-10
Restore to a Point in Time 26-10
Clone an Autonomous Database 26-11
Terminate an Autonomous Database 26-13
Using the API to Manage Autonomous Databases 26-13
Monitor Performance with Autonomous Database Metrics 26-14
View Top Six Metrics for an Autonomous Database 26-14
View Aggregated Metrics for Autonomous Databases in a Compartment 26-15
Autonomous Database Metrics and Dimensions 26-16
27
Connecting to Autonomous Databases
Download the Wallet for an Autonomous Database 27-1
Get the APEX and SQL Developer Web URLs for an Autonomous Database 27-3
28
Using Autonomous Data Guard with Autonomous Database onExadata Cloud@Customer
Enabling Autonomous Data Guard on an Autonomous Container Database 28-1
Create an Autonomous Data Guard Enabled Autonomous Container Database 28-2
View Details of a Data Guard Enabled Primary or Standby AutonomousContainer Database 28-4
Perform a Failover to Standby Autonomous Container Database 28-4
Perform a Switchover to Standby or Primary Autonomous Container Database 28-5
Reinstate Data Guard Enabled Standby Autonomous Container Database 28-5
Terminate a Data Guard Enabled Primary Autonomous Container Database 28-6
Terminate a Data Guard Enabled Standby Autonomous Container Database 28-6
Operations Performed Using the APIs 28-7
Enabling Autonomous Data Guard on an Autonomous Database 28-8
View Autonomous Data Guard Enablement 28-8
Create an Autonomous Data Guard Enabled Autonomous Database 28-8
View Details of a Data Guard Enabled Primary or Standby AutonomousDatabase 28-10
Maintenance Scheduling and Patching Data Guard Enabled Autonomous ContainerDatabase 28-11
Configure Automatic Maintenance Schedule for a Data Guard EnabledAutonomous Container Database 28-11
View the Next Scheduled Maintenance Run of a Data Guard EnabledAutonomous Container Database 28-12
xiv
View the Maintenance History of a Data Guard Enabled Autonomous ContainerDatabase 28-13
Immediately Patch a Data Guard Enabled Autonomous Container Database 28-13
Reschedule or Skip scheduled Maintenance for Data Guard EnabledAutonomous Container Database 28-14
29
Using Performance Hub to Analyze Database Performance
Performance Hub Features 29-1
Time Range Selector 29-2
Time Zone Selector 29-3
ASH Analytics Tab 29-3
SQL Monitoring Tab 29-3
Blocking Sessions Tab 29-4
Using the Oracle Cloud Infrastructure Console 29-4
Navigate to Performance Hub in the Oracle Cloud Infrastructure ConsoleInterface of an Autonomous Database 29-4
View the Average Active Sessions Data by a Selected Dimension 29-5
Filter Average Active sessions Data 29-6
View the SQL Monitoring Report 29-6
View the Blocking and Waiting Sessions 29-7
Setting the Minimum Wait Time 29-8
Killing a Session 29-8
Displaying Lock Details 29-8
Displaying Wait Event Information 29-9
Displaying Session Details 29-9
Displaying SQL Details 29-9
Index
xv
What’s New in Oracle ExadataCloud@Customer Gen2
Oracle is constantly adding new capabilities to Oracle Exadata Cloud@Customer andADB-D on Oracle Exadata Cloud@Customer. This preface provides a brief overviewof all new features as they are released.
• What’s New in Oracle Exadata Cloud@Customer
• What’s New in ADB-D on Oracle Exadata Cloud@Customer
What’s New in Oracle Exadata Cloud@Customer• Exadata Cloud@Customer Infrastructure Patching Automation
• Customer Maintenance Contacts
• X8M-2 System Support
• Enable and Manage Data Guard Associations
• Oracle Exadata Cloud@Customer Deployment Assistant
• Oracle Grid Infrastructure and Oracle Database Patching
• Per-Second Billing for OCPU Usage
• Shared Database Home Resource Tags
• Create and Manage Multiple Virtual Machines per Exadata System (MultiVM)
• Scale OCPUs Without Cloud Connectivity
• Configure Oracle Database Character Set and National Character Set
• Specify a Time Zone While Provisioning Oracle Exadata Cloud@CustomerInfrastructure
• Shared Database Homes for Oracle Exadata Cloud@Customer
• X7-2 System Support
Exadata Cloud@Customer Infrastructure Patching Automation
• Services: Database
• Release Date: December 08, 2020
You can now schedule a maintenance window for Oracle-managed ExadataCloud@Customer infrastructure patching. For more information, see Maintaining anExadata Cloud@Customer System.
What’s New in Oracle Exadata Cloud@Customer Gen2
xvi
Related Topics
• Maintaining an Exadata Cloud@Customer SystemLearn how to perform patching operations on Exadata Cloud@Customerinfrastructure.
Customer Maintenance Contacts
• Services: Database
• Release Date: September 22, 2020
• Release Notes: Exadata Cloud@Customer: Customer Maintenance Contacts
X8M-2 System Support
• Services: Database
• Release Date: August 18, 2020
• Release Notes: Exadata Cloud@Customer: X8M-2 System Support
Enable and Manage Data Guard Associations
• Services: Database
• Release Date: August 18, 2020
• Release Notes: Exadata Cloud@Customer: Enable and Manage Data GuardAssociations
Oracle Exadata Cloud@Customer Deployment Assistant
• Services: Database
• Release Date: August 08, 2020
• Release Notes: Exadata Cloud@Customer: Deployment Assistant
Oracle Grid Infrastructure and Oracle Database Patching
• Services: Database
• Release Date: July 28, 2020
• Release Notes: Exadata Cloud@Customer: Oracle Grid Infrastructure and OracleDatabase Patching
Per-Second Billing for OCPU Usage
• Services: Database
• Release Date: July 14, 2020
• Release Notes: Exadata Cloud@Customer: Per-Second Billing for OCPU Usage
What’s New in Oracle Exadata Cloud@Customer Gen2
xvii
Shared Database Home Resource Tags
• Services: Database
• Release Date: June 23, 2020
• Release Notes: Exadata Cloud@Customer: Shared Database Home ResourceTags
Create and Manage Multiple Virtual Machines per Exadata System(MultiVM)
• Services: Database
• Release Date: June 13, 2020
• Release Notes: Exadata Cloud@Customer: Create and Manage Multiple VirtualMachines per Exadata System (MultiVM)
Scale OCPUs Without Cloud Connectivity
• Services: Database
• Release Date: June 13, 2020
• Release Notes: Exadata Cloud@Customer: Scale OCPUs Without CloudConnectivity
Configure Oracle Database Character Set and National Character Set
• Services: Database
• Release Date: May 7, 2020
• Release Notes: Exadata Cloud@Customer: Configure Oracle DatabaseCharacter Set and National Character Set
Specify a Time Zone While Provisioning Oracle ExadataCloud@Customer Infrastructure
• Services: Database
• Release Date: May 7, 2020
• Release Notes: Exadata Cloud@Customer: Specify a Time Zone WhileProvisioning Oracle Exadata Cloud@Customer Infrastructure
Shared Database Homes for Oracle Exadata Cloud@Customer
• Services: Database
What’s New in Oracle Exadata Cloud@Customer Gen2
xviii
• Release Date: March 31, 2020
• Release Notes: Exadata Cloud@Customer: Shared Database Homes
X7-2 System Support
• Services: Database
• Release Date: March 19, 2020
• Release Notes: Exadata Cloud@Customer: X7-2 System Support
What’s New in ADB-D on Oracle Exadata Cloud@Customer• Access Control List (ACL) to Restrict Access to Autonomous Data Guard Enabled
Autonomous Databases
• ADB-D on Exadata Cloud@Customer: Monitor Performance with AutonomousDatabase Metrics
• ADB-D on Exadata Cloud@Customer: Autonomous Data Guard
• Access Control List (ACL) to Restrict Access to Autonomous Databases
• Oracle Key Vault (OKV) Integration
• X8M-2 System Support
• Per-Second Billing for Autonomous Database OCPU Usage
• Oracle Autonomous Database on Oracle Exadata Cloud@Customer
Access Control List (ACL) to Restrict Access to Autonomous DataGuard Enabled Autonomous Databases
• Services: Database
• Release Date: January 26, 2021
An access control list (ACL) provides additional protection to your database byallowing only the clients with specific IP addresses to connect to the database. Youcan add IP addresses individually, or in CIDR blocks.
Related Topics
• Create an Autonomous Data Guard Enabled Autonomous Database
• Manage Access Control List of an Autonomous Database
ADB-D on Exadata Cloud@Customer: Monitor Performance withAutonomous Database Metrics
• Services: Database
• Release Date: December 15, 2020
What’s New in Oracle Exadata Cloud@Customer Gen2
xix
You can monitor the health, capacity, and performance of your AutonomousDatabases with metrics, alarms, and notifications. You can use Oracle CloudInfrastructure console or Monitoring APIs to view metrics.
Related Topics
• Monitor Performance with Autonomous Database Metrics
ADB-D on Exadata Cloud@Customer: Autonomous Data Guard
• Services: Database
• Release Date: November 17, 2020
Enabling Autonomous Data Guard on an Autonomous Container Database ondedicated Exadata infrastructure creates a standby (peer) Autonomous ContainerDatabase that provides data protection, high availability, and facilitates disasterrecovery for the primary database.
Related Topics
• Using Autonomous Data Guard with Autonomous Database on ExadataCloud@CustomerLearn how to enable a Data Guard association between databases, change therole of a database in a Data Guard association using either a switchover or afailover operation, and reinstate a failed database.
Access Control List (ACL) to Restrict Access to AutonomousDatabases
• Services: Database
• Release Date: November 10, 2020
An access control list (ACL) provides additional protection to your database byallowing only the clients with specific IP addresses to connect to the database. Youcan add IP addresses individually, or in CIDR blocks.
Related Topics
• Access Control Lists (ACLs) for Autonomous Databases on ExadataCloud@Customer
• Create an Autonomous Database
• Manage Access Control List of an Autonomous Database
• Clone an Autonomous Database
Oracle Key Vault (OKV) Integration
• Services: Database
• Release Date: October 27, 2020
Integrate your on-premises Oracle Key Vault (OKV) with Autonomous Database onExadata Cloud@Customer to secure your critical data on-premises.
What’s New in Oracle Exadata Cloud@Customer Gen2
xx
Oracle Key Vault integration enables you to take complete control of your encryptionkeys and store them securely on an external, centralized key management device.
Related Topics
• Managing Encryption Keys on External Devices
X8M-2 System Support
• Services: Database
• Release Date: September 25, 2020
• Release Notes: ADB-D on Exadata Cloud@Customer: X8M-2 System Support
Per-Second Billing for Autonomous Database OCPU Usage
• Services: Database
• Release Date: July 21, 2020
• Release Notes: Exadata Cloud@Customer: Per-Second Billing for AutonomousDatabase OCPU Usage
Oracle Autonomous Database on Oracle Exadata Cloud@Customer
• Services: Database
• Release Date: June 23, 2020
• Release Notes: Exadata Cloud@Customer: Oracle Autonomous Database
What’s New in Oracle Exadata Cloud@Customer Gen2
xxi
1Introduction to Oracle ExadataCloud@Customer
Learn how you can leverage the combined capabilities of Oracle Exadata and OracleCloud Infrastructure with Oracle Exadata Cloud@Customer
Oracle Autonomous Database on Oracle Exadata Cloud@Customer combines thebenefits of a self-driving, self-securing, and self-repairing database managementsystem and the security and control offered by having it deployed securely on premisebehind your firewall.
• About Oracle Exadata Cloud@CustomerWith Oracle Exadata Cloud@Customer, you can maintain absolute control overyour data while leveraging the combined capabilities of Oracle Exadata and OracleCloud Infrastructure managed by Oracle.
• Per-Second Billing for OCPU Usage
• Per-Second Billing for Autonomous Database OCPU Usage
• System Configuration Options for Oracle Exadata Cloud@CustomerTo meet the needs of your enterprise, you can select from one of four OracleExadata X8M-2 systems, Oracle Exadata X8-2 systems, or Oracle Exadata X7-2systems.
• Oracle Exadata Cloud@Customer X8M-2 System SpecificationsReview the technical specifications for each system configuration option for OracleExadata Cloud@Customer.
• Oracle Exadata Cloud@Customer X8-2 System SpecificationsReview the technical specifications for each system configuration option for OracleExadata Cloud@Customer.
• Oracle Exadata Cloud@Customer X7-2 System SpecificationsReview the technical specifications for each system configuration option for OracleExadata Cloud@Customer.
• Plan Your Configuration Settings on StorageThe proportions that you select for your DATA, RECO, and SPARSE disk groupsprofoundly affect your storage space. Review the best options for your enterpriseneeds.
• Moving to Oracle Cloud Using Zero Downtime Migration
About Oracle Exadata Cloud@CustomerWith Oracle Exadata Cloud@Customer, you can maintain absolute control over yourdata while leveraging the combined capabilities of Oracle Exadata and Oracle CloudInfrastructure managed by Oracle.
Oracle Exadata Cloud@Customer enables you to apply the combined power of OracleExadata and Oracle Cloud Infrastructure inside your own data center. You have fullaccess to the features and capabilities of Oracle Database along with the intelligent
1-1
performance and scalability of Oracle Exadata, but with Oracle owning and managingthe Exadata infrastructure. You can use the Oracle Cloud Infrastructure console andAPIs to manage Oracle Exadata Cloud@Customer just as with any other cloudresource, while maintaining absolute sovereignty over your data.
Each Oracle Exadata Cloud@Customer system configuration contains compute nodes(database servers) and Oracle Exadata Storage Servers that are interconnected usinga high-speed, low-latency InfiniBand network, and intelligent Oracle Exadata software.Each configuration is equipped with a fixed amount of memory, storage, and networkresources.
Oracle Exadata Cloud@Customer uses virtual machine (VM) technology to separatethe customer-managed and components managed by Oracle on each compute node.You have root privilege for the Oracle Exadata compute node VMs, so you canmanage the Oracle Database, Oracle Grid Infrastructure, and Oracle Exadata systemsoftware. However, you do not have administrative access to the physical computenode hardware, which Oracle administers.
Oracle Exadata Cloud@Customer uses Oracle Exadata Storage Servers for databasestorage. The storage is allocated to disk groups managed by Oracle AutomaticStorage Management (Oracle ASM). You have full administrative access to theOracle ASM disk groups, but Oracle administers the Oracle Exadata Storage Serverhardware and software.
In addition to the compute node hardware and Oracle Exadata Storage Servers,Oracle also manages other Oracle Exadata Cloud@Customer infrastructurecomponents, including the network switches, power distribution units (PDUs), andintegrated lights-out management (ILOM) interfaces.
Subscription to Oracle Exadata Cloud@Customer can include all of the requiredOracle Database software licenses, or you can choose to bring Oracle Databasesoftware licenses that you already own to Oracle Exadata Cloud@Customer. Ifyou choose to include Oracle Database software licenses in your Oracle ExadataCloud@Customer subscription, then the included licenses contain all of the features ofOracle Database Enterprise Edition, plus all of the database enterprise managementpacks, and all of the Enterprise Edition options, such as Oracle Database In-Memoryand Oracle Real Application Clusters (Oracle RAC). Exadata Cloud@Customer alsocomes with cloud-specific software tools that assist with administration tasks, such asbackup, recovery, and patching.
On each Oracle Exadata Cloud@Customer system, you can create one or moredatabases. Apart from the inherent storage and processing capacity of your OracleExadata system, there is no set maximum for the number of databases that you cancreate.
Per-Second Billing for OCPU UsageExadata Cloud@Customer Gen2 uses per-second billing for OCPUs. This means thatOCPU usage is billed by the second, with a minimum usage period of 1 minute.
Per-Second Billing for Autonomous Database OCPU UsageExadata Cloud@Customer Gen2 uses per-second billing for OCPUs. This means thatOCPU usage is billed by the second, with a minimum usage period of 1 minute.
Chapter 1Per-Second Billing for OCPU Usage
1-2
System Configuration Options for Oracle ExadataCloud@Customer
To meet the needs of your enterprise, you can select from one of four Oracle ExadataX8M-2 systems, Oracle Exadata X8-2 systems, or Oracle Exadata X7-2 systems.
Exadata Cloud@Customer is offered in the following system configurations:
• Base System: Contains two compute nodes and three Oracle Exadata StorageServers. A Base System is an entry-level configuration. Compared to otherconfigurations, a Base System contains Oracle Exadata Storage Servers withsignificantly less storage capacity, and compute nodes with significantly lessmemory and processing power.
• Quarter Rack: Contains two compute nodes and three Oracle Exadata StorageServers.
• Half Rack: Contains four compute nodes and six Oracle Exadata Storage Servers.
• Full Rack: Contains eight compute nodes and 12 Oracle Exadata Storage Servers.
Each system configuration is equipped with a fixed amount of memory, storage, andnetwork resources. All system configurations are based on Oracle Exadata X8M-2,X8-2, or X7-2 systems.
Oracle Exadata Cloud@Customer X8M-2 SystemSpecifications
Review the technical specifications for each system configuration option for OracleExadata Cloud@Customer.
Table 1-1 Oracle Exadata Cloud@Customer X8M-2 System Specifications
Property Base Rack Quarter Rack Half Rack Full Rack
Number ofCompute Nodes
2 2 4 8
Total MaximumNumber ofEnabled CPUCores
48 100 200 400
Total RAMCapacity
656 GB 2780 GB 5560 GB 11120 GB
PersistentMemory
0 4.6 TB 9.2 TB 18.4 TB
Number ofExadata StorageServers
3 3 6 12
Total Raw FlashStorage Capacity
38.4 TB 76.8 TB 153.6 TB 307.2 TB
Total UsableStorageCapacity**
74 TB 149 TB 299 TB 598 TB
Chapter 1System Configuration Options for Oracle Exadata Cloud@Customer
1-3
Table 1-1 (Cont.) Oracle Exadata Cloud@Customer X8M-2 SystemSpecifications
Property Base Rack Quarter Rack Half Rack Full Rack
Max number ofVMs
4 8 8 8
** TB=1024^4
Oracle Exadata Cloud@Customer X8-2 SystemSpecifications
Review the technical specifications for each system configuration option for OracleExadata Cloud@Customer.
Table 1-2 Oracle Exadata Cloud@Customer X8-2 System Specifications
Property Base System Quarter Rack Half Rack Full Rack
Number ofCompute Nodes
2 2 4 8
Total MaximumNumber ofEnabled CPUCores
48 100 200 400
Total RAMCapacity
720 GB 1440 GB 2880 GB 5760 GB
Number ofExadata StorageServers
3 3 6 12
Total Raw FlashStorage Capacity
38.4 TB 76.8 TB 153.6 TB 307.2 TB
Total Raw DiskStorage Capacity
252 TB 504 TB 1008 TB 2016 TB
Total UsableStorage Capacity
74.8 TB 149.7 TB 299.4 TB 598.7 TB
MaximumNumber of VMs
5 5 5 5
Oracle Exadata Cloud@Customer X7-2 SystemSpecifications
Review the technical specifications for each system configuration option for OracleExadata Cloud@Customer.
Chapter 1Oracle Exadata Cloud@Customer X8-2 System Specifications
1-4
Table 1-3 Oracle Exadata Cloud@Customer X7-2 System Specifications
Property Base System Quarter Rack Half Rack Full Rack
Number ofCompute Nodes
2 2 4 8
Total MaximumNumber ofEnabled CPUCores
44 92 184 368
Total RAMCapacity
480 GB 1440 GB 2880 GB 5760 GB
Number ofExadata StorageServers
3 3 6 12
Total Raw FlashStorage Capacity
19.2 TB 76.8 TB 153.6 TB 307.2 TB
Total Raw DiskStorage Capacity
144 TB 360 TB 720 TB 1440 TB
Total UsableStorage Capacity
42.7 TB 106.9 TB 213.8 TB 427.6 TB
MaximumNumber of VMs
6 6 6 6
Plan Your Configuration Settings on StorageThe proportions that you select for your DATA, RECO, and SPARSE disk groups profoundlyaffect your storage space. Review the best options for your enterprise needs.
• About Storage Configuration for Oracle Exadata Cloud@CustomerAs part of configuring each Exadata Cloud@Customer VM cluster, the storagespace inside the Exadata Storage Servers is configured for use by OracleAutomatic Storage Management (ASM).
• Allocation of Storage Space Options on Oracle Exadata Storage ServersSelect the storage option that best meets your planned use case on your OracleExadata Storage Servers.
• Allocation Proportions for DATA, RECO and SPARSE Disk GroupsDetermine the storage allocation between the DATA, RECO, and SPARSE disk groupsfor Oracle Exadata Storage Servers.
About Storage Configuration for Oracle Exadata Cloud@CustomerAs part of configuring each Exadata Cloud@Customer VM cluster, the storage spaceinside the Exadata Storage Servers is configured for use by Oracle Automatic StorageManagement (ASM).
By default, the following ASM disk groups are created:
• The DATA disk group is primarily intended for the storage of Oracle Databasedata files. Also, a small amount of space is allocated from the DATA disk groupto support the shared file systems that are used to store software binaries (andpatches) and files associated with the cloud-specific tooling. You should not store
Chapter 1Plan Your Configuration Settings on Storage
1-5
your own data, including Oracle Database data files, backups, trace files, and soon, inside the system-related ACFS file systems.
• The RECO disk group is primarily used for storing the Fast Recovery Area (FRA),which can be used to provide a local store for files related to backup and recovery.By default, the FRA is used to store archived redo log files and the backup controlfile. If you configure your VM cluster with the option to allocate storage for localbackups, then you can use the FRA as a database backup destination. Finally, ifyou enable flashback features on a database, then the FRA is used to store theflashback logs.
In addition, you can choose to create the SPARSE disk group. The SPARSE disk group isrequired to support Exadata snapshot functionality. Exadata snapshots enable space-efficient clones of Oracle databases that can be created and destroyed very quicklyand easily. Snapshot clones are often used for development, testing, or other purposesthat require a transient database. For more information about Exadata snapshotfunctionality, see "Setting Up Oracle Exadata Storage Snapshots" in Oracle ExadataSystem Software User's Guide.
Related Topics
• Setting Up Oracle Exadata Storage Snapshots
Allocation of Storage Space Options on Oracle Exadata StorageServers
Select the storage option that best meets your planned use case on your OracleExadata Storage Servers.
As an input to the virtual machine (VM) cluster creation process, you must chooseoptions that determine how storage space in the Oracle Exadata Storage Servers isallocated to the Oracle ASM disk groups. Your choices profoundly affect how storagespace in the Exadata Storage Servers is allocated to the ASM disk groups. Considerwhich option best meets your needs:
• Allocate Storage for Exadata Snapshots
If you select this option, then the SPARSE disk group is created, and less spaceis allocated to the DATA and RECO disk groups. If you do not select this option,then the SPARSE disk group is not created, and you cannot use Exadata snapshotfunctionality.
• Allocate Storage for Local Backups
If you select this option, then more space is allocated to the RECO disk group toaccommodate local backups to Oracle Exadata storage. If you do not select thisoption, then more space is allocated to the DATA disk group, but you cannot uselocal Oracle Exadata storage as a backup destination for any databases in the VMcluster.
Chapter 1Plan Your Configuration Settings on Storage
1-6
Allocation Proportions for DATA, RECO and SPARSE Disk GroupsDetermine the storage allocation between the DATA, RECO, and SPARSE disk groups forOracle Exadata Storage Servers.
Exadata Storage Server Configuration Allocation With No Exadata SnapshotStorage or Local Backup
When you select Allocate Storage for Exadata Snapshots: No and EnableBackups on Local Exadata Storage: No, then storage allocation is as follows:
• DATA Disk Group: 80%
• RECO Disk Group: 20%
• SPARSE Disk Group 0% (The SPARSE disk group is not created.)
Exadata Storage Server Configuration Allocation With No Exadata SnapshotStorage and Local Backup Enabled
When you select Allocate Storage for Exadata Snapshots: No and EnableBackups on Local Exadata Storage: Yes, so that backups are enabled on localstorage, then storage allocation is as follows:
• DATA Disk Group: 40%
• RECO Disk Group: 60%
• SPARSE Disk Group 0% (The SPARSE disk group is not created.)
Exadata Storage Server Configuration Allocation With Exadata SnapshotStorage and No Local Backup
When you select Allocate Storage for Exadata Snapshots: Yes and EnableBackups on Local Exadata Storage: No, so that storage is allocated for Exadatasnapshots, then storage allocation is as follows:
• DATA Disk Group: 60%
• RECO Disk Group: 20%
• SPARSE Disk Group 20%
Exadata Storage Server Configuration Allocation With Both Exadata SnapshotStorage and Local Backup Enabled
When you select Allocate Storage for Exadata Snapshots: Yes and EnableBackups on Local Exadata Storage: Yes, so that storage is allocated for Exadatasnapshots, and storage is allocated for local backups, then storage allocation is asfollows:
• DATA Disk Group: 35%
• RECO Disk Group: 50%
• SPARSE Disk Group 15%
Moving to Oracle Cloud Using Zero Downtime Migration
Chapter 1Moving to Oracle Cloud Using Zero Downtime Migration
1-7
Oracle now offers the Zero Downtime Migration service, a quick and easy way to moveon-premises databases and Oracle Cloud Infrastructure Classic databases to OracleCloud Infrastructure. You can migrate databases to the following types of Oracle CloudInfrastructure systems: Exadata, Exadata Cloud@Customer, bare metal, and virtualmachine.
Zero Downtime Migration leverages Oracle Active Data Guard to create a standbyinstance of your database in an Oracle Cloud Infrastructure system. You switch overonly when you are ready, and your source database remains available as a standby.Use the Zero Downtime Migration service to migrate databases individually or atthe fleet level. See Move to Oracle Cloud Using Zero Downtime Migration for moreinformation.
Related Topics
• Move to Oracle Cloud Using Zero Downtime Migration
Chapter 1Moving to Oracle Cloud Using Zero Downtime Migration
1-8
2Preparing for Exadata Cloud@Customer
Review the site and network requirements, and the checklists to prepare and deployExadata Cloud@Customer in a customer data center.
• Site Requirements for Oracle Exadata Cloud@CustomerReview the requirements for provisioning Oracle Exadata Cloud@Customer atyour site.
• Network Requirements for Oracle Exadata Cloud@CustomerReview the network requirements for provisioning Oracle ExadataCloud@Customer at your site.
• IP Addresses and Subnets for Exadata Cloud@CustomerYou must allocate a range of IP addresses to the administration network, andanother range of IP addresses to the InfiniBand network.
• Uplinks for Exadata Cloud@CustomerEnsure that your Exadata Cloud@Customer system meets control plane serverand compute node uplink requirements.
• Network Cabling for Exadata Cloud@CustomerYou can choose to use the supplied network equipment, or you can build your ownSFP network.
• Checklists for Exadata Cloud@Customer DeploymentsTo determine your readiness for an Exadata Cloud@Customer deployment, reviewthe deployment checklists.
Site Requirements for Oracle Exadata Cloud@CustomerReview the requirements for provisioning Oracle Exadata Cloud@Customer at yoursite.
• Space Requirements for Oracle Exadata Cloud@CustomerReview the space requirements for each Exadata Cloud@Customer X8 rack.
• Weight of Oracle Exadata Cloud X8 RacksReview and prepare to manage the weight of each Exadata Cloud@Customer X8rack.
• Receiving, Unpacking, and Access for Oracle Exadata Cloud@Customer RacksReview and prepare the receiving area that is large enough for the Exadata Rackpackage.
• Flooring for Oracle Exadata Cloud@Customer RacksEnsure that the Exadata Cloud@Customer system is installed on raised flooringthat is capable of supporting the Exadata Rack.
• Electrical Power for Oracle Exadata Cloud@Customer RacksExadata Cloud@Customer can operate effectively over a wide range of voltagesand frequencies.
2-1
• Temperature and Humidity Ranges for Oracle Exadata Cloud@CustomerExcessive internal temperatures can result in full or partial shutdown of ExadataCloud@Customer system components.
• Ventilation for Oracle Exadata Cloud@Customer RacksAlways provide adequate space in front and behind the rack for proper ventilation.
Space Requirements for Oracle Exadata Cloud@CustomerReview the space requirements for each Exadata Cloud@Customer X8 rack.
Table 2-1 Space Requirements for Oracle Exadata
Description Millimeters (mm) Inches (”)
Height 2000 mm 78.74”
Width 601 mm 23.66”
Depth 1197 mm 47.13”
Weight of Oracle Exadata Cloud X8 RacksReview and prepare to manage the weight of each Exadata Cloud@Customer X8rack.
Model (X8) Kilograms (kg) Pounds (lbs)
Base System 435.9 kg 961.1 lbs
Quarter Rack 449.0 kg 989.8 lbs
Half Rack 591.5 kg 1304.1 lbs
Full Rack 883.9 kg 1948.7 lbs
Receiving, Unpacking, and Access for Oracle ExadataCloud@Customer Racks
Review and prepare the receiving area that is large enough for the Exadata Rackpackage.
Description Millimeters (mm) Inches (”)
Shipping Height 2159 mm 85 inches
Shipping Width 1219 mm 48 inches
Shipping Depth 1575 mm 62 inches
If your loading dock meets the height and ramp requirements for a standard freightcarrier truck, then you can use a pallet jack to unload the rack. If the loading dock doesnot meet the requirements, then you must provide a standard forklift, or other meansto unload the rack. You can also request that the rack is shipped in a truck with a liftgate.
Use a conditioned space to remove the packaging material to reduce particles beforeentering the data center. Allow enough space for unpacking it from its shippingcartons.
Chapter 2Site Requirements for Oracle Exadata Cloud@Customer
2-2
Use the information in the following table to ensure that there is a clear pathwayfor moving the Exadata Cloud@Customer rack. Also, the entire access route to theinstallation site should be free of raised-pattern flooring that can cause vibration.
Access Route Item With Shipping Pallet Without Shipping Pallet
Minimum door height 2184 mm (86 inches) 2040 mm (80.32 inches)
Minimum door width 1270 (50 inches) 640 mm (25.19 inches)
Minimum elevator depth 1625.6 mm (64 inches) 1240 mm (48.82 inches)
Maximum incline 6 degrees 6 degrees
Minimum elevator, pallet jack,and floor loading capacity
1134 kg (2500 lbs) 1134 kg (2500 lbs)
Flooring for Oracle Exadata Cloud@Customer RacksEnsure that the Exadata Cloud@Customer system is installed on raised flooring that iscapable of supporting the Exadata Rack.
The site floor and the raised flooring must be able to support the total weight ofthe Exadata Cloud@Customer rack that you have selected. Review specificationsaccordingly.
Electrical Power for Oracle Exadata Cloud@Customer RacksExadata Cloud@Customer can operate effectively over a wide range of voltages andfrequencies.
Reliability of Power Sources
Each rack must have a reliable power source. Damage can occur if the voltage rangesare exceeded. Electrical disturbances such as the following can damage ExadataCloud@Customer:
• Fluctuations caused by brownouts
• Wide and rapid variations in input voltage levels or in input power frequency
• Electrical storms
• Faults in the distribution system, such as defective wiring
To protect Exadata Cloud@Customer from such disturbances, you should have adedicated power distribution system, power-conditioning equipment, and lightningarresters or power cables to protect from electrical storms.
Power Distribution Unit Specifications
Each rack has two pre-installed power distribution units (PDUs). The PDUs acceptdifferent power sources. You must choose the type of PDU that is correct for your datacenter and the Exadata Cloud@Customer rack.
Model (X8) Minimum PDU Rating (kVA)
Base System 15 kVA
Quarter Rack 15 kVA
Half Rack 15 kVA
Chapter 2Site Requirements for Oracle Exadata Cloud@Customer
2-3
Model (X8) Minimum PDU Rating (kVA)
Full Rack 22 kVA
The following list outlines the available PDUs for Exadata Cloud@Customer,depending on your region. Follow each of the links to access detailed specifications foreach PDU type:
• Americas, Japan, and Taiwan
– Low-Voltage 15 kVA Single-Phase
– Low-Voltage 15 kVA Three-Phase
– Low-Voltage 22 kVA Single-Phase
– Low-Voltage 24 kVA Three-Phase
• Europe, the Middle East and Africa (EMEA), and Asia Pacific (APAC), except forJapan and Taiwan
– High-Voltage 15 kVA Three-Phase
– High-Voltage 22 kVA Single-Phase
– High-Voltage 24 kVA Three-Phase
Facility Power Requirements
To prevent catastrophic failures, design the input power sources to ensure thatadequate power is provided to the PDUs.
Use dedicated AC breaker panels for all power circuits that supply power to the PDU.When planning for power distribution requirements, balance the power load betweenavailable AC supply branch circuits. In the United States of America and Canada,ensure that the overall system AC input current load does not exceed 80 percent ofthe branch circuit AC current rating.
Note:
Electrical work and installations must comply with applicable local, state, ornational electrical codes.
PDU power cords are 4 meters (13.12 feet) long, and 1–1.5 meters (3.3–4.9feet) of the cord is routed within the rack cabinet. The installation site ACpower receptacle must be within 2 meters (6.6 feet) of the rack.
Circuit Breaker Requirements
If computer equipment is subjected to repeated power interruptions and fluctuations,then it is susceptible to a higher rate of component failure.
You are responsible for supplying the circuit breakers. One circuit breaker is requiredfor each power cord. In addition to circuit breakers, provide a stable power source,such as an uninterruptible power supply (UPS) to reduce the possibility of componentfailures.
Chapter 2Site Requirements for Oracle Exadata Cloud@Customer
2-4
Use dedicated AC breaker panels for all power circuits that supply power to the server.Servers require grounded electrical circuits.
Note:
Electrical work and installations must comply with applicable local, state, ornational electrical codes.
Electrical Grounding Guidelines
The cabinets for Oracle Exadata Rack are shipped with grounding-type power cords.
• Always connect the cords to grounded power outlets.
• Check the grounding type, because different grounding methods can be used,depending on your location.
• Refer to documentation such as IEC documents for the correct grounding method.
• Ensure that the facility administrator or qualified electrical engineer verifies thegrounding method for the building, and performs the grounding work.
Temperature and Humidity Ranges for Oracle ExadataCloud@Customer
Excessive internal temperatures can result in full or partial shutdown of ExadataCloud@Customer system components.
Temperature and Humidity Ranges
Note:
Studies have shown that temperature increases of 10 degrees Celsius (15degrees Fahrenheit) above 20 degrees Celsius (70 degrees Fahrenheit)reduce long-term electronics reliability by 50 percent.
Condition OperatingRequirement
Non-operatingRequirement
OptimalRequirement
Temperature 5–32 degrees Celsius(59–89.6 degreesFahrenheit)
-40–70 degreesCelsius (-40–158degrees Fahrenheit)
21–23 degreesCelsius (70–74degrees Fahrenheit)
Relative Humidity 10–90 percentrelative humidity, non-condensing
Up to 93 percentrelative humidity
45–50 percent, non-condensing
Altitude 3048 meters (10000feet) maximum
12,000 meters (40000feet) maximum
Maximum ambienttemperature isreduced by 1 degreeCelsius for every 300meters of altitude over900 meters above sealevel.
Chapter 2Site Requirements for Oracle Exadata Cloud@Customer
2-5
Temperature and Humidity Guidelines
To minimize the chance of downtime because of component failure, setconditions to the optimal temperature and humidity ranges. Maintaining an ExadataCloud@Customer system for extended periods at or near the operating limits cansignificantly increase the potential for hardware component failure.
The ambient temperature range of 21–23 degrees Celsius (70–74 degrees Fahrenheit)is optimal for server reliability and operator comfort. Most computer equipmentcan operate in a wide temperature range, but near 22 degrees Celsius (72degrees Fahrenheit) is desirable because it is easier to maintain safe humiditylevels. Operating in this temperature range provides a safety buffer in case the airconditioning system fails for some time.
The ambient relative humidity range of 45–50 percent is suitable for safe dataprocessing operations. Most computer equipment can operate in a wide range (20–80percent), but the range of 45–50 percent is recommended for the following reasons:
• The optimal range helps protect computer systems from corrosion problemsassociated with high humidity levels..
• The optimal range provides the greatest operating time buffer in case the airconditioning system fails for some time.
• The optimal range avoids failures or temporary malfunctions caused byinterference from static discharges that can occur when relative humidity is toolow. Electrostatic discharge (ESD) is easily generated, and hard to dissipate inareas of low relative humidity, such as below 35 percent. ESD becomes criticalwhen humidity drops below 30 percent
Ventilation for Oracle Exadata Cloud@Customer RacksAlways provide adequate space in front and behind the rack for proper ventilation.
Do not obstruct the front or rear of the rack with equipment or objects that mightprevent air from flowing through the rack. Each Exadata Cloud@Customer rack drawscool air in through the front of the rack, and discharges warm air out the rear ofthe rack. There is no air flow requirement for the left and right sides, because offront-to-back cooling.
Each Exadata Cloud@Customer rack is designed to function while installed in anatural convection air flow. To ensure adequate air flow, allow a minimum clearance of1219.2 mm (48 inches) at the front of the server, and 914 mm (36 inches) at the rear ofthe server for ventilation.
Use perforated tiles, approximately 400 CFM/tile, in front of the rack for cold air intake.The tiles can be arranged in any order in front of the rack, as long as cold air fromthe tiles can flow into the rack. Inadequate cold air flow could result in a higher inlettemperature in the servers because of exhaust air recirculation. The following is therecommended number of floor tiles:
• Four floor tiles for an Exadata Cloud@Customer Full Rack.
• Three floor tiles for an Exadata Cloud@Customer Half Rack.
• One floor tile for an Exadata Cloud@Customer Quarter Rack or Base System.
Chapter 2Site Requirements for Oracle Exadata Cloud@Customer
2-6
Network Requirements for Oracle ExadataCloud@Customer
Review the network requirements for provisioning Oracle Exadata Cloud@Customerat your site.
• Network Requirements for Oracle Exadata Cloud@CustomerTo provide secure and reliable network connectivity for different application andmanagement functions, Exadata Cloud@Customer uses different networks .
• Data Center Network Services for Exadata Cloud@CustomerBefore you deploy Exadata Cloud@Customer, ensure that your data centernetwork meets requirements.
Network Requirements for Oracle Exadata Cloud@CustomerTo provide secure and reliable network connectivity for different application andmanagement functions, Exadata Cloud@Customer uses different networks .
The following list outlines the minimum network requirements to install an ExadataCloud@Customer system:
• Client networkThis network connects the Exadata Cloud@Customer database servers to yourexisting client network and is used for client access to the database servers.Applications access databases on Exadata Cloud@Customer through this networkusing Single Client Access Name (SCAN) and Oracle Real Application Clusters(Oracle RAC) Virtual IP (VIP) interfaces.
The client access network uses a pair of network interfaces on each databaseserver, which are connected to the customer network.
• Backup networkThis network is similar to the client access network, as it connects the ExadataCloud@Customer Oracle Database servers to your existing network. It can beused for access to the database servers for various purposes, including backupsand bulk data transfers.
Like the client network, the backup network uses a pair of network interfaces oneach database server, which are connected to the customer network.
• Control plane networkThis virtual private network (VPN) connects the two control plane servers thatare located in the Exadata Cloud@Customer rack to Oracle Cloud Infrastructure.The VPN facilitates secure customer-initiated operations using the OracleCloud Infrastructure Console and APIs. It also facilitates secure monitoringand administration of the Oracle-managed infrastructure components in ExadataCloud@Customer.
• Administration networkThis network connects Exadata Cloud@Customer servers and switches to thetwo control plane servers that are located in the Exadata Cloud@Customer rack.It facilitates customer-initiated operations using the Oracle Cloud InfrastructureConsole and APIs. It also facilitates monitoring and administration of the Oracle-managed infrastructure components in Exadata Cloud@Customer.
Chapter 2Network Requirements for Oracle Exadata Cloud@Customer
2-7
This network is fully contained within the Exadata Cloud@Customer rack, anddoes not connect to your corporate network. However, the Exadata infrastructureis indirectly connected to your corporate network through the control planeservers. This connection is required to provide Domain Name System (DNS) andNetwork Time Protocol (NTP) services to the Exadata infrastructure. Therefore,the IP addresses that are allocated to the administration network must not existelsewhere in your corporate network.
Each Oracle Database server and Exadata Storage Server has two networkinterfaces connected to the administration network. One provides managementaccess to the server through one of the embedded Ethernet ports (NET0).The other provides access to the Integrated Lights-Out Management (ILOM)subsystem through a dedicated ILOM Ethernet port. Exadata Cloud@Customeris delivered with the ILOM and NET0 ports connected to the Ethernet switch in therack. Cabling or configuration changes to these interfaces are not permitted.
• InfiniBand or RDMA Over Converged Ethernet (ROCE) networkThis network connects the database servers, Exadata Storage Servers, andcontrol plane servers using the InfiniBand or ROCE switches on the rack. Eachserver contains two InfiniBand network interfaces (IB0 and IB1) or ROCE interface(re0 and re1) that are connected to separate InfiniBand or ROCE switches inthe rack. Primarily, Oracle Database uses this network for Oracle RAC clusterinterconnect traffic, and for accessing data on Exadata Storage Servers.
This non-routable network is fully contained within the Exadata Cloud@Customerrack, and does not connect to your corporate network. However, because thecontrol plane servers are connected to the InfiniBand or ROCE network and toyour corporate network, the IP addresses that are allocated to the InfiniBand orROCE network must not exist elsewhere in your corporate network.
Data Center Network Services for Exadata Cloud@CustomerBefore you deploy Exadata Cloud@Customer, ensure that your data center networkmeets requirements.
Domain Name System (DNS) Requirements
As part of the deployment process, you must decide on the host names and IPaddresses to be used for various Exadata Cloud@Customer network interfaces.Oracle requires that you register the host names and IP addresses for the ExadataCloud@Customer client and backup network interfaces in your corporate DNS. Atleast one reliable DNS server is required, which must be accessible to the controlplane servers and to all of the servers on the client network. Up to three DNS serverscan be registered in Exadata Cloud@Customer to ensure coverage in case a server isunavailable.
Network Time Protocol (NTP) Services Requirements
Exadata Cloud@Customer uses NTP to ensure that all system components aresynchronized to the same time. At least one reliable NTP server is required, whichmust be accessible to the control plane servers and to all of the servers on the clientnetwork. Up to three NTP servers can be registered in Exadata Cloud@Customer toensure coverage in case a server is unavailable.
Chapter 2Network Requirements for Oracle Exadata Cloud@Customer
2-8
IP Addresses and Subnets for Exadata Cloud@CustomerYou must allocate a range of IP addresses to the administration network, and anotherrange of IP addresses to the InfiniBand network.
InfiniBand Requirements for Oracle Cloud@Customer
No overlap is permitted between the address ranges for the administration networkand the InfiniBand network, and all IP addresses should be unique within yourcorporate network. You must also allocate IP addresses from your corporate networkto the control plane servers. These network configuration details are specified whenyou create the Exadata infrastructure.
When you create the Exadata infrastructure, the console pre-populates default valuesfor the administration network CIDR block and the InifinBand network CIDR block. Youcan use the suggested CIDR blocks if there is no overlap with existing IP addresses inyour corporate network.
Review IP address requirements for each of these networks. The table specifies themaximum and minimum CIDR block prefix length that are allowed for each network.The maximum CIDR block prefix length defines the smallest block of IP addressesthat are required for the network. To allow for possible future expansion within ExadataCloud@Customer, you can choose a smaller CIDR block prefix length, within theallowable range, which reserves more IP addresses for the network.
Network Type IP Address Requirements
Administration network Maximum CIDR block prefix length:
/23
Minimum CIDR block prefix length:
/16
InifinBand network Maximum CIDR block prefix length:
/22
Minimum CIDR block prefix length:
/19
Control plane network 2 IP addresses, 1 for each control plane server
Host Name and IP Address Requirements for Oracle Cloud@Customer
To connect to your corporate network, Exadata Cloud@Customer requires severalhost names and IP addresses for network interfaces on the client network and thebackup network. The precise number of IP addresses depends on the Exadata systemshape. These network configuration details, including host names and IP addresses,are specified when you create a VM cluster network. All IP addresses must be
Chapter 2IP Addresses and Subnets for Exadata Cloud@Customer
2-9
statically assigned IP addresses, not dynamically assigned (DHCP) addresses. Theclient network and the backup network require separate subnets.
The following table outlines the IP address requirements for the client and backupnetworks. The table specifies the maximum and recommended CIDR block prefixlength for each network. The maximum CIDR block prefix length defines the smallestblock of IP addresses that are required for the network. To allow for possible futureexpansion within Exadata Cloud@Customer, a smaller CIDR block prefix length isrecommended, which reserves more IP addresses for the network.
Network Type IP Address Requirementsfor Base System, QuarterRack, or Half Rack
IP Address Requirementsfor Full Rack
Client network Maximum CIDR block prefixlength:
/28
Recommended CIDR blockprefix length:
/27
Maximum CIDR block prefixlength:
/27
Recommended CIDR blockprefix length:
/26
Backup network Maximum CIDR block prefixlength:
/29
Recommended CIDR blockprefix length:
/28
Maximum CIDR block prefixlength:
/28
Recommended CIDR blockprefix length:
/27
Uplinks for Exadata Cloud@CustomerEnsure that your Exadata Cloud@Customer system meets control plane server andcompute node uplink requirements.
Control Plane Servers
Four uplinks (2 per server) are required to connect the control plane servers to yourcorporate network and the control plane virtual private network (VPN).
Compute Node Connections
Typically, four uplinks are required for each compute node to connect to your corporatenetwork. Using this configuration, two uplinks support the client network and the othertwo uplinks support the backup network.
On Quarter Rack, Half Rack, or Full Rack systems, you can choose to use 10 GbpsRJ45 copper, 10 Gbps SFP+ fiber, or 25Gbps SFP28 fiber network connections toyour corporate network. However, you cannot mix copper and fiber networks on the
Chapter 2Uplinks for Exadata Cloud@Customer
2-10
same physical server. For example, you cannot use fiber for the client network andcopper for the backup network.
On Base System configurations, the options are more limited because of the physicalnetwork interfaces that are available on each compute node. On Base Systems, youcan choose to use copper or fiber network connections only for the client network,while the backup network uses a fiber connection.
You can also use shared network interfaces on the Base System for the clientnetwork and the backup network, which reduces the uplink requirement to two uplinksfor each compute node. Using shared network interfaces also enables you to usecopper network connections to support both the client and backup networks on BaseSystem configurations. However, in general, Oracle recommends that you do not useshared network interfaces, because sharing networks compromises the bandwidth andavailability of both networks. Shared network interfaces are not supported for Quarter,Half, and Full Rack configurations.
Network Cabling for Exadata Cloud@CustomerYou can choose to use the supplied network equipment, or you can build your ownSFP network.
Supplied Network Equipment Option
Every Exadata Cloud@Customer rack is shipped with all of the network equipmentand cables that are required to interconnect all hardware in the ExadataCloud@Customer rack.
Small Form-Factory Pluggable Network Option
Oracle supplies small form-factor pluggable (SFP) network interfaces to enableconnectivity to your corporate network. However, if you choose to configure an SFPnetwork, then you are responsible to provide the required cabling to connect theExadata compute nodes and control plane servers to your corporate network.
Checklists for Exadata Cloud@Customer DeploymentsTo determine your readiness for an Exadata Cloud@Customer deployment, review thedeployment checklists.
• System Components Checklist for Exadata Cloud@CustomerUse this checklist to ensure that the system component considerations areaddressed.
• Data Center Room Checklist for Exadata Cloud@CustomerUse this checklist to ensure that the data center room requirements areaddressed.
• Data Center Environment Checklist for Oracle Exadata Cloud@CustomerUse this checklist to ensure that the data center environment requirements areaddressed.
• Access Route Checklist for Oracle Exadata Cloud@CustomerUse this checklist to ensure that the access route requirements are addressed.
• Facility Power Checklist for Oracle Exadata Cloud@CustomerUse this checklist to ensure that the facility power requirements are addressed.
Chapter 2Network Cabling for Exadata Cloud@Customer
2-11
• Safety Checklist for Oracle Exadata Cloud@CustomerUse this checklist to ensure that safety requirements are addressed.
• Logistics Checklist for Exadata Cloud@CustomerUse this checklist to ensure that the logistics requirements are addressed.
• Network Configuration Checklist for Oracle Exadata Cloud@CustomerUse this checklist to ensure that the network configuration requirements areaddressed.
• Reracking Checklist for Oracle Exadata Cloud@CustomerUse this checklist to determine your readiness for reracking.
System Components Checklist for Exadata Cloud@CustomerUse this checklist to ensure that the system component considerations are addressed.
• How many racks do you plan to install?
• Will additional equipment be attached to or installed in the rack?If additional equipment is attached, then ensure that the additional equipmentmeets Oracle guidelines, and there is sufficient power and cooling.
Data Center Room Checklist for Exadata Cloud@CustomerUse this checklist to ensure that the data center room requirements are addressed.
Answer yes, no, not applicable, or add your comments. Or let the site survey team fillin the requested information.
• Has the rack location been allocated and is it vacant?
• Does the floor layout meet the equipment maintenance access requirements?
• Will the rack be positioned so that the exhaust air of one rack does not enter theair inlet of another rack?
• Have cabinet stabilization measures been considered?
• If the data center has a raised floor:
– Does the raised floor satisfy the weight requirements for the rack?
– Is permission required to remove floor tiles for cabling and servicing below thefloor?
• Will the rack location require any non-standard cable lengths?
• Is the floor-to-ceiling height a minimum of 2914 mm (114.72 inches)?
• Is the depth of the raised floor a minimum of 46 cm (18 inches)?
Data Center Environment Checklist for Oracle ExadataCloud@Customer
Use this checklist to ensure that the data center environment requirements areaddressed.
Answer yes, no, not applicable, or add your comments. Or, let the site survey team fillin the requested information.
Chapter 2Checklists for Exadata Cloud@Customer Deployments
2-12
• Does the computer room air conditioning meet temperature and humidityrequirements?
• Does the installation floor layout satisfy the ventilation requirements?
• If the room cooling is from a raised floor:
– Are the perforated floor tiles each rated at 400 CFM or greater?
– Can additional perforated floor tiles be obtained if required for additionalcooling?
• Does the data center air conditioning provide sufficient front-to-back airflow?
• Is airflow adequate to prevent hot spots?
• Can the data center continuously satisfy the environmental requirements?
Access Route Checklist for Oracle Exadata Cloud@CustomerUse this checklist to ensure that the access route requirements are addressed.
Answer yes, no, not applicable, or add your comments. Or, let the site survey team fillin the requested information.
• Has the access route been checked for clearance of the rack, including theminimum width and height requirements for all doors on the route?
• Are there any stairs, ramps, or thresholds that are of concern?If yes, then provide details.
• Are all access route incline angles within the permitted range (under 6 degrees)?
• Are all the surfaces acceptable for rolling the new unpacked and packedequipment?
• If a pallet jack is to be used:
– Can the pallet jack support the weight of the rack?
– Are the pallet jack tines compatible with the shipping pallet?
• If there are stairs, is a loading elevator available for the equipment?
• If an elevator is to be used:
– Does the elevator car meet the height, width, and depth requirements forcarrying the rack?
– Do the elevator doors meet the height and width requirements for moving therack?
– Does the elevator meet the weight requirements for transporting the rack?
• Can the complete access route support the weight of the rack?
• Is the access route onto the raised floor rated for dynamic loading of the rack?
Facility Power Checklist for Oracle Exadata Cloud@CustomerUse this checklist to ensure that the facility power requirements are addressed.
Answer yes, no, not applicable, or add your comments. Or, let the site survey team fillin the requested information.
Chapter 2Checklists for Exadata Cloud@Customer Deployments
2-13
• Have the operating voltage and electric current requirements been reviewed?
• What type of power supply will be used?
– Single-phase or 3-phase.
– Low-voltage or High-voltage.
• Are enough power outlets provided within 2 meters for each rack?
• Do the power outlets have appropriate socket receptacles for the planned PowerDistribution Units (PDUs)?
• Will optional ground cables be attached to the rack?
• Are the electrical circuits suitable in terms of voltage and current-carryingcapacities?
• Does the power frequency meet the equipment specifications?
• Are power outlets available for the new equipment at the designated location?
• Will system power be delivered from two separate grids?
• Is there a UPS to power the equipment?
• Are the minimum required power sources available to support the power load (kWor kVA) for the new hardware?
Safety Checklist for Oracle Exadata Cloud@CustomerUse this checklist to ensure that safety requirements are addressed.
Answer yes, no, not applicable, or add your comments. Or, let the site survey team fillin the requested information.
• Is there an emergency power shut off?
• Is there a fire protection system in the data center room?
• Is the computer room adequately equipped to extinguish a fire?
• Is antistatic flooring installed?
• Is the area below the raised floor free of obstacles and blockages?
Logistics Checklist for Exadata Cloud@CustomerUse this checklist to ensure that the logistics requirements are addressed.
Answer yes, no, not applicable, or add your comments. Or, let the site survey team fillin the requested information.
• Is contact information for the data center personnel available?
• Is there security or access control for the data center?
• Are there any security background checks or security clearances required forOracle personnel to access the data center?If yes, then provide the process for Oracle to follow.
• How many days in advance must background checks be completed?
• Are there any additional security access issues?
• Is computer room access available for installation personnel?
Chapter 2Checklists for Exadata Cloud@Customer Deployments
2-14
• Are laptops allowed in the data center?
• Are cell phones allowed in the data center?
• Are cameras allowed in the data center?
• Does the building have a delivery dock?
• Is there a delivery / unpacking / staging area?
• Is inside delivery planned (direct to the final rack location in the data center room)?
• If the delivery is not inside, then is the site prepared for uncrating?
• Is the delivery / unpacking / staging area protected from the elements?
• Does the building have adequate receiving space?
• Is the unpacking area air-conditioned to avoid thermal shock for various hardwarecomponents?
• Will sufficient moving personnel be available to transport the rack?
• Is union labor required for any part of the delivery or installation?
• Is the site prepared for uncrating and packaging removal?Package removal should take place outside the data center room.
• Is uncrating of cabinet and packaging removal required?
• Are there any restrictions on delivery truck length, width, or height?
• Is there storage space (cabinet) for the ride along spares?If not, does the customer allow cardboard boxes and other packing material in thecomputer room, since the spares are packed in cardboard boxes?
• Is there a time constraint on dock access?If yes, provide time constraints.
• Is a tail or side lift required on the delivery carrier to unload the equipment at thedelivery dock?
• Will any special equipment be required to place the rack in the data center room?For example:
– Stair walkers
– Lifters
– Ramps
– Steel plates
– Floor covers
• Does the delivery carrier require any special equipment, such as non-floordamaging rollers, transport dollies, pallet jacks, or fork lifts?
Network Configuration Checklist for Oracle Exadata Cloud@CustomerUse this checklist to ensure that the network configuration requirements areaddressed.
Answer yes, no, not applicable, or add your comments. Or, let the site survey team fillin the requested information.
Chapter 2Checklists for Exadata Cloud@Customer Deployments
2-15
• Will the required network cables be laid from the network equipment to the locationwhere the Oracle Exadata Rack will be installed?
• Will the network cables that will connect to the Oracle Exadata Rack be labeled?
• Will the 10 GbE or 25 GbE interfaces be used for the client access network?If so, has the customer ordered the appropriate cables to their switch?
• Will the Cisco Ethernet switch have IP routing disabled (recommended)?
Reracking Checklist for Oracle Exadata Cloud@CustomerUse this checklist to determine your readiness for reracking.
Use this checklist to ensure that the reracking requirements are addressed.
Note:
• Reracking requires prior approval. The checklist below provides highlevel guidance on re-racking requirements. Oracle maintains a detailedinternal checklist that must be approved prior to performing reracking.
• You must purchase the Oracle Reracking service.
• Oracle does not provide technical support for customer-suppliedequipment.
Answer yes, no, not applicable, or add your comments. Or, let the site survey team tofill in the requested information.
• Have you purchased the Oracle Reracking Service?
• Is there a cart capable of carrying the weight of the servers to move thecomponents and associated cabling from the supplied rack to the rack that yousupply?
• Is the target rack empty?
• Attach pictures of the target rack (inside and outside).
• Does the target rack meet the following requirements?
– Height: 42 RU
– Width: 600 mm (23.62 inches)
– Depth: 1112 mm (43.78 inches) without front and rear doors
If the rack is less than 42 RU tall, then the rack must be at least 30 RU tall, andyou must provide compatible PDUs to install in the target rack.
• Is the distance between the front and rear mounting planes between the minimumof 610 mm and the maximum 915 mm (24–36 inches)?
• Is the clearance depth in the front of the front mounting plane (distance to the frontcabinet door) at least 25.4 mm (1 inch)?
• Does the target rack meet the following minimum load capacity?
– 19 kg (41.89 lb) per RU
Chapter 2Checklists for Exadata Cloud@Customer Deployments
2-16
– 785 kg (1730.63 lb) total
• Is the rack a four-post rack (mounting at both front and rear)?
Note:
Two-post racks are not compatible.
• Does the target rack's horizontal opening and unit vertical pitch conform toANSI/EIA 310-D-1992 or IEC 60297 standards?
• Does the target rack have RETMA rail support?
Note:
Oracle Exadata rack requires 19 inches (483 mm) for RETMA railspacing width. The minimum rack width of 600 mm (23.63 inches) isrecommended to accommodate the PDU and cable harnesses on theside. If the rack is less than 600 mm wide, then it must have additionaldepth to accommodate mounting behind the server cable managementarms.
• Does the target rack support Oracle cable management arms?
• Does the target rack support installation of Oracle vented and solid filler panels?
• Can the target rack provide tie-downs along the left rear side of the rack (asviewed from the front of the rack) to support the lnfiniBand cables?
• Can the target rack provide tie-downs for the Ethernet wiring harness?
• Is there sufficient space for the cable harnesses and the PDUs in the target rack?
• Can a label with the Oracle Exadata Rack serial number be printed and attachedto the target rack?
• Does the target rack support installation of standard Oracle PDUs?If not, then complete the following checklist items:
– Can you provide provide an equivalent pair of PDUs?
– Can you provide provide two PDUs, each with a capacity of 10 kVA?
– Can you provide provide at least 17 x lOA C13 plugs per PDU?
– Can you provide a single PDU and its circuits to support the Oracle ExadataRack power requirements in case one PDU fails?
– Can you ensure that power loads are evenly distributed across all circuits of asingle PDU?
– Can you provide appropriate power drops for the PDUs?
Chapter 2Checklists for Exadata Cloud@Customer Deployments
2-17
3Provisioning Exadata Cloud@CustomerSystems
Learn how to provision an Exadata Cloud@Customer system.
• About Provisioning Oracle Exadata Cloud@Customer SystemsTo provision an Oracle Exadata Cloud@Customer system, you must work withOracle to set up and configure the system.
• Required IAM Policy for Provisioning ServersReview the identity access management (IAM) policy for provisioning OracleExadata Cloud@Customer systems.
• Prerequisites for Provisioning Oracle Exadata Cloud@Customer ServersBefore you provision your X8M-2, X8-2, and X7-2 servers, you must set uptenancy, and your network and other infrastructure must meet requirements.
• Using the Console to Provision Oracle Exadata Cloud@CustomerLearn how to use the console to create your infrastructure, and to edit, downloada configuration file, activate, and check the status of your infrastructure for OracleExadata Cloud@Customer.
• Using the API for Oracle Exadata Cloud@CustomerOracle Exadata Cloud@Customer uses the same API as Oracle CloudInfrastructure.
About Provisioning Oracle Exadata Cloud@CustomerSystems
To provision an Oracle Exadata Cloud@Customer system, you must work with Oracleto set up and configure the system.
Provisioning an Oracle Exadata Cloud@Customer system is a collaborative process.The process is performed in the following sequence:
1. You create the Oracle Exadata Cloud@Customer infrastructure.
2. You generate a file containing the infrastructure configuration details, and provideit to Oracle.
3. The Oracle Exadata Cloud@Customer system is physically installed in your datacenter.
4. Oracle uses the infrastructure configuration file to perform initial systemconfiguration. At the end of this task, Oracle supplies you with an activation file.
5. You activate the Exadata Cloud@Customer infrastructure by using the suppliedactivation file.
3-1
When the provisioning process is complete, the Oracle Exadata Cloud@Customersystem is ready for you to use. You can then create a virtual machine (VM) cluster, andlater create some databases.
Caution:
Avoid entering confidential information when assigning descriptions, tags, or friendlynames to your cloud resources through the Oracle Cloud Infrastructure Console, theAPIs, or the command-line interface.
Required IAM Policy for Provisioning ServersReview the identity access management (IAM) policy for provisioning Oracle ExadataCloud@Customer systems.
A policy is An IAM document that specifies who has what type of access to yourresources. It is used in different ways: to mean an individual statement written inthe policy language; to mean a collection of statements in a single, named "policy"document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean theoverall body of policies your organization uses to control access to resources.
A compartment is a collection of related resources that can be accessed onlyby certain groups that have been given permission by an administrator in yourorganization.
To use Oracle Cloud Infrastructure, you must be given the required type of access ina policy written by an administrator, whether you're using the Console, or the RESTAPI with a software development kit (SDK), a command-line interface (CLI), or someother tool. If you try to perform an action, and receive a message that you don’thave permission, or are unauthorized, then confirm with your administrator the type ofaccess you've been granted, and which compartment you should work in.
For administrators: The policy in "Let database admins manage DB systems" lets thespecified group do everything with databases, and related database resources.
If you're new to policies, then see "Getting Started with Policies" and "CommonPolicies". If you want to dig deeper into writing policies for databases, then see "Detailsfor the Database Service".
Related Topics
• Let database admins manage DB systems
• Getting Started with Policies
• Common Policies
• Details for the Database Service
Chapter 3Required IAM Policy for Provisioning Servers
3-2
Prerequisites for Provisioning Oracle ExadataCloud@Customer Servers
Before you provision your X8M-2, X8-2, and X7-2 servers, you must set up tenancy,and your network and other infrastructure must meet requirements.
• Before you can provision Exadata Cloud@Customer infrastructure, yourOracle Cloud Infrastructure tenancy must be enabled to use Oracle ExadataCloud@Customer. Review the information in this publication, and contact Oraclefor further details.
• In preparation for the provisioning process, ensure that your corporate data centerand network infrastructure meet the requirements described in this publication.
Using the Console to Provision Oracle ExadataCloud@Customer
Learn how to use the console to create your infrastructure, and to edit, downloada configuration file, activate, and check the status of your infrastructure for OracleExadata Cloud@Customer.
• Using the Console to Create InfrastructureTo create your Oracle Exadata Cloud@Customer infrastructure, be prepared toprovide values for the fields required for configuring the infrastructure.
• Using the Console to Edit Oracle Exadata Cloud@Customer InfrastructureTo edit your Oracle Exadata Cloud@Customer infrastructure, be prepared toprovide values for the infrastructure configuration.
• Using the Console to Download a File Containing Configuration DataTo download an Oracle Exadata Cloud@Customer configuration file, complete thisprocedure.
• Using the Console to Activate Exadata Cloud@Customer InfrastructureTo activate Oracle Exadata Cloud@Customer infrastructure, ensure that you meetthe prerequisites, and complete this procedure.
• Using the Console to Check the Status of Exadata Cloud@CustomerInfrastructureTo find the status of your Oracle Exadata Cloud@Customer infrastructure, use thisprocedure to check the Infrastructure Details page.
• Using the Console to Move Exadata Cloud@Customer InfrastructureTo relocate Oracle Exadata Cloud@Customer infrastructure to anothercompartment, use this procedure.
• Using the Console to Delete Exadata Cloud@Customer InfrastructureTo delete Oracle Exadata Cloud@Customer infrastructure, complete theprerequisites, and then complete this procedure.
• Managing Infrastructure Maintenance ContactsLearn to manage your Exadata infrastructure maintenance contacts.
Chapter 3Prerequisites for Provisioning Oracle Exadata Cloud@Customer Servers
3-3
Using the Console to Create InfrastructureTo create your Oracle Exadata Cloud@Customer infrastructure, be prepared toprovide values for the fields required for configuring the infrastructure.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Under Region, select the region that you want to associate with the OracleExadata infrastructure.
The region that is associated with your Oracle Exadata infrastructure cannot bechanged after the Oracle Exadata infrastructure is created. Therefore, ensurethat you select the most appropriate region for your infrastructure. Consider thefollowing factors:
• Consider any business policies or regulations that preclude the use of aparticular region. For example, you can be required to maintain all operationswithin national boundaries.
• Consider the physical proximity of the region to your data center.Needless extra physical separation adds unnecessary latency to networkcommunications between Oracle Cloud Infrastructure and your corporate datacenter.
3. Click Exadata Infrastructure.
4. Click Create Exadata Infrastructure.
5. In the Create Exadata Infrastructure page, provide the requested information:
• Oracle Cloud Infrastructure region: The region that is associated with yourOracle Exadata infrastructure cannot be changed after the Oracle Exadatainfrastructure is created. Therefore, check the displayed region to ensure thatyou are using the most appropriate region for your infrastructure.
See step 2 (earlier in this procedure) for further considerations. To switchregions now, use the Region menu at the top of the console.
• Choose a compartment: From the list of available compartments, choose thecompartment that you want to contain the Oracle Exadata infrastructure.
See also Understanding Compartments.
• Provide the display name: The display name is a user-friendly name thatyou can use to identify the Exadata infrastructure. The name doesn't need tobe unique, because an Oracle Cloud Identifier (OCID) uniquely identifies theOracle Exadata infrastructure.
• Select the Exadata system model: From the list, choose the model of theOracle Exadata hardware that is being used.
The Oracle Exadata system model and system shape combine to define theamount of CPU, memory, and storage resources that are available in theExadata infrastructure. For more details, see "System Configuration".
• Select an Exadata system shape: Together with the Oracle Exadata systemmodel, the Oracle Exadata system shape defines the amount of CPU,memory, and storage resources that are available in the Oracle Exadatainfrastructure.
– Base System: includes two compute nodes and three Oracle ExadataStorage Servers. A Base System is an entry-level configuration.
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-4
Compared to other configurations, a Base System contains OracleExadata Storage Servers with significantly less storage capacity, andcompute nodes with significantly less memory and processing power.
– Quarter Rack: includes two compute nodes and three Oracle ExadataStorage Servers.
– Half Rack: includes four compute nodes and six Oracle Exadata StorageServers.
– Full Rack: includes eight compute nodes and 12 Oracle Exadata StorageServers.
• Configure the cloud control plane network
Each Oracle Exadata Cloud@Customer system contains two control planeservers, which enable connectivity to Oracle Cloud Infrastructure. The controlplane servers are connected to the control plane network, which is a subnet onyour corporate network. The following settings define the network parameters:
– Control Plane Server 1 IP Address: Provide the IP address for the firstcontrol plane server. This IP address is for the network interface thatconnects the first control plane server to your corporate network using thecontrol plane network.
– Control Plane Server 2 IP Address: Provide the IP address for thesecond control plane server. This IP is address for the network interfacethat connects the second control plane server to your corporate networkusing the control plane network.
– Netmask: Specify the IP netmask for the control plane network.
– Gateway: Specify the IP address of the control plane network gateway.
– HTTPS Proxy: (Optional) You can choose to use this field to specify yourcorporate HTTPS proxy. The expected format is as follows, where serveris the server name, domain is the domain name, and port is the assignedport:
http://server.domain:port
For example:
http://proxy.example.com:80
For enhanced security, when possible, Oracle recommends that you usean HTTPS proxy.
• Configure the Oracle Exadata system networks
Each Oracle Exadata Cloud@Customer system contains two systemnetworks, which are not connected to your corporate network. The followingsettings define IP address allocations for these networks:
– Administration Network CIDR Block: Specifies the IP address rangefor the administration network using CIDR notation. The administrationnetwork provides connectivity that enables Oracle to administer theExadata system components, such as the Exadata compute servers,storage servers, network switches, and power distribution units. You canaccept the suggested default, or specify a custom value.
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-5
The maximum CIDR block prefix length is /23, which defines the smallestblock of IP addresses that are required for the network. To allow forpossible future expansion within Exadata Cloud@Customer, a smallerCIDR block prefix length is recommended, which reserves more IPaddresses for the network. The minimum CIDR block prefix length is /16.
Ensure that the IP address range does not conflict with other hosts yourcorporate network, and does not overlap with the InfiniBand network CIDRblock.
• InfiniBand Network CIDR Block: Specifies the IP address range for theExadata InfiniBand network using CIDR notation. The Exadata InfiniBandnetwork provides the high-speed low-latency interconnect used by Exadatasoftware for internal communications between various system components.You can accept the suggested default, or specify a custom value.
The maximum CIDR block prefix length is /22, which defines the smallestblock of IP addresses that are required for the network. To allow for possiblefuture expansion within Exadata Cloud@Customer, a smaller CIDR blockprefix length is recommended, which reserves more IP addresses for thenetwork. The minimum CIDR block prefix length is /19.
Ensure that the IP address range does not conflict with other hosts yourcorporate network, and does not overlap with the administration network CIDRblock.
• Configure DNS and NTP services
Each Exadata Cloud@Customer system requires access to Domain NamesSystem (DNS) and Network Time Protocol (NTP) services. The followingsettings specify the servers that provide these services to the Exadatainfrastructure:
– DNS Servers: Provide the IP address of a DNS server that is accessibleusing the control plane network. You may specify up to three DNS servers.
– NTP Servers: Provide the IP address of an NTP server that is accessibleusing the control plane network. You may specify up to three NTP servers.
– Time Zone: The default time zone for the Exadata Infrastructure is UTC,but you can specify a different time zone. The time zone options are thosesupported in both the Java.util.TimeZone class and the Oracle Linuxoperating system.
Note:
If you want to set a time zone other than UTC or the browser-detected time zone, then select the Select another timezone option, select a Region or country, and then select thecorresponding Time zone.
If you do not see the region or country you want, then selectMiscellaneous, and then select an appropriate Time zone.
• Show Advanced Options
You have the option to configure advanced options.
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-6
– Tags: (Optional) You can choose to apply tags. If you have permissions tocreate a resource, then you also have permissions to apply free-form tagsto that resource. To apply a defined tag, you must have permissions to usethe tag namespace. For more information about tagging, see "ResourceTags". If you are not sure if you should apply tags, then skip this option(you can apply tags later) or ask your administrator.
6. Provide maintenance detailsClick Modify Maintenance.
In the Edit Automatic Maintenance dialog that opens, configure automaticmaintenance schedule.
No preference: The system assigns a date and start time for infrastructuremaintenance.
Specify a schedule: Choose your preferred month, week, weekday, start time,and lead time for infrastructure maintenance.
Lead Time: Specify the minimum number of weeks ahead of the maintenanceevent you would like to receive a notification message.
7. Provide maintenance contacts.Maintenance contacts are required for service request based communications forhardware replacement and other maintenance events.
You can skip adding maintenance contacts while creating your infrastructure.However, you must add a primary contact prior to activating your infrastructure.Ensure that you provide the details of the contact that you used while registeringthe Customer Support Identifier (CSI) associated with this infrastructure, as aprimary contact.
Optionally, you can add a maximum of nine secondary contacts. Both the primaryand secondary contacts receive all notifications about hardware replacement,network issues, and software maintenance runs. Note that you can promoteany secondary contacts as the primary anytime you want. When you promotea secondary contact to primary, the current primary contact will be demotedautomatically to secondary.
8. Click Create Exadata Infrastructure.
If all of your inputs are valid, then the Infrastructure Details page appears. Thepage outlines the next steps in the provisioning process. Initially after creation, thestate of the Oracle Exadata infrastructure is Requires-Activation.
Related Topics
• Understanding Compartments
• System Configuration Options for Oracle Exadata Cloud@Customer
• Resource Tags
Using the Console to Edit Oracle Exadata Cloud@CustomerInfrastructure
To edit your Oracle Exadata Cloud@Customer infrastructure, be prepared to providevalues for the infrastructure configuration.
You can only edit Oracle Exadata Cloud@Customer infrastructure networking if thecurrent state of the Oracle Exadata infrastructure is Requires Activation. Also,
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-7
ensure that you do not edit the Exadata infrastructure after you download theconfiguration file and provide it to Oracle.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Select Region and Compartment, and provide the region and the compartmentwhere the Oracle Exadata infrastructure you want to edit is located.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that you want to edit.
The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
5. Click Edit Infrastructure Networking.
6. Use the Edit Infrastructure Networking dialog to edit the Oracle Exadatainfrastructure networking:
a. Configure the cloud control plane network
Each Oracle Exadata Cloud@Customer system contains two control planeservers, which enable connectivity to Oracle Cloud Infrastructure. The controlplane servers are connected to the control plane network, which is a subnet onyour corporate network. The following settings define the network parameters:
• Control Plane Server 1 IP Address: Provide the IP address for the firstcontrol plane server. This IP address is for the network interface thatconnects the first control plane server to your corporate network using thecontrol plane network.
• Control Plane Server 2 IP Address: Provide the IP address for thesecond control plane server. This IP address is for the network interfacethat connects the second control plane server to your corporate networkusing the control plane network.
• Netmask: Specify the IP netmask for the control plane network.
• Gateway: Specify the IP address of the control plane network gateway.
• HTTPS Proxy: (Optional) You can use this field to specify your corporateHTTPS proxy. The expected format is as follows, where server is theserver name, domain is the domain name, and port is the assigned port:
http://server.domain:port
For example:
http://proxy.example.com:80
For enhanced security, when possible, Oracle recommends that you usean HTTPS proxy.
b. Configure the Exadata system networksEach Oracle Exadata Cloud@Customer system contains two systemnetworks, which are not connected to your corporate network. The followingsettings define IP address allocations for these networks:
• Administration Network CIDR Block: Specifies the IP address rangefor the administration network using CIDR notation. The administration
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-8
network provides connectivity that enables Oracle to administer theExadata system components, such as the Exadata compute servers,storage servers, network switches, and power distribution units.
The maximum CIDR block prefix length is /23, which defines the smallestblock of IP addresses that are required for the network. To allow forpossible future expansion within Oracle Exadata Cloud@Customer, asmaller CIDR block prefix length is recommended, which reserves more IPaddresses for the network. The minimum CIDR block prefix length is /16.
Ensure that the IP address range does not conflict with other hosts yourcorporate network, and does not overlap with the InfiniBand network CIDRblock.
• InfiniBand Network CIDR Block: Specifies the IP address range forthe Exadata InfiniBand network using CIDR notation. The ExadataInfiniBand network provides the high-speed low-latency interconnect usedby Exadata software for internal communications between various systemcomponents.
The maximum CIDR block prefix length is /22, which defines the smallestblock of IP addresses that are required for the network. To allow forpossible future expansion within Oracle Exadata Cloud@Customer, asmaller CIDR block prefix length is recommended, which reserves more IPaddresses for the network. The minimum CIDR block prefix length is /19.
Ensure that the IP address range does not conflict with other hosts yourcorporate network, and does not overlap with the administration networkCIDR block.
c. Configure DNS and NTP servicesEach Oracle Exadata Cloud@Customer system requires access to DomainNames System (DNS) and Network Time Protocol (NTP) services. Thefollowing settings specify the servers that provide these services to theExadata infrastructure:
• DNS Servers: Provide the IP address of a DNS server that is accessibleusing the control plane network. You can specify up to three DNS servers.
• NTP Servers: Provide the IP address of an NTP server that is accessibleusing the control plane network. You may specify up to three NTP servers.
• Time zone: The default time zone for the Exadata Infrastructure is UTC,but you can specify a different time zone. The time zone options are thosesupported in both the Java.util.TimeZone class and the Oracle Linuxoperating system.
Note:
If you want to set a time zone other than UTC or the browser-detected time zone, then select the Select another timezone option, select a Region or country, and then select thecorresponding Time zone.
If you do not see the region or country you want, then selectMiscellaneous, and then select an appropriate Time zone.
7. Click Save Changes.
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-9
Using the Console to Download a File Containing Configuration DataTo download an Oracle Exadata Cloud@Customer configuration file, complete thisprocedure.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the Oracle Exadatainfrastructure for which you want to download a file containing the infrastructureconfiguration details.
3. Click Exadata Infrastructure.
4. Click the name of the Oracle Exadata infrastructure for which you want todownload a file containing the infrastructure configuration details.
The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
5. Click Download Configuration.
Your browser downloads a file containing the infrastructure configuration details.
When you provide the generated infrastructure configuration file to Oracle, ensure thatit has not been altered in any way. Also, ensure that you do not edit the OracleExadata infrastructure after you download the configuration file and provide it toOracle.
Using the Console to Activate Exadata Cloud@CustomerInfrastructure
To activate Oracle Exadata Cloud@Customer infrastructure, ensure that you meet theprerequisites, and complete this procedure.
• Ensure that you have added a primary contact. You cannot activate yourinfrastructure without adding a primary maintenance contact.
• Locate the activation file. This file is supplied to you by Oracle after installation andinitial configuration of your Oracle Exadata Cloud@Customer system.
• Ensure that your infrastructure current state is Requires Activation. You can onlyactivate Oracle Exadata if its state is Requires Activation.
1. Download the activation file.
2. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
3. Choose Region and Compartment, and select the region and compartment thatcontains the Oracle Exadata infrastructure that you want to activate.
4. Click Exadata Infrastructure.
5. Click the name of the Oracle Exadata infrastructure that you want to activate.
The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
6. Click Activate.
The Activate button is only available if the Oracle Exadata infrastructure requiresactivation. You cannot activate Oracle Exadata infrastructure multiple times.
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-10
7. Use the Activate dialog to upload the activation file, and then click Activate Now.
After activation, the state of the Oracle Exadata infrastructure changes to Active.
Using the Console to Check the Status of Exadata Cloud@CustomerInfrastructure
To find the status of your Oracle Exadata Cloud@Customer infrastructure, use thisprocedure to check the Infrastructure Details page.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the Oracle Exadatainfrastructure that you are interested in.
3. Click Exadata Infrastructure.
4. Click the name of the Oracle Exadata infrastructure that you are interested in.
The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
5. Check the icon on the Infrastructure Details page. The color of the icon and thetext below it indicates the status of the Oracle Exadata infrastructure.
• Creating: Yellow icon. The Oracle Exadata infrastructure definition is beingcreated in the control plane.
• Requires Activation: Yellow icon. The Oracle Exadata infrastructure isdefined in the control plane, but it must be provisioned and activated before itcan be used.
• Active: Green icon. The Oracle Exadata infrastructure is successfullyprovisioned and activated.
• Deleting: Gray icon. The Oracle Exadata infrastructure is being deleted byusing the Console or API.
• Deleted: Gray icon. The Oracle Exadata infrastructure is deleted, and is nolonger available. This state is transitory. It is displayed for a short time, afterwhich the Oracle Exadata infrastructure is no longer displayed.
• Activation Failed: Red icon. An error condition currently prevents theactivation of the Oracle Exadata infrastructure. Typically, this state is auto-correcting, and does not require user intervention.
Using the Console to Move Exadata Cloud@Customer InfrastructureTo relocate Oracle Exadata Cloud@Customer infrastructure to another compartment,use this procedure.
You can change the compartment that contains your Exadata Cloud@Customerinfrastructure by moving it.
When you move Exadata infrastructure, the compartment change is also applied to theassociated VM cluster networks. However, the compartment change does not affectany other associated resources, such as the VM clusters, which remain in their currentcompartment.
To move Oracle Exadata Cloud@Customer infrastructure:
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-11
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Select Region and Compartment, and provide the region and compartment thatcontains the Oracle Exadata infrastructure that you want to move.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that you want to move.
The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
5. Click Move Resource.
6. In the resulting dialog, choose the new compartment for the Oracle Exadatainfrastructure, and click Move Resource.
Using the Console to Delete Exadata Cloud@Customer InfrastructureTo delete Oracle Exadata Cloud@Customer infrastructure, complete the prerequisites,and then complete this procedure.
Deleting Exadata Cloud@Customer infrastructure removes it from the Cloud ControlPlane.
If you are deleting Oracle Exadata infrastructure before activation, then if required, youcan create replacement Oracle Exadata infrastructure without any input from Oracle.
In you are deleting active Oracle Exadata infrastructure, then to create replacementOracle Exadata infrastructure, you must repeat the full provisioning process, includingthe tasks that Oracle performs.
Before you can delete active Exadata infrastructure, you must:
• Terminate all of the resources that it contains, including the databases, VM cluster,and VM cluster network.
• Lodge a service request (SR) with Oracle indicating your intention to delete theOracle Exadata infrastructure. In response to the SR, Oracle flags the OracleExadata infrastructure as ready for deletion.
After Oracle has flagged the Oracle Exadata infrastructure, delete the Exadatainfrastructure by using the following process:
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Select Region and Compartment, and provide the region and compartment thatcontains the Oracle Exadata infrastructure that you want to delete.
3. Click Exadata Infrastructure.
4. Click the name of the Oracle Exadata infrastructure that you want to delete.
The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
5. Click Delete.
6. In the resulting dialog, enter the Oracle Exadata infrastructure name and clickDelete Exadata Infrastructure to confirm the action.
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-12
Managing Infrastructure Maintenance ContactsLearn to manage your Exadata infrastructure maintenance contacts.
• View Primary Maintenance ContactYou must associate primary contact with the Customer Support Identifier (CSI).
• Add Secondary ContactsYou can add up to nine secondary contacts.
• Edit Maintenance ContactsEdit maintenance contacts to update details.
• Promote a Secondary Contact to PrimaryYou can promote a secondary contact to primary. The current primary isautomatically demoted to secondary.
• Remove a Secondary ContactYou can remove a secondary contact anytime you want to.
View Primary Maintenance ContactYou must associate primary contact with the Customer Support Identifier (CSI).
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Select Region and Compartment, and provide the region and compartment thatcontains the Oracle Exadata infrastructure for which you want to view contactdetails.
3. Click Exadata Infrastructure.
4. Click the name of the Oracle Exadata infrastructure for which you want to viewcontact details.The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
5. Find the CSI and the primary contact under Maintenance.The operations team sets the infrastructure maintenance Service Level Objective(SLO) to Degraded:
• If the primary contact CSI verification has failed.
• If the primary contact is missing.
• If the primary contact is verified and unresponsive.
Also, a warning message is displayed on the Console as follows:
"Ensure that the primary contact associated with your Customer Support Identifier (CSI) is available for Oracle support to coordinate maintenance-related activities. The infrastructure maintenance Service Level Objective (SLO) is set to degraded status without proper primary contact."
Add a primary contact before you activate the infrastructure.
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-13
Add Secondary ContactsYou can add up to nine secondary contacts.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Select Region and Compartment, and provide the region and compartment thatcontains the Oracle Exadata infrastructure for which you want to add secondarycontacts.
3. Click Exadata Infrastructure.
4. Click the name of the Oracle Exadata infrastructure for which you want to addsecondary contacts.The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
5. Click Manage Contacts.
6. In the Manage Exadata Infrastructure Contacts window, click Add Contact.
7. In the Add Contacts window, add contact details.
8. Click Add Contacts.
Edit Maintenance ContactsEdit maintenance contacts to update details.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Select Region and Compartment, and provide the region and compartment thatcontains the Oracle Exadata infrastructure for which you want to edit maintenancecontact details.
3. Click Exadata Infrastructure.
4. Click the name of the Oracle Exadata infrastructure for which you want to editmaintenance contact details.The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
5. Click Manage Contacts.
6. In the Manage Exadata Infrastructure Contacts window, click the actions button,and then select Edit Contact.
7. In the Edit Contacts window, edit the details.
8. Click Save.
Promote a Secondary Contact to PrimaryYou can promote a secondary contact to primary. The current primary is automaticallydemoted to secondary.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Select Region and Compartment, and provide the region and compartmentthat contains the Oracle Exadata infrastructure for which you want to promotea secondary contact to primary.
Chapter 3Using the Console to Provision Oracle Exadata Cloud@Customer
3-14
3. Click Exadata Infrastructure.
4. Click the name of the Oracle Exadata infrastructure for which you want to promotea secondary contact to primary.The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
5. Click Manage Contacts.
6. In the Manage Exadata Infrastructure Contacts window, click the actions button,and then select Make Primary.
7. In the Promote to Primary Contact dialog, click Promote.
Remove a Secondary ContactYou can remove a secondary contact anytime you want to.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Select Region and Compartment, and provide the region and compartmentthat contains the Oracle Exadata infrastructure for which you want to remove asecondary contact.
3. Click Exadata Infrastructure.
4. Click the name of the Oracle Exadata infrastructure for which you want to removea secondary contact.The Infrastructure Details page displays information about the selected OracleExadata infrastructure.
5. Click Manage Contacts.
6. In the Manage Exadata Infrastructure Contacts window, click the actions button,and then select Remove.
7. In the Remove Infrastructure Contact dialog, click Remove.
Using the API for Oracle Exadata Cloud@CustomerOracle Exadata Cloud@Customer uses the same API as Oracle Cloud Infrastructure.
For information about using the API and signing requests, see "REST APIs" and"Security Credentials". For information about SDKs, see "Software Development Kitsand Command Line Interface".
Use these API operations to manage Exadata Cloud@Customer infrastructure:
• ActivateExadataInfrastructure
• CreateExadataInfrastructure
• DeleteExadataInfrastructure
• DownloadExadataInfrastructureConfigFile
• GenerateRecommendedVmClusterNetwork
• GetExadataInfrastructure
• ListExadataInfrastructure
• UpdateExadataInfrastructure
Chapter 3Using the API for Oracle Exadata Cloud@Customer
3-15
Related Topics
• REST APIs
• Security Credentials
• Software Development Kits and Command Line Interface
• ActivateExadataInfrastructure
• CreateExadataInfrastructure
• DeleteExadataInfrastructure
• DownloadExadataInfrastructureConfigFile
• GenerateRecommendedVmClusterNetwork
• GetExadataInfrastructure
• ListExadataInfrastructure
• UpdateExadataInfrastructure
Chapter 3Using the API for Oracle Exadata Cloud@Customer
3-16
4Managing VM Clusters on ExadataCloud@Customer
Learn to manage virtual machine (VM) clusters on Exadata Cloud@Customer.
• About Managing VM Clusters on Exadata Cloud@CustomerThe VM cluster provides a link between your Exadata Cloud@Customerinfrastructure and Oracle Database.
• Required IAM Policy for Managing VM ClustersReview the identity access management (IAM) policy for managing virtual machine(VM) clusters on Oracle Exadata Cloud@Customer Systems.
• Prerequisites for VM Clusters on Exadata Cloud@CustomerTo connect to the VM cluster compute node, you use an SSH public key.
• Using the Console for VM Clusters on Exadata Cloud@CustomerLearn how to use the console to create, edit, download a configurationfile, validate, and terminate your infrastructure network, and manage yourinfrastructure for Oracle Exadata Cloud@Customer.
• Using the API for VM Clusters on Exadata Cloud@CustomerReview the list of API calls to manage your Exadata Cloud@Customer VM clusternetworks and VM clusters.
• Introduction to Scale Up or Scale Down OperationsWith the Multiple VMs per Exadata system (MultiVM) feature release, you canscale up or scale down your VM cluster resources.
About Managing VM Clusters on Exadata Cloud@CustomerThe VM cluster provides a link between your Exadata Cloud@Customer infrastructureand Oracle Database.
Before you can create any databases on your Exadata Cloud@Customerinfrastructure, you must create a VM cluster network, and you must associate it witha VM cluster. Each Exadata Cloud@Customer infrastructure deployment can supporteight VM cluster networks and associated VM clusters.
The VM cluster network specifies network resources, such as IP addresses andhost names, that reside in your corporate data center and are allocated to ExadataCloud@Customer. The VM cluster network includes definitions for the Exadata clientnetwork and the Exadata backup network. The client network and backup networkcontain the network interfaces that you use to connect to the VM cluster computenodes, and ultimately the databases that reside on those compute nodes.
The VM cluster provides a link between your Exadata Cloud@Customer infrastructureOracle Databases you deploy. The VM cluster contains an installation of OracleClusterware, which supports databases in the cluster. In the VM cluster definition, youalso specify the number of enabled CPU cores, which determines the amount of CPUresources that are available to your databases.
4-1
Note:
Avoid entering confidential information when assigning descriptions, tags,or friendly names to your cloud resources through the Oracle CloudInfrastructure Console, API, or CLI.
Required IAM Policy for Managing VM ClustersReview the identity access management (IAM) policy for managing virtual machine(VM) clusters on Oracle Exadata Cloud@Customer Systems.
A policy is an IAM document that specifies who has what type of access to yourresources. It is used in different ways: to mean an individual statement written inthe policy language; to mean a collection of statements in a single, named "policy"document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean theoverall body of policies your organization uses to control access to resources.
A compartment is a collection of related resources that can be accessed onlyby certain groups that have been given permission by an administrator in yourorganization.
To use Oracle Cloud Infrastructure, you must be given the required type of access ina policy written by an administrator, whether you're using the Console, or the RESTAPI with a software development kit (SDK), a command-line interface (CLI), or someother tool. If you try to perform an action, and receive a message that you don’thave permission, or are unauthorized, then confirm with your administrator the type ofaccess you've been granted, and which compartment you should work in.
For administrators: The policy in "Let database admins manage DB systems" lets thespecified group do everything with databases, and related database resources.
If you're new to policies, then see "Getting Started with Policies" and "CommonPolicies". If you want to dig deeper into writing policies for databases, then see "Detailsfor the Database Service".
Related Topics
• Let database admins manage DB systems
• Getting Started with Policies
• Common Policies
• Details for the Database Service
Prerequisites for VM Clusters on Exadata Cloud@CustomerTo connect to the VM cluster compute node, you use an SSH public key.
The public key is in OpenSSH format, from the key pair that you plan to use forconnecting to the VM cluster compute nodes through SSH. The following shows anexample of a public key, which is abbreviated for readability.
ssh-rsa AAAAB3NzaC1yc2EAAAABJQAA....lo/gKMLVM2xzc1xJr/Hc26biw3TXWGEakrK1OQ== rsa-key-20160304
Chapter 4Required IAM Policy for Managing VM Clusters
4-2
Related Topics
• Managing Key Pairs on Linux Instances
Using the Console for VM Clusters on ExadataCloud@Customer
Learn how to use the console to create, edit, download a configuration file, validate,and terminate your infrastructure network, and manage your infrastructure for OracleExadata Cloud@Customer.
• Using the Console to Create a VM Cluster NetworkTo create your VM cluster network with the Console, be prepared to provide valuesfor the fields required for configuring the infrastructure.
• Using the Console to Edit a VM Cluster NetworkYou can only edit a VM cluster network that is not associated with a VM cluster.
• Using the Console to Download a File Containing the VM Cluster NetworkConfiguration DetailsTo provide VM cluster network information to your network administrator, you candownload and supply a file containing the network configuration.
• Using the Console to Validate a VM Cluster NetworkYou can only validate a VM cluster network if its current state is RequiresValidation, and if the underlying Exadata infrastructure is activated.
• Using the Console to Terminate a VM Cluster NetworkBefore you can terminate a VM cluster network, you must first terminate theassociated VM cluster, if one exists, and all the databases it contains.
• Using the Console to Create a VM ClusterTo create your VM cluster, be prepared to provide values for the fields required forconfiguring the infrastructure.
• Using the Console to Scale the Resources on a VM ClusterStarting in Exadata Cloud@Customer Gen2, you can scale up or down multipleresources at the same time. You can also scale up or down resources one at atime.
• Using the Console to Stop, Start, or Reboot a VM Cluster Compute NodeUse the console or API calls to stop, start, or reboot a compute node.
• Using the Console to Check the Status of a VM Cluster Compute NodeReview the health status of a VM cluster compute node.
• Using the Console to Update the License Type on a VM ClusterTo modify licensing, be prepared to provide values for the fields required formodifying the licensing information.
• Using the Console to Move a VM Cluster to Another CompartmentTo change the compartment that contains your VM cluster on ExadataCloud@Customer, use this procedure.
• Using the Console to Terminate a VM clusterBefore you can terminate a VM cluster, you must first terminate the databases thatit contains.
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-3
Using the Console to Create a VM Cluster NetworkTo create your VM cluster network with the Console, be prepared to provide values forthe fields required for configuring the infrastructure.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the Exadata infrastructurefor which you want to create a VM cluster network.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure for which you want to create a VMcluster network.
The Infrastructure Details page displays information about the selected Exadatainfrastructure.
5. Click Create VM Cluster Network.
6. Provide the requested information in the Data Center Network Details page:
a. Provide the display name.
The display name is a user-friendly name that you can use to identify theVM cluster network. The name doesn't need to be unique because an OracleCloud Identifier (OCID) uniquely identifies the VM cluster network.
b. Provide client network details.
The client network is the primary channel for application connectivity toExadata Cloud@Customer resources. The following settings define therequired network parameters:
• VLAN ID: Provide a virtual LAN identifier (VLAN ID) for the client networkbetween 1 and 4094, inclusive. To specify no VLAN tagging, enter "1".(This is equivalent to a "NULL" VLAN ID tag value.)
Note:
The values "0" and "4095" are reserved and cannot be entered.
• CIDR Block: Using CIDR notation, provide the IP address range for theclient network.The following table specifies the maximum and recommended CIDR blockprefix lengths for each Exadata system shape. The maximum CIDR blockprefix length defines the smallest block of IP addresses that are requiredfor the network. To allow for possible future expansion within ExadataCloud@Customer, a smaller CIDR block prefix length is recommended,which reserves more IP addresses for the network.
Exadata System Shape Base System, QuarterRack, or Half Rack
Full Rack
Maximum CIDR blockprefix length
/28 /27
Recommended CIDRblock prefix length
/27 /26
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-4
• Netmask: Specify the IP netmask for the client network.
• Gateway: Specify the IP address of the client network gateway.
• Hostname Prefix: Specify the prefix that is used to generate thehostnames in the client network.
• Domain Name: Specify the domain name for the client network.
c. Provide backup network details.
The backup network is the secondary channel for connectivity to ExadataCloud@Customer resources. It is typically used to segregate applicationconnections on the client network from other network traffic. The followingsettings define the required network parameters:
• VLAN ID: Provide a virtual LAN identifier (VLAN ID) for the backupnetwork between 1 and 4094, inclusive. To specify no VLAN tagging, enter"1". (This is equivalent to a "NULL" VLAN ID tag value.)
Note:
The values "0" and "4095" are reserved, and cannot be entered.
• CIDR Block: Using CIDR notation, provide the IP address range for thebackup network.The following table specifies the maximum and recommended CIDR blockprefix lengths for each Exadata system shape. The maximum CIDR blockprefix length defines the smallest block of IP addresses that are requiredfor the network. To allow for possible future expansion within ExadataCloud@Customer, a smaller CIDR block prefix length is recommended,which reserves more IP addresses for the network.
Exadata System Shape Base System, QuarterRack, or Half Rack
Full Rack
Maximum CIDR blockprefix length
/29 /28
Recommended CIDRblock prefix length
/28 /27
• Netmask: Specify the IP netmask for the backup network.
• Gateway: Specify the IP address of the backup network gateway.
• Hostname Prefix: Specify the prefix that is used to generate thehostnames in the backup network.
• Domain Name: Specify the domain name for the backup network.
d. Provide DNS and NTP server details.
The VM cluster network requires access to Domain Names System (DNS)and Network Time Protocol (NTP) services. The following settings specify theservers that provide these services:
• DNS Servers: Provide the IP address of a DNS server that is accessibleusing the client network. You may specify up to three DNS servers.
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-5
• NTP Servers: Provide the IP address of an NTP server that is accessibleusing the client network. You may specify up to three NTP servers.
e. Configure Advanced Options.
Tags: (Optional) You can choose to apply tags. If you have permissions tocreate a resource, then you also have permissions to apply free-form tags tothat resource. To apply a defined tag, you must have permissions to use thetag namespace. For more information about tagging, refer to information aboutresource tags. If you are not sure if you should apply tags, then skip this option(you can apply tags later) or ask your administrator.
7. Click Review Configuration.
The Review Configuration page displays detailed information about the VM clusternetwork, including the hostname and IP address allocations. These allocations areinitially system-generated, and are based on your inputs to the Specify Parameterspage.
8. (Optional) You can choose to adjust the system-generated network definitions onthe Review Configuration page.
a. Click Edit IP Allocation.
b. Use the Edit dialog to adjust the system-generated network definitions to meetyour requirements.
c. Click Save Changes.
9. Click Create VM Cluster Network.
The VM Cluster Network Details page is now displayed. Initially after creation, thestate of the VM cluster network is Requires Validation.
Related Topics
• Resource Tags
Using the Console to Edit a VM Cluster NetworkYou can only edit a VM cluster network that is not associated with a VM cluster.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the Exadata infrastructurethat is associated with the VM cluster network that you want to edit.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that is associated with the VM clusternetwork that you are interested in.
The Infrastructure Details page displays information about the selected Exadatainfrastructure.
5. Click the name of the VM cluster network that you want to edit.
The VM Cluster Network Details page displays information about the selected VMcluster network.
6. Click Edit VM Cluster Network.
7. Use the Edit dialog to edit the VM cluster network attributes:
a. Client Network
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-6
The client network is the primary channel for application connectivity toExadata Cloud@Customer resources. You can edit the following clientnetwork settings:
• VLAN ID: Provide a virtual LAN identifier (VLAN ID) for the client networkbetween 1 and 4094, inclusive. To specify no VLAN tagging, enter "1".(This is equivalent to a "NULL" VLAN ID tag value.)
Note:
The values "0" and "4095" are reserved and cannot be entered.
• Netmask: Specify the IP netmask for the client network.
• Gateway: Specify the IP address of the client network gateway.
• Hostname: Specify the hostname for each address in the client network.
• IP Address: Specify the IP address for each address in the client network.
b. Backup Network
The backup network is the secondary channel for connectivity to ExadataCloud@Customer resources. It is typically used to segregate applicationconnections on the client network from other network traffic. You can edit thefollowing backup network settings:
• VLAN ID: Provide a virtual LAN identifier (VLAN ID) for the backupnetwork between 1 and 4094, inclusive. To specify no VLAN tagging, enter"1". (This is equivalent to a "NULL" VLAN ID tag value.)
Note:
The values "0" and "4095" are reserved and cannot be entered.
• Hostname: Specify the hostname for each address in the backupnetwork.
• IP Address: Specify the IP address for each address in the backupnetwork.
c. Configure DNS and NTP Servers
The VM cluster network requires access to Domain Names System (DNS) andNetwork Time Protocol (NTP) services. You can edit the following settings:
• DNS Servers: Provide the IP address of a DNS server that is accessibleusing the client network. You may specify up to three DNS servers.
• NTP Servers: Provide the IP address of an NTP server that is accessibleusing the client network. You may specify up to three NTP servers.
8. Click Save Changes.
After editing, the state of the VM cluster network is Requires Validation.
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-7
Using the Console to Download a File Containing the VM ClusterNetwork Configuration Details
To provide VM cluster network information to your network administrator, you candownload and supply a file containing the network configuration.
Use this procedure to download a configuration file that you can supply toyour network administrator. The file contains the information needed to configureyour corporate DNS and other network devices to work along with ExadataCloud@Customer.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the Exadata infrastructurethat is associated with the VM cluster network that you are interested in.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that is associated with the VM clusternetwork that you are interested in.
The Infrastructure Details page displays information about the selected Exadatainfrastructure.
5. Click the name of the VM cluster network for which you want to download a filecontaining the VM cluster network configuration details.
The VM Cluster Network Details page displays information about the selected VMcluster network.
6. Click Download Network Configuration.
Your browser downloads a file containing the VM cluster network configurationdetails.
Using the Console to Validate a VM Cluster NetworkYou can only validate a VM cluster network if its current state is Requires Validation,and if the underlying Exadata infrastructure is activated.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the Exadata infrastructurethat is associated with the VM cluster network that you want to validate.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that is associated with the VM clusternetwork that you are interested in.
The Infrastructure Details page displays information about the selected Exadatainfrastructure.
5. Click the name of the VM cluster network that you want to validate.
The VM Cluster Network Details page displays information about the selected VMcluster network.
6. Click Validate VM Cluster Network.
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-8
Validation performs a series of automated checks on the VM cluster network. TheValidate VM Cluster Network button is only available if the VM cluster networkrequires validation.
7. In the resulting dialog, click Validate to confirm the action.
After successful validation, the state of the VM cluster network changes toValidated and the VM cluster network is ready to use. If validation fails forany reason, examine the error message and resolve the issue before repeatingvalidation.
Using the Console to Terminate a VM Cluster NetworkBefore you can terminate a VM cluster network, you must first terminate theassociated VM cluster, if one exists, and all the databases it contains.
Terminating a VM cluster network removes it from the Cloud Control Plane.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the Exadata infrastructurethat is associated with the VM cluster network that you want to terminate.
3. Click Exadata Infrastructure.
4. Click the name of the Exadata infrastructure that is associated with the VM clusternetwork that you are interested in.
The Infrastructure Details page displays information about the selected Exadatainfrastructure.
5. Click the name of the VM cluster network that you want to terminate.
The VM Cluster Network Details page displays information about the selected VMcluster network.
6. Click Terminate.
7. In the resulting dialog, enter the name of the VM cluster network, and clickTerminate VM Cluster Network to confirm the action.
Using the Console to Create a VM ClusterTo create your VM cluster, be prepared to provide values for the fields required forconfiguring the infrastructure.
To create a VM cluster, ensure that you that have:
• Active Exadata infrastructure available to host the VM cluster.
• A validated VM cluster network available for the VM cluster to use.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region that contains your Exadata infrastructure.
3. Click VM Clusters.
4. Click Create VM Cluster.
5. Provide the requested information in the Create VM Cluster page:
a. Choose a compartment: From the list of available compartments, choose thecompartment that you want to contain the VM cluster.
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-9
b. Provide the display name: The display name is a user-friendly name thatyou can use to identify the VM cluster. The name doesn't need to be uniquebecause an Oracle Cloud Identifier (OCID) uniquely identifies the VM cluster.
c. Select Exadata Cloud@Customer Infrastructure: From the list, choose theExadata infrastructure to host the VM cluster. You are not able to create a VMcluster without available and active Exadata infrastructure.
d. Select a VM Cluster Network: From the list, choose a VM cluster networkdefinition to use for the VM cluster. You must have an available and validatedVM cluster network before you can create a VM cluster.
e. Choose the Oracle Grid Infrastructure version:From the list, choose the ofOracle Grid Infrastructure release that you want to install on the VM cluster.
The Oracle Grid Infrastructure release determines the Oracle Databasereleases that can be supported on the VM cluster. You cannot run an OracleDatabase release that is later than the Oracle Grid Infrastructure softwarerelease.
f. Specify the OCPU count per VM: Specify the OCPU count for eachindividual VM. The count must be a value greater than 2 and up to the numberof remaining unallocated CPU cores.
If you specify a value of zero, then the VM cluster compute nodes are allshut down at the end of the cluster creation process. In this case, you canlater start the compute nodes by scaling the CPU resources. See Using theConsole to Scale the Resources on a VM Cluster.
Otherwise, this value must be a multiple of the number of compute nodes sothat every compute node has the same number of CPU cores enabled.
g. Requested OCPU count for the VM Cluster: Displays the total number ofCPU cores allocated to the VM cluster based on the value you specified in theSpecify the OCPU count per VM field.
h. Specify the memory per VM (GB): Specify the memory for each individualVM. The value must be a multiple of 1 GB and is limited by the availablememory on the Exadata infrastructure.
i. Requested memory for the VM Cluster (GB): Displays the total amount ofmemory allocated to the VM cluster based on the value you specified in theSpecify the memory per VM (GB) field.
j. Specify the local file system size per VM (GB): Specify the size for eachindividual VM. The value must be a multiple of 1 GB and is limited by theavailable size of the file system on the X8-2 and X7-2 infrastructures.
Note that the minimum size of local system storage must be 60 GB. Eachtime when you create a new VM cluster, the space remaining out of the totalavailable space is utilized for the new VM cluster.
For more information and instructions to specify the size for each individualVM, see Introduction to Scale Up or Scale Down Operations.
k. Reserved local storage per VM (GB): Displays the size reserved internallyfor root file systems, Oracle Grid Infrastructure Homes, and diagnostic logs.
l. Configure the Exadata Storage: The following settings define how theExadata storage is configured for use with the VM cluster. These settingscannot be changed after creating the VM cluster. See also StorageConfiguration.
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-10
• Specify Usable Exadata Storage: Specify the size for each individualVM. The minimum recommended size is 2 TB.
• Allocate Storage for Exadata Snapshots: Check this option to createa sparse disk group, which is required to support Exadata snapshotfunctionality. Exadata snapshots enable space-efficient clones of Oracledatabases that can be created and destroyed very quickly and easily.
• Allocate Storage for Local Backups: Check this option to configurethe Exadata storage to enable local database backups. If you select thisoption, more space is allocated to the RECO disk group to accommodatethe backups. If you do not select this option, you cannot use local Exadatastorage as a backup destination for any databases in the VM cluster.
m. Add SSH Key: Specify the public key portion of an SSH key pair that youwant to use to access the VM cluster compute nodes. You can upload a filecontaining the key, or paste the SSH key string.
To provide multiple keys, upload multiple key files or paste each key intoa separate field. For pasted keys, ensure that each key is on a single,continuous line. The length of the combined keys cannot exceed 10,000characters.
n. Choose a license type:
• Bring Your Own License (BYOL): Select this option if your organizationalready owns Oracle Database software licenses that you want to use onthe VM cluster.
• License Included: Select this option to subscribe to Oracle Databasesoftware licenses as part of Exadata Cloud@Customer.
o. Show Advanced Options:
• Time zone: The default time zone for the Exadata Infrastructure is UTC,but you can specify a different time zone. The time zone options are thosesupported in both the Java.util.TimeZone class and the Oracle Linuxoperating system.
Note:
If you want to set a time zone other than UTC or the browser-detected time zone, then select the Select another timezone option, select a Region or country, and then select thecorresponding Time zone.
If you do not see the region or country you want, then selectMiscellaneous, and then select an appropriate Time zone.
• Tags: Optionally, you can apply tags. If you have permissions to createa resource, you also have permissions to apply free-form tags to thatresource. To apply a defined tag, you must have permissions to use thetag namespace. For more information about tagging, see Resource Tags.If you are not sure if you should apply tags, skip this option (you can applytags later) or ask your administrator.
6. Click Create VM Cluster.
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-11
The VM Cluster Details page is now displayed. While the creation process isrunning, the state of the VM cluster is Pending. When the VM cluster creationprocess completes, the state of the VM cluster changes to Available.
Related Topics
• Plan Your Configuration Settings on Storage
• Using the Console to Scale the Resources on a VM ClusterStarting in Exadata Cloud@Customer Gen2, you can scale up or down multipleresources at the same time. You can also scale up or down resources one at atime.
• Resource Tags
Using the Console to Scale the Resources on a VM ClusterStarting in Exadata Cloud@Customer Gen2, you can scale up or down multipleresources at the same time. You can also scale up or down resources one at a time.
Why should I scale down the resources?
• Use Case 1: If you have allocated all of the resources to one virtual machine,and if you want to create multiple virtual machines, then there wouldn't be anyresources available to allocate the new virtual machine. So scale down theresources as needed before you can create any additional virtual machines.
• Use Case 2: If you want to allocate different resources based on the workload,then scale down or scale up accordingly. For example, you may want to run nightlybatch jobs for reporting/ETL and scale down the VM once the job is over.
How long it takes to scale down the resources?
As part of scale down, you can scale down any combinations of the followingresources:
• OCPU
• Memory
• Local storage
• Exadata storage
Each individual operation can take approximately 15 minutes and all the operationsrun in a series if multiple scale down is executed. For example, scale down Memoryand Local Storage from the Console. In general, local storage and memory scale downtakes more time than the other two.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the VM cluster for which youwant to scale the CPU resources.
3. Click VM Clusters.
4. Click the name of the VM cluster for which you want to scale the CPU resources.
The VM Cluster Details page displays information about the selected VM cluster.
5. Click Scale Up/Down.
6. In the dialog box, adjust any or all of the following:
• OCPU Count:
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-12
The OCPU Count value must be a multiple of the number of compute nodesso that every compute node has the same number of CPU cores enabled.
If you set the OCPU Count to zero, then the VM cluster compute nodes areall shut down. If you change from a zero setting, then the VM cluster computenodes are all started. Otherwise, modifying the number of enabled CPU coresis an online operation, and compute nodes are not rebooted because of thisoperation. See also System Configuration.
Note:
If you have explicitly set the CPU_COUNT database initializationparameter, that setting is not affected by modifying the number ofCPU cores that are allocated to the VM cluster. Therefore, if youhave enabled the Oracle Database instance caging feature, thedatabase instance does not use extra CPU cores until you alterthe CPU_COUNT setting. If CPU_COUNT is set to 0 (the default setting),then Oracle Database continuously monitors the number of CPUsreported by the operating system and uses the current count.
• Memory:Specify the memory for each individual VM. The value must be a multiple of 1GB and is limited by the available memory on the Exadata infrastructure.
When you scale up or down the memory, the associated compute nodes arerebooted in a rolling manner one compute node at a time to minimize theimpact on the VM cluster.
• Local file system size:Specify the size for each individual VM. The value must be a multiple of 1GB and is limited by the available size of the file system on the Exadatainfrastructure.
When you scale up or down the local file system size, the associated computenodes are rebooted in a rolling manner one compute node at a time tominimize the impact on the VM cluster.
Reserved local storage per VM (GB): Displays the size reserved internallyfor root file systems, Oracle Grid Infrastructure Homes, and diagnostic logs.
• Usable Exadata storage size:Specify the total amount of Exadata storage that is allocated to the VM cluster.This storage is allocated evenly from all of the Exadata Storage Servers. Theminimum recommended size is 2 TB.
You may reduce the Exadata storage allocation for a VM cluster. However, youmust ensure that the new amount covers the existing contents, and you shouldalso allow for anticipated data growth.
Note:
When you downsize, the new size must be at least 15% more thanthe currently used size.
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-13
Modifying the Exadata storage allocated to the VM cluster is an onlineoperation. Compute nodes are not rebooted because of this operation.
7. . Click Save Changes.
Related Topics
• System Configuration Options for Oracle Exadata Cloud@Customer
Using the Console to Stop, Start, or Reboot a VM Cluster ComputeNode
Use the console or API calls to stop, start, or reboot a compute node.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that is associated with the VM cluster thatcontains the compute node that you want to stop, start, or reboot.
3. Click VM Clusters.
4. Click the name of the VM cluster that contains the compute node that you want tostop, start, or reboot.
The VM Cluster Details page displays information about the selected VM cluster.
5. In the Resources list, click Nodes.
The list of compute nodes is displayed.
6. In the list of nodes, click the Actions icon (three dots) for a node, and then clickone of the following actions:
a. Start: Restarts a stopped node. After the node is restarted, the Stop action isenabled.
b. Stop: Shuts down the node. After the node is stopped, the Start action isenabled.
c. Reboot: Shuts down the node, and then restarts it.
Using the Console to Check the Status of a VM Cluster ComputeNode
Review the health status of a VM cluster compute node.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that is associated with the VM cluster thatcontains the compute node that you are interested in.
3. Click VM Clusters.
4. Click the name of the VM cluster that contains the compute node that you areinterested in.
The VM Cluster Details page displays information about the selected VM cluster.
5. In the Resources list, click Nodes.
The list of compute nodes displays. For each compute node in the VM cluster, thename, state, and client IP address are displayed.
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-14
6. In the node list, find the compute node that you are interested in and check itsstate.
The color of the icon and the associated text it indicates its status.
• Available: Green icon. The node is operational.
• Starting: Yellow icon. The node is starting because of a start or reboot actionin the Console or API.
• Stopping: Yellow icon. The node is stopping because of a stop or rebootaction in the Console or API.
• Stopped: Yellow icon. The node is stopped.
• Failed: Red icon. An error condition prevents the continued operation of thecompute node.
Using the Console to Update the License Type on a VM ClusterTo modify licensing, be prepared to provide values for the fields required for modifyingthe licensing information.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the VM cluster for which youwant to update the license type.
3. Click VM Clusters.
4. Click the name of the VM cluster for which you want to update the license type.
The VM Cluster Details page displays information about the selected VM cluster.
5. Click Update License Type.
6. In the dialog box, choose one of the following license types and then click SaveChanges.
• Bring Your Own License (BYOL): Select this option if your organizationalready owns Oracle Database software licenses that you want to use on theVM cluster.
• License Included: Select this option to subscribe to Oracle Databasesoftware licenses as part of Exadata Cloud@Customer.
Updating the license type does not change the functionality or interrupt theoperation of the VM cluster.
Using the Console to Move a VM Cluster to Another CompartmentTo change the compartment that contains your VM cluster on ExadataCloud@Customer, use this procedure.
When you move a VM cluster, the compartment change is also applied to thecompute nodes and databases that are associated with the VM cluster. However,the compartment change does not affect any other associated resources, such as theExadata infrastructure, which remains in its current compartment.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the VM cluster that you wantto move.
Chapter 4Using the Console for VM Clusters on Exadata Cloud@Customer
4-15
3. Click VM Clusters.
4. Click the name of the VM cluster that you want to move.
The VM Cluster Details page displays information about the selected VM cluster.
5. Click Move Resource.
6. In the resulting dialog, choose the new compartment for the VM cluster, and clickMove Resource.
Using the Console to Terminate a VM clusterBefore you can terminate a VM cluster, you must first terminate the databases that itcontains.
Terminating a VM cluster removes it from the Cloud Control Plane. In the process, thecompute node VMs and their contents are destroyed.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the VM cluster that you wantto terminate.
3. Click VM Clusters.
4. Click the name of the VM cluster that you want to terminate.
The VM Cluster Details page displays information about the selected VM cluster.
5. Click Terminate.
6. In the resulting dialog, enter the name of the VM cluster, and click Terminate VMCluster to confirm the action.
Using the API for VM Clusters on ExadataCloud@Customer
Review the list of API calls to manage your Exadata Cloud@Customer VM clusternetworks and VM clusters.
For information about using the API and signing requests, see "REST APIs" and"Security Credentials". For information about SDKs, see "Software Development Kitsand Command Line Interface".
Use these API operations to manage Exadata Cloud@Customer VM cluster networksand VM clusters:
VM cluster networks:
• GenerateRecommendedVmClusterNetwork
• CreateVmClusterNetwork
• DeleteVmClusterNetwork
• GetVmClusterNetwork
• ListVmClusterNetwork
• UpdateVmClusterNetwork
• ValidateVmClusterNetwork
Chapter 4Using the API for VM Clusters on Exadata Cloud@Customer
4-16
VM clusters:
• CreateVmCluster
• DeleteVmCluster
• GetVmCluster
• ListVmCluster
• UpdateVmCluster
For the complete list of APIs, see "Database Service API".
Related Topics
• REST APIs
• Security Credentials
• Software Development Kits and Command Line Interface
• GenerateRecommendedVmClusterNetwork
• CreateVmClusterNetwork
• DeleteVmClusterNetwork
• GetVmClusterNetwork
• ListVmClusterNetwork
• UpdateVmClusterNetwork
• ValidateVmClusterNetwork
• CreateVmCluster
• DeleteVmCluster
• GetVmCluster
• ListVmCluster
• UpdateVmCluster
• Database Service API
Introduction to Scale Up or Scale Down OperationsWith the Multiple VMs per Exadata system (MultiVM) feature release, you can scale upor scale down your VM cluster resources.
• Scaling Up or Scaling Down the VM Cluster Resources
• Calculating the Minimum Required Memory
• Calculating the ASM Storage
• Estimating How Much Local Storage You Can Provision to Your VMs
• Scaling Local Storage Down
Scaling Up or Scaling Down the VM Cluster Resources
Chapter 4Introduction to Scale Up or Scale Down Operations
4-17
You can scale up or scale down the memory, local disk size (/u02), ASM Storage,and CPUs. Scaling up or down of these resources requires thorough auditing ofexisting usage and capacity management by the customer DB administrator. Reviewthe existing usage to avoid failures during or after a scale down operation. Whilescaling up, consider how much of these resources are left for the next VM cluster youare planning to create. Exadata Cloud@Customer Cloud tooling calculates the currentusage of memory, local disk, and ASM storage in the VM cluster, adds headroom toit, and arrives at a "minimum" value below which you cannot scale down, and expectsthat you specify the value below this minimum value.
Note:
For memory and /u02 scale up or scale down operations, if the differencebetween the current value and the new value is less than 2%, then nochange will be made to that VM. This is because memory change involvesrebooting the VM, and /u02 change involves bringing down the Oracle GridInfrastructure stack and un-mounting /u02. Productions customers will notresize for such a small increase or decrease, and hence such requests are ano-op.
Calculating the Minimum Required Memory
Cloud tooling provides dbaasapi to identify the minimum required memory. As rootuser, you have to run dbaasapi and pass a JSON file with sample content as follows.The only parameter that you need to update in the input.json is new_mem_size,which is the new memory to which you want the VM Cluster to be re-sized.
Copy# cat input.json{"object": "db","action": "get","operation": "precheck_memory_resize","params": {"dbname": "grid","new_mem_size" : "30 gb","infofile": "/tmp/result.json"},"outputfile": "/tmp/info.out","FLAGS": ""}# dbaasapi -i input.json# cat /tmp/result.json{"is_new_mem_sz_allowed" : 0,"min_req_mem" : 167}
The result indicates that 30 GB is not sufficient and the minimum required memoryis 167 GB, and that is the maximum you can reshape down to. On a safer side, you
Chapter 4Introduction to Scale Up or Scale Down Operations
4-18
must choose a value greater than 167 GB, as there could be fluctuations of that orderbetween this calculation and the next reshape attempt.
Calculating the ASM Storage
Use the following formula to calculate the minimum required ASM storage:
• For each disk group, for example, DATA, RECO, note the total size and free size byrunning the asmcmd lsdg command on any domU of the VM cluster.
• Calculate the used size as (Total size - Free size) / 3 for each disk group. The /3 isused because the disk groups are triple mirrored.
• DATA:RECO ratio is:
80:20 if Local Backups option was NOT selected in the user interface.
40:60 if Local Backups option was selected in the user interface.
• Ensure that the new total size as given in the user interface passes the followingconditions:Used size for DATA * 1.15 <= (New Total size * DATA % )
Used size for RECO * 1.15 <= (New Total size * RECO % )
Example 4-1 Calculating the ASM Storage
1. Run the asmcmd lsdg command in the domU:
• Without SPARSE:
[root@scaqak01dv0305 ~]# /u01/app/19.0.0.0/grid/bin/asmcmd lsdgASMCMD>State Type Rebal Sector Logical_Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files NameMOUNTED HIGH N 512 512 4096 4194304 12591936 10426224 1399104 3009040 0 Y DATAC5/MOUNTED HIGH N 512 512 4096 4194304 3135456 3036336 348384 895984 0 N RECOC5/ASMCMD>
• With SPARSE:
[root@scaqak01dv0305 ~]# /u01/app/19.0.0.0/grid/bin/asmcmd lsdgASMCMD>State Type Rebal Sector Logical_Sector Block AU Total_MB Free_MB Req_mir_free_MB Usable_file_MB Offline_disks Voting_files NameMOUNTED HIGH N 512 512 4096 4194304 12591936 10426224 1399104 3009040 0 Y DATAC5/MOUNTED HIGH N 512 512 4096 4194304 3135456 3036336 348384 895984 0 N RECOC5/MOUNTED HIGH N 512 512 4096 4194304
Chapter 4Introduction to Scale Up or Scale Down Operations
4-19
31354560 31354500 3483840 8959840 0 N SPRC5/ASMCMD>
Note:
The listed values of all attributes for SPARSE diskgroup(SPRC5) present the virtual size. In Exadata DB Systemsand Exadata Cloud@Customer, we use the ratio of 1:10 forphysicalSize:virtualSize. Hence, for all purposes of our calculationwe must use 1/10th of the values displayed above in case of SPARSEfor those attributes.
2. Used size for a disk group = (Total_MB - Free_MB) /3
• Without SPARSE:Used size for DATAC5 = (12591936 - 10426224 ) / 3 = 704.98 GB
Used size for RECO5 = (3135456 - 3036336 ) / 3 = 32.26 GB
• With SPARSE:Used size for DATAC5 = (12591936 - 10426224 ) / 3 ~= 704.98 GB
Used size for RECO5 = (3135456 - 3036336 ) /3 ~= 32.26 GB
Used size for SPC5 = (1/10 * (31354560 - 31354500)) / 3 ~= 0 GB
3. Storage distribution among diskgroups
• Without SPARSE:DATA:RECO ratio is 80:20 in this example.
• With SPARSE:DATA RECO: SPARSE ratio is 60:20:20 in this example.
4. New requested size should pass the following conditions:
• Without SPARSE: (For example, 5 TB in user interface.)5 TB = 5120 GB ; 5120 *.8 = 4096 GB; 5120 *.2 = 1024 GB
For DATA: (704.98 * 1.15 ) <= 4096 GB
For RECO: (32.36 * 1.15) <= 1024 GB
• With SPARSE: (For example, 8 TB in the user interface.)8 TB = 8192 GB; 8192 *.6 = 4915 GB; 8192 *.2 = 1638 GB; 8192 *.2 = 1638GB
For DATA: (704.98 * 1.15 ) <= 4915 GB
For RECO: (32.36 * 1.15) <= 1638 GB
For SPR: (0 * 1.15) <= 1638 GB
Above resize will go through. If above conditions are not met by the new size, thenresize will fail the precheck.
Estimating How Much Local Storage You Can Provision to Your VMs
X8-2 and X7-2 Systems
Chapter 4Introduction to Scale Up or Scale Down Operations
4-20
You specify how much space is provisioned from local storage to each VM. This spaceis mounted at location /u02, and is used primarily for Oracle Database homes. Theamount of local storage available will vary with the number of virtual machines runningon each physical node, as each VM requires a fixed amount of storage (137 GB) forthe root file systems, GI homes, and diagnostic log space. Refer to the table belowto see the maximum amount of space available to provision to local storage (/u02)across all VMs.
Total space available to all VMs on an ExaCC X7 node is 1237 GB. Total spaceavailable to all VMs on a ExaCC X8 database node is 1037 GB.
Table 4-1 Space allocated to VMs
#VMs Space Consumed byVM Image or GI
X8-2 Space forALL /u02 (GB)
X7-2 Space forALL /u02 (GB)
1 137 900 1100
2 274 763 963
3 411 626 826
4 548 489 689
5 685 352 552
6 822 N/A 415
For an X8-2, to get the max space available for the nth VM, take the number in thetable above and subtract anything previously allocated for /u02 to the other VMs. So ifyou allocated 60 GB to VM1, 70 GB to VM2, 80 GB to VM3, 60 GB to VM4 (total 270GB) in an X8-2, the maximum available for VM 5 would be 352 - 270 = 82 GB.
In ExaCC Gen 2, we require a minimum of 60 GB per /u02, so with that minimum sizethere is a maximum of 5 VMs in X8-2 and 6 VMs in X7-2.
X8M-2 Systems
The maximum number of VMs for an X8M-2 will be 8, regardless of whether there islocal disk space or other resources available.
For an X8M-2 system, the fixed consumption per VM is 160 GB.
Total space available to all VMs on an ExaCC X8M databases node is 2500 GB.Although there is 2500 GB per database node, with a single VM, you can allocate amaximum of 900 GB local storage. Similarly, for the second VM, there is 1800 GB localstorage available given the max limit of 900 GB per VM. With the third VM, the amountof space available is 2500 - (160Gb * 3) = 2020 GB. And so on for 4 and more VMs.
Table 4-2 Space allocated to VMs
#VMs Space Consumed by VMImage or GI
X8M-2 Quarter/Half/FullRack Space for All /u02(GB)*
1 160 900
2 320 1800
3 480 2020
4 640 1860
Chapter 4Introduction to Scale Up or Scale Down Operations
4-21
Table 4-2 (Cont.) Space allocated to VMs
#VMs Space Consumed by VMImage or GI
X8M-2 Quarter/Half/FullRack Space for All /u02(GB)*
5 800 1700
6 960 1540
7 1120 1380
8 1280 1220
*Max 900 GB per VM
For an X8M-2, to get the max space available for the nth VM, take the number in thetable above and subtract anything previously allocated for /u02 to the other VMs. So,for a quarter and larger rack, if you allocated 60 GB to VM1, 70 GB to VM2, 80 GBto VM3, 60 GB to VM4 (total 270 GB) in an X8M-2, the maximum available for VM 5would be 1700 - 270 = 1430 GB. However, the per VM maximum is 900 GB, so thatwould take precedent and limits VM5 to 900 GB.
Scaling Local Storage Down
Scale Down Local Space Operation Guidelines
Scale down operation expects you to input local space value that you want each nodeto scale down to.
• Resource Limit Based On Recommended MinimumsScale down operation must meet 60 GB recommended minimum size requirementfor local storage.
• Resource Limit Based On Current UtilizationThe scale down operation must leave 15% buffer on top of highest local spaceutilization across all nodes in the cluster.
The lowest local space per node allowed is higher of the above two limits.
Run df –kh command on each node to find out the node with the highest localstorage.
You can also use the utility like cssh to issue the same command from all hosts in acluster by typing it just once.
Lowest value of local storage each node can be scaled down to would be = 1.15x(highest value of local space used among all nodes).
Chapter 4Introduction to Scale Up or Scale Down Operations
4-22
5Managing Backup Destinations for ExadataCloud@Customer
Learn to manage backup destinations for Exadata Cloud@Customer on Oracle ZeroData Loss Recovery Appliance or Network File System (NFS).
• About Managing Backup Destinations for Exadata Cloud@CustomerFor backups, you can either use the Exadata Cloud@Customer backup facility, oryou can configure a backup location on a location you manage.
• Required IAM Policy for Backup DestinationsReview the identity access management (IAM) policy for backup destinations forOracle Exadata Cloud@Customer Systems.
• Prerequisites for Backup Destinations for Exadata Cloud@CustomerTo configure backup destinations on a Zero Data Loss Recovery Appliancelocation, or an NFS backup location, review the prerequisites.
• Using the Console for Backup Destinations for Exadata Cloud@CustomerLearn how to use the console to create, edit, move, and terminate a backupdestination for your infrastructure for Oracle Exadata Cloud@Customer.
• Using the API for Backup Destinations for Exadata Cloud@CustomerReview the list of API calls to manage your Exadata Cloud@Customer backupdestinations.
About Managing Backup Destinations for ExadataCloud@Customer
For backups, you can either use the Exadata Cloud@Customer backup facility, or youcan configure a backup location on a location you manage.
Exadata Cloud@Customer provides a backup facility, which you can configureindividually on each database. See: "Managing Databases on ExadataCloud@Customer" and "Managing Database Backup and Recovery on ExadataCloud@Customer".
If you want to store backups on a Recovery Appliance, or on a network file storage(NFS) location that you manage, then you must first create a backup destination. Eachbackup destination defines the properties that are required to connect to the RecoveryAppliance or NFS location, and each backup destination must be accessible in yourdata center from the VM cluster nodes.
The Exadata Cloud@Customer backup facility can also store backups on OracleCloud Infrastructure object storage, or on local Exadata storage on your ExadataCloud@Customer system. However, you do not need to create a backup destinationfor any of these other locations. Instead, applicable options for backup to cloud objectstorage or local Exadata storage are available directly when you create a database.
5-1
Note:
Avoid entering confidential information when assigning descriptions, tags,or friendly names to your cloud resources through the Oracle CloudInfrastructure Console, API, or CLI.
Related Topics
• Managing Oracle Databases on Oracle Exadata Cloud@Customer
• Managing Database Backup and Recovery on Oracle Exadata Cloud@Customer
Required IAM Policy for Backup DestinationsReview the identity access management (IAM) policy for backup destinations forOracle Exadata Cloud@Customer Systems.
A policy is An IAM document that specifies who has what type of access to yourresources. It is used in different ways: to mean an individual statement written inthe policy language; to mean a collection of statements in a single, named "policy"document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean theoverall body of policies your organization uses to control access to resources.
A compartment is a collection of related resources that can be accessed onlyby certain groups that have been given permission by an administrator in yourorganization.
To use Oracle Cloud Infrastructure, you must be given the required type of access ina policy written by an administrator, whether you're using the Console, or the RESTAPI with a software development kit (SDK), a command-line interface (CLI), or someother tool. If you try to perform an action, and receive a message that you don’thave permission, or are unauthorized, then confirm with your administrator the type ofaccess you've been granted, and which compartment you should work in.
For administrators: The policy in "Let database admins manage DB systems" lets thespecified group do everything with databases, and related database resources.
If you're new to policies, then see "Getting Started with Policies" and "CommonPolicies". If you want to dig deeper into writing policies for databases, then see "Detailsfor the Database Service".
Related Topics
• Let database admins manage DB systems
• Getting Started with Policies
• Common Policies
• Details for the Database Service
Chapter 5Required IAM Policy for Backup Destinations
5-2
Prerequisites for Backup Destinations for ExadataCloud@Customer
To configure backup destinations on a Zero Data Loss Recovery Appliance location, oran NFS backup location, review the prerequisites.
• For a Zero Data Loss Recovery Appliance backup destination:
– The appliance must be configured with a virtual private catalog (VPC) user,which is used for taking the backups.
– The appliance must be configured with the unique database name of thedatabase being backed up, and a mapping to the VPC user.
– The appliance must be accessible from the Exadata Cloud@Customer systemusing the Oracle Net Services connection string, which is provided by the ZeroData Loss Recovery Appliance administrator.
• For an NFS backup destination:
– Exadata Cloud@Customer non-autonomous databases:
* You must mount the NFS server location to a local mount point directoryon each node in the VM cluster.
* The local directory path and the NFS server location must each be thesame across all of the VM cluster nodes.
* You must ensure that the NFS mount is maintained continuously on all ofthe VM cluster nodes.
* The NFS-mounted file system must be readable and writable by theoracle operating system user on all of the VM cluster nodes.
– Exadata Cloud@Customer Autonomous Databases:
* Ensure that the NFS server is accessible from the Autonomous VM clusterover the IP addresses that you have specified.
* The NFS-mounted file system must be readable and writable by theoracle operating system user on all of the VM cluster nodes.
Using the Console for Backup Destinations for ExadataCloud@Customer
Learn how to use the console to create, edit, move, and terminate a backupdestination for your infrastructure for Oracle Exadata Cloud@Customer.
• Using the Console to Create a Backup DestinationTo create a backup destination, be prepared to provide values for the backupdestination configuration.
• Using the Console to Edit a Backup DestinationTo edit a backup destination, be prepared to provide values for the backupdestination configuration.
Chapter 5Prerequisites for Backup Destinations for Exadata Cloud@Customer
5-3
• Using the Console to Move a Backup Destination to Another CompartmentTo move a backup destination, be prepared to provide values for the backupdestination configuration.
• Using the Console to Terminate a Backup DestinationTo terminate a backup destination, be prepared to provide values for the backupdestination configuration.
Using the Console to Create a Backup DestinationTo create a backup destination, be prepared to provide values for the backupdestination configuration.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region that contains your Exadata infrastructure.
3. Click Backup Destinations.
4. Click Create Backup Destination.
5. Provide the requested information in the Create Backup Destination page:
a. Choose a compartment.
From the list of available compartments, choose the compartment that youwant to contain the backup destination.
b. Name your backup destination.
Specify a user-friendly name that you can use to identify the backupdestination. The name doesn't need to be unique because an Oracle CloudIdentifier (OCID) uniquely identifies the backup destination.
c. Choose either a Zero Data Loss Recovery Appliance or a network file system(NFS) backup destination.
Select Recovery Appliance or Network Storage (NFS).
• If you select Recovery Appliance, then you must also specify thefollowing for Zero Data Loss Recovery Appliance:
– Provide the Recovery Appliance connection string: Specify theOracle Net Services connection string that connects to the appliance.This information is typically provided by the Zero Data Loss RecoveryAppliance administrator.
– Provide the Virtual Private Catalog (VPC) Users: Provide a VPCuser name for connecting to the Zero Data Loss Recovery Appliance.You can specify multiple VPC user names in case you want to usethe appliance as a backup destination for multiple databases. Thisinformation is typically provided by the Zero Data Loss RecoveryAppliance administrator.
• If you select Network Storage (NFS), then you must also specify thefollowing:
– Self-mount for non-autonomous databases:
Provide the local NFS mount point path: Specify the local directorypath on each VM cluster node where the NFS server location ismounted. The local directory path and the NFS server location musteach be the same across all of the VM cluster nodes.
Chapter 5Using the Console for Backup Destinations for Exadata Cloud@Customer
5-4
– Auto-mount for Autonomous Databases:
Use this destination for Autonomous Databases:
* NFS server: Specify the IP address of the NFS server. Optionally,you can specify up to four IP addresses.
* NFS export share: Specify the directory path where the exportedfile system is mounted.
d. Configure Advanced Options.
• Tags: (Optional) You can choose to apply tags. If you have permissionsto create a resource, then you also have permissions to apply free-formtags to that resource. To apply a defined tag, you must have permissionsto use the tag namespace. For more information about tagging, referto information about resource tags. If you are not sure if you shouldapply tags, then skip this option (you can apply tags later), or ask youradministrator.
6. Click Create Backup Destination.
The Backup Destination Details page displays the newly created backupdestination.
Related Topics
• Resource Tags
Using the Console to Edit a Backup DestinationTo edit a backup destination, be prepared to provide values for the backup destinationconfiguration.
You can only edit a backup destination if it is not currently associated with database.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the backup destination thatyou want to edit.
3. Click Backup Destinations.
4. Click the name of the backup destination that you want to edit.
The Backup Destination Details page displays information about the selectedbackup destination.
5. Click Edit.
6. Use the Edit Backup Destination dialog to edit the backup destination attributes:
Note:
You cannot edit a Backup Destination if there is already a databaseattached to it.
• If you are editing a Zero Data Loss Recovery Appliance backup destination:
– Provide the Recovery Appliance connection string: Specify the OracleNet Services connection string that connects to the Recovery Appliance.
Chapter 5Using the Console for Backup Destinations for Exadata Cloud@Customer
5-5
This information is typically provided by the Recovery Applianceadministrator.
– Provide the Virtual Private Catalog (VPC) Users: Provide a VPC username for connecting to the Recovery Appliance. You can specify multipleVPC user names in case you want to use the Recovery Appliance asa backup destination for multiple databases. This information is typicallyprovided by the Recovery Appliance administrator.
• If you are editing an NFS backup destination:
– Self-mount for non-autonomous databases:
Provide the local NFS mount point path: Specify the local directory pathon each VM cluster node where the NFS server location is mounted. Thelocal directory path and the NFS server location must each be the sameacross all of the VM cluster nodes.
– Auto-mount for Autonomous Databases:
Use this destination for Autonomous Databases:
* NFS server: Specify the IP address of the NFS server. Optionally, youcan specify up to four IP addresses.
* NFS export share: Specify the directory path where the exported filesystem is mounted.
7. Click Save Changes.
Using the Console to Move a Backup Destination to AnotherCompartment
To move a backup destination, be prepared to provide values for the backupdestination configuration.
You can change the compartment that contains your backup destination by moving it.
When you move a backup destination, the compartment change does not affect otherassociated resources. These other resources, such as the associated databases,remain in their current compartment.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the backup destination thatyou want to move.
3. Click Backup Destinations.
4. Click the name of the backup destination that you want to move.
The Backup Destination Details page displays information about the selectedbackup destination.
5. Click Move Resource.
6. In the resulting dialog, choose the new compartment for the backup destinationand click Move Resource.
Chapter 5Using the Console for Backup Destinations for Exadata Cloud@Customer
5-6
Using the Console to Terminate a Backup DestinationTo terminate a backup destination, be prepared to provide values for the backupdestination configuration.
Terminating a backup destination removes it from the Cloud Control Plane. Before youcan terminate a backup destination, you must ensure that it is not associated with anydatabases.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the backup destination thatyou want to terminate.
3. Click Backup Destinations.
4. Click the name of the backup destination that you want to terminate.
The Backup Destination Details page displays information about the selectedbackup destination.
5. Click Terminate.
6. In the resulting dialog, enter the backup destination name and click TerminateBackup Destination to confirm the action.
Using the API for Backup Destinations for ExadataCloud@Customer
Review the list of API calls to manage your Exadata Cloud@Customer backupdestinations.
For information about using the API and signing requests, see "REST APIs" and"Security Credentials". For information about SDKs, see "Software Development Kitsand Command Line Interface".
Use these API operations to manage Exadata Cloud@Customer backup destinations:
• CreateBackupDestination
• DeleteBackupDestination
• GetBackupDestination
• ListBackupDestination
• UpdateBackupDestination
• ChangeBackupDestinationCompartment
For the complete list of APIs, see "Database Service API".
Related Topics
• REST APIs
• Security Credentials
• Software Development Kits and Command Line Interface
• CreateBackupDestination
Chapter 5Using the API for Backup Destinations for Exadata Cloud@Customer
5-7
• DeleteBackupDestination
• GetBackupDestination
• ListBackupDestination
• UpdateBackupDestination
• ChangeBackupDestinationCompartment
• Database Service API
Chapter 5Using the API for Backup Destinations for Exadata Cloud@Customer
5-8
6Creating Oracle Database Homes on anExadata Cloud@Customer System
Learn to create Oracle Database Homes on Exadata Cloud@Customer.
• About Creating Oracle Database Homes on an Exadata Cloud@Customer SystemYou can add Oracle Database homes (referred to as Database Homes inOracle Cloud Infrastructure) to an existing VM cluster by using the Oracle CloudInfrastructure Console, the API, or the CLI.
• Required IAM Policy for Creating Oracle Database HomesReview the identity access management (IAM) policy for creating Oracle Databasehomes on Oracle Exadata Cloud@Customer Systems.
• Using the Console to Create Oracle Database Home on ExadataCloud@CustomerTo create an Oracle Database home in an existing VM cluster with the Console, beprepared to provide values for the fields required.
• Using the API for Creating Oracle Database Home on Exadata Cloud@CustomerTo create an Oracle Database home, review the list of API calls.
About Creating Oracle Database Homes on an ExadataCloud@Customer System
You can add Oracle Database homes (referred to as Database Homes in OracleCloud Infrastructure) to an existing VM cluster by using the Oracle Cloud InfrastructureConsole, the API, or the CLI.
A Database Home is a directory location on the Exadata database compute nodes thatcontains Oracle Database software binary files.
Note:
Avoid entering confidential information when assigning descriptions, tags,or friendly names to your cloud resources through the Oracle CloudInfrastructure Console, API, or CLI.
You can also add and remove Database homes, and perform other management taskson a Database home by using the dbaascli utility.
Related Topics
• Using the dbaascli Utility on Exadata Cloud@CustomerLearn to use the dbaascli utility on Exadata Cloud@Customer.
6-1
Required IAM Policy for Creating Oracle Database HomesReview the identity access management (IAM) policy for creating Oracle Databasehomes on Oracle Exadata Cloud@Customer Systems.
A policy is an IAM document that specifies who has what type of access to yourresources. It is used in different ways: to mean an individual statement written inthe policy language; to mean a collection of statements in a single, named "policy"document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean theoverall body of policies your organization uses to control access to resources.
A compartment is a collection of related resources that can be accessed onlyby certain groups that have been given permission by an administrator in yourorganization.
To use Oracle Cloud Infrastructure, you must be given the required type of access ina policy written by an administrator, whether you're using the Console, or the RESTAPI with a software development kit (SDK), a command-line interface (CLI), or someother tool. If you try to perform an action, and receive a message that you don’thave permission, or are unauthorized, then confirm with your administrator the type ofaccess you've been granted, and which compartment you should work in.
For administrators: The policy in "Let database admins manage DB systems" lets thespecified group do everything with databases, and related database resources.
If you're new to policies, then see "Getting Started with Policies" and "CommonPolicies". If you want to dig deeper into writing policies for databases, then see "Detailsfor the Database Service".
Related Topics
• Let database admins manage DB systems
• Getting Started with Policies
• Common Policies
• Details for the Database Service
Using the Console to Create Oracle Database Home onExadata Cloud@Customer
To create an Oracle Database home in an existing VM cluster with the Console, beprepared to provide values for the fields required.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster on which you want to create theDatabase Home.
4. Under Resources, click Database Homes.
5. Click Create Database Home.
Chapter 6Required IAM Policy for Creating Oracle Database Homes
6-2
6. In the Create Database Home dialog, enter the following:
• Database Home display name: The display name for the Database Home.
• Database version: The Oracle Database version for this Database Home.Your Database Homes can have different database versions on the ExadataVM Cluster.
• Show Advanced Options
You have the option to configure advanced options.
– Tags: (Optional) You can choose to apply tags. If you have permissions tocreate a resource, then you also have permissions to apply free-form tagsto that resource. To apply a defined tag, you must have permissions to usethe tag namespace. For more information about tagging, see "ResourceTags". If you are not sure if you should apply tags, then skip this option(you can apply tags later) or ask your administrator.
Note that after Home install, patch to the latest if the latest patch is available.
7. Click Create.
When the Database Home creation is complete, the status changes fromProvisioning to Available.
Related Topics
• Resource Tags
Using the API for Creating Oracle Database Home onExadata Cloud@Customer
To create an Oracle Database home, review the list of API calls.
For information about using the API and signing requests, see "REST APIs" and"Security Credentials". For information about SDKs, see "Software Development Kitsand Command Line Interface".
To create Database Homes in Exadata Cloud@Customer, use the API operationCreateDbHome.
For the complete list of APIs, see "Database Service API".
Related Topics
• REST APIs
• Security Credentials
• Software Development Kits and Command Line Interface
• CreateDbHome
• Database Service API
Chapter 6Using the API for Creating Oracle Database Home on Exadata Cloud@Customer
6-3
7Managing Oracle Database Homes onExadata Cloud@Customer Systems
Learn to manage Oracle Database homes on Exadata Cloud@Customer.
• About Managing Oracle Database Homes on Exadata Cloud@Customer SystemsYou can delete or view information about Oracle Database Homes (referred toas Database Homes in Oracle Cloud Infrastructure) by using the Oracle CloudInfrastructure Console, the API, or the CLI.
• Required IAM Policy for Managing Oracle Database HomesReview the identity access management (IAM) policy for managing OracleDatabase homes on Oracle Exadata Cloud@Customer Systems.
• Using the Console for Oracle Database Home on Exadata Cloud@CustomerLearn how to use the Console to manage Oracle Database homes.
• Differences Between Managing Resources with dbaascli and the Database APILearn how Oracle Cloud@Customer automatically synchronizes dbaascli utilityparameters and Database Service API properties of Oracle Database instanceand Oracle Database Home.
• Using the API for Managing Oracle Database Home on Exadata Cloud@CustomerReview the list of API calls to manage Oracle Database home.
About Managing Oracle Database Homes on ExadataCloud@Customer Systems
You can delete or view information about Oracle Database Homes (referred toas Database Homes in Oracle Cloud Infrastructure) by using the Oracle CloudInfrastructure Console, the API, or the CLI.
To find out how to delete or view information about Database Homes manually, See"Using the dbaascli Utility on Exadata Cloud@Customer."
Note:
Avoid entering confidential information when assigning descriptions, tags,or friendly names to your cloud resources through the Oracle CloudInfrastructure Console, API, or CLI.
Related Topics
• Using the dbaascli Utility on Exadata Cloud@CustomerLearn to use the dbaascli utility on Exadata Cloud@Customer.
7-1
Required IAM Policy for Managing Oracle Database HomesReview the identity access management (IAM) policy for managing Oracle Databasehomes on Oracle Exadata Cloud@Customer Systems.
A policy is an IAM document that specifies who has what type of access to yourresources. It is used in different ways: to mean an individual statement written inthe policy language; to mean a collection of statements in a single, named "policy"document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean theoverall body of policies your organization uses to control access to resources.
A compartment is a collection of related resources that can be accessed onlyby certain groups that have been given permission by an administrator in yourorganization.
To use Oracle Cloud Infrastructure, you must be given the required type of access ina policy written by an administrator, whether you're using the Console, or the RESTAPI with a software development kit (SDK), a command-line interface (CLI), or someother tool. If you try to perform an action, and receive a message that you don’thave permission, or are unauthorized, then confirm with your administrator the type ofaccess you've been granted, and which compartment you should work in.
For administrators: The policy in "Let database admins manage DB systems" lets thespecified group do everything with databases, and related database resources.
If you're new to policies, then see "Getting Started with Policies" and "CommonPolicies". If you want to dig deeper into writing policies for databases, then see "Detailsfor the Database Service".
Related Topics
• Let database admins manage DB systems
• Getting Started with Policies
• Common Policies
• Details for the Database Service
Using the Console for Oracle Database Home on ExadataCloud@Customer
Learn how to use the Console to manage Oracle Database homes.
• Using the Console to View Information About an Oracle Database HomeTo view the configuration details of an Oracle Database home, use this procedure.
• Using the Console to Delete an Oracle Database HomeTo delete an Oracle Database home with the Console, use this procedure.
Using the Console to View Information About an Oracle DatabaseHome
To view the configuration details of an Oracle Database home, use this procedure.
Chapter 7Required IAM Policy for Managing Oracle Database Homes
7-2
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Click Compartment, and select your compartment.
A list of VM Clusters is displayed for the compartment you selected.
3. In the list of VM clusters, click the VM cluster that contains the Database Home inwhich you are interested.
4. Under Resources, click Database Homes.
5. In the list of Database Homes, find the Database Home you want to view, and thenclick the Database Home name to display details about it.
Using the Console to Delete an Oracle Database HomeTo delete an Oracle Database home with the Console, use this procedure.
You cannot delete an Oracle Database home that contains databases. Before you candelete an Oracle Database home, you must first terminate the databases to emptythe Database Home. When you use dbaascli in the backend to move databases, thebackend is synced on the Kubernetes Control Plane side by a Sync WF running every10 minutes continuously. You can also terminate a database by using the Console.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Select Compartment, and choose the Compartment that you want to view.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster that contains the Database Homethat you want to delete.
4. Under Resources, click Database Homes.
5. In the list of Database Homes, find the Database Home that you want to delete,and click thje Database Home name to display details about it.
6. On the Database Home Details page, click Delete.
Related Topics
• Using the Console to Terminate a DatabaseYou can terminate a database and thereby remove the terminated database fromthe Cloud Control Plane.
Differences Between Managing Resources with dbaascliand the Database API
Learn how Oracle Cloud@Customer automatically synchronizes dbaascli utilityparameters and Database Service API properties of Oracle Database instance andOracle Database Home.
You can manage resources using host tooling such as dbaascli or dbaasapi, ortools based on the Database service API (including the Oracle Cloud InfrastructureConsole, SDKs, and the API itself). For the management operations discussed in thistopic, if you perform them using dbaascli or dbaasapi, then the updates are not visible
Chapter 7Differences Between Managing Resources with dbaascli and the Database API
7-3
in tools based on the Database Service API until the next synchronization operation,which happens every 10 minutes.
The following table lists operations that you perform using dbaascli or dbaasapi, andmaps these operations to the related Database Service API parameters:
Operation Host Tooling Parameters(dbaascli / dbaasapi)
Database Service APIParameters
Creating Database Home name, DatabaseVersion,dbHomeLocation,createTime
displayName, dbVersion,dbHomeLocation,timeCreated
Updating Database Home DatabaseVersion,dbHomeLocation
dbVersion,dbHomeLocation
Creating Database dbName, dbUniqueName,pdbName, characterSet,NlsCharacterSet, dbClass,createTime
dbName, dbUniqueName,pdbName, characterSet,ncharacterSet, dbType,timeCreated
Updating Database dbHomeId, dbUniqueName,dbClass
dbHomeId, dbUniqueName,dbType
If you terminate a Database Home using the dbaascli or dbaasapi, the status of theDatabase Home is displayed as Terminated in the Database Service REST API basedtools. If you terminate a database, the status of the database is displayed as Failed.
Using the API for Managing Oracle Database Home onExadata Cloud@Customer
Review the list of API calls to manage Oracle Database home.
For information about using the API and signing requests, see "REST APIs" and"Security Credentials". For information about SDKs, see "Software Development Kitsand Command Line Interface".
Use these API operations to manage Database Homes:
• ListDbHomes
• GetDbHome
• DeleteDbHome
For the complete list of APIs, see "Database Service API".
Related Topics
• REST APIs
• Security Credentials
• Software Development Kits and Command Line Interface
• ListDbHomes
• GetDbHome
• DeleteDbHome
• Database Service API
Chapter 7Using the API for Managing Oracle Database Home on Exadata Cloud@Customer
7-4
8Managing Oracle Databases on OracleExadata Cloud@Customer
Learn about the prerequisites, supported versions, creating and configuring OracleDatabase for use in Oracle Exadata Cloud@Customer, and other database-relatedadministrative tasks.
• Prerequisites and Limitations for Creating and Managing Oracle Databases onOracle Exadata Cloud@CustomerReview the prerequisites for creating and managing Oracle Databases on OracleExadata Cloud@Customer.
• Oracle Database Releases Supported by Oracle Exadata Cloud@CustomerLearn about the versions of Oracle Database that Oracle ExadataCloud@Customer supports.
• About Provisioning and Configuring Oracle Databases on Oracle ExadataCloud@CustomerLearn about provisioning and configuring Oracle Database on Oracle ExadataCloud@Customer
• Required IAM Policy for Managing Oracle Databases on Oracle ExadataCloud@CustomerReview the identity access management (IAM) policy for managing OracleDatabase on Oracle Exadata Cloud@Customer Systems.
• Using the Console to Manage Databases on Oracle Exadata Cloud@CustomerTo create or terminate a database, complete procedures using the Oracle Exadataconsole.
• Using the API to Manage Database ComponentsUse various API features to help manage your databases on Oracle ExadataCloud@Customer.
Prerequisites and Limitations for Creating and ManagingOracle Databases on Oracle Exadata Cloud@Customer
Review the prerequisites for creating and managing Oracle Databases on OracleExadata Cloud@Customer.
Before you can create and use an Oracle Database on Exadata Cloud@Customer,you must:
• Provision Exadata Cloud@Customer infrastructure
• Configure a VM cluster
• Create any required backup destinations
You can create one or more databases on each Oracle Exadata Cloud@Customersystem. Other than the storage and processing limits of your Oracle Exadata system,
8-1
there is no maximum for the number of databases that you can create. By default,databases on Exadata Cloud@Customer use Oracle Database Enterprise Edition- Extreme Performance. This edition provides all the features of Oracle DatabaseEnterprise Edition, plus all of the database enterprise management packs, and all ofthe Enterprise Edition options, such as Oracle Database In-Memory, and Oracle RealApplication Clusters (Oracle RAC). If you use your own Oracle Database licenses,then your ability to use various features is limited by your license holdings.
Oracle Database Releases Supported by Oracle ExadataCloud@Customer
Learn about the versions of Oracle Database that Oracle Exadata Cloud@Customersupports.
Exadata Cloud@Customer supports the following Oracle Database software releases:
• Oracle Database 19c
• Oracle Database 18c
• Oracle Database 12c Release 2
• Oracle Database 12c Release 1
• Oracle Database 11g Release 2
About Provisioning and Configuring Oracle Databases onOracle Exadata Cloud@Customer
Learn about provisioning and configuring Oracle Database on Oracle ExadataCloud@Customer
When you provision a database, you can associate it with a backup destination, andenable automatic backups. Each Oracle Database is configured as follows:
• Each database is configured with Oracle Real Application Clusters (Oracle RAC)database instances running on every node in the virtual machine (VM) cluster.
• Each database uses a separate set of Oracle binaries in a separate Oracle homelocation.
• Each database is configured with default instance parameter settings. While thedefaults are reasonable for many cases, you should review the instance parametersettings to ensure that they meet your specific application needs.In particular, review the Oracle Database system global area (SGA) and programglobal area (PGA) instance parameter settings, especially if your VM clustersupports multiple databases. Also, ensure that the sum of all Oracle Databasememory allocations never exceeds the available physical memory on eachcompute node.
• Each database using Oracle Database 12c Release 1 or a later release isconfigured as a container database (CDB). One pluggable database (PDB) iscreated inside the CDB. By default:
– The first PDB is configured with a local PDB administration user account,named PDBADMIN.
Chapter 8Oracle Database Releases Supported by Oracle Exadata Cloud@Customer
8-2
– The PDBADMIN user account is initially configured with the same administrationpassword as the CDB SYS and SYSTEM users.
– The PDBADMIN user account is initially configured with basic privilegesassigned through two roles; CONNECT and PDB_DBA. However, for most practicaladministrative purposes you must assign extra privileges to the PDBADMIN useraccount, or to the PDB_DBA role.
You can use native Oracle Database facilities to create extra PDBs, and tomanage all of your PDBs. The dbaascli utility also provides a range of convenientPDB management functions.
• Depending on your Oracle Database release, each database contains web-based monitoring and management tools provided by Oracle Enterprise ManagerDatabase Express (EM Express), or by Oracle Enterprise Manager DatabaseControl (Database Control). The dbaascli utility also provides a range ofconvenient database management functions.
Note:
Avoid entering confidential information when assigning descriptions, tags,or friendly names to your cloud resources through the Oracle CloudInfrastructure Console, API, or CLI.
Required IAM Policy for Managing Oracle Databases onOracle Exadata Cloud@Customer
Review the identity access management (IAM) policy for managing Oracle Databaseon Oracle Exadata Cloud@Customer Systems.
A policy is an IAM document that specifies who has what type of access to yourresources. It is used in different ways: to mean an individual statement written inthe policy language; to mean a collection of statements in a single, named "policy"document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean theoverall body of policies your organization uses to control access to resources.
A compartment is a collection of related resources that can be accessed onlyby certain groups that have been given permission by an administrator in yourorganization.
To use Oracle Cloud Infrastructure, you must be given the required type of access ina policy written by an administrator, whether you're using the Console, or the RESTAPI with a software development kit (SDK), a command-line interface (CLI), or someother tool. If you try to perform an action, and receive a message that you don’thave permission, or are unauthorized, then confirm with your administrator the type ofaccess you've been granted, and which compartment you should work in.
For administrators: The policy in "Let database admins manage DB systems" lets thespecified group do everything with databases, and related database resources.
If you're new to policies, then see "Getting Started with Policies" and "CommonPolicies". If you want to dig deeper into writing policies for databases, then see "Detailsfor the Database Service".
Chapter 8Required IAM Policy for Managing Oracle Databases on Oracle Exadata Cloud@Customer
8-3
Related Topics
• Let database admins manage DB systems
• Getting Started with Policies
• Common Policies
• Details for the Database Service
Using the Console to Manage Databases on Oracle ExadataCloud@Customer
To create or terminate a database, complete procedures using the Oracle Exadataconsole.
• Using the Console to Create a DatabaseTo create an Oracle Database with the console, use this procedure.
• Using the Console to Move a Database to Another Database HomeLearn to move a database to another Database Home.
• Using the Console to Terminate a DatabaseYou can terminate a database and thereby remove the terminated database fromthe Cloud Control Plane.
Using the Console to Create a DatabaseTo create an Oracle Database with the console, use this procedure.
1. Open the navigation menu Under Database, and click [email protected] Clusters is selected by default.
2. Choose your Compartment.A list of VM Clusters is displayed for the chosen Compartment.
3. Click the name of a VM cluster where you want to create the database.In the VM Cluster Details page, under Resources, Databases is selected bydefault.
4. Click Create Database.(or)
• Open the navigation menu. Under Database, click [email protected] Clusters is selected by default.
• Choose your Compartment.A list of VM Clusters is displayed for the chosen Compartment.
• Click the name of a VM cluster where you want to create the database.In the VM Cluster Details page, under Resources, Databases is selected bydefault.
• Click Database Homes.
• Click the name of the Database Home where you want to create the database.
• Click Create Database.
Chapter 8Using the Console to Manage Databases on Oracle Exadata Cloud@Customer
8-4
5. Provide the requested information in the Create Database page:
• Provide the database name: Specify a user-friendly name that you can useto identify the database. The name doesn't need to be unique because anOracle Cloud Identifier (OCID) uniquely identifies the database.
• Provide a unique name for the database: Optionally specify a unique namefor the database. This attribute defines the value of the DB_UNIQUE_NAMEdatabase parameter. The value is case insensitive, it can be up to 30characters in length, and include alphanumeric characters, underscore (_),number sign (#), and dollar sign ($).
If you plan to configure the database for backup to a Recovery Appliancebackup destination, then the unique database name must match the name thatis configured in the Recovery Appliance.
• Select a database version: From the list, choose the Oracle Databasesoftware release that you want to deploy.
• Database Home: Select an existing Database Home or create one asapplicable. Note that this field is not available when you create a Databasefrom the Database Home details page.
– Select an existing Database Home: If one or more Database Homesalready exist for the database version you have selected, then this optionis selected by default. And, you will be presented with a list of DatabaseHomes. Select a Database Home from the list.
– Create a new Database Home: If no Database Homes exist for thedatabase version you have selected, then this option is selected bydefault.
• Provide the name of the first PDB: (Optional) Specify the name for the firstPDB. A PDB is created with the database.
To avoid potential service name collisions when using Oracle Net Services toconnect to the PDB, ensure that the PDB name is unique across the entireVM cluster. If you do not provide the name of the first PDB, then a system-generated name is used.
• Provide the administration password: Provide and confirm the OracleDatabase administration password. This password is used for administrationaccounts and functions in the database, including:
– The password for the Oracle Database SYS and SYSTEMusers.
– The Transparent Data Encryption (TDE) keystore password.
For Oracle Database 12c Release 1 or later releases, the password forthe PDB administration user in the first PDB (PDBADMIN).must be nine to 30characters, and contain at least two uppercase, two lowercase, two numeric,and two special characters. The special characters must be _, #, or -. Inaddition, the password must not contain the name of the tenancy or anyreserved words, such as Oracle or Table, regardless of casing.
• Choose the database workload type: Select the workload type that bestsuits your application from one of the following options:
– Online Transactional Processing (OLTP): Select this option to configurethe database for a transactional workload, with a bias toward highvolumes of random data access.
Chapter 8Using the Console to Manage Databases on Oracle Exadata Cloud@Customer
8-5
– Decision Support System (DSS): Select this option to configure thedatabase for a decision support or data warehouse workload, with a biastoward large data scanning operations.
• Backup Destination Type: Select a backup destination for the database.From the list, choose an option:
– None: Select to not define a backup configuration for the database.
– Local: Select to store backups locally in the Oracle Exadata StorageServers on your Oracle Exadata Cloud@Customer system.This option is available only if you enabled backups on local OracleExadata storage in the VM cluster that you want to host the database.
– Object Storage: Select to store backups in an Oracle-managed objectstorage container on Oracle Cloud Infrastructure.To use this option, your Oracle Exadata Cloud@Customer system musthave egress connectivity to Oracle Cloud Infrastructure Object Storage.
– NFS: Select to store backups in one of your previously defined backupdestinations that uses Network File System (NFS) storage. For moreinformation, refer to the information about backup destinations in thispublication.
If you select this option, then you must also choose from the list of NFSBackup Destinations.
– Recovery Appliance: Select to store backups in one of your previouslydefined backup destinations that uses Oracle Zero Data Loss RecoveryAppliance. Refer to the information about backup destination options inthis document.
If you select Oracle Zero Data Loss Recovery Appliance as your backupoption, then you must also:
* Choose from the list of appliance Backup Destinations.
* Choose from the VPC User list, which contains the list of virtualprivate catalog (VPC) user names that are defined in the Oracle ZeroData Loss Recovery Appliance backup destination.
* Provide the Password for the VPC user.
Note:
If you select a backup destination, then you cannot change abackup location after the database is created. However, if youselect None now, then you can select a backup destination afterthe database is created.
– Enable automatic backups: Select this option to enable daily backupsusing the policy for automatic backups.
This option is only enabled when you select a Backup Destination Typeother than None. You can change this setting after database creation.
• (Optional) Select Show Advanced Options. From this window, you can selectthe following options:
Chapter 8Using the Console to Manage Databases on Oracle Exadata Cloud@Customer
8-6
– Backup retention period: From the list, you can choose the length oftime that you want automatic backups to be retained.
For backups to local Exadata storage, you can choose a retention periodof 7 days or 14 days. The default retention period is 7 days.
For backups to Oracle Cloud Infrastructure Object Storage, or to an NFSbackup destination, you can choose one of the following preset retentionperiods: 7 days, 14 days, 30 days, 45 days, or 60 days. The defaultretention period is 30 days.
This option does not apply to Oracle Zero Data Loss Recovery Appliancebackup destinations. For backups to Oracle Zero Data Loss RecoveryAppliance, the retention policy that is implemented in the appliancecontrols the retention period.
– Character set: The character set for the database. The default isAL32UTF8.
– National character set: The national character set for the database. Thedefault is AL16UTF16.
– Tags: (Optional) You can choose to apply tags. If you have permissionsto create a resource, you also have permissions to apply free-form tagsto that resource. To apply a defined tag, you must have permissionsto use the tag namespace. For more information about tagging, referto information about resource tags.If you are not sure if you shouldapply tags, then skip this option (you can apply tags later), or ask youradministrator.
6. Click Create Database.
Related Topics
• Resource Tags
• Managing Backup Destinations for Exadata Cloud@CustomerLearn to manage backup destinations for Exadata Cloud@Customer on OracleZero Data Loss Recovery Appliance or Network File System (NFS).
Using the Console to Move a Database to Another Database HomeLearn to move a database to another Database Home.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment that contains the VM cluster that hosts the databasethat you want to terminate.
3. Click the name of the VM cluster that contains the database that you want toterminate.
4. In the Resources list of the VM Cluster Details page, click Databases.
5. Click the name of the database that you want to terminate.
The Database Details page displays information about the selected database.
6. Click Move Database.
7. In the resulting dialog, select the target Database Home.
Chapter 8Using the Console to Manage Databases on Oracle Exadata Cloud@Customer
8-7
8. Click Move Database.
The database will be stopped in the current home and then restarted in the destinationhome. While the database is being moved, the Database Home status displays asMoving Database. When the operation completes, Database Home is updated withthe current home. If the operation is unsuccessful, the status of the database displaysas Failed, and the Database Home field provides information about the reason for thefailure.
Using the Console to Terminate a DatabaseYou can terminate a database and thereby remove the terminated database from theCloud Control Plane.
Terminating a database removes it from the Cloud Control Plane. In the process, all ofthe associated data files and backups are destroyed.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment that contains the VM cluster that hosts the databasethat you want to terminate.
3. Click the name of the VM cluster that contains the database that you want toterminate.
4. In the Resources list of the VM Cluster Details page, click Databases.
5. Click the name of the database that you want to terminate.
The Database Details page displays information about the selected database.
6. Click Terminate.
7. In the resulting dialog, enter the name of the database, and then click TerminateDatabase to confirm the action.
Using the API to Manage Database ComponentsUse various API features to help manage your databases on Oracle ExadataCloud@Customer.
For information about using the API and signing requests, see "REST APIs" and"Security Credentials". For information about SDKs, see "Software Development Kitsand Command Line Interface".
Use the following API operations to manage various database components.
Database homes:
• CreateDbHome
• DeleteDbHome
• GetDbHome
• ListDbHomes
Databases:
• GetDatabase
Chapter 8Using the API to Manage Database Components
8-8
• ListDatabases
Nodes:
• GetDbNode
• List DbNodes
For the complete list of APIs, see "Database Service API".
Related Topics
• REST APIs
• Security Credentials
• Software Development Kits and Command Line Interface
• CreateDbHome
• DeleteDbHome
• GetDbHome
• ListDbHomes
• GetDatabase
• ListDatabases
• GetDbNode
• List DbNodes
• Database Service API
Chapter 8Using the API to Manage Database Components
8-9
9Using Oracle Data Guard with ExadataCloud@Customer
Learn to configure and manage Data Guard associations in your VM cluster.
• About Using Oracle Data Guard with Exadata Cloud@CustomerThis topic explains how to use the Console or the API to manage Data Guardassociations in your VM cluster.
• Required IAM Policy for Managing Oracle Data Guard Associations on OracleExadata Cloud@CustomerReview the identity access management (IAM) policy for managing Oracle DataGuard associations on Oracle Exadata Cloud@Customer Systems.
• Prerequisites for Using Oracle Data Guard with Exadata Cloud@CustomerReview the list of prerequisites for using Data Guard with ExadataCloud@Customer.
• Working with Data GuardOracle Data Guard ensures high availability, data protection, and disaster recoveryfor enterprise data.
• Using the Console to Manage Oracle Data Guard AssociationsLearn how to enable a Data Guard association between databases, change therole of a database in a Data Guard association using either a switchover or afailover operation, and reinstate a failed database.
• Using the API To Manage Data Guard Associations on an ExadataCloud@Customer SystemLearn how to use the API to manage Data Guard associations on an ExadataCloud@Customer system.
About Using Oracle Data Guard with ExadataCloud@Customer
This topic explains how to use the Console or the API to manage Data Guardassociations in your VM cluster.
When you use the Console or the API to enable Data Guard for an Exadata databasecompute node database:
• The standby database is a physical standby.
• The peer databases (primary and standby) are in the same compartment and thedatabase versions are identical.
• You are limited to one standby database for each primary database.
To configure a Data Guard system across regions or between on-premises andExadata database compute nodes, or to configure your database with multiplestandbys, you must access the database host directly and set up Data Guardmanually.
9-1
For complete information on Oracle Data Guard, see the Data Guard Concepts andAdministration documentation on the Oracle Document Portal.
Related Topics
• Data Guard Concepts and Administration
• Oracle Document Portal
Required IAM Policy for Managing Oracle Data GuardAssociations on Oracle Exadata Cloud@Customer
Review the identity access management (IAM) policy for managing Oracle Data Guardassociations on Oracle Exadata Cloud@Customer Systems.
A policy is an IAM document that specifies who has what type of access to yourresources. It is used in different ways: to mean an individual statement written inthe policy language; to mean a collection of statements in a single, named "policy"document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean theoverall body of policies your organization uses to control access to resources.
A compartment is a collection of related resources that can be accessed onlyby certain groups that have been given permission by an administrator in yourorganization.
To use Oracle Cloud Infrastructure, you must be given the required type of access ina policy written by an administrator, whether you're using the Console, or the RESTAPI with a software development kit (SDK), a command-line interface (CLI), or someother tool. If you try to perform an action, and receive a message that you don’thave permission, or are unauthorized, then confirm with your administrator the type ofaccess you've been granted, and which compartment you should work in.
For administrators: The policy in "Let database admins manage DB systems" lets thespecified group do everything with databases, and related database resources.
If you're new to policies, then see "Getting Started with Policies" and "CommonPolicies". If you want to dig deeper into writing policies for databases, then see "Detailsfor the Database Service".
Related Topics
• Let database admins manage DB systems
• Getting Started with Policies
• Common Policies
• Details for the Database Service
Prerequisites for Using Oracle Data Guard with ExadataCloud@Customer
Review the list of prerequisites for using Data Guard with Exadata Cloud@Customer.
Chapter 9Required IAM Policy for Managing Oracle Data Guard Associations on Oracle Exadata Cloud@Customer
9-2
• Compute NodesA VM cluster Data Guard implementation requires two Exadata database computenodes, one containing the primary database and one containing the standbydatabase.
• PasswordFor Data Guard operations to work, the SYS password and the TDE walletpassword of the primary and standby databases must all be the same.
Compute NodesA VM cluster Data Guard implementation requires two Exadata database computenodes, one containing the primary database and one containing the standby database.
When you enable Data Guard for an Exadata database compute node database, theExadata database compute node with the database to be used as the standby mustalready exist before you enable Data Guard.
PasswordFor Data Guard operations to work, the SYS password and the TDE wallet password ofthe primary and standby databases must all be the same.
If you change any one of these passwords, you must update the rest of the passwordsto match.
If you make any change to the TDE wallet (such as adding a master key for a newPDB or changing the wallet password), you must copy the wallet from the primaryto the standby so that Data Guard can continue to operate. For Oracle Databaseversions earlier than 12.2, if you change the SYS password on one of the peers, youneed to manually sync the password file between the DB systems.
Working with Data GuardOracle Data Guard ensures high availability, data protection, and disaster recovery forenterprise data.
The Data Guard implementation requires two databases, one in a primary role andone in a standby role. The two databases compose a Data Guard association.Most of your applications access the primary database. The standby database is atransactionally consistent copy of the primary database.
Data Guard maintains the standby database by transmitting and applying redo datafrom the primary database. If the primary database becomes unavailable, you can useData Guard to switch or fail over the standby database to the primary role.
• SwitchoverA switchover reverses the primary and standby database roles.
• FailoverA failover transitions the standby database into the primary role after the existingprimary database fails or becomes unreachable.
• ReinstateReinstates a database into the standby role in a Data Guard association.
Chapter 9Working with Data Guard
9-3
SwitchoverA switchover reverses the primary and standby database roles.
Each database continues to participate in the Data Guard association in its new role.A switchover ensures no data loss. You can use a switchover before you performplanned maintenance on the primary database. Performing planned maintenance ona Exadata database compute node with a Data Guard association is typically done byswitching the primary to the standby role, performing maintenance on the standby, andthen switching it back to the primary role.
FailoverA failover transitions the standby database into the primary role after the existingprimary database fails or becomes unreachable.
A failover might result in some data loss when you use Maximum Performanceprotection mode.
ReinstateReinstates a database into the standby role in a Data Guard association.
You can use the reinstate command to return a failed database into service aftercorrecting the cause of failure.
Note:
You can't terminate a primary database that has a Data Guard associationwith a peer (standby) database. Delete the standby database first.Alternatively, you can switch over the primary database to the standby role,and then terminate it.
You can't terminate a VM cluster that includes Data Guard enableddatabases. You must first remove the Data Guard association by terminatingthe standby database.
Using the Console to Manage Oracle Data GuardAssociations
Learn how to enable a Data Guard association between databases, change the roleof a database in a Data Guard association using either a switchover or a failoveroperation, and reinstate a failed database.
When you enable Data Guard, a separate Data Guard association is created for theprimary and the standby database.
• Using the Console to Enable Data Guard on an Exadata Cloud@CustomerSystemLearn to enable Data Guard association between databases.
Chapter 9Using the Console to Manage Oracle Data Guard Associations
9-4
• Using the Console To Perform a Database SwitchoverYou initiate a switchover operation by using the Data Guard association of theprimary database.
• Using the Console To Perform a Database FailoverYou initiate a failover operation by using the Data Guard association of the standbydatabase.
• Using the Console To Reinstate a DatabaseAfter you fail over a primary database to its standby, the standby assumes theprimary role and the old primary is identified as a disabled standby.
• Using the Console To Terminate a Data Guard Association on an ExadataCloud@Customer SystemOn a VM cluster, you remove a Data Guard association by terminating the standbydatabase.
Using the Console to Enable Data Guard on an ExadataCloud@Customer System
Learn to enable Data Guard association between databases.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster that contains the database for whichyou want to assume the primary role, and then click the name of that database.
4. Under Resources, click Data Guard Associations.
5. Click Enable Data Guard.
6. On the Enable Data Guard page, configure your Data Guard association.
• Data Guard association details:
– Protection mode: The protection mode used for this Data Guardassociation.
Maximum Performance provides the highest level of data protection that ispossible without affecting the performance of a primary database.
Maximum Availability provides highest level of protection of data withoutcompromising availability of database.
– Transport type: The redo transport type used for this Data Guardassociation.
The redo transport type used for this Data Guard association.
Async - Asynchronous transport mode used with Maximum Performanceprotection mode.
Sync - Synchronous transport mode used with Maximum Performanceand Maximum Availability protection mode.
• Select peer VM cluster: Specify the following values for the standby:
Chapter 9Using the Console to Manage Oracle Data Guard Associations
9-5
– Peer Region: Currently, the peer region is auto-populated and you cannotchange it. The primary and secondary databases could be running ontwo different VM clusters on a shared Exadata Cloud@Customer system,or on two geographically separated Exadata Cloud@Customer systemsmanaged from a single Oracle Cloud Infrastructure region.
– Peer Exadata: Select the Exadata Cloud@Customer infrastructure wherethe standby database is located. Click the CHANGE COMPARTMENThyperlink to choose a compartment.
– Peer VM Cluster: Select the Exadata database compute node thatcontains the standby database. Click the CHANGE COMPARTMENThyperlink to choose a compartment.
• Configure standby database: Enter the database admin password of theprimary database in the Database password field. This same database adminpassword will be used for the standby database.The admin password and the TDE password must be the same. If they arenot, follow the instructions in Changing the Database Passwords to align them.
7. Click Enable Data Guard.
When the association is created, the details for a database and its peer display theirrespective roles as Primary or Standby.
Using the Console To Perform a Database SwitchoverYou initiate a switchover operation by using the Data Guard association of the primarydatabase.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster that contains the primary databaseyou want to switch over.
4. Click the name of the primary database.
5. Under Resources, click Data Guard Associations.
6. For the Data Guard association on which you want to perform a switchover, clickthe Actions icon (three dots), and then click Switchover.
7. In the Switchover Database dialog box, enter the database admin password, andthen click OK.
This database should now assume the role of the standby, and the standby shouldassume the role of the primary in the Data Guard association.
Using the Console To Perform a Database FailoverYou initiate a failover operation by using the Data Guard association of the standbydatabase.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
Chapter 9Using the Console to Manage Oracle Data Guard Associations
9-6
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster that contains the primary database'speer standby you want to fail over to.
4. Click the name of the standby database.
5. Under Resources, click Data Guard Associations.
6. For the Data Guard association on which you want to perform a failover, click theActions icon (three dots), and then click Failover.
7. In the Failover Database dialog box, enter the database admin password, andthen click OK.
This database should now assume the role of the primary, and the old primary's roleshould display as Disabled Standby.
Using the Console To Reinstate a DatabaseAfter you fail over a primary database to its standby, the standby assumes the primaryrole and the old primary is identified as a disabled standby.
After you correct the cause of failure, you can reinstate the failed database as afunctioning standby for the current primary by using its Data Guard association.
Before you can reinstate a version 12.2 or later database, you must perform somesteps on the database host to stop the database or start it in MOUNT mode.
Set your ORACLE_UNQNAME environment variable to the value of the Database UniqueName (as seen in the ), and then run these commands:
srvctl stop database -d db-unique-name -o abort
srvctl start database -d db-unique-name -o mount
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster that contains the primary database.
4. Click the name of the primary database.
5. Under Resources, click Data Guard Associations.
You will see the database you want to reinstate listed.
6. Click the Actions icon (three dots), and then click Reinstate.
7. In the Reinstate Database dialog box, enter the database admin password, andthen click OK.
This database should now be reinstated as the standby in the Data Guard association.
Chapter 9Using the Console to Manage Oracle Data Guard Associations
9-7
Using the Console To Terminate a Data Guard Association on anExadata Cloud@Customer System
On a VM cluster, you remove a Data Guard association by terminating the standbydatabase.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster that contains the standby databaseyou want to terminate.
4. Click the name of the standby database.
5. For the standby database you want to terminate, click the Actions icon (threedots), and then click Terminate.
6. In the Terminate Database dialog box, enter the name of the database, and thenclick OK.
Using the API To Manage Data Guard Associations on anExadata Cloud@Customer System
Learn how to use the API to manage Data Guard associations on an ExadataCloud@Customer system.
For information about using the API and signing requests, see REST APIs andSecurity Credentials. For information about SDKs, see Software Development Kits andCommand Line Interface.
The following table lists the REST API endpoints to manage Data Guard associations.
Operation REST API Endpoint
Create a Data Guard association. CreateDataGuardAssociation
View details of the specified Data Guardassociation's configuration information.
GetDataGuardAssociation
View the list of all Data Guard associations forthe specified database.
ListDataGuardAssociations
Perform a switchover to transition a primarydatabase of a Data Guard association intostandby role.
SwitchoverDataGuardAssociation
Perform a failover to transition a standbydatabase identified by the databaseIdparameter into the specified Data Guardassociation's primary role after the existingprimary database fails or becomesunreachable.
FailoverDataGuardAssociation
Chapter 9Using the API To Manage Data Guard Associations on an Exadata Cloud@Customer System
9-8
Operation REST API Endpoint
Reinstate a database identified by thedatabaseId parameter into standby role in aData Guard association.
ReinstateDataGuardAssociation
Delete a standby database. DeleteDatabase
For the complete list of APIs, see Database Service API.
Chapter 9Using the API To Manage Data Guard Associations on an Exadata Cloud@Customer System
9-9
10Managing Database Backup and Recoveryon Oracle Exadata Cloud@Customer
Learn how to work with the backup and recovery facilities provided by Oracle ExadataCloud@Customer.
• About Managing Backup Destinations for Oracle Exadata Cloud@CustomerLearn how configure backup when creating the database on Oracle ExadataCloud@Customer.
• Required IAM Policy for Backup and RecoveryReview the identity access management (IAM) policy for backup and recovery onOracle Exadata Cloud@Customer Systems.
• Using the Console to Manage Backup and RecoveryLearn how to use the console to view a list of available backups, edit backupsettings, and restore a database for Oracle Exadata Cloud@Customer.
• Use the API to Manage Database Backup and RecoveryLearn how to use the API to manage database backup and recovery with OracleExadata Cloud@Customer.
About Managing Backup Destinations for Oracle ExadataCloud@Customer
Learn how configure backup when creating the database on Oracle ExadataCloud@Customer.
Oracle Exadata Cloud@Customer provides automatic database backup facilitiesthat use Oracle Recovery Manager (RMAN). When you create a database onOracle Exadata Cloud@Customer, you can specify a backup destination and enableautomatic backups. For more information, refer to the information in this publicationabout managing backup destinations for Oracle Exadata Cloud@Customer.
After database creation, you can also:
• View a list of available backups.
• Enable or disable automatic backups.
• Edit backup settings.
• Restore a database.
You can perform these operations by using either the Console, or the API.
Automatic database backups are configured as follows:
• Automatic backups are scheduled daily. The automatic backup process can run atany time within the daily backup window, which is between midnight and 6:00 AMin the time zone of the virtual machine (VM) cluster that hosts the database.
10-1
• Automatic backups use a combination of full (RMAN level 0) and incremental(RMAN level 1) database backups:
– For backups to a Zero Data Loss Recovery Appliance, after an initial fullbackup is performed, Zero Data Loss Recovery Appliance creates andvalidates virtual full backups from each daily incremental backup.
– For backups to a network file system (NFS) backup destination, incrementalbackups are always performed after an initial full backup is taken. Also, theincremental backups are merged into the full backup when they become olderthan the retention period.
– For backups to all other storage types, the default interval between fullbackups is seven days.
• The retention period defines the period for which automatic backups aremaintained:
– For backups to Zero Data Loss Recovery Appliance, the retention policy that isimplemented in the appliance controls the retention period.
– For backups to local Exadata storage, you can choose a retention period of 7days, or 14 days. The default retention period is 7 days.
– For backups to Oracle Cloud Infrastructure Object Storage, or to an NFSbackup destination, you can choose one of the following preset retentionperiods: 7 days, 14 days, 30 days, 45 days, or 60 days. The default retentionperiod is 30 days.
• By default, Oracle Database runs in ARCHIVELOG mode, and archived redo log filesare backed up every 60 minutes.
• Regardless of the backup destination, backups of user data are encrypted bydefault.
While a backup is in progress, Oracle recommends that you avoid performing actionsthat could interfere with availability, such as restarting compute nodes, or applyingpatches. If an automatic backup operation fails, then the backup is deferred until thenext day’s backup window.
When required, you can restore Oracle Database to:
• The latest available restore point.
• A specific point in time by providing a time stamp.
• An Oracle Database System Change Number (SCN).
Note:
The backup and recovery facilities described in this topic cater only fordatabase backup and recovery, which includes Oracle Database data files,log files, control files, and the server parameter (SP) file. You are responsiblefor backing up other files on your compute nodes. In particular, Oraclestrongly recommends that you back up the Transparent Data Encryption(TDE) keystore (wallet). Without the TDE keystore, the Oracle Databasebackups are effectively useless, because you cannot read the data containedin the backup.
Chapter 10About Managing Backup Destinations for Oracle Exadata Cloud@Customer
10-2
Note:
If TAG based recovery fails with error ORA-01152, then use RecoveryManager (RMAN) directly to complete the recovery.
If the server parameter file (SPFILE) recovery fails for local configurationusing dbaascli, then use Recovery Manager (RMAN) directly to completethe recovery.
Required IAM Policy for Backup and RecoveryReview the identity access management (IAM) policy for backup and recovery onOracle Exadata Cloud@Customer Systems.
To use Oracle Cloud Infrastructure, you must be given the required type of access ina policy written by an administrator, whether you're using the Console or the RESTAPI with an SDK, CLI, or other tool. If you try to perform an action and get a messagethat you don’t have permission or are unauthorized, confirm with your administrator thetype of access you've been granted and in which compartment you should work.
If you're new to policies, see "Getting Started with Policies" and "Common Policies".
Related Topics
• Getting Started with Policies
• Common Policies
Using the Console to Manage Backup and RecoveryLearn how to use the console to view a list of available backups, edit backup settings,and restore a database for Oracle Exadata Cloud@Customer.
• Viewing a List of Available Backups with the ConsoleTo view a list of available backups with Oracle Exadata Cloud@Customer,complete this procedure.
• Editing Backup Settings with the ConsoleTo edit backup destinations, change backup schedules and other backupadministration, you can use with the Oracle Exadata Cloud@Customer console.
• Restoring a Database with the ConsoleTo restore a database to a point in time, to a system change number (SCN), or tothe latest backup, use the Exadata Cloud@Customer Console.
Chapter 10Required IAM Policy for Backup and Recovery
10-3
Viewing a List of Available Backups with the ConsoleTo view a list of available backups with Oracle Exadata Cloud@Customer, completethis procedure.
Note:
Only the managed backups are synced to the Console. If you configurebackups directly in the backend, then they are not synced to the Console.This is an expected behavior and Oracle has no plans to change thisbehavior.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the VM cluster that hosts thedatabase in which you are interested.
3. Click VM Clusters.
4. Click the name of the VM cluster that hosts the database in which you areinterested.
5. In the Resources list of the VM Cluster Details page, click Databases.
6. Click the name of the database in which you are interested.
The Database Details page displays information about the selected database,which includes a list of the available backups.
Editing Backup Settings with the ConsoleTo edit backup destinations, change backup schedules and other backupadministration, you can use with the Oracle Exadata Cloud@Customer console.
Use this procedure to change the available backup settings:
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the VM cluster that hosts thedatabase for which you want to edit backup settings.
3. Click VM Clusters.
4. Click the name of the VM cluster that hosts the database for which you want toedit backup settings.
5. In the Resources list of the VM Cluster Details page, click Databases.
6. Click the name of the database for which you want to edit backup settings.
The Database Details page displays information about the selected database.
7. Click Backup Settings.
8. Your current backup configuration determines the changes that you can make inthe Backup Settings dialog, as follows:
Chapter 10Using the Console to Manage Backup and Recovery
10-4
• If automatic backups are not configured (Backup Destination Type is setto None), then you can use the following settings to define the backupconfiguration for the database:
– Backup Destination Type: From the list, choose an option.
* None Select if you do not define a backup configuration for thedatabase.
* Local Select to store backups locally in the Exadata Storage Serverson your Exadata Cloud@Customer system.
This option is available only if you enabled backups on local Exadatastorage in the VM cluster that you want to host the database.
* Object Storage Select to store backups in an object storage containermanaged by Oracle on Oracle Cloud Infrastructure.
To use this option, your Exadata Cloud@Customer system must haveegress connectivity to Oracle Cloud Infrastructure Object Storage.
* NFS Select to store backups in one of your previously definedbackup destinations that uses Network File System (NFS) storage.See "Managing Backup Destinations for Exadata Cloud@Customer".
If you select this option, then you must also choose from the list ofNFS Backup Destinations.
* Recovery Appliance Select to store backups in one of yourpreviously defined backup destinations that uses Oracle Zero DataLoss Recovery Appliance. See "Managing Backup Destinations forExadata Cloud@Customer".
If you select this option, then you must also provide the followinginformation:
* Choose Backup Destinations from the list of RecoveryAppliance .
* Choose from the VPU User list, which contains the list ofvirtual private catalog (VPC) user names that are defined in theRecovery Appliance backup destination.
* Provide the Password for the VPC user.
Note:
If you select a backup destination (other than None), thenyou cannot change it later.
– Enable automatic backups: Select this option to enable daily backupsusing the policy for automatic backups.
This option is only enabled when you select a Backup Destination Typeother than None. You can change this setting later.
– Backup retention period: Select this option to choose one of the optionsfor the length of time that automatic backups are retained.
For backups to local Exadata storage, you can choose a retention periodof 7 days, or 14 days. The default retention period is 7 days.
Chapter 10Using the Console to Manage Backup and Recovery
10-5
For backups to Oracle Cloud Infrastructure Object Storage or to an NFSbackup destination, you can choose one of the following preset retentionperiods: 7 days, 14 days, 30 days, 45 days, or 60 days. The defaultretention period is 30 days.
This option does not apply to Recovery Appliance backup destinations.For backups to Oracle Zero Data Loss Recovery Appliance, the retentionpolicy that is implemented in the appliance controls the retention period.
• If automatic backups were previously configured, then you can make thefollowing changes:
– For Oracle Zero Data Loss Recovery Appliance backup destinations, youcan update the Password for the virtual private catalog (VPC) user that isused to access the appliance.
– For backup destinations that do not use Oracle Zero Data Loss RecoveryAppliance, you can update the Backup retention period for automaticbackups:
* For backups to local Exadata storage, you can choose a retentionperiod of 7 days or 14 days. The default retention period is 7 days.
* For backups to Oracle Cloud Infrastructure Object Storage, or to anNFS backup destination, you can choose one of the following presetretention periods: 7 days, 14 days, 30 days, 45 days, or 60 days. Thedefault retention period is 30 days.
* For backups to Oracle Zero Data Loss Recovery Appliance, theretention policy that is implemented in the appliance controls theretention period.
– You can set the option to Enable automatic backups. Select this optionto enable automatic database backups. Deselect this option to suspendautomatic database backups.
9. Click Save Changes.
Related Topics
• Managing Backup Destinations for Exadata Cloud@Customer
Restoring a Database with the ConsoleTo restore a database to a point in time, to a system change number (SCN), or to thelatest backup, use the Exadata Cloud@Customer Console.
Use the following procedure to restore a database:
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose the Region and Compartment that contains the VM cluster that hosts thedatabase that you want to restore.
3. Click VM Clusters.
4. Click the name of the VM cluster that hosts the database that you want to restore.
5. In the Resources list of the VM Cluster Details page, click Databases.
6. Click the name of the database that you want to restore.The Database Details page displays information about the selected database.
7. Click Restore Database.
Chapter 10Using the Console to Manage Backup and Recovery
10-6
8. In the resulting dialog box, select one of the following options, and click RestoreDatabase:
• Restore to latest: The database is restored and recovered with zero, or leastpossible, data loss.
• Restore to a timestamp: The database is restored and recovered to thespecified timestamp.
• Restore to SCN: The database is restored and recovered to the specifiedOracle Database System Change Number (SCN). The specified SCN must bevalid otherwise the operation fails.
Note:
Backup fails after a point in time restore to a timestamp or SCN on NFSstorage. Wait for 10 minutes or so before proceeding with the backup.
Use the API to Manage Database Backup and RecoveryLearn how to use the API to manage database backup and recovery with OracleExadata Cloud@Customer.
For information about using the API and signing requests, see "REST APIs" and"Security Credentials". For information about SDKs, see "Software Development Kitsand Command Line Interface".
Use these API operations to manage database backup and recovery:
• GetBackup
• ListBackups
• RestoreDatabase
• UpdateDatabase - To enable and disable automatic backups.
For the complete list of APIs, see "Database Service API".
Related Topics
• REST APIs
• Security Credentials
• Software Development Kits and Command Line Interface
• GetBackup
• ListBackups
• RestoreDatabase
• UpdateDatabase
• Database Service API
Chapter 10Use the API to Manage Database Backup and Recovery
10-7
11Connecting to an ExadataCloud@Customer System
Learn how to connect to an Exadata Cloud@Customer system using SSH, and howto connect to an Exadata Cloud@Customer database using Oracle Net Services(SQL*Net).
• Connecting to a Compute Node with SSHYou can connect to the compute nodes in an Exadata Cloud@Customer systemby using a Secure Shell (SSH) connection.
• Connecting to a Database with Oracle Net ServicesYou can connect to the compute nodes in an Exadata Cloud@Customer systemusing Oracle Net Services.
Connecting to a Compute Node with SSHYou can connect to the compute nodes in an Exadata Cloud@Customer system byusing a Secure Shell (SSH) connection.
Most Unix-style systems (including Linux, Oracle Solaris, and macOS) include an SSHclient. For Microsoft Windows systems, you can download a free SSH client calledPuTTY from the following site: "http://www.putty.org".
• Prerequisites for Connecting to an Exadata Cloud@Customer SystemTo access a compute node in an Exadata Cloud@Customer system using SSH,be prepared to provide the host name or IP address of the compute node.
• Connecting to a Compute Node from a Microsoft Windows System Using PuTTYLearn to access a compute node from a Microsoft Windows system using PuTTY.
• Accessing a Database After You Connect to the Compute NodeAfter you connect to a compute node, you can use the following series ofcommands to identify a database and connect to it.
• Connecting from a Unix-Style SystemTo access a compute node on an Oracle Cloud@Customer system from a Unix-style system using SSH, use this procedure.
Related Topics
• http://www.putty.org/
Prerequisites for Connecting to an Exadata Cloud@Customer SystemTo access a compute node in an Exadata Cloud@Customer system using SSH, beprepared to provide the host name or IP address of the compute node.
• An SSH private key file that corresponds to a public key that is registered in thesystem.When you create a VM cluster on your Exadata Cloud@Customer system, youmust specify the public key portion of one or more SSH key pairs. You can
11-1
also register extra keys separately after you create the VM cluster. The publickeys are stored in the authorized_keys file at ~/.ssh/authorized_keys. Separateauthorized_keys files are located under the home directories of the oracle andopc OS users.
• The host name or IP address for the compute node that you want to access.See "To check the status of a VM cluster compute node".
Related Topics
• Using the Console to Check the Status of a VM Cluster Compute Node
Connecting to a Compute Node from a Microsoft Windows SystemUsing PuTTY
Learn to access a compute node from a Microsoft Windows system using PuTTY.
1. Run the PuTTY program (putty.exe).
The PuTTY Configuration window is displayed, showing the Session panel.
2. In the Host Name (or IP address) field, enter the host name or IP address of thecompute node that you want to access.
3. Confirm that the Connection type option is set to SSH.
4. In the Category tree, expand Connection if necessary and then click Data.
The Data panel is displayed.
5. In the Auto-login username field, enter the operating system user you want toconnect as:
a. Connect as oracle to perform operations as the Oracle Database softwareowner; this user does not have root user access to the compute node.
b. Connect as opc to perform operations that require root access to the computenode, such as patching. This user can use the sudo -s command to gain rootuser access to the compute node.
6. Confirm that the When username is not specified option is set to Prompt.
7. In the Category tree, expand SSH and then click Auth.
The Auth panel is displayed.
8. Click the Browse button next to the Private key file for authentication field.Then, navigate to and open the private key file that corresponds to a public keythat is registered in the system.
9. In the Category tree, click Session.
The Session panel is displayed.
10. In the Saved Sessions field, enter a name for the connection configuration. Then,click Save.
11. Click Open to open the connection.
The PuTTY Configuration window closes and the PuTTY terminal windowdisplays.
Chapter 11Connecting to a Compute Node with SSH
11-2
Accessing a Database After You Connect to the Compute NodeAfter you connect to a compute node, you can use the following series of commandsto identify a database and connect to it.
1. Log in as the oracle user. For example:
$ ssh -i keyfile oracle@node01[oracle@node01 ~]$
2. Use the srvctl utility located under the Oracle Grid Infrastructure home directoryto list the databases on the system. For example:
[oracle@node01 ~]$ /u01/app/12.2.0.1/grid/bin/srvctl config database -vnc122 /u02/app/oracle/product/12.2.0/dbhome_6 12.2.0.1.0s12c /u02/app/oracle/product/12.2.0/dbhome_2 12.2.0.1.0
3. Identify the database instances for the database that you want to access. Forexample:
[oracle@node01 ~]$ /u01/app/12.2.0.1/grid/bin/srvctl status database -d s12cInstance s12c1 is running on node node01Instance s12c2 is running on node node02
4. Configure the environment settings for the database that you want to access. Forexample:
[oracle@node01 ~]$ . oraenvORACLE_SID = [oracle] ? s12cThe Oracle base has been set to /u02/app/oracle[oracle@node01 ~]$ export ORACLE_SID=s12c1
5. You can use the svrctl command to display more detailed information about thedatabase. For example:
[oracle@node01 ~]$ srvctl config database -d s12cDatabase unique name: s12cDatabase name:Oracle home: /u02/app/oracle/product/12.2.0/dbhome_2Oracle user: oracleSpfile: +DATAC4/s12c/spfiles12c.oraPassword file: +DATAC4/s12c/PASSWORD/passwdDomain: example.comStart options: openStop options: immediateDatabase role: PRIMARYManagement policy: AUTOMATICServer pools:Disk Groups: DATAC4Mount point paths:Services:
Chapter 11Connecting to a Compute Node with SSH
11-3
Type: RACStart concurrency:Stop concurrency:OSDBA group: dbaOSOPER group: racoperDatabase instances: s12c1,s12c2Configured nodes: node01,node02CSS critical: noCPU count: 0Memory target: 0Maximum memory: 0Default network number for database services:Database is administrator managed
6. You can access the database by using SQL*Plus. For example:
[oracle@node01 ~]$ sqlplus / as sysdba
SQL*Plus: Release 12.2.0.1.0 Production ...
Copyright (c) 1982, 2016, Oracle. All rights reserved.
Connected to:Oracle Database 12c EE Extreme Perf Release 12.2.0.1.0 - 64bit Production
SQL>
Connecting from a Unix-Style SystemTo access a compute node on an Oracle Cloud@Customer system from a Unix-stylesystem using SSH, use this procedure.
• Enter the following SSH command to access the compute node:
$ ssh –i private-keyuser@node
In the preceding syntax:
– private-key is the full path and name of the file that contains the SSH privatekey that corresponds to a public key that is registered in the system.
– user is the operating system user that you want to use to connect:
* To perform operations as the Oracle Database software owner, connect asoracle. This user does not have root user access to the compute node.
* To perform operations that require root access to the compute node, suchas patching, connect as opc. The opc user can use the sudo -s commandto gain root access to the compute node.
– node is the host name or IP address for the compute node that you want toaccess.
Chapter 11Connecting to a Compute Node with SSH
11-4
Connecting to a Database with Oracle Net ServicesYou can connect to the compute nodes in an Exadata Cloud@Customer system usingOracle Net Services.
• Using Oracle Net Services to Connect to a DatabaseOracle Database Exadata Cloud@Customer supports remote database access byusing Oracle Net Services.
• Prerequisites for Connecting to a Database with Oracle Net ServicesReview the prerequisites to connect to an Oracle Database instance on OracleCloud@Customer using Oracle Net Services.
• Connecting to a Database Using SCANTo create an Oracle Net Services connection by using the SCAN listeners, you canchoose between two approaches.
• Connecting to a Database Using a Node ListenerTo connect to an Oracle Database instance on Exadata Cloud@Customer with aconnect descriptor that bypasses the SCAN listeners, use this procedure to routeyour connection directly to a node listener.
Using Oracle Net Services to Connect to a DatabaseOracle Database Exadata Cloud@Customer supports remote database access byusing Oracle Net Services.
Because Exadata Cloud@Customer uses Oracle Grid Infrastructure, you can makeOracle Net Services connections by using Single Client Access Name (SCAN)connections. SCAN is a feature that provides a consistent mechanism for clients toaccess the Oracle Database instances running in a cluster.
By default, the SCAN is associated with three virtual IP addresses (VIPs). Each SCANVIP is also associated with a SCAN listener that provides a connection endpoint forOracle Database connections using Oracle Net Services. To maximize availability,Oracle Grid Infrastructure distributes the SCAN VIPs and SCAN listeners across theavailable cluster nodes. In addition, if there is a node shutdown or failure, then theSCAN VIPs and SCAN listeners are automatically migrated to a surviving node. Byusing SCAN connections, you enhance the ability of Oracle Database clients to have areliable set of connection endpoints that can service all of the databases running in thecluster.
The SCAN listeners are in addition to the Oracle Net Listeners that run on everynode in the cluster, which are also known as the node listeners. When an Oracle NetServices connection comes through a SCAN connection, the SCAN listener routes theconnection to one of the node listeners, and plays no further part in the connection. Acombination of factors, including listener availability, database instance placement, andworkload distribution, determines which node listener receives each connection.
Note:
This documnentation provides basic requirements for connecting to yourExadata Cloud@Customer databases by using Oracle Net Services.
Chapter 11Connecting to a Database with Oracle Net Services
11-5
Prerequisites for Connecting to a Database with Oracle Net ServicesReview the prerequisites to connect to an Oracle Database instance on OracleCloud@Customer using Oracle Net Services.
To connect to an Oracle Database on Exadata Cloud@Customer with Oracle NetServices, you need the following:
• The IP addresses for your SCAN VIPs, or the hostname or IP address for acompute node that hosts the database that you want to access.
• The database identifier: Either the database system identifier (SID), or a servicename.
Connecting to a Database Using SCANTo create an Oracle Net Services connection by using the SCAN listeners, you canchoose between two approaches.
• Connecting to a Database Using a Connect Descriptor that References All of theSCAN VIPsYou can set up a connect descriptor for Oracle Exadata Cloud@Customer Systemusing multiple SCAN listeners.
• Connecting to a Database Use a Connect Descriptor that References a CustomSCAN NameYou can set up a connect descriptor for Oracle Exadata Cloud@Customer Systemusing a custom SCAN name.
Connecting to a Database Using a Connect Descriptor that References All ofthe SCAN VIPs
You can set up a connect descriptor for Oracle Exadata Cloud@Customer Systemusing multiple SCAN listeners.
This approach requires you to supply all of the single client access name (SCAN)virtual IP (VIP) addresses, and enables Oracle Net Services to connect to an availableSCAN listener.
• Use the following template to define a Net Services alias, which is typically used toprovide a convenient name for the connect descriptor:
alias-name = (DESCRIPTION= (ADDRESS_LIST= (ADDRESS=(PROTOCOL=tcp)(HOST=SCAN-VIP-1)(PORT=1521)) (ADDRESS=(PROTOCOL=tcp)(HOST=SCAN-VIP-2)(PORT=1521)) (ADDRESS=(PROTOCOL=tcp)(HOST=SCAN-VIP-3)(PORT=1521))) (CONNECT_DATA=(sid-or-service-entry)))
Where:
alias-name is the name you use to identify the alias.
SCAN-VIP-[1–3] are the IP addresses for the SCAN VIPs.
Chapter 11Connecting to a Database with Oracle Net Services
11-6
sid-or-service-entry identifies the database SID or service name using one ofthe following formats:
• SID=sid-name. For example: SID=S12C1.
• SERVICE_NAME=service-name. For example:SERVICE_NAME=PDB1.example.yourcloud.com.
Note:
By default, Oracle Net Services randomly selects one of the addressesin the address list to balance the load between the SCAN listeners.
Connecting to a Database Use a Connect Descriptor that References a CustomSCAN Name
You can set up a connect descriptor for Oracle Exadata Cloud@Customer Systemusing a custom SCAN name.
Using this approach, you define a custom single client access name (SCAN) namein your domain name server (DNS), which resolves to the three SCAN virtual IPaddresses (VIPs).
• Use the following template to define a Net Services alias that references thecustom SCAN name:
alias-name = (DESCRIPTION= (ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=scan-name)(PORT=1521))) (CONNECT_DATA=(sid-or-service-entry)))
Where:
alias-name is the name you use to identify the alias.
scan-name is the custom SCAN name.
sid-or-service-entry identifies the database SID or service name using one ofthe following formats:
• SID=sid-name. For example: SID=S12C1.
• SERVICE_NAME=service-name. For example:SERVICE_NAME=PDB1.example.yourcloud.com.
Alternatively, you can use the easy connect method to specify a connect descriptorwith the following format:
scan-name:1521/sid-or-service-entry
For example:
exa1scan.example.com:1521/S12C1
Chapter 11Connecting to a Database with Oracle Net Services
11-7
Or
exa1scan.example.com:1521/PDB1.example.yourcloud.com
Connecting to a Database Using a Node ListenerTo connect to an Oracle Database instance on Exadata Cloud@Customer with aconnect descriptor that bypasses the SCAN listeners, use this procedure to route yourconnection directly to a node listener.
By using this method, you give up the high-availability and load-balancing providedby SCAN. However, this method may be desirable if you want to direct connectionsto a specific node or network interface. For example, you might want to ensure thatconnections from a program that performs bulk data loading use the backup network.
Using this approach, you direct your connection using the hostname or IP address ofthe node.
Example 11-1 Defining a Net Service Alias That Directly References the Node
alias-name = (DESCRIPTION= (CONNECT_TIMEOUT=timeout) (ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=node)(PORT=1521))) (CONNECT_DATA=(sid-or-service-entry)))
Where:
alias-name is the name you use to identify the alias.
timeout specifies a timeout period (in seconds), which enables you toterminate a connection attempt without having to wait for a TCP timeout. The(CONNECT_TIMEOUT=timeout) parameter is optional.
node is the hostname or IP address for the compute node that you want to use.
sid-or-service-entry identifies the database SID or service name using one of thefollowing formats:
• SID=sid-name. For example, SID=S12C1.
• SERVICE_NAME=service-name. For example,SERVICE_NAME=PDB1.example.oraclecloudatcust.com.
Alternatively, you can use the easy connect method to specify a connect descriptorwith the following format:
node:1521/sid-or-service-entry
For example:
exa1node01.example.com:1521/S12C1
Or
exa1node01.example.com:1521/PDB1.example.oraclecloudatcust.com
Chapter 11Connecting to a Database with Oracle Net Services
11-8
12Maintaining an Exadata Cloud@CustomerSystem
Learn how to perform patching operations on Exadata Cloud@Customerinfrastructure.
• User-Managed Maintenance Updates
• Oracle Managed Exadata Cloud@Customer Infrastructure Maintenance Updates
User-Managed Maintenance UpdatesMaintaining a secure Exadata Cloud@Customer system in the best working orderrequires you to perform the following tasks regularly:
• Patching the Oracle Grid Infrastructure and Oracle Database software onthe Exadata compute nodes. See Patching and Updating an ExadataCloud@Customer System Manually and Oracle Clusterware Configuration andAdministration for information and instructions.
• Updating the operating system and the tooling on the compute nodes. SeePatching and Updating an Exadata Cloud@Customer System Manually forinformation and instructions.
Oracle Managed Exadata Cloud@Customer InfrastructureMaintenance Updates
In addition to the maintenance tasks you perform, Oracle manages the patching andupdating of all other infrastructure components, including the physical compute nodes(Dom0), Exadata storage servers, Exadata InfiniBand switches, ROCE switches, andControl Plane servers. This is referred to as Exadata Cloud@Customer infrastructuremaintenance.
• Overview of the Infrastructure Patching Process
• Scheduling Oracle-Managed Infrastructure Updates
• Monitoring Patching Operations Using Lifecycle State Information
• Receive Notifications about Your Infrastructure Maintenance Updates
Overview of the Infrastructure Patching Process
Infrastructure maintenance begins with patching of the Exadata compute nodes.Compute nodes are updated in a rolling fashion, with a single node being shutdown, patched, and then brought back online while other nodes remain operational.This process continues until all nodes are patched. After compute node patching
12-1
completes, Oracle patches the storage nodes. Storage server patching does notimpact VM cluster nodes availability.
Note that while databases are expected to be available during the patching process,Oracle does not verify that all database services and pluggable databases areavailable after a node is brought back online, as these can depend on the applicationservice definition. Oracle recommends reviewing the documentation on workloadmanagement, application continuity, and client failover best practices to reduce thepotential for an outage with your applications. By following the documentation'sguidelines, the impact of infrastructure patching will be only minor service degradationdue to connection loss as compute nodes are sequentially patched.
Oracle recommends that you follow the Maximum Availability Architecture (MAA)best practices and use Data Guard to ensure the highest availability for your criticalapplications. For databases with Data Guard enabled, Oracle recommends that youseparate the patching windows for the infrastructure instances running the primary andstandby databases, and perform a switchover prior to the maintenance operations forthe infrastructure instance hosting the primary database. This allows you to avoid anyimpact to your primary database during infrastructure patching.
Based on the shape of the rack, maintenance can take up to 30 hours from theschedule start time.
• Maintenance window will start with performing prechecks on all the ExaC@Cinfrastructure components. This will take approximately 2 hours to complete.
• Each Dom0 takes 90 minutes on an average
• Each storage cell takes 60 minutes on an average
• InfiniBand or RoCE switches take 60 minutes on an average
• Control Plane Server takes 240 minutes on an average
The approximate computed time for infrastructure patching operations is as follows:
• Quarter Rack (2 Dom0/3 Storage Cells): Approximately 13 hours
• Half Rack (4 Dom0/6 Storage Cells): Approximately 19 hours
• Full Rack (8 Dom0/12 Storage Cells): Approximately 31 hours
Scheduling Oracle-Managed Infrastructure Updates
Exadata Cloud Service updates are released on a quarterly basis. You can set amaintenance window to determine the time your quarterly infrastructure maintenancewill begin. You can also view scheduled maintenance runs and the maintenancehistory of your Exadata Cloud@Customer in the Oracle Cloud Infrastructure Console.For more information, see the following:
• Set the Automatic Maintenance Schedule for Exadata Cloud@CustomerInfrastructure
• View or Edit the Time of the Next Scheduled Maintenance for ExadataCloud@Customer Infrastructure
• View the Maintenance History of Exadata Cloud@Customer Infrastructure
In exceptional cases, Oracle might need to update your system apart from the regularquarterly updates to apply time-sensitive changes such as security updates. While you
Chapter 12Oracle Managed Exadata Cloud@Customer Infrastructure Maintenance Updates
12-2
cannot opt out of these infrastructure updates, Oracle alerts you in advance throughthe Cloud Notification Portal to help you plan for them.
• Set the Automatic Maintenance Schedule for Exadata Cloud@CustomerInfrastructureLearn how to set the maintenance schedule for an Exadata Cloud@Customerinfrastructure.
• View or Edit the Time of the Next Scheduled Maintenance for ExadataCloud@Customer InfrastructureLearn how to view and edit the time of the next scheduled maintenance.
• View the Maintenance History of Exadata Cloud@Customer InfrastructureLearn how to view the maintenance history for an Exadata Cloud@CustomerInfrastructure.
Set the Automatic Maintenance Schedule for Exadata Cloud@CustomerInfrastructure
Learn how to set the maintenance schedule for an Exadata Cloud@Customerinfrastructure.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose your Compartment.
3. Click Exadata Infrastructure.
4. In the list of Exadata Infrastructures, find the infrastructure you want to set themaintenance window for and click its highlighted name.
5. On the infrastructure details page, under Maintenance, click the edit link in theMaintenance Details field.
6. In the Edit Automatic Maintenance page, select Specify a schedule.
7. Under Maintenance months, specify at least one month for each quarter duringwhich Exadata infrastructure maintenance will take place. You can select morethan one month per quarter. If you specify a long lead time for advancednotification (for example, 4 weeks), you may wish to specify 2 or 3 months perquarter during which maintenance runs can occur. This will ensure that yourmaintenance updates are applied in a timely manner after accounting for yourrequired lead time. Lead time is discussed in the following steps.
8. Optional. Under Week of the month, specify which week of the monthmaintenance will take place. Weeks start on the 1st, 8th, 15th, and 22nd days ofthe month, and have a duration of 7 days. Weeks start and end based on calendardates, not days of the week. Maintenance cannot be scheduled for the fifth weekof months that contain more than 28 days. If you do not specify a week of themonth, Oracle will run the maintenance update in a week to minimize disruption.
9. Optional. Under Day of the week, specify the day of the week on which themaintenance will occur. If you do not specify a day of the week, Oracle will run themaintenance update on a weekend day to minimize disruption.
10. Optional. Under Start hour, specify the hour during which the maintenance runwill begin. If you do not specify a start hour, Oracle will pick the least disruptivetime to run the maintenance update.
11. Under Lead Time, specify the minimum number of weeks ahead of themaintenance event you would like to receive a notification message. Your lead
Chapter 12Oracle Managed Exadata Cloud@Customer Infrastructure Maintenance Updates
12-3
time ensures that a newly released maintenance update is scheduled to accountfor your required minimum period of advanced notification.
12. Click Save Changes.
View or Edit the Time of the Next Scheduled Maintenance for ExadataCloud@Customer Infrastructure
Learn how to view and edit the time of the next scheduled maintenance.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose your Compartment.
3. Click Exadata Infrastructure.
4. In the list of Exadata Infrastructures, find the infrastructure you want to set themaintenance window for and click its highlighted name.
5. On the infrastructure details page, under Maintenance, click the view link in theNext Maintenance field.
6. On the Maintenance page, scheduled maintenance events are listed.
7. Optional. To change the time of the next scheduled maintenance, click the Editlink in the Scheduled Start Time field.
8. In the Edit Infrastructure Maintenance Scheduled Start Time page, enter adate and time in the Scheduled Start time field.
The following restrictions apply:
• Infrastructure maintenance cannot be rescheduled to occur more than sixmonths after the announcement of the maintenance update's availability. Ifa new patch is announced prior to your rescheduled maintenance run, thenewer patch will be applied on your specified date. You can reschedule yourmaintenance to take place earlier than it is currently scheduled. You cannotreschedule start time less than two hours from the current time.
• Oracle reserves certain dates each quarter for internal maintenanceoperations, and you cannot schedule your maintenance on these dates.
View the Maintenance History of Exadata Cloud@Customer InfrastructureLearn how to view the maintenance history for an Exadata Cloud@CustomerInfrastructure.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose your Compartment.
3. Click Exadata Infrastructure.
4. In the list of Exadata Infrastructures, find the infrastructure you want to set themaintenance window for and click its highlighted name.
5. On the infrastructure details page, under Maintenance, click the view link in theNext Maintenance field.
6. Click Maintenance History to see a list of past maintenance events includingdetails on their completion state.
Chapter 12Oracle Managed Exadata Cloud@Customer Infrastructure Maintenance Updates
12-4
Monitoring Patching Operations Using Lifecycle State Information
The lifecycle state of your infrastructure resource (either the cloud Exadatainfrastructure or the DB system resource) enables you to monitor when the patchingof your infrastructure resource begins and ends. In the Oracle Cloud InfrastructureConsole, you can see lifecycle state details messages on the Exadata InfrastructureDetails or DB System Details page when a tool tip is displayed beside the Status field.You can also access these messages using the ListExadataInfrastructures API, andusing tools based on the API, including SDKs and the OCI CLI.
During patching operations, you can expect the following:
• If you specify a maintenance window, then patching begins at your specifiedstart time. The patching process starts with a series of prerequisite checksto ensure that your system can be successfully patched. These checks takeapproximately 30 minutes to complete. While the system is performing the checks,the infrastructure resource's lifecycle state remains "Available," and there is nolifecycle state message.
For example, if you specify that patching should begin at 8:00 a.m., then Oraclebegins patching operations at 8:00, but the infrastructure resource's lifecycle statedoes not change from "Available" to "Maintenance in Progress" until approximately8:30 a.m.
• When Exadata compute node patching starts, the infrastructure resource'slifecycle state is "Maintenance in Progress", and the associated lifecycle statemessage is "The underlying infrastructure of this system (dbnodes) is beingupdated."
• When cell storage patching starts, the infrastructure resource's lifecycle state is"Maintenance in Progress", and the associated lifecycle state message is "Theunderlying infrastructure of this system (cell storage) is being updated and this willnot impact Database availability."
• After cell patching is complete, the networking switches are patched one at a time,in a rolling fashion.
• When patching is complete, the infrastructure resource's lifecycle state is"Available", and the Console and API-based tools do not provide a lifecycle statemessage.
Receive Notifications about Your Infrastructure Maintenance Updates
There are two ways to receive notifications. One is through email to infrastructuremaintenance contacts and the other one is to subscribe to the maintenance eventsand get notified.
Oracle schedules maintenance run of your infrastructure based on your schedulingpreferences and sends email notifications to all your infrastructure maintenancecontacts. You can login to the console and view details of the schedule maintenancerun. Appropriate maintenance related events will be generated as Oracle prepares foryour scheduled maintenance run, for example, precheck, patching started, patchingend, and so on. For more information about all maintenance related events, seeExadata Cloud@Customer Infrastructure Patching Event Types. In case, if there
Chapter 12Oracle Managed Exadata Cloud@Customer Infrastructure Maintenance Updates
12-5
are any failures, then Oracle reschedules your maintenance run, generates relatednotification, and notifies your infrastructure maintenance contacts.
For more information about Oracle Cloud Infrastructure Events, see Overview ofEvents. To receive additional notifications other than the ones sent to infrastructuremaintenance contacts, you can subscribe to infrastructure maintenance events andget notified using the Oracle Notification service, see Notifications Overview.
• Infrastructure Maintenance Contacts
Infrastructure Maintenance Contacts
Maintenance contacts are required for service request based communications forhardware replacement and other maintenance events.
Add a primary maintenance contact and optionally add a maximum of nine secondarycontacts. Both the primary and secondary contacts receive all notifications abouthardware replacement, network issues, and software maintenance runs.
You can promote any secondary contacts as the primary anytime you want. When youpromote a secondary contact to primary, the current primary contact will be demotedautomatically to secondary.
For more information, see: Using the Console to Create Infrastructure and ManagingInfrastructure Maintenance Contacts.
Related Topics
• Using the Console to Create InfrastructureTo create your Oracle Exadata Cloud@Customer infrastructure, be prepared toprovide values for the fields required for configuring the infrastructure.
• Managing Infrastructure Maintenance ContactsLearn to manage your Exadata infrastructure maintenance contacts.
Chapter 12Oracle Managed Exadata Cloud@Customer Infrastructure Maintenance Updates
12-6
13Patching an Exadata Cloud@CustomerSystem
Learn how to perform patching operations on Exadata database compute nodes andDatabase Homes by using the Console, API, or the CLI.
For information and instructions on patching the system by using the dbaascli utility,see "Patching and Updating an Exadata Cloud@Customer System Manually".
• Required IAM Policy for Patching an Exadata Cloud@Customer SystemReview the identity access management (IAM) policy for Patching an ExadataCloud@Customer System
• About Patching VM Clusters and Database Homes
• Prerequisites for Patching an Exadata Cloud@Customer SystemCheck and apply the latest Cloud patches that are dowloaded and made availableby Oracle on the CPS host.
• Using the Console for Patching an Exadata Cloud@Customer SystemLearn how to use the console to view the history of patch operations on VM clusterand Database Homes, apply patches, and monitor the status of patch operations.
• Using the API for Patching an Exadata Cloud@Customer SystemUse various API features to help manage patching an Oracle ExadataCloud@Customer system.
Related Topics
• Patching and Updating an Exadata Cloud@Customer System Manually
Required IAM Policy for Patching an ExadataCloud@Customer System
Review the identity access management (IAM) policy for Patching an ExadataCloud@Customer System
A policy is an IAM document that specifies who has what type of access to yourresources. It is used in different ways: to mean an individual statement written inthe policy language; to mean a collection of statements in a single, named "policy"document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean theoverall body of policies your organization uses to control access to resources.
A compartment is a collection of related resources that can be accessed onlyby certain groups that have been given permission by an administrator in yourorganization.
To use Oracle Cloud Infrastructure, you must be given the required type of access ina policy written by an administrator, whether you're using the Console, or the RESTAPI with a software development kit (SDK), a command-line interface (CLI), or someother tool. If you try to perform an action, and receive a message that you don’t
13-1
have permission, or are unauthorized, then confirm with your administrator the type ofaccess you've been granted, and which compartment you should work in.
For administrators: The policy in "Let database admins manage DB systems" lets thespecified group do everything with databases, and related database resources.
If you're new to policies, then see "Getting Started with Policies" and "CommonPolicies". If you want to dig deeper into writing policies for databases, then see "Detailsfor the Database Service".
Related Topics
• Let database admins manage DB systems
• Getting Started with Policies
• Common Policies
• Details for the Database Service
About Patching VM Clusters and Database HomesPatching an VM Clusters updates the components on all the compute nodes in thatsystem. VM cluster patching updates the grid infrastructure (GI) and Database Homepatching updates the Oracle Database software shared by the databases in thathome.
Currently, the following patches are available:
Table 13-1 VM Cluster and Oracle Database patches
Version VM Cluster Patch Database Patch
19.0.0.0 April 2020, January 2020 April 2020, January 2020,October 2019, July 2019
18.0.0.0 April 2020, January 2020 April 2020, January 2020,October 2019, July 2019
12.2.0.1 April 2020, January 2020 April 2020, January 2020,October 2019, July 2019
12.1.0.2 April 2020, January 2020 April 2020, January 2020,October 2019, July 2019
11.2.0.4 Not applicable April 2020, January 2020,October 2019, July 2019
Consider the following best practices:
• Because patching a system requires a reboot, plan to run the operations at a timewhen they will have minimal impact on users.
• Oracle recommends that you back up your databases before you apply anypatches. For information about backing up the databases, see ManagingDatabase Backup and Recovery on Exadata Cloud@Customer.
• Your Oracle Grid Infrastructure must be at or higher version than the databaseversion you want to patch to. This may require you to first patch a VM clusterbefore you patch the Databases Homes within that system.
Chapter 13About Patching VM Clusters and Database Homes
13-2
• To patch a database to a version other than the database version of the currenthome, move the database to a Database Home running the target version. SeeMoving Databases to Another Home.
Related Topics
• Managing Database Backup and Recovery on Oracle Exadata Cloud@CustomerLearn how to work with the backup and recovery facilities provided by OracleExadata Cloud@Customer.
• Using the Console to Move a Database to Another HomeYou can update the version of a VM cluster database by moving it to a DatabaseHome that is running the version of Oracle Database you are interested in.
Prerequisites for Patching an Exadata Cloud@CustomerSystem
Check and apply the latest Cloud patches that are dowloaded and made available byOracle on the CPS host.
Ensure that the following conditions are met to avoid patching failures:
• The /u01 directory on the database host file system has at least 15 GB of freespace for the execution of patching processes.
• The Oracle Clusterware is up and running on the VM cluster.
• All nodes of the VM cluster are up and running.
Using the Console for Patching an ExadataCloud@Customer System
Learn how to use the console to view the history of patch operations on VM clusterand Database Homes, apply patches, and monitor the status of patch operations.
Oracle recommends that you use the precheck action to ensure your VM cluster orDatabase Home has met the requirements for the patch you want to apply.
• Using the Console to Perform a Patch Operation on a VM ClusterLearn to apply patches on a VM cluster.
• Using the Console to Perform a Patch Operation on a Database HomeLearn to apply patches on a Database Home.
• Using the Console to View Patch HistoryEach patch history entry represents an attempted patch operation and indicateswhether the operation was successful or failed. You can retry a failed patchoperation. Repeating an operation results in a new patch history entry.
• Using the Console to Move a Database to Another HomeYou can update the version of a VM cluster database by moving it to a DatabaseHome that is running the version of Oracle Database you are interested in.
Using the Console to Perform a Patch Operation on a VM ClusterLearn to apply patches on a VM cluster.
Chapter 13Prerequisites for Patching an Exadata Cloud@Customer System
13-3
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster on which you want to perform apatch operation.
4. Under Oracle Grid Infrastructure Version, click View Patches.
5. Review the scope:
• VM Cluster: Automatically set to the context from which you have launchedthis page.
• Database Home: Automatically set to the context from which you havelaunched this page. If you have not set the context, then select the DatabaseHome first.
6. Review the list of available patches for the VM cluster.
7. Click the Actions icon (three dots) for the patch you are interested in, and thenclick one of the following actions:
• Run Precheck: Check for any prerequisites to make sure that the patch canbe successfully applied. Oracle highly recommends that you run this operationbefore you apply a patch.
• Apply Patch: Applies the selected patch.
8. Confirm when prompted.
The patch list displays the status of the operation. While a patch is being applied, thepatch's status displays as Patching and the VM cluster's status displays as Updating.Lifecycle operations on the VM clusterand its resources might be temporarilyunavailable. If patching completes successfully, the patch's status changes to Appliedand the VM cluster's status changes to Available. You can view more details about anindividual patch operation by clicking Patch History.
Using the Console to Perform a Patch Operation on a Database HomeLearn to apply patches on a Database Home.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster where the Database Home islocated.
4. Under Resources, click Database Homes.
5. In the list of Database Homes, click the Database Home on which you want toperform a patch operation.
6. Under Database Software Version, click View Patches.
7. Review the scope:
Chapter 13Using the Console for Patching an Exadata Cloud@Customer System
13-4
• Database Home: Automatically set to the context from which you havelaunched this page.
8. Review the list of available patches for the Database Home.
9. Click the Actions icon (three dots) for the patch you are interested in, and thenclick one of the following actions:
• Run Precheck: Check for any prerequisites to make sure that the patch canbe successfully applied. Oracle highly recommends that you run this operationbefore you apply a patch.
• Apply Patch: Applies the selected patch.
10. Confirm when prompted.
The patch list displays the status of the operation. While a patch is being applied, thepatch's status displays as Patching and the status of the Database Home and thedatabases in it display as Updating. During the operation, each database in the homeis stopped and then restarted. If patching completes successfully, the patch's statuschanges to Applied and the Database Home's status changes to Available. You canview more details about an individual patch operation by clicking Patch History.
Using the Console to View Patch HistoryEach patch history entry represents an attempted patch operation and indicateswhether the operation was successful or failed. You can retry a failed patch operation.Repeating an operation results in a new patch history entry.
Patch history views in the Console do not show patches that were applied by usingcommand line tools such as dbaascli.
• Using the Console to View the Patch History of a VM ClusterLearn how to view the history of patches applied on a VM cluster.
• Using the Console to View the Patch History of a Database HomeLearn how to view the history of patches applied on a Database Home.
Using the Console to View the Patch History of a VM ClusterLearn how to view the history of patches applied on a VM cluster.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster you are interested in.
4. Under Oracle Grid Infrastructure Version, click View Patches.
5. Click Patch History.
The history of patch operations for that VM cluster is displayed, along with the historyof patch operations on its Database Homes.
Using the Console to View the Patch History of a Database HomeLearn how to view the history of patches applied on a Database Home.
Chapter 13Using the Console for Patching an Exadata Cloud@Customer System
13-5
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster where the Database Home islocated.
4. Under Resources, click Database Homes.
A list of Database Homes is displayed.
5. In the list of Database Homes, click the Database Home you are interested in.
6. Under Database Software Version, click View Patches.
7. Click Patch History.
The history of patch operations for that Database Home is displayed, along with thehistory of patch operations on the VM cluster to which it belongs.
Using the Console to Move a Database to Another HomeYou can update the version of a VM cluster database by moving it to a DatabaseHome that is running the version of Oracle Database you are interested in.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
VM Clusters is selected by default.
2. Choose your Compartment.
A list of VM Clusters is displayed for the chosen Compartment.
3. In the list of VM clusters, click the VM cluster where the database you want tomove is located.
4. Under Resources, click Database Homes.
5. In the list of Database Homes, click the Database Home you are interested in.
A list of databases is displayed.
6. In the list of databases, click the database you are interested in.
7. Go to Actions, and then click Move to Another Home.
8. Select the target Database Home.
9. Click Move Database.
The database will be stopped in the current home and then restarted in thedestination home.
10. Confirm the move operation.
The database will be stopped in the current home and then restarted in the destinationhome. While the database is being moved, the Database Home status displays asMoving Database. When the operation completes, Database Home is updated with thecurrent home. If the operation is unsuccessful, the status of the database displays asFailed, and the Database Home field provides information about the reason for thefailure.
Chapter 13Using the Console for Patching an Exadata Cloud@Customer System
13-6
Using the API for Patching an Exadata Cloud@CustomerSystem
Use various API features to help manage patching an Oracle ExadataCloud@Customer system.
For information about using the API and signing requests, see "REST APIs" and"Security Credentials". For information about SDKs, see "Software Development Kitsand Command Line Interface".
Use these API operations to manage patching VM clusters and Database Homes.
VM cluster:
• UpdateVmCluster
Database Homes:
• CreateDbHome
• UpdateDbHome
• DeleteDbHome
Database:
• CreateDatabase
• UpdateDatabase
• DeleteDatabase
For the complete list of APIs for the Database service, see "Database Service API".
Related Topics
• REST APIs
• Security Credentials
• Software Development Kits and Command Line Interface
• UpdateVmCluster
• CreateDbHome
• UpdateDbHome
• DeleteDbHome
• CreateDatabase
• UpdateDatabase
• DeleteDatabase
• Database Service API
Chapter 13Using the API for Patching an Exadata Cloud@Customer System
13-7
14Patching and Updating an ExadataCloud@Customer System Manually
This topic describes the responsibilities and procedures for patching and updatingvarious components in Exadata Cloud@Customer.
Note:
For more guidance on achieving continuous service during patchingoperations, see the Continuous Availability white paper.
• Managing VM Clusters on Exadata Cloud@CustomerOracle performs patches and updates to all of the Oracle-managed systemcomponents on Exadata Cloud@Customer.
• Administering Software ImagesOracle maintains a library of cloud software images and provides capabilitiesto view the library and download images to your Oracle Database ExadataCloud@Customer DomU. Using these facilities, you can control the version ofOracle binaries that is used when a new Oracle Home is created.
• Managing Oracle Database and Oracle Grid Infrastructure PatchesYou are responsible for routine patching of Oracle Database and Oracle GridInfrastructure software.
• Manually Patching Oracle Database and Oracle Grid Infrastructure SoftwareFor Oracle Java VM, daylight savings time, and some routine or one-off patches, itcan be necessary for you to patch software manually.
• Updating the Compute Node Operating SystemLearn about standard Exadata tools and techniques that you can use to updatethe operating system components on the Exadata Cloud@Customer computenodes.
• Cloud Tooling UpdatesYou are responsible for updating the cloud-specific tooling included on the ExadataCloud@Customer compute nodes.
Managing VM Clusters on Exadata Cloud@CustomerOracle performs patches and updates to all of the Oracle-managed systemcomponents on Exadata Cloud@Customer.
Oracle patches and updates include the physical compute nodes (Dom0), networkswitches, power distribution units (PDUs), integrated lights-out management (ILOM)interfaces, and the Exadata Storage Servers.
In all but rare exceptional circumstances, you receive advance communication aboutthese updates to help you plan for them. If there are corresponding recommended
14-1
updates for your compute node virtual machines (VMs), then Oracle providesnotification about them.
Wherever possible, scheduled updates are performed in a manner that preservesservice availability throughout the update process. However, there can be somenoticeable impact on performance and throughput while individual system componentsare unavailable during the update process.
For example, Dom0 patching typically requires a reboot. In such cases, whereverpossible, the compute nodes are restarted in a rolling manner, one at a time, toensure that the service remains available throughout the process. However, eachcompute node is unavailable for a short time while it restarts, and the overall servicecapacity diminishes accordingly. If your applications cannot tolerate the restarts, thentake mitigating action as needed. For example, shut down an application while Dom0patching occurs.
Administering Software ImagesOracle maintains a library of cloud software images and provides capabilities to viewthe library and download images to your Oracle Database Exadata Cloud@CustomerDomU. Using these facilities, you can control the version of Oracle binaries that is usedwhen a new Oracle Home is created.
When you create a new database deployment with a new Oracle Home, the OracleDatabase binaries are sourced from a software image that is stored and set as adefault in your Exadata Cloud@Customer DomU ACFS volume. Over time, the softwareimages in your Exadata Cloud@Customer instance will become old if they are notmaintained. Using an old software image means that you need to apply patches tonewly installed binaries to bring them up to date, which is unnecessarily laborious andpossibly prone to error.
Software image administration uses the dbaascli utility, which is part of thecloud-specific tooling included in Exadata Cloud@Customer. To use the latestenhancements, you should update to the latest version of the cloud tools. See CloudTooling Update.
Note:
If you create a new database deployment in an existing Oracle Homedirectory location, and if the default software image version is higher orlower than the Oracle Home version, a check is made to know if the imagesrequired for creating the database exist on DomU. If the image does not exist,an internal command is issued by the cloud automation software to downloadand use the required image from control plane server to DomU to create thedatabase.
When you create a new Oracle Home, it will be created with the RU thatis set as the default image for that Database version. If you want to createa new Oracle Home with the RU that is higher or lower than the defaultimage, you first need to change the default image to match with the RU thatyou want to create a new Oracle Home with by using Activating a Softwareimage.
Chapter 14Administering Software Images
14-2
• Viewing Information About Downloaded Software ImagesYou can view information about Oracle Database software images that aredownloaded to your Exadata Cloud@Customer environment by using the dbimagelist subcommand of the dbaascli utility.
• Viewing Information About Available Software ImagesYou can view information about Oracle Database software images that areavailable to download to your Exadata Cloud@Customer environment by usingthe cswlib list subcommand of the dbaascli utility.
• Downloading a Software ImageYou can download available software images and make them available inyour Exadata Cloud@Customer environment by using the cswlib downloadsubcommand of the dbaascli utility.
• Activating a Software ImageYou can use the following procedure to activate a specific software image, makingit the default software image for the corresponding software release in yourExadata Cloud@Customer environment.
• Deleting a Software ImageYou can use the following procedure to delete a software image from your ExadataCloud@Customer environment.
Related Topics
• Cloud Tooling Update
Viewing Information About Downloaded Software ImagesYou can view information about Oracle Database software images that aredownloaded to your Exadata Cloud@Customer environment by using the dbimagelist subcommand of the dbaascli utility.
1. Connect to a compute node as the opc user.
For detailed instructions, see Connecting to a Compute Node Through SecureShell (SSH).
2. Start a root-user command shell:
$ sudo -s#
3. Run the dbaascli command with the dbimage list option:
# dbaascli dbimage list
The command displays a list of software images that are downloaded to yourExadata Cloud@Customer environment, including version and bundle patchinformation.
4. Exit the root-user command shell:
# exit$
Chapter 14Administering Software Images
14-3
Related Topics
• Connecting to a Compute Node Through Secure Shell (SSH)
Viewing Information About Available Software ImagesYou can view information about Oracle Database software images that are available todownload to your Exadata Cloud@Customer environment by using the cswlib listsubcommand of the dbaascli utility.
1. Connect to a compute node as the opc user.
For detailed instructions, see Connecting to a Compute Node Through SecureShell (SSH).
2. Start a root-user command shell:
$ sudo -s#
3. Run the dbaascli command with the cswlib list option:
# dbaascli cswlib list [ --oss_uri download_location ]
The command displays a list of available software images, including version andbundle patch information that you can use to download the software image.
4. Exit the root-user command shell:
# exit$
Related Topics
• Connecting to a Compute Node Through Secure Shell (SSH)
Downloading a Software ImageYou can download available software images and make them available in yourExadata Cloud@Customer environment by using the cswlib download subcommandof the dbaascli utility.
1. Connect to a compute node as the opc user.
For detailed instructions, see Connecting to a Compute Node Through SecureShell (SSH).
2. Start a root-user command shell:
$ sudo -s#
Chapter 14Administering Software Images
14-4
3. Run the dbaascli command with the cswlib download option:
# dbaascli cswlib download --version software_version --bp software_bp [--bp_update ( yes | no )] [--cdb ( yes | no )] [--oss_uri download_location]
In the preceding command:
• software_version — specifies an Oracle Database software version. Forexample, 11204, 12102, 12201, 18000, 19000.
• software_bp — identifies a bundle patch release. For example, APR2018,JAN2019, OCT2019, and so on.
• --bp_update — optionally indicates whether the downloaded software imagebecomes the current default software image. Default is no.
• --cdb — optionally specifies whether the downloaded software imagesupports the Oracle multitenant architecture. Default is yes. If you specify --cdb no, then a separate software image is downloaded that contains binariesto support non-container databases (non-CDB).
4. Exit the root-user command shell:
# exit$
Related Topics
• Connecting to a Compute Node Through Secure Shell (SSH)
Activating a Software ImageYou can use the following procedure to activate a specific software image, makingit the default software image for the corresponding software release in your ExadataCloud@Customer environment.
1. Connect to a compute node as the opc user.
For detailed instructions, see Connecting to a Compute Node Through SecureShell (SSH).
2. Start a root-user command shell:
$ sudo -s#
3. Run the dbaascli command with the dbimage activateBP option:
# dbaascli dbimage activateBP --version software_version --bp software_bp [--cdb ( yes | no )]
In the preceding command:
• software_version — specifies the Oracle Database software version. Forexample, 11204, 12102, 12201, 18000, 19000.
Chapter 14Administering Software Images
14-5
• software_bp — identifies the bundle patch release. For example, APR2018,JAN2019, OCT2019, and so on.
• --cdb — optionally specifies whether to activate a software image thatsupports the Oracle multitenant architecture. Default is yes. If you specify--cdb no, then the command acts on the software image that containsbinaries to support non-container databases (non-CDB). Please note that Gen2 ExaCC only supports non-CDB for 12.1 and 19c.
The command fails and outputs an error message if the specified software imageis not already downloaded to your Exadata Cloud@Customer environment.
4. Exit the root-user command shell:
# exit$
Related Topics
• Connecting to a Compute Node Through Secure Shell (SSH)
Deleting a Software ImageYou can use the following procedure to delete a software image from your ExadataCloud@Customer environment.
WARNING:
If you delete an image that is not available on Control Plane server, youmay not be able to get it back. To check if the image you are planning tosee is available on Control Plane servers, use the dbaascli cswlib listcommand. If the version you are purging is available in the control planeserver, you can use the dbaascli cswlib download command at a laterpoint in time to get the deleted image back.
1. Connect to a compute node as the opc user.
For detailed instructions, see Connecting to a Compute Node Through SecureShell (SSH).
2. Start a root-user command shell:
$ sudo -s#
3. Run the dbaascli command with the dbimage purge option:
# dbaascli dbimage purge --version software_version --bp software_bp [--cdb ( yes | no )]
In the preceding command:
• software_version — specifies the Oracle Database software version. Forexample, 11204, 12102, 12201, 18000, 19000.
Chapter 14Administering Software Images
14-6
• software_bp — identifies the bundle patch release. For example, APR2018,JAN2019, OCT2019, and so on.
• --cdb — optionally specifies whether to remove the software image thatsupports the Oracle multitenant architecture. Default is yes. If you specify--cdb no, then the software image that contains binaries to support non-container databases (non-CDB) is removed.
If the command will remove a software image that is not currently available inthe software image library, and therefore cannot be downloaded again, then thecommand pauses and prompts for confirmation.
You cannot remove the current default software image for any software version. Toavoid this restriction, you must make another software image the current default.
4. Exit the root-user command shell:
# exit$
Related Topics
• Connecting to a Compute Node Through Secure Shell (SSH)
Managing Oracle Database and Oracle Grid InfrastructurePatches
You are responsible for routine patching of Oracle Database and Oracle GridInfrastructure software.
• About the dbaascli UtilityOn Exadata Cloud@Customer, routine patching of the Oracle Database andOracle Grid Infrastructure software is facilitated by using the dbaascli utility.
• List Available PatchesTo produce a list of available patches for Oracle Exadata Cloud@Customer, youcan use the dbaascli command.
• Check Prerequisites Before Applying a PatchTo list the prerequisites before applying a patch for Oracle ExadataCloud@Customer, run this procedure.
• Apply a PatchTo apply patches for Oracle Exadata Cloud@Customer., use the dbaasclicommand.
• List Applied PatchesTo list the applied patches for Oracle Exadata Cloud@Customer, use thisprocedure.
• Roll Back a PatchTo roll back patches for Oracle Exadata Cloud@Customer, complete thisprocedure.
Chapter 14Managing Oracle Database and Oracle Grid Infrastructure Patches
14-7
About the dbaascli UtilityOn Exadata Cloud@Customer, routine patching of the Oracle Database and OracleGrid Infrastructure software is facilitated by using the dbaascli utility.
The dbaascli utility provides a simple means for applying routine patches, whichOracle periodically loads on to the Cloud Control Plane servers.
The dbaascli utility is part of the cloud-specific tooling bundle that is included withExadata Cloud@Customer. Therefore, before performing the following procedures,ensure that you have the latest version of the cloud-specific tooling on all of thecompute nodes in the VM cluster.
List Available PatchesTo produce a list of available patches for Oracle Exadata Cloud@Customer, you canuse the dbaascli command.
1. Connect to a compute node as the opc user and start a command shell as theroot user.
2. Execute the dbaascli patch db list command:
# dbaascli patch db list --oh hostname:oracle_home
In the preceding command, --oh specifies a compute node and Oracle homedirectory for which you want to list the available patches. In this context, an Oraclehome directory can be an Oracle Database home directory or the Oracle GridInfrastructure home directory.
For example:
# dbaascli patch db list --oh hostname1:/u02/app/oracle/product/12.1.0.2/dbhome_1
Note:
The list of available patches is determined by interrogating the databaseto establish the patches that have already been applied. When a patchis applied, the corresponding database entry is made as part of theSQL patching operation, which is run at the end of the patch workflow.Therefore, the list of available patches can include partially appliedpatches along with patches that are currently being applied.
Check Prerequisites Before Applying a PatchTo list the prerequisites before applying a patch for Oracle Exadata Cloud@Customer,run this procedure.
You can perform the prerequisites-checking operation using the dbaascli commandas follows:
Chapter 14Managing Oracle Database and Oracle Grid Infrastructure Patches
14-8
1. Connect to a compute node as the opc user and start a command shell as theroot user.
2. Execute the dbaascli patch db prereq command:
• On a specific instance:
# dbaascli patch db prereq --patchid patchid --instance1 hostname:oracle_home [--dbnames dbname[,dbname2 ...]]
• By specifying only database names:
# dbaascli patch db prereq --patchid patchid --dbnames dbname[,dbname2 ...] [-alldbs]
In the preceding commands:
– patchid identifies the patch to be pre-checked. .
– --instance1 specifies a compute node and Oracle Home directory thatis subject to the pre-check operation. In this context, an Oracle Homedirectory may be an Oracle Database home directory or the Oracle GridInfrastructure home directory.
– --dbnames specifies the database names for the databases that are thetarget of the pre-check operation.
– -alldbs specifies that you want to pre-check all of the databases thatshare the same Oracle Database binaries (Oracle Home) as the specifieddatabases.
For example:
# dbaascli patch db list --oh hostname1:/u02/app/oracle/product/12.1.0.2/dbhome_1
Chapter 14Managing Oracle Database and Oracle Grid Infrastructure Patches
14-9
Apply a PatchTo apply patches for Oracle Exadata Cloud@Customer., use the dbaascli command.
Tip:
The default SSH configuration will close the terminal session after a fewminutes of inactivity, but some of the dbaascli patching commands (inparticular the patch db apply command) may take longer than the SSHtimeout. As a result, the terminal session where the patch db applycommand is running may be killed before the patching operation is completeon all nodes.
To avoid this situation, use a utility like nohup or screen to avoid killing thepatching operation if the terminal connection is lost for any reason.
For example:
# nohup dbaascli patch db apply 23456789 --instance1 hostname1:/u02/app/oracle/product/12.1.0.2/dbhome_1 --run_datasql 1 >apply_23456789.out 2>&1 &
This example invokes the dbaascli command through the nohup wrapperin the background, and redirects standard output and standard error to thefile apply_23456789.out. The command will keep running even if theterminal gets killed. In that case, reconnect to the system and continuemonitoring apply_23456789.out for completion.
The dbaascli patching operation:
• Can be used to patch some or all of your compute nodes using one command.
• Coordinates multi-node patching in a rolling manner.
• Can run patch-related SQL after patching all the compute nodes in the cluster.
1. Connect to a compute node as the opc user, and start a command shell as theroot user.
2. Run the command dbaascli patch db apply:
For example, on a specific instance, use this syntax:
# dbaascli patch db apply --patchid patchid --instance1 hostname:oracle_home --dbnames dbname[,dbname2 ...]] [--run_datasql 1]
By specifying only database names:
# dbaascli patch db apply --patchid patchid --dbnames dbname[,dbname2 ...] [--run_datasql 1] [-alldbs]
Chapter 14Managing Oracle Database and Oracle Grid Infrastructure Patches
14-10
In the preceding commands:
• patchid identifies the patch to be applied.
• --instance1 specifies a compute node and Oracle home directory that issubject to the patching operation. In this context, an Oracle home directorycan be an Oracle Database home directory or the Oracle Grid Infrastructurehome directory.If you use this argument to specify a shared Oracle home directory, and youdo not specify the --dbnames argument, then all of the databases that sharethe specified Oracle home are patched. After the operation, the Oracle homedirectory location remains unchanged; however, the patch level informationembedded in the Oracle home name is adjusted to reflect the patchingoperation.
• --dbnames specifies the database names for the databases that are the targetof the patching operation.If you use this argument to patch a database that uses a shared Oraclehome, and you do not specify the -alldbs option, then a new Oracle homecontaining the patched Oracle Database binaries is created and the databaseis moved to the new Oracle home.
• -alldbs patches all of the databases that share the same Oracle Databasebinaries (Oracle home as the databases specified in the --dbnames argument.After the operation, the Oracle home directory location remains unchanged;however, the patch level information embedded in the Oracle home name isadjusted to reflect the patching operation.
• --run_datasql 1 instructs the command to run patch-related SQL commands.
– Only run patch-related SQL after all of the compute nodes are patched.Take care not to specify this argument if you are patching a node, andfurther nodes remain to be patched.
– This argument can only be specified with a patching operation on acompute node. If you have patched all of your nodes, and you did notspecify this argument, then you must manually run the SQL commandsassociated with the patch. Typically, running the SQL commands manuallyinvolves running the catbundle.sql script for Oracle Database 11g, or thedatapatch utility for Oracle Database 12c, or later releases. Refer to thepatch documentation for full details.
For example:
# dbaascli patch db apply 23456789 --instance1 hostname1:/u02/app/oracle/product/12.1.0.2/dbhome_1 --run_datasql 1
List Applied PatchesTo list the applied patches for Oracle Exadata Cloud@Customer, use this procedure.
You can use the opatch utility to list the patches that have been applied to an OracleDatabase or Grid Infrastructure installation.
To produce a list of applied patches for an Oracle Database installation:
1. Connect to a compute node as the oracle user.
Chapter 14Managing Oracle Database and Oracle Grid Infrastructure Patches
14-11
2. Set the ORACLE_HOME variable to the location of the Oracle Database installationyou want to examine. For example:
$ export ORACLE_HOME=/u02/app/oracle/product/12.1.0.2/dbhome_1
3. Execute the opatch command with the lspatches option:
$ $ORACLE_HOME/OPatch/opatch lspatches
To produce a list of applied patches for Oracle Grid Infrastructure:
1. Connect to a compute node as the opc user.
2. Become the grid user:
$ sudo -s# su - grid
3. Execute the opatch command with the lspatches option:
$ $ORACLE_HOME/OPatch/opatch lspatches
Roll Back a PatchTo roll back patches for Oracle Exadata Cloud@Customer, complete this procedure.
To roll back a patch or a failed patch attempt, use the dbaascli command.
Rollback patch operations:
• Can be used to roll back a patch on some or all of your compute nodes using onecommand.
• Coordinate multi-node operations in a rolling manner.
• Can run rollback-related SQL after rolling back the patch on all the compute nodesin the cluster.
1. Connect to a compute node as the opc user, and start a command shell as theroot user.
2. Run the dbaascli command with the -rollback_async option:
• On specific instances:
# dbaascli patch db switchback --patchid patchid --instance1 hostname:oracle_home [--dbnames dbname[,dbname2 ...]] [--run_datasql 1]
• By specifying only database names:
# dbaascli patch db switchback --patchid patchid --dbnames dbname[,dbname2 ...] [--run_datasql 1] [-alldbs]
In the preceding commands:
• --patchid identifies the patch that you want to roll back.
Chapter 14Managing Oracle Database and Oracle Grid Infrastructure Patches
14-12
• --instance1 specifies the compute node host name and Oracle homedirectory that is subject to the rollback operation. In this context, an Oraclehome directory can be either an Oracle Database home directory (Oraclehome), or the Oracle Grid Infrastructure (Grid home) directory.If you use this argument to specify a shared Oracle home directory, and youdo not specify the --dbnames argument, then all of the databases that sharethe specified Oracle home are rolled back.
• --dbnames specifies the database names for the databases that are the targetof the rollback operation.
• -alldbs specifies that you want to roll back all of the databases that share thesame Oracle Database binaries (Oracle home) as the databases specified inthe --dbnames argument.
• --run_datasql 1 instructs the command to run rollback-related SQLcommands.
Note:
– Only run rollback-related SQL after all of the compute nodes arerolled back. If you are rolling back a node, and further nodesremain to be rolled back, then do not specify this argument.
– You can only specify this argument as part of a rollbackoperation on a compute node. If you have rolled back all of yournodes, and you did not specify this argument, then you mustrun the SQL commands associated with the rollback operationmanually. Refer to the patch documentation for full details.
For example:
# dbaascli patch db switchback 34567890 --instance1 hostname1:/u02/app/oracle/product/12.1.0.2/dbhome_1 --run_datasql 1
Manually Patching Oracle Database and Oracle GridInfrastructure Software
For Oracle Java VM, daylight savings time, and some routine or one-off patches, it canbe necessary for you to patch software manually.
To perform routine patching of Oracle Database and Oracle Grid Infrastructuresoftware, Oracle recommends that you use the facilities provided by Oracle ExadataCloud@Customer. However, under some circumstances, it can be necessary for youto patch the Oracle Database or Oracle Grid Infrastructure software manually:
• Oracle Java Virtual Machine (OJVM) Patching: Because they cannot be appliedin a rolling fashion, patches for the Oracle Database OJVM component are notincluded in the routine patch sets for Exadata Cloud@Customer. If you need toapply patches to the OJVM component of Oracle Database, then you must do somanually. See My Oracle Support Doc ID 1929745.1.
Chapter 14Manually Patching Oracle Database and Oracle Grid Infrastructure Software
14-13
• Daylight Savings Time (DST) Patching: Because they cannot be applied in arolling fashion, patches for the Oracle Database DST definitions are not includedin the routine patch sets for Exadata Cloud@Customer. If you need to applypatches to the Oracle Database DST definitions, you must do so manually. SeeMy Oracle Support Doc ID 412160.1.
• Non-routine or One-off Patching: If you encounter a problem that requires apatch which is not included in any routine patch set, then work with Oracle SupportServices to identify and apply the appropriate patch.
For general information about patching Oracle Database, refer to information aboutpatch set updates and requirements in Oracle Database Upgrade Guide for yourrelease.
Related Topics
• https://support.oracle.com/rs?type=doc&id=1929745.1
• https://support.oracle.com/rs?type=doc&id=412160.1
Updating the Compute Node Operating SystemLearn about standard Exadata tools and techniques that you can use to update theoperating system components on the Exadata Cloud@Customer compute nodes.
You are responsible for managing patches and updates to the operating systemenvironment on the compute node VMs. For further information, read aboutupdating Exadata Database Machine servers in Oracle Exadata Database MachineMaintenance Guide.
• Preparing for an Operating System UpdateTo prepare for an operating system update for Oracle Exadata Cloud@Customer,review this checklist of tasks.
• Updating the Operating System on All Compute Nodes of an Oracle ExadataCloud@Customer SystemTo update the operating system on the compute node virtual machines, use thepatchmgr tool.
• Installing Additional Operating System PackagesReview these guidelines before you install additional operating system packagesfor Oracle Exadata Cloud@Customer.
Related Topics
• Updating Oracle Exadata Database Machine Database Servers
Preparing for an Operating System UpdateTo prepare for an operating system update for Oracle Exadata Cloud@Customer,review this checklist of tasks.
Before you update your operating system, do each of these preparation tasks:
Determine the latest software update. Before you begin an update, to determine thelatest software to use, review Exadata Cloud Service Software Versions in My OracleSupport note 2333222.1.
Chapter 14Updating the Compute Node Operating System
14-14
Related Topics
• https://support.oracle.com/rs?type=doc&id=2333222.1
Updating the Operating System on All Compute Nodes of an OracleExadata Cloud@Customer System
To update the operating system on the compute node virtual machines, use thepatchmgr tool.
Note:
Customers who do not have My Oracle Support patch download privilegemay obtain the Exadata patchmgr update utility and recent ExadataSystem Software releases using the Exadata Cloud@Customer Gen 2 utilityexadata_updates.sh. For more information, see My Oracle Support Doc2730739.1.
The patchmgr utility manages the entire update of one or more compute nodesremotely, including the pre-restart, restart, and post-restart steps of an Oracle ExadataCloud@Customer system.
You can run the utility either from one of your Oracle Exadata Cloud@Customercompute nodes, or from another server running Oracle Linux. The server on which yourun the utility is known as the driving system. You cannot use the driving system toupdate itself. Therefore, if the driving system is one of the compute nodes in a VMcluster that you are updating, then you must run the patchmgr utility more than once.The following scenarios describe typical ways of performing the updates:
• Non-Exadata Driving SystemThe simplest way to run the update the system is to use a separate Oracle Linuxserver to update all compute nodes in one operation.
• Exadata Compute Node Driving SystemYou can use one compute node to drive the updates for the rest of the computenodes in the VM cluster. Then, you can use one of the updated nodes to drive theupdate on the original driving system. For example, consider updating a half racksystem with four compute nodes; node1, node2, node3, and node4. You could firstuse node1 to drive the updates of node2, node3, and node4. Then, you could usenode2 to drive the update of node1.
The driving system requires root user SSH access to each compute node beingupdated.
The following procedure is based on an example that assumes the following:
• The system has two compute nodes, node1 and node2.
• The target Exadata software version is 18.1.4.0.0.180125.3.
• Each node is used as the driving system to update the other node.
1. Gather the environment details.
Chapter 14Updating the Compute Node Operating System
14-15
a. Using SSH, connect to node1 as root and run the following command todetermine the current Exadata software version:
[root@node1 ~]# imageinfo -ver 12.2.1.1.4.171128
b. Switch to the grid user, and identify all nodes in the cluster.
[root@node1 ~]# su - grid
[grid@node1 ~]$ olsnodesnode1node2
2. Configure the driving system.
a. Switch back to the root user on node1 and check whether an SSH key pair(id_rsa and id_rsa.pub) exists. If not, then generate it.
[root@node1 ~]# ls /root/.ssh/id_rsa*ls: cannot access /root/.ssh/id_rsa*: No such file or directory[root@node1 ~]# ssh-keygen -t rsaGenerating public/private rsa key pair.Enter file in which to save the key (/root/.ssh/id_rsa):Enter passphrase (empty for no passphrase):Enter same passphrase again:Your identification has been saved in /root/.ssh/id_rsa.Your public key has been saved in /root/.ssh/id_rsa.pub.The key fingerprint is:93:47:b0:83:75:f2:3e:e6:23:b3:0a:06:ed:00:20:a5 [email protected] key's randomart image is:+--[ RSA 2048]----+|o.. + . ||o. o * ||E . o o || . . = || o . S = || + = . || + o o || . . + . || ... |+-----------------+
b. Distribute the public key to the target nodes, and verify this step. In theexample, the only target node is node2.
[root@node1 ~]# scp -i ~root/.ssh/id_rsa.pub opc@node2:/tmp/id_rsa.node1.pub
[root@node2 ~]# ls -al /tmp/id_rsa.node1.pub-rw-r--r-- 1 opc opc 442 Feb 28 03:33 /tmp/id_rsa.node1.pub
Chapter 14Updating the Compute Node Operating System
14-16
[root@node2 ~]# dateWed Feb 28 03:33:45 UTC 2018
c. On the target node (node2 in the example), add the root public key of node1 tothe root authorized_keys file.
[root@node2 ~]# cat /tmp/id_rsa.node1.pub >> ~root/.ssh/authorized_keys
d. Download patchmgr into /root/patch on the driving system (node1 in thisexample).You can download the patchmgr bundle from Oracle Support by using MyOracle Support Patch ID 21634633. Always obtain the latest available Exadatapatchmgr update utility to install any Exadata System Software release.
For further information, see also dbnodeupdate.sh and dbserver.patch.zip:Updating Exadata Database Server Software using the DBNodeUpdate Utilityand patchmgr: My Oracle Support Doc ID 1553103.1.
e. Unzip the patchmgr bundle.Depending on the version that you downloaded, the name of your ZIP file candiffer.
[root@node1 ~]# cd /root/patch/18.1.4.0.0.180125.3[root@node1 patch]# unzip dbserver.patch.zipArchive: p21634633_181400_Linux-x86-64.zip creating: dbserver_patch_5.180228.2/creating: dbserver_patch_5.180228.2/ibdiagtools/inflating: dbserver_patch_5.180228.2/ibdiagtools/cable_check.plinflating: dbserver_patch_5.180228.2/ibdiagtools/setup-sshinflating: dbserver_patch_5.180228.2/ibdiagtools/VERSION_FILEextracting: dbserver_patch_5.180228.2/ibdiagtools/xmonib.shinflating: dbserver_patch_5.180228.2/ibdiagtools/monitordinflating: dbserver_patch_5.180228.2/ibdiagtools/checkbadlinks.plcreating: dbserver_patch_5.180228.2/ibdiagtools/topologies/inflating: dbserver_patch_5.180228.2/ibdiagtools/topologies/VerifyTopologyUtility.pminflating: dbserver_patch_5.180228.2/ibdiagtools/topologies/verifylib.pminflating: dbserver_patch_5.180228.2/ibdiagtools/topologies/Node.pminflating: dbserver_patch_5.180228.2/ibdiagtools/topologies/Rack.pminflating: dbserver_patch_5.180228.2/ibdiagtools/topologies/Group.pminflating: dbserver_patch_5.180228.2/ibdiagtools/topologies/Switch.pminflating: dbserver_patch_5.180228.2/ibdiagtools/topology-zfsinflating: dbserver_patch_5.180228.2/ibdiagtools/dclicreating: dbserver_patch_5.180228.2/ibdiagtools/netcheck/inflating: dbserver_patch_5.180228.2/ibdiagtools/netcheck/remoteScriptGenerator.pminflating: dbserver_patch_5.180228.2/ibdiagtools/netcheck/CommonUtils.pminflating: dbserver_patch_5.180228.2/ibdiagtools/netcheck/
Chapter 14Updating the Compute Node Operating System
14-17
SolarisAdapter.pminflating: dbserver_patch_5.180228.2/ibdiagtools/netcheck/LinuxAdapter.pminflating: dbserver_patch_5.180228.2/ibdiagtools/netcheck/remoteLauncher.pminflating: dbserver_patch_5.180228.2/ibdiagtools/netcheck/remoteConfig.pminflating: dbserver_patch_5.180228.2/ibdiagtools/netcheck/spawnProc.pminflating: dbserver_patch_5.180228.2/ibdiagtools/netcheck/runDiagnostics.pminflating: dbserver_patch_5.180228.2/ibdiagtools/netcheck/OSAdapter.pminflating: dbserver_patch_5.180228.2/ibdiagtools/SampleOutputs.txtinflating: dbserver_patch_5.180228.2/ibdiagtools/infinicheckinflating: dbserver_patch_5.180228.2/ibdiagtools/ibping_testinflating: dbserver_patch_5.180228.2/ibdiagtools/tar_ibdiagtoolsinflating: dbserver_patch_5.180228.2/ibdiagtools/verify-topologyinflating: dbserver_patch_5.180228.2/installfw_exadata_sshcreating: dbserver_patch_5.180228.2/linux.db.rpms/inflating: dbserver_patch_5.180228.2/md5sum_files.lstinflating: dbserver_patch_5.180228.2/patchmgrinflating: dbserver_patch_5.180228.2/xcpinflating: dbserver_patch_5.180228.2/ExadataSendNotification.pminflating: dbserver_patch_5.180228.2/ExadataImageNotification.plinflating: dbserver_patch_5.180228.2/kernelupgrade_oldbios.shinflating: dbserver_patch_5.180228.2/cellboot_usb_pci_pathinflating: dbserver_patch_5.180228.2/exadata.img.envinflating: dbserver_patch_5.180228.2/README.txtinflating: dbserver_patch_5.180228.2/exadataLogger.pminflating: dbserver_patch_5.180228.2/patch_bug_26678971inflating: dbserver_patch_5.180228.2/dcliinflating: dbserver_patch_5.180228.2/patchReport.pyextracting: dbserver_patch_5.180228.2/dbnodeupdate.zipcreating: dbserver_patch_5.180228.2/plugins/inflating: dbserver_patch_5.180228.2/plugins/010-check_17854520.shinflating: dbserver_patch_5.180228.2/plugins/020-check_22468216.shinflating: dbserver_patch_5.180228.2/plugins/040-check_22896791.shinflating: dbserver_patch_5.180228.2/plugins/000-check_dummy_bashinflating: dbserver_patch_5.180228.2/plugins/050-check_22651315.shinflating: dbserver_patch_5.180228.2/plugins/005-check_22909764.shinflating: dbserver_patch_5.180228.2/plugins/000-check_dummy_perlinflating: dbserver_patch_5.180228.2/plugins/030-check_24625612.shinflating: dbserver_patch_5.180228.2/patchmgr_functionsinflating: dbserver_patch_5.180228.2/exadata.img.hwinflating: dbserver_patch_5.180228.2/libxcp.so.1inflating: dbserver_patch_5.180228.2/imageLogger
Chapter 14Updating the Compute Node Operating System
14-18
inflating: dbserver_patch_5.180228.2/ExaXMLNode.pminflating: dbserver_patch_5.180228.2/fwverify
f. In the directory that contains the patchmgr utility, create the dbs_group file,which contains the list of compute nodes to update. Include the nodes listedafter running the olsnodes command in step 1, except for the driving system.In this example, dbs_group only contains node2.
[root@node1 patch]# cd /root/patch/18.1.4.0.0.180125.3/dbserver_patch_5.180228[root@node1 dbserver_patch_5.180228]# cat dbs_groupnode2
3. Run a patching precheck operation.
[root@node1 dbserver_patch_5.180228]# ./patchmgr -dbnodes dbs_group -precheck -iso_repo zipped_iso_file -target_version target-version -nomodify_at_prereq
Note:
Run the precheck operation with the -nomodify_at_prereq option toprevent any changes to the system that could impact the backup youtake in the next step. Otherwise, the backup might not be able to roll thesystem back to its original state, should it be necessary.
The output should look similar to the following example:
[root@node1 dbserver_patch_5.180228]# ./patchmgr -dbnodes dbs_group -precheck -iso_repo /root/patch/18.1.4.0.0.180125.3/exadata_ol6_18.1.4.0.0.180125.3_Linux-x86-64.zip -target_version 18.1.4.0.0.180125.3 -nomodify_at_prereq ************************************************************************************************************NOTE patchmgr release: 5.180228 (always check MOS 1553103.1 for the latest release of dbserver.patch.zip)NOTEWARNING Do not interrupt the patchmgr session.WARNING Do not resize the screen. It may disturb the screen layout.WARNING Do not reboot database nodes during update or rollback.WARNING Do not open logfiles in write mode and do not try to alter them.************************************************************************************************************2018-02-28 21:22:45 +0000 :Working: DO: Initiate precheck on 1 node(s)2018-02-28 21:24:57 +0000 :Working: DO: Check free space and verify SSH equivalence for the root user to node22018-02-28 21:26:15 +0000 :SUCCESS: DONE: Check free space and verify SSH equivalence for the root user to node22018-02-28 21:26:47 +0000 :Working: DO: dbnodeupdate.sh
Chapter 14Updating the Compute Node Operating System
14-19
running a precheck on node(s).2018-02-28 21:28:23 +0000 :SUCCESS: DONE: Initiate precheck on node(s).
4. Back up the current system.
[root@node1 dbserver_patch_5.180228]# ./patchmgr -dbnodes dbs_group -backup -iso_repo zipped_iso_file -target_version target-version -allow_active_network_mounts
Note:
Ensure that you take the backup at this point, before any modificationsare made to the system.
The output should look similar to the following example:
[root@node1 dbserver_patch_5.180228]# ./patchmgr -dbnodes dbs_group -backup -iso_repo /root/patch/18.1.4.0.0.180125.3/exadata_ol6_18.1.4.0.0.180125.3_Linux-x86-64.zip -target_version 18.1.4.0.0.180125.3 -allow_active_network_mounts ************************************************************************************************************NOTE patchmgr release: 5.180228 (always check MOS 1553103.1 for the latest release of dbserver.patch.zip)NOTEWARNING Do not interrupt the patchmgr session.WARNING Do not resize the screen. It may disturb the screen layout.WARNING Do not reboot database nodes during update or rollback.WARNING Do not open logfiles in write mode and do not try to alter them.************************************************************************************************************2018-02-28 21:29:00 +0000 :Working: DO: Initiate backup on 1 node(s).2018-02-28 21:29:00 +0000 :Working: DO: Initiate backup on node(s)2018-02-28 21:29:01 +0000 :Working: DO: Check free space and verify SSH equivalence for the root user to node22018-02-28 21:30:18 +0000 :SUCCESS: DONE: Check free space and verify SSH equivalence for the root user to node22018-02-28 21:30:51 +0000 :Working: DO: dbnodeupdate.sh running a backup on node(s).2018-02-28 21:35:50 +0000 :SUCCESS: DONE: Initiate backup on node(s).2018-02-28 21:35:50 +0000 :SUCCESS: DONE: Initiate backup on 1 node(s).
5. Remove all custom RPMs from the target compute nodes. Custom RPMs arereported in precheck results. They include RPMs that were manually installed afterthe system was provisioned.
Chapter 14Updating the Compute Node Operating System
14-20
• If you are updating the system from version 12.1.2.3.4.170111, and theprecheck results include krb5-workstation-1.10.3-57.el6.x86_64, thenremove it. This item is considered a custom RPM for this version.
• Do not remove exadata-sun-vm-computenode-exact or oracle-ofed-release-guest. These two RPMs are handled automatically during the updateprocess.
6. Perform the update. To ensure that the update process in not interrupted, use thecommand nohup. For example:
[root@node1 dbserver_patch_5.180228]# nohup ./patchmgr -dbnodes dbs_group -upgrade -nobackup -iso_repo zipped_iso_file -target_version target-version -allow_active_network_mounts &
The output should look similar to the following example:
[root@node1 dbserver_patch_5.180228]# nohup ./patchmgr -dbnodes dbs_group -upgrade -nobackup -iso_repo /root/patch/18.1.4.0.0.180125.3/exadata_ol6_18.1.4.0.0.180125.3_Linux-x86-64.zip -target_version 18.1.4.0.0.180125.3 -allow_active_network_mounts & ************************************************************************************************************NOTE patchmgr release: 5.180228 (always check MOS 1553103.1 for the latest release of dbserver.patch.zip)NOTENOTE Database nodes will reboot during the update process.NOTEWARNING Do not interrupt the patchmgr session.WARNING Do not resize the screen. It may disturb the screen layout.WARNING Do not reboot database nodes during update or rollback.WARNING Do not open logfiles in write mode and do not try to alter them.*********************************************************************************************************2018-02-28 21:36:26 +0000 :Working: DO: Initiate prepare steps on node(s).2018-02-28 21:36:26 +0000 :Working: DO: Check free space and verify SSH equivalence for the root user to node22018-02-28 21:37:44 +0000 :SUCCESS: DONE: Check free space and verify SSH equivalence for the root user to node22018-02-28 21:38:43 +0000 :SUCCESS: DONE: Initiate prepare steps on node(s).2018-02-28 21:38:43 +0000 :Working: DO: Initiate update on 1 node(s).2018-02-28 21:38:43 +0000 :Working: DO: Initiate update on node(s)2018-02-28 21:38:49 +0000 :Working: DO: Get information about any required OS upgrades from node(s).2018-02-28 21:38:59 +0000 :SUCCESS: DONE: Get information about any required OS upgrades from node(s).2018-02-28 21:38:59 +0000 :Working: DO: dbnodeupdate.sh running an update step on all nodes.
Chapter 14Updating the Compute Node Operating System
14-21
2018-02-28 21:48:41 +0000 :INFO : node2 is ready to reboot.2018-02-28 21:48:41 +0000 :SUCCESS: DONE: dbnodeupdate.sh running an update step on all nodes.2018-02-28 21:48:41 +0000 :Working: DO: Initiate reboot on node(s)2018-02-28 21:48:57 +0000 :SUCCESS: DONE: Initiate reboot on node(s)2018-02-28 21:48:57 +0000 :Working: DO: Waiting to ensure node2 is down before reboot.2018-02-28 21:56:18 +0000 :Working: DO: Initiate prepare steps on node(s).2018-02-28 21:56:19 +0000 :Working: DO: Check free space and verify SSH equivalence for the root user to node22018-02-28 21:57:37 +0000 :SUCCESS: DONE: Check free space and verify SSH equivalence for the root user to node22018-02-28 21:57:42 +0000 :SEEMS ALREADY UP TO DATE: node22018-02-28 21:57:43 +0000 :SUCCESS: DONE: Initiate update on node(s)
7. After the update operation completes, verify the version of the Exadata softwareon the compute node that was updated.
[root@node2 ~]# imageinfo -ver18.1.4.0.0.180125.3
8. Repeat steps 2 through 7 of this procedure using the updated compute node asthe driving system to update the remaining compute node. In this example update,you would now use node2 to update node1.
9. As root On each compute node, run the uptrack-install command to install theavailable ksplice updates.
[root@node1 ~]# uptrack-install --all -y
[root@node2 ~]# uptrack-install --all -y
Related Topics
• https://support.oracle.com/rs?type=doc&id=2730739.1
• https://support.oracle.com/rs?type=doc&id=1553103.1
• https://support.oracle.com/rs?type=doc&id=21634633
Installing Additional Operating System PackagesReview these guidelines before you install additional operating system packages forOracle Exadata Cloud@Customer.
You are permitted to install and update operating system packages on OracleExadata Cloud@Customer as long as you do not modify the kernel or InfiniBand-specific packages. However, Oracle technical support, including installation, testing,certification and error resolution, does not apply to any non-Oracle software that youinstall.
Chapter 14Updating the Compute Node Operating System
14-22
Also be aware that if you add or update packages separate from an OracleExadata software update, then these package additions or updates can introduceproblems when you apply an Oracle Exadata software update. Problems can occurbecause additional software packages add new dependencies that can interrupt anOracle Exadata update. For this reason, Oracle recommends that you minimizecustomization.
If you install additional packages, then Oracle recommends that you have scripts toautomate the removal and reinstallation of those packages. After an Oracle Exadataupdate, if you install additional packages, then verify that the additional packages arestill compatible, and that you still need these packages.
For more information, refer to Oracle Exadata Database Machine Maintenance Guide.
Related Topics
• Installing, Updating and Managing Non-Oracle Software
Cloud Tooling UpdatesYou are responsible for updating the cloud-specific tooling included on the ExadataCloud@Customer compute nodes.
Note:
You can update the cloud-specific tooling by downloading and applying asoftware package containing the updated tools.
• Checking the Installed Cloud Tooling Release for UpdatesTo check the installed cloud tooling release for Oracle Exadata Cloud@Customer,complete this procedure.
• Updating the Cloud Tooling ReleaseTo update the cloud tooling release for Oracle Exadata Cloud@Customer,complete this procedure.
Checking the Installed Cloud Tooling Release for UpdatesTo check the installed cloud tooling release for Oracle Exadata Cloud@Customer,complete this procedure.
To check the installed cloud tooling release for updates:
1. Connect to a compute node as the opc user, and start a command shell as theroot user.
2. Use the following command to display information about the installed cloud tooling,and to list the available updates:
# dbaascli patch tools list
The command output displays:
• The version of the cloud tooling that is installed on the compute node.
Chapter 14Cloud Tooling Updates
14-23
• The list of available updates.
• Notification of the cloud tooling version that is installed on the other computenodes in the VM cluster.
Updating the Cloud Tooling ReleaseTo update the cloud tooling release for Oracle Exadata Cloud@Customer, completethis procedure.
To update the cloud tooling release:
1. Connect to a compute node as the opc user, and start a command shell as theroot user.
2. Download and apply the cloud tooling update:
• To update to the latest available cloud tooling release, use the followingcommand:
# dbaascli patch tools apply --patchid LATEST
• To update to a specific cloud tooling release, use the following command:
# dbaascli patch tools apply --patchid patchid
In the preceding command, patchid is a cloud tooling patch identifier, asreported in the output of the dbaascli patch tools list command.
The cloud tooling update is applied to all nodes in the VM cluster.
Chapter 14Cloud Tooling Updates
14-24
15Using Enterprise Manager Expressand Database Control on ExadataCloud@Customer
Learn how to access Enterprise Manager Database Express (EM Express) andEnterprise Manager Database Control (Database Control), which are web-based toolsfor monitoring and managing Oracle Database.
• About Accessing Enterprise Manager Database ExpressLearn to manage a CDB or PDB using Enterprise Manager Database Express (EMExpress).
• Setting the Port for EM Express to Manage a PDB (Oracle Database 12.1 Only)In Oracle Database 12c Release 1, configure a unique HTTPS port for thecontainer database (CDB), and for each pluggable database (PDB) that you wantto manage using EM Express.
• Accessing Enterprise Manager Database ExpressTo manage a container database (CBD) or pluggable database (PDB), beprepared to provide the port number allocated to the CDB or PDB that you want tomanage.
• Accessing Enterprise Manager 11g Database ControlTo manage a database with Enterprise Manager 11g Database Control, beprepared to provide the port number allocated to the database that you want tomanage.
About Accessing Enterprise Manager Database ExpressLearn to manage a CDB or PDB using Enterprise Manager Database Express (EMExpress).
Enterprise Manager Database Express is available on Exadata Cloud@Customerdatabases created using Oracle Database 12c Release 1 (12.1) or later.
How you access EM Express depends on whether you want to manage a CDB orPDB:
• To manage the CDB: When an Oracle Database is created, ExadataCloud@Customer automatically sets a port for EM Express access to the CDB.You do not need to perform any manual configuration steps. Each database isallocated a unique port number. The allocations use ports in a range starting with5500, 5501, 5502, and so on.
• To manage a PDB: With Oracle Database 12c Release 2 or later, you canconfigure EM Express to access the CDB and all PDBs on a single port, whichis known as the global port. The global port lets you use EM Express to connectto all of the PDBs in the CDB by using the HTTPS port for the CDB. You do notneed to perform any manual configuration steps. Each database is allocated a
15-1
unique port number. The allocations use ports in a range starting with 5500, 5501,5502, and so on.For an Oracle Database 12c release 1 database, you must manually set a port foreach PDB that you want to manage, using EM Express.
To confirm the port that is in use for a specific database, connect to the database as adatabase administrator, and run the query shown in the following example:
SQL> select dbms_xdb_config.getHttpsPort() from dual;DBMS_XDB_CONFIG.GETHTTPSPORT()------------------------------ 5502
Setting the Port for EM Express to Manage a PDB (OracleDatabase 12.1 Only)
In Oracle Database 12c Release 1, configure a unique HTTPS port for the containerdatabase (CDB), and for each pluggable database (PDB) that you want to manageusing EM Express.
1. Start SQL*Plus, and log in to the CDB or PDB as the SYS user with SYSDBAprivileges.
2. Run the procedure DBMS_XDB_CONFIG.SETHTTPSPORT, specifying the port number.
SQL> exec dbms_xdb_config.sethttpsport(port-number)
Accessing Enterprise Manager Database ExpressTo manage a container database (CBD) or pluggable database (PDB), be prepared toprovide the port number allocated to the CDB or PDB that you want to manage.
To access Enterprise Manager Express ( EM Express), direct your browser to the URL:
https://node-ip-address:port/em
Where:
node-ip-address is the client network IP address of the compute node hosting EMExpress.
port is the EM Express port used by the database.
If your browser displays a warning that your connection is not secure or not private,then use the browser’s advanced option to ignore the warning, and continue. Youreceive this warning because Exadata Cloud@Customer uses a self-signed certificateto provide HTTPS (secure HTTP) connectivity, and such certificates are consideredsuspicious by many web browsers.
Chapter 15Setting the Port for EM Express to Manage a PDB (Oracle Database 12.1 Only)
15-2
Accessing Enterprise Manager 11g Database ControlTo manage a database with Enterprise Manager 11g Database Control, be prepared toprovide the port number allocated to the database that you want to manage.
Enterprise Manager 11g Database Control is available on Exadata Cloud@Customerdatabases created using Oracle Database 11g Release 2. Each database is allocateda unique port number in a range starting with 1158, 1159, 1160, and so on.
You can confirm the Database Control port for a database by searching forREPOSITORY_URL in the $ORACLE_HOME/host_sid/sysman/config/emd.properties file.In the preceding file name, host is the host name of the compute node hostingDatabase Control, and sid is the Oracle Database system identifier (SID).
You can access Database Control by directing your browser to the URL:
https://node-ip-address:port/em
Where:
node-ip-address is the client network IP address of the compute node hostingDatabase Control.
port is the Database Control port used by the database.
If your browser displays a warning that your connection is not secure or not private,then use the browser’s advanced option to ignore the warning and continue. Youreceive this warning because Exadata Cloud@Customer uses a self-signed certificateto provide HTTPS (secure HTTP) connectivity, and such certificates are consideredsuspicious by many web browsers.
Chapter 15Accessing Enterprise Manager 11g Database Control
15-3
16Oracle Exadata Cloud@CustomerDeployment Assistant
Oracle Exadata Cloud@Customer Deployment Assistant is an automated installationand configuration tool that enables you to set up your Oracle ExadataCloud@Customer machine and create an Oracle Database instance with minimaleffort.
• Using Oracle Exadata Cloud@Customer Deployment AssistantOracle Exadata Cloud@Customer Deployment Assistant gathers yourconfiguration details and creates the Oracle Exadata Cloud@Customerinfrastructure configuration file. The configuration file drives the automatedinstallation and configuration processes for Oracle Exadata Cloud@Customerinfrastructure.
• Accessing Oracle Exadata Cloud@Customer Deployment AssistantFollow these steps to run the Deployment Assistant.
• Step 1: Pre-InstallationCreate Exadata Cloud@Customer infrastructure, VM cluster network, anddownload the infrastructure configuration file before your engineered systemarrives at your premises.
• Step 2: Onsite InstallationEnsure that you activate the Exadata Cloud@Customer infrastructure and validatethe VM cluster network.
• Step 3: Post-InstallationCreate a VM cluster, install Oracle Database, and validate your installation beforeperforming any administrative tasks.
Using Oracle Exadata Cloud@Customer DeploymentAssistant
Oracle Exadata Cloud@Customer Deployment Assistant gathers your configurationdetails and creates the Oracle Exadata Cloud@Customer infrastructure configurationfile. The configuration file drives the automated installation and configurationprocesses for Oracle Exadata Cloud@Customer infrastructure.
Before your engineered system arrives, do the following:
• Work with your network and database administrators to evaluate the currentnetwork settings, such as current IP address use and network configuration.
• Define the settings for the rack, such as network configuration and backupmethod.
• Download the Oracle Exadata Cloud@Customer infrastructure configuration file.
16-1
During deployment, if you find any discrepancies at any stage, then click Close andcomplete later to exit Oracle Exadata Cloud@Customer Deployment Assistant. Youwill lose all of your settings and you will have to start afresh the next time.
Accessing Oracle Exadata Cloud@Customer DeploymentAssistant
Follow these steps to run the Deployment Assistant.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Exadata Infrastructure.
3. Click Deployment Assistant.
4. Choose a deployment type.
• New Deployment: Creates an Exadata Cloud@Customer infrastructure andall the resources needed to create your first Oracle Database.Select a Compartment, and then click Continue.
• Existing Deployment: Uses an existing Exadata Cloud@Customerinfrastructure and guides you through completing the deployment.
a. Select a Compartment.
b. Select an Exadata Cloud@Customer infrastructure.
c. Select a VM Cluster Network or create one.
d. Click Continue.
5. If you have created an Exadata Cloud@Customer infrastructure and if it is inActive state, then do the following:
a. Go the Exadata Cloud@Customer infrastructure details page.
b. Click Deployment Assistant.
6. If you have created an Exadata Cloud@Customer infrastructure and if it is inRequires Activation state, then do the following:
a. Go the Exadata Cloud@Customer infrastructure details page.
b. Click More Actions and then select Deployment Assistant.
Step 1: Pre-InstallationCreate Exadata Cloud@Customer infrastructure, VM cluster network, and downloadthe infrastructure configuration file before your engineered system arrives at yourpremises.
1. Create Oracle Exadata Cloud@Customer infrastructure.
For more information and instructions, see Using the Console to CreateInfrastructure.
2. Create VM cluster network.
For more information and instructions, see Using the Console to Create a VMCluster Network.
3. Download the Oracle Exadata Cloud@Customer configuration file.
Chapter 16Accessing Oracle Exadata Cloud@Customer Deployment Assistant
16-2
For more information and instructions, see Using the Console to Download a FileContaining Configuration Data.
Step 2: Onsite InstallationEnsure that you activate the Exadata Cloud@Customer infrastructure and validate theVM cluster network.
1. Add Infrastructure Contacts.
Maintenance contacts are required for service request based communications forhardware replacement and other maintenance events.
You must add a primary contact to activate your infrastructure. Ensure that youprovide the details of the contact that you used while registering the CustomerSupport Identifier (CSI) associated with this infrastructure, as a primary contact.
For more information and instructions, see Managing Infrastructure MaintenanceContacts
2. Activate Oracle Exadata Cloud@Customer infrastructure.
For more information and instructions, see Using the Console to Activate ExadataCloud@Customer Infrastructure.
3. Validate the VM cluster network.
You can only validate a VM cluster network if its current state is RequiresValidation and if the underlying Exadata infrastructure is activated.
For more information and instructions, see Using the Console to Validate a VMCluster Network.
Step 3: Post-InstallationCreate a VM cluster, install Oracle Database, and validate your installation beforeperforming any administrative tasks.
1. Create VM cluster.
For more information and instructions, see Using the Console to Create a VMCluster.
2. Create Oracle Database.
For more information and instructions, see Using the Console to Create aDatabase.
Chapter 16Step 2: Onsite Installation
16-3
17Using the dbaascli Utility on ExadataCloud@Customer
Learn to use the dbaascli utility on Exadata Cloud@Customer.
• About Using the dbaascli Utility on Exadata Cloud@CustomerYou can use the dbaascli utility to perform various database lifecycle andadministration operations on Exadata Cloud@Customer such as changing thepassword of a database user, starting a database, managing pluggable databases(PDBs), scaling the CPU core count in disconnected mode, and more.
• dbaascli database bounceTo shut down and restart a specified Exadata Cloud@Customer database, use thecommand dbaascli database bounce.
• dbaascli database changepasswordTo change the password of a database user, use the command dbaasclidatabase changepassword.
• dbaascli cpuscale get_statusTo check the status of current or last scale request performed, use the commanddbaascli cpuscale get_status.
• dbaascli cpuscale updateTo scale up or down the CPU core count for a virtual machine in a VM cluster indisconnected mode, use the command dbaascli cpuscale update.
• dbaascli database moveTo move a database to another Oracle Home directory location, use the commanddbaascli database move.
• dbaascli database startTo start the specified database use the command dbaascli database start.
• dbaascli database statusTo check the status of the specified database, use the command dbaasclidatabase status.
• dbaascli database stopTo stop the specified database, use the command dbaascli database stop.
• dbaascli database updateTo modify the globally unique database name or to reconfigure online redo logfiles, use dbaascli database update.
• dbaascli dbhome infoUse the dbaascli dbhome info command to view information about Oracle Homedirectory locations.
• dbaascli dbhome purgeUse the command dbaascli dbhome purge to delete unused Oracle homedirectory locations.
17-1
• dbaascli dbimage listTo display information about Oracle Database software images that aredownloaded to your Exadata Cloud@Customer environment, use the commanddbaascli dbimage list.
• dbaascli listener bounceTo stop and restart the Oracle Net listener that is associated with the specifieddatabase, run the command dbaascli listener bounce.
• dbaascli listener startTo start an Oracle Net listener that is associated with the specified database, runthe command dbaascli listener start.
• dbaascli listener statusTo obtain the status of the Oracle Net listener that is associated with the specifieddatabase, use the command dbaascli listener status.
• dbaascli listener stopTo stop the Oracle Net listener that is associated with the specified database, usethe command dbaascli listener stop.
• dbaascli patch db applyTo apply an Oracle Database or Oracle Grid Infrastructure patch, use thecommand dbaascli patch db apply.
• dbaascli patch db listTo check whether Oracle Database or Oracle Grid Infrastructure patches areavailable, run the command dbaascli patch db list.
• dbaascli patch db prereqTo check the prerequisites for an Oracle Database or Oracle Grid Infrastructurepatch, use the command dbaascli patch db prereq.
• dbaascli patch db switchbackTo roll back an Oracle Database or Oracle Grid Infrastructure patch, use thecommand dbaascli patch db switchback.
• dbaascli patch tools applyTo download and apply a cloud tooling update, run the command dbaascli patchtools apply.
• dbaascli patch tools listTo display information about your installed cloud tools and to list the availableupdates, use the command dbaascli patch tools list.
• dbaascli pdb checkdbTo display information about a container database (CDB), run the commanddbaascli pdb checkdb --dbname.
• dbaascli pdb checknodeTo display information about pluggable databases (PDBs) that are associatedwith a specific container database (CDB) and a specific compute node run thecommand dbaascli pdb checknode.
• dbaascli pdb checkpdbTo display information about a pluggable database (PDB) run the commanddbaascli pdb checkpdb.
• dbaascli pdb closeTo close a pluggable database (PDB) run the command dbaascli pdb close.
Chapter 17
17-2
• dbaascli pdb connect_infoTo retrieve network connection information for a pluggable database (PDB) run thecommand dbaascli pdb connect_info.
• dbaascli pdb connect_stringTo display Oracle Net connect string information for a pluggable database (PDB)run the command dbaascli pdb connect_string.
• dbaascli pdb createTo create a new pluggable database (PDB) run the command dbaascli pdbcreate.
• dbaascli pdb deleteTo delete a pluggable database (PDB) run the command dbaascli pdb delete.
• dbaascli pdb infoTo display more detailed information about a pluggable database (PDB) use thecommand dbaascli pdb info.
• dbaascli pdb local_cloneTo create a new pluggable database (PDB) as a clone of an existing PDB in thesame container database (CDB) run the command dbaascli pdb local_clone.
• dbaascli pdb openTo open a pluggable database (PDB) run the command dbaascli pdb open.
• dbaascli pdb remote_clone
• dbaascli pdb renameTo change the name of a pluggable database (PDB) use the command dbaasclipdb rename.
• dbaascli pdb resizeTo modify the size limits for a pluggable database (PDB) use the commaddbaascli pdb resize.
• dbaascli tde rotate masterkeyTo change or rotate the master encryption key for the specified database, run thecommand dbaascli tde rotate masterkey.
• dbaascli tde statusTo display information about the keystore for the specified database run thecommand dbaascli tde status.
About Using the dbaascli Utility on ExadataCloud@Customer
You can use the dbaascli utility to perform various database lifecycle andadministration operations on Exadata Cloud@Customer such as changing thepassword of a database user, starting a database, managing pluggable databases(PDBs), scaling the CPU core count in disconnected mode, and more.
You must use DBaaS console or command-line interface to scale resources. Thecapabilities of the dbaascli utility are in addition to, and separate from, the OracleCloud Infrastructure Console, API, or command-line interface (CLI).
To use the utility, you must be connected to an Exadata Cloud@Customer computenode. See "Connecting to a Compute Node with SSH".
Chapter 17About Using the dbaascli Utility on Exadata Cloud@Customer
17-3
Many dbaascli commands can be run as the oracle user. However, some commandsrequire root administrator privileges.
To scale OCPUs up or down in a VM cluster in disconnected mode, run the dbaasclicpuscale update and dbaascli cpuscale get_status commands from any nodeinside a VM cluster to change the CPU core count for that cluster. If you have morethan one VM cluster, then run a separate command from any node inside each VMcluster you want to scale up or down. These commands are designed to not work ifissued during the normal connected mode and will time out 600 seconds (10 minutes).
Related Topics
• Connecting to a Compute Node with SSH
dbaascli database bounceTo shut down and restart a specified Exadata Cloud@Customer database, use thecommand dbaascli database bounce.
Prerequisites
Run the command as the oracle user.
To use the utility, you must be connected to an Exadata Cloud@Customer computenode.
See "Connecting to a Compute Node with SSH".
Syntax
dbaascli database bounce --dbname dbname
In the command, dbname specifies the name of the database that you want to act on.
Options
The dbname option of database bounce specifies the name of the database that youwant to shut down and restart. The dbname option is prefixed with two minus signs (--).
Usage Notes
The command performs a database shutdown in immediate mode. The database isthen restarted and opened. In Oracle Database 12c or later, all of the PDBs are alsoopened.
Example 17-1 Shut Down and Restart the Database
In the following command, you shut down and restart the database sales1
$ dbaascli database bounce --dbname sales1
Related Topics
• Connecting to a Compute Node with SSH
Chapter 17dbaascli database bounce
17-4
dbaascli database changepasswordTo change the password of a database user, use the command dbaascli databasechangepassword.
Prerequisites
Run the command as the root user.
Syntax
dbaascli database changepassword --dbname dbname
In the command, dbname specifies the name of the database that you want to act on.
Options
The dbname option of database changepassword specifies the name of the databasethat you want to shut down and restart. The dbname option is prefixed with two minussigns (--).
Usage Notes
Enter the database user name and new password when prompted.
dbaascli cpuscale get_statusTo check the status of current or last scale request performed, use the commanddbaascli cpuscale get_status.
Prerequisites
Run the command as the root user.
See "Connecting to a Compute Node with SSH".
Syntax
Displays various command execution states as it progresses from scheduled,running, and finally to success or failure.
$ dbaascli cpuscale get_status
dbaascli cpuscale updateTo scale up or down the CPU core count for a virtual machine in a VM cluster indisconnected mode, use the command dbaascli cpuscale update.
Prerequisites
Run the command as the root user.
See "Connecting to a Compute Node with SSH".
Chapter 17dbaascli database changepassword
17-5
Syntax
Exadata Cloud@Customer is considered to be in a "Disconnected" mode when thereis a loss of connectivity with the DBaaS control plane running on Oracle CloudInfrastructure (OCI).
$ dbaascli cpuscale update --coreCount coreCount --message message
In the command, coreCount specifies the number of CPUs that you want to scale up ordown per VM in a cluster. Optionally, you can include a message for your reference.
dbaascli database moveTo move a database to another Oracle Home directory location, use the commanddbaascli database move.
Prerequisites
• Before performing a move operation, ensure that all of the database instancesassociated with the database are up and running.
• Run the command as the root user.
Syntax
# dbaascli database move --dbname dbname --ohome oraclehome
In the command:
• dbname specifies the name of the database that you want to move.
• oraclehome specifies the path to an existing Oracle Home directory location, whichyou want the specified database to use.
dbaascli database startTo start the specified database use the command dbaascli database start.
Prerequisites
Run the command as the Oracle user.
Syntax
dbaascli database start --dbname dbname
In the command, dbname specifies the name of the database that you want to start.
Usage Notes
The command starts and opens the database. In Oracle Database 12c or later, all ofthe PDBs are also opened.
Chapter 17dbaascli database move
17-6
dbaascli database statusTo check the status of the specified database, use the command dbaascli databasestatus.
Prerequisites
Run the command as the Oracle user.
Syntax
dbaascli database status --dbname dbname
In the command, dbname specifies the name of the database for which you want tocheck the status.
Usage Notes
Output from the command includes the open mode of the database, the softwarerelease and edition of the database, and release version of other softwarecomponents.
dbaascli database stopTo stop the specified database, use the command dbaascli database stop.
Prerequisites
Run the command as the Oracle user.
Syntax
dbaascli database stop --dbname dbname
In the command, dbname specifies the name of the database that you want to stop.
Usage Notes
The command performs a database shutdown in immediate mode. No newconnections or new transactions are permitted. Active transactions are rolled back,and all connected users are disconnected.
dbaascli database updateTo modify the globally unique database name or to reconfigure online redo log files,use dbaascli database update.
Prerequisites
For all options, run the command as the root user.
Chapter 17dbaascli database status
17-7
Modifying the Globally Unique Database Name
Run the following command to modify a globally unique database name:
dbaascli database update --dbname dbname --db_unique_name dbname_uniquename [--precheck]
In the command, dbname specifies the name of the database that you want to updateand dbname_uniquename specifies the user configurable portion of the new globallyunique database name.
The command modifies the DB_UNIQUE_NAME database parameter and relatedconfiguration entries that reference it, including entries in the Oracle Cluster Registry(OCR) and database server parameter file (SPFILE). File locations that reference theglobally unique database name are also updated, including the location of the datafiles and keystore.
The value for the --db_unique_name option must begin with the dbname value, followedby an underscore character. If you do not use this convention, then the command failswith an error .
To ensure that the update can proceed before you perform the update operation, youcan use the option --precheck to run a series of prerequisite checks. No changes aremade when using the --precheck option.
Reconfiguring Online Redo Logs
dbaascli database update --dbname dbname --redosize redosize [--groups numgroups] [--precheck]
Run the following command to reconfigure online redo logs:
In the command, the variable dbname specifies the name of the database that youwant to move and the variable redosize specifies the size of each online redo logfile in megabytes. The valid range is for redosize is between 1000m and 16000m, andthe value that you enter for the variable numgroups optionally specifies the number ofonline redo log groups to create. The default value for the variable numgroups is 4.
Before performing the update operation, you can use the --precheck option to run aseries of prerequisite checks to ensure that the update can proceed. No changes aremade when you use the --precheck option.
dbaascli dbhome infoUse the dbaascli dbhome info command to view information about Oracle Homedirectory locations.
Prerequisites
Run the command as root user.
Chapter 17dbaascli dbhome info
17-8
Syntax
dbaascli dbhome info
When prompted:
• Press Enter to view information about all of the Oracle homes that are registeredin the VM cluster.
• To view information about a particular Oracle home, specify an Oracle homename.
dbaascli dbhome purgeUse the command dbaascli dbhome purge to delete unused Oracle home directorylocations.
Prerequisite
Run the command as the root user.
Syntax
dbaascli dbhome purge
Options
When prompted, enter:
• 1 to specify the Oracle home name for the location being purged.
• 2 to specify the Oracle home directory path for the location being purged.
When next prompted, enter the Oracle home name or directory path for the locationbeing purged. If your entries are valid, and the Oracle home is not associated witha database, then the Oracle binaries are removed from the Oracle home directorylocation. The associated metadata is also removed from the system.
dbaascli dbimage listTo display information about Oracle Database software images that are downloadedto your Exadata Cloud@Customer environment, use the command dbaascli dbimagelist.
Prerequisites
Run the command as the root user.
Syntax
# dbaascli dbimage list
Chapter 17dbaascli dbhome purge
17-9
Usage Notes
The command displays a list of software images that are downloaded to your ExadataCloud@Customer environment, including version and bundle patch information.
dbaascli listener bounceTo stop and restart the Oracle Net listener that is associated with the specifieddatabase, run the command dbaascli listener bounce.
Prerequisites
Run the dbaascli listener bounce command as the oracle user.
Syntax
dbaascli listener bounce --dbname dbname
In the preceeding command dbname specifies the name of the database that you wantto stop and restart.
dbaascli listener startTo start an Oracle Net listener that is associated with the specified database, run thecommand dbaascli listener start.
Prerequisites
Run the dbaascli listener start command as the oracle user:
Syntax
dbaascli listener start --dbname dbname
In the preceeding command dbname specifies the name of the database that you wantto move.
dbaascli listener statusTo obtain the status of the Oracle Net listener that is associated with the specifieddatabase, use the command dbaascli listener status.
Prerequisites
Run the command as the oracle user.
Syntax
dbaascli listener stop --dbname dbname
Chapter 17dbaascli listener bounce
17-10
In the command, dbname specifies the name of the database whose listener you wantto stop.
dbaascli listener stopTo stop the Oracle Net listener that is associated with the specified database, use thecommand dbaascli listener stop.
Prerequisites
Run the command as the oracle user.
Syntax
dbaascli listener stop --dbname dbname
In the command, dbname specifies the name of the database whose listener you wantto stop.
dbaascli patch db applyTo apply an Oracle Database or Oracle Grid Infrastructure patch, use the commanddbaascli patch db apply.
Prerequisites
Run the command as the root user.
Syntax
You can use this command to apply an Oracle Database or Oracle Grid Infrastructurepatch.
To apply a patch to a specific instance, use the following command:
# dbaascli patch db apply --patchid patchid --instance1 hostname:oracle_home [--dbnames dbname[,dbname2 ...]] [--run_datasql 1]
To apply a patch by specifying only database names, use the following command:
# dbaascli patch db apply --patchid patchid --dbnames dbname[,dbname2 ...] [--run_datasql 1] [-alldbs]
To apply a patch to Oracle Grid Infrastructure, use the following command:
# dbaascli patch db apply --patchid patchid --dbnames grid
To run the command in the background, append an ampersand (&):
# dbaascli patch db apply --patchid 29708703 --dbnames DB18 &
Chapter 17dbaascli listener stop
17-11
To learn more about the patch db apply command options, use the followingcommand:
# dbaascli patch db apply ?
In the preceding commands:
• patchid identifies the patch that you want to apply.
• --instance1 specifies a compute node and Oracle home directory that is subjectto the patching operation. In this context, an Oracle home directory can beeither an Oracle Database home directory, or the Oracle Grid Infrastructure homedirectory.
If you use this argument to specify a shared Oracle home directory and you do notspecify the --dbnames argument, then all of the databases that share the specifiedOracle Home are patched. After the operation, the Oracle home directory locationremains unchanged; however, the patch level information embedded in the Oraclehome name is adjusted to reflect the patching operation.
• --dbnames specifies the database names for the databases that are the target ofthe patching operation.
If you use this argument to patch a database that uses a shared Oracle home,and you do not specify the -alldbs option, then a new Oracle home containing thepatched Oracle Database binaries is created, and the database is moved to thenew Oracle home.
• -alldbs patches all of the databases that share the same Oracle Databasebinaries (Oracle home) as the databases specified in the --dbnames argument.
After the operation, the Oracle home directory location remains unchanged;however, the patch level information embedded in the Oracle home name isadjusted to reflect the patching operation.
• --run_datasql 1 instructs the command to execute patch-related SQLcommands.
Usage Notes
• Patch-related SQL should only be run after all of the compute nodes are patched.Take care not to specify this argument if you are patching a node and furthernodes remain to be patched.
• This argument can only be specified along with a patching operation on a computenode. If you have patched all of your nodes and you did not specify this argument,you need to manually execute the SQL commands associated with the patch,which typically involves running the catbundle.sql script for Oracle Database11g or the datapatch utility for Oracle Database 12c, or later. Refer to the patchdocumentation for full details.
Chapter 17dbaascli patch db apply
17-12
dbaascli patch db listTo check whether Oracle Database or Oracle Grid Infrastructure patches are available,run the command dbaascli patch db list.
Prerequisites
Run the command as the root user.
Syntax
dbaascli patch db list --oh hostname:oracle_home
In the preceding command, --oh hostname: specifies a compute node, andoracle_home specifies the Oracle home directory for which you want to list theavailable patches. In this context, an Oracle home directory may be an OracleDatabase home directory or the Oracle Grid Infrastructure home directory
Usage Notes
The list of available patches is determined by interrogating the database toestablish the patches that have already been applied. When a patch is applied, thecorresponding database entry is made as part of the SQL patching operation, whichis run at the end of the patch workflow. Therefore, the list of available patches mayinclude partially applied patches along with patches that are currently being applied.
dbaascli patch db prereqTo check the prerequisites for an Oracle Database or Oracle Grid Infrastructure patch,use the command dbaascli patch db prereq.
Prerequisites
You must run the command as the root user.
Syntax
To check patch prerequisites on a specific instance, use the following command:
# dbaascli patch db prereq --patchid patchid --instance1hostname:oracle_home [--dbnames dbname[,dbname2 ...]]To check patch prerequisites by specifying only database names, use the followingcommand:
# dbaascli patch db prereq --patchid patchid --dbnamesdbname[,dbname2 ...] [-alldbs]In the preceding commands:
• patchid identifies the patch identifier for which you want prerequisites to bechecked before installing the patch.
• --instance1 specifies a compute node and Oracle home directory on which youwant the prerequisite checks to be performed. In this context, an Oracle home
Chapter 17dbaascli patch db list
17-13
directory can be an Oracle Database home directory, or it can be the Oracle GridInfrastructure home directory.
• --dbnames specifies the database names for the databases on which you wantprerequisite checks to be performed.
• -alldbs specifies that you want to check all of the databases that share the sameOracle home (the same Oracle Database binaries) as the specified databases.
dbaascli patch db switchbackTo roll back an Oracle Database or Oracle Grid Infrastructure patch, use the commanddbaascli patch db switchback.
Prerequisites
You must run the command as the root user.
Syntax
To roll back a patch on specific instances, use the following command syntax:
# dbaascli patch db switchback --patchid patchid --instance1 hostname:oracle_home [--dbnames dbname[,dbname2 ...]] [--run_datasql 1]
To roll back a patch by specifying only database names, use the following command:
# dbaascli patch db switchback --patchid patchid --dbnamesdbname[,dbname2 ...] [--run_datasql 1] [-alldbs]In the preceding commands:
• patchid identifies the patch to be rolled back.
• --instance1 specifies a compute node and Oracle Home directory that is subjectto the rollback operation. In this context, an Oracle home directory can be anOracle Database home directory or the Oracle Grid Infrastructure home directory.
If you use this argument to specify a shared Oracle home directory, and you do notspecify the --dbnames argument, then all of the databases that share the specifiedOracle home are rolled back.
• --dbnames specifies the database names for the databases that are the target ofthe rollback operation.
• -alldbs specifies that you want to roll back all of the databases that share thesame Oracle Database binaries (Oracle home) as the databases specified in the--dbnames argument.
• --run_datasql 1 instructs the command to run rollback-related SQL commands.
Usage Notes
• You can only run rollback-related SQL after all of the compute nodes are rolledback. Take care not to specify this argument if you are rolling back a node, andfurther nodes remain to be rolled back.
• You can only specify this argument with a rollback operation on a compute node.Therefore, if you have rolled back all of your nodes, and you did not specify this
Chapter 17dbaascli patch db switchback
17-14
argument, then you must manually run the SQL commands associated with therollback operation. Refer to the patch documentation for full details.
dbaascli patch tools applyTo download and apply a cloud tooling update, run the command dbaascli patchtools apply.
Prerequisite
Run the command as the root user.
Syntax
• To update to the latest available cloud tooling, use the command:
dbaascli patch tools apply --patchid LATEST
• To update to a specific cloud tooling release, use the following command:
dbaascli patch tools apply --patchid patchid
In the preceding command, patchid is a cloud tooling patch identifier, as reported inthe output of the dbaascli patch db list command.
Usage Notes
The cloud tooling update is applied to all nodes in the VM cluster.
dbaascli patch tools listTo display information about your installed cloud tools and to list the available updates,use the command dbaascli patch tools list.
Prerequisites
Run the command as the root user.
Syntax
# dbaascli patch tools list
Usage Notes
The command output displays:.
• The version of the cloud tooling that is installed on the compute node.
• The list of available updates.
• Notification of the cloud tooling version that is installed on the other computenodes in the VM cluster.
Chapter 17dbaascli patch tools apply
17-15
dbaascli pdb checkdbTo display information about a container database (CDB), run the command dbaasclipdb checkdb --dbname.
Prerequisites
Run the command as the oracle user.
Syntax
# dbaascli pdb checkdb --dbname dbname
Options
In the command, dbname specifies the name of the CDB for which you want to displayinformation.
Usage Notes
The information returned by this command includes the number of instances, and theCPU count that is associated with the CDB.
dbaascli pdb checknodeTo display information about pluggable databases (PDBs) that are associated with aspecific container database (CDB) and a specific compute node run the commanddbaascli pdb checknode.
Prerequisites
Run the command as the oracle user.
Syntax
$ dbaascli pdb checknode --node nodenum --dbname dbname
Options
In the command:
• nodenum specifies the node number for a compute node in the ExadataCloud@Customer environment. You can display a list of compute nodes andcorresponding node numbers by using the olsnodes command.
• dbname specifies the name of the container database that hosts the PDB.
Usage Notes
The command displays statuses for all PDBs that are associated with the specifiedcompute node and CDB, including the open mode for each PDB.
Chapter 17dbaascli pdb checkdb
17-16
dbaascli pdb checkpdbTo display information about a pluggable database (PDB) run the command dbaasclipdb checkpdb.
Prerequisites
Run the command as the oracle user.
Syntax
$ dbaascli pdb checkpdb --pdbname pdbname --dbname dbname
Options
In the command:
• pdbname specifies the name of the PDB that you want to check.
• dbname specifies the name of the container database that hosts the PDB.
Usage Notes
The command displays the status for the specified PDB, including the open mode andrestricted status.
dbaascli pdb closeTo close a pluggable database (PDB) run the command dbaascli pdb close.
Prerequisite
Run the command as the oracle user.
Syntax
dbaascli pdb close --pdbname pdbname --dbname dbname
Options
In the command:
• pdbname specifies the name of the PDB that you want to close.
• dbname specifies the name of the container database that hosts the PDB.
Usage Notes
Upon successful completion of running this command, the PDB is closed on all of thecontainer database instances.
Chapter 17dbaascli pdb checkpdb
17-17
dbaascli pdb connect_infoTo retrieve network connection information for a pluggable database (PDB) run thecommand dbaascli pdb connect_info.
Prerequisite
Run the command as the oracle user.
Syntax
dbaascli pdb connect_info --pdbname pdbname --dbname dbname
Options
In the command:
• pdbname specifies the name of the PDB for which you want to retrieve connectioninformation
• dbname specifies the name of the container database that hosts the PDB
Usage Notes
The command outputs a zip file that contains tnsnames.ora, sqlnet.ora, and ojdbcsproperties for the PDB.
dbaascli pdb connect_stringTo display Oracle Net connect string information for a pluggable database (PDB) runthe command dbaascli pdb connect_string.
Prerequisite
Run the command as the oracle user.
Syntax
dbaascli pdb connect_string --pdbname pdbname --dbname dbname
Options
In the command:
• pdbname specifies the name of the PDB for which you want to display connectstring information
• dbname specifies the name of the container database that hosts the PDB
Chapter 17dbaascli pdb connect_info
17-18
dbaascli pdb createTo create a new pluggable database (PDB) run the command dbaascli pdb create.
Prerequisite
Run the command as the oracle user.
Syntax
dbaascli pdb create --pdbname pdbname --dbname dbname [--maxsize maxsize] [--maxcpu maxcpu]
Options
In the command:
• pdbname specifies the name of the new PDB that you want to create.
• dbname specifies the name of the container database that hosts the new PDB.
• maxsize optionally specifies the maximum total size of data files and temporaryfiles for tablespaces belonging to the PDB. Setting this option is effectivelythe same as setting the MAXSIZE PDB storage clause in the CREATE PLUGGABLEDATABASE SQL command. You can impose a limit by specifying an integer followedby a size unit (K, M, G, or T), or you can specify UNLIMITED to explicitly enforce nolimit.
• maxcpu optionally specifies the maximum number of CPUs that are available tothe PDB. Setting this option is effectively the same as setting the CPU_COUNTparameter in the PDB.
Usage Notes
During the PDB creation process, you are prompted to specify the administrationpassword for the new PDB.
dbaascli pdb deleteTo delete a pluggable database (PDB) run the command dbaascli pdb delete.
Prerequisite
Run the command as the oracle user.
Syntax
dbaascli pdb delete --pdbname pdbname --dbname dbname
Options
In the command:
• pdbname specifies the name of the PDB that you want to delete
Chapter 17dbaascli pdb create
17-19
• dbname specifies the name of the container database that hosts the PDB
dbaascli pdb infoTo display more detailed information about a pluggable database (PDB) use thecommand dbaascli pdb info.
Prerequisite
(Run the command as the oracle user.
Syntax
dbaascli pdb info [--pdbname pdbname] --dbname dbname [--detailed]
Options
In the command:
• pdbname optionally specifies the name of the PDB for which you want to displayinformation. If this you do not specify this option, then the command displaysinformation about all of the PDBs in the specified container database.
• dbname specifies the name of the container database that hosts the PDB.
Usage Notes
The command displays information such as the CPU count and storage usage thatis associated with a PDB. You can add the optional --detailed argument to displayextra information, including the list of compute nodes where a PDB is open in read/write mode.
dbaascli pdb local_cloneTo create a new pluggable database (PDB) as a clone of an existing PDB in the samecontainer database (CDB) run the command dbaascli pdb local_clone.
Prerequisite
Run the command as the oracle user.
Syntax
dbaascli pdb local_clone --pdbname sourcepdbname --target_pdbname targetpdbname --dbname dbname
Options
In the command:
• sourcepdbname specifies the name of the PDB that you want to clone
• targetpdbname specifies the name of the new PDB that you want to create
• dbname specifies the name of the container database that hosts the PDBs
Chapter 17dbaascli pdb info
17-20
Usage Notes
The newly cloned PDB inherits administration passwords from the source PDB.
dbaascli pdb openTo open a pluggable database (PDB) run the command dbaascli pdb open.
Prerequisite
Run the command as the oracle user.
Syntax
dbaascli pdb open --pdbname pdbname --dbname dbname
Options
In the command:
• pdbname specifies the name of the PDB that you want to open
• dbname specifies the name of the container database that hosts the PDB.
Usage Notes
Upon successful completion, the PDB is opened on all of the container databaseinstances.
dbaascli pdb remote_cloneTo create a new pluggable database (PDB) as a clone of an existing PDB in anothercontainer database (CDB), run the command dbaascli pdb remote_clone.
Prerequisite
Run the command as the oracle user.
Syntax
$ dbaascli pdb remote_clone --pdbname sourcepdbname --source_db sourcedbname --source_db_scan sourcedbscan --dbname dbname
Options
In the command:
• pdbname specifies the name of the source PDB that you want to clone.
• sourcedbname specifies the name (DB_UNIQUE_NAME) of the CDB that hosts thesource PDB.
• sourcedbscan specifies the Single Client Access Name (SCAN) that is used toconnect to the source database.
• dbname specifies the name (DB_NAME) of the CDB that hosts the newly cloned PDB.
Chapter 17dbaascli pdb open
17-21
Usage Notes
When promoted, you must supply the SYS user password for the source PDB.
The newly cloned PDB inherits administration passwords from the source PDB. Thecloned PDB is named using the following format: dbname_sourcepdbname
This command is supported only for databases that are not in a Data Guardconfiguration and use Oracle Database version 12.2.0.1, or later.
dbaascli pdb renameTo change the name of a pluggable database (PDB) use the command dbaascli pdbrename.
Prerequisite
Run the command as the oracle user.
Syntax
dbaascli pdb rename --pdbname oldname --newname newname --dbname dbname
Options
In the command:
• oldname specifies the old name of the PDB that you want to rename
• newname specifies the new name of the PDB that you want to rename
• dbname specifies the name of the container database that hosts the PDB
dbaascli pdb resizeTo modify the size limits for a pluggable database (PDB) use the commad dbaasclipdb resize.
Prerequisite
Run the command as the oracle user.
Syntax
dbaascli pdb resize --pdbname pdbname --dbname dbname [--maxsize maxsize] [--maxcpu maxcpu]
Options
In the command:
• pdbname specifies the name of the new PDB that you want to modify
• dbname specifies the name of the container database that hosts the PDB
Chapter 17dbaascli pdb rename
17-22
• maxsize optionally specifies the maximum total size of data files and temporaryfiles for tablespaces belonging to the PDB. Setting this option is effectively thesame as setting the MAXSIZE PDB storage clause in the CREATE PLUGGABLEDATABASE SQL command. You can impose a limit by specifying an integer followedby a size unit (K, M, G, or T), or you can specify UNLIMITED to explicitly enforce nolimit
• maxcpu optionally specifies the maximum number of CPUs that are available tothe PDB. Setting this option is effectively the same as setting the CPU_COUNTparameter in the PDB.
Usage Notes
When you run the command, you must specify at least one of optional attributes,--maxsize or --maxcpu. You can specify both optional attributes in one command.
dbaascli tde rotate masterkeyTo change or rotate the master encryption key for the specified database, run thecommand dbaascli tde rotate masterkey.
Prerequisite
Run the command as the oracle user.
Syntax
dbaascli tde rotate masterkey --dbname dbname
Options
--dbname dbname specifies the name of the database that you want to act on.
Usage Notes
Enter the keystore password when prompted. The keystore password is initially set tothe administration password that you specified when you created the database.
dbaascli tde statusTo display information about the keystore for the specified database run the commanddbaascli tde status.
Prerequisite
Run the command as the oracle user.
Syntax
$ dbaascli tde status --dbname dbname
Options
In the command, dbname specifies the name of the database that you want to check.
Chapter 17dbaascli tde rotate masterkey
17-23
Usage Notes
Output from the command includes the type of keystore, and the status of thekeystore.
Chapter 17dbaascli tde status
17-24
18Monitoring and Managing Exadata StorageServers with ExaCLI
Learn to use the ExaCLI command-line utility to perform monitoring and managementfunctions on Exadata storage servers in the Exadata Cloud Service.
• About the ExaCLI CommandThe ExaCLI command provides a subset of the commands found in the on-premises Exadata command line utility.
• Exadata Storage Server Username and PasswordYou need a username and password to connect to the Exadata Storage Server.
• ExaCLI CommandUse ExaCLI (exacli) to configure cell, database node configuration, and objectsin the remote node environment, and to monitor your Exadata Cloud@Customerservices and objects.
• Connecting to a Storage Server with ExaCLITo use ExaCLI on storage servers, you will need to know your target storageserver's IP address.
About the ExaCLI CommandThe ExaCLI command provides a subset of the commands found in the on-premisesExadata command line utility.
ExaCLI offers a subset of the commands found in the on-premises Exadata commandline utility. The utility runs on the database compute nodes in the Exadata CloudService.
Related Topics
• Using the CellCLI Utility
Exadata Storage Server Username and PasswordYou need a username and password to connect to the Exadata Storage Server.
On Exadata Cloud@Customer, the preconfigured user for Exadata Storage Server iscloud_user_clustername, where clustername is the name of the virtual machine (VM)cluster that is being used.
You can determine the name of the VM cluster by running the following crsctlcommand as the grid user on any cluster node:
$ crsctl get cluster name
18-1
The password for cloud_user_clustername is initially set to a random value, whichyou can view by running the following command as the opc user on any cluster node:
$ /opt/exacloud/get_cs_data.py --data_file /opt/exacloud/cs_data.enc
ExaCLI CommandUse ExaCLI (exacli) to configure cell, database node configuration, and objects inthe remote node environment, and to monitor your Exadata Cloud@Customer servicesand objects.
Purpose
ExaCLI (exacli) enables you configure your Exadata Cloud@Customer system,and to obtain real-time information about your Exadata Cloud Service. To obtaininformation about the services and options on your system, run ExaCLI using themonitoring command parameter that you require.
To obtain a list of the system monitoring parameters you can use with ExaCLI, run theLIST parameter.
Syntax
exacli -c [username@]remotehost[:port] [-l username] [--xml] [--cookie-jar filename] [-e {command | 'command; command' | @batchfile}]
Options
Option Description
-c [username@]remotehost or --connect[username@]remotehost[:port]
Specifies the remote node to which you wantto connect. ExaCLI prompts for the user nameif not specified.
-l username or --login-name username Specifies the user name to log into theremote node. The preconfigured user iscloud_user_clustername.
--xml Displays the output in XML format.
--cookie-jar [filename] Specifies the filename of the cookie jar to use.If you do not specify a filename, then thecookie is stored in a default cookie jar locatedat HOME/.exacli/cookiejar, where HOME isthe home directory of the operating systemuser running the exacli command.
The presence of a valid cookie allowsthe ExaCLI user to run commands withoutrequiring the user to log in during subsequentExaCLI sessions.
Chapter 18ExaCLI Command
18-2
Option Description
-e command or -e 'command[; command]'or -e @batchFile
Specifies either the ExaCLI commands to run,or a batch file. After running the commands,ExaCLI quits.
If you are specifying multiple commands torun, then enclose the commands in singlequotes to prevent the shell from interpretingthe semicolon.
To start an interactive ExaCLI session, omitthis command.
--cert-proxy proxy[:port] Specifies the proxy server that you want touse when downloading certificates. If port isomitted, then port 80 is used by default.
-n or --no-prompt Suppresses prompting for user input.
Command Parameters
To obtain information about objects and services on your system, use these ExaCLIcommand parameters.
Table 18-1 Command
Command Parameter Description
ACTIVEREQUEST Lists all active requests that are currentlybeing served by the storage servers.
ALERTDEFINITION Lists all possible alerts and their sources forstorage servers.
ALERTHISTORY Lists all alerts that have been issues for thestorage servers.
CELL Used to list the details of a specific attributeof the storage servers or storage cells. Thesyntax is as follows: LIST CELL ATTRIBUTESA,B,C, with A, B, and C being attributes. Tosee all cell attributes, use the LIST CELLATTRIBUTES ALL command.
CELLDISK Lists the attributes of the cell disks in thestorage servers. Use the following syntax tolist the cell disk details: LIST CELLDISKcell_disk_name DETAIL.
DATABASE Lists details of the databases. Uses the regularLIST command syntax: LIST DATABASE andLIST DATABASE DETAIL. You can also usethis command to show an individual attributewith the following syntax: LIST DATABASEATTRIBUTES NAME.
FLASHCACHE Lists the details of the Exadata system'sflash cache. For this object, you can use thefollowing syntax patterns: LIST FLASHCACHEDETAIL or LIST FLASHCACHE ATTRIBUTESattribute_name.
Chapter 18ExaCLI Command
18-3
Table 18-1 (Cont.) Command
Command Parameter Description
FLASHCACHECONTENT Lists the details of all objects in the flashcache, or the details of a specified object ID.To list all the details of all objects, use LISTFLASHCACHECONTENT DETAIL.
To list details for a specific object, use a whereclause as follows: LIST FLASHCACHECONTENTWHERE objectNumber=12345 DETAIL.
Example query: finding the object_id valueof an object
select object_name, data_object_id from user_objects where object_name = 'BIG_CENSUS';OBJECT_NAME DATA_OBJECT_ID----------------------------------------BIG_CENSUS 29152
FLASHLOG Lists the attributes for the Oracle ExadataSmart Flash Log.
GRIDDISK Lists the details of a particular grid disk.The syntax is similar to the CELLDISKcommand syntax. To view all attributes: LISTGRIDDISK grid_disk_name DETAIL. Toview specified attributes of the grid disk: LISTGRIDDISK grid_disk_name ATTRIBUTESsize, name.
IBPORT Lists details of the InfiniBand ports. Syntax isLIST IBPORT DETAIL.
IORMPLAN Use the ExaCLI CREATE, ALTER, DROP, andLIST commands with IORMPLAN. To see thedetails of all IORM plans, use LIST IORMPLANDETAIL. You can also use the command tocreate and alter IORM plans, and to applyplans to storage servers.
IORMPROFILE Lists any IORM profiles that have been set onthe storage servers. You can also refer back tothe profile attribute on the DATABASE object if adatabase has an IORM profile on it. Syntax isLIST IORMPROFILE.
LIST Lists the command parameter optionsavailable with ExaCLI for the ExadataCloud@Customer services and objects.
Chapter 18ExaCLI Command
18-4
Table 18-1 (Cont.) Command
Command Parameter Description
LUN The LUN (logical unit number) object returnsthe number and the detail of the physical disksin the storage servers. List the LUNs of thedisks with LIST LUN. List the details of eachLUN with LIST LUN lun_number DETAIL.
METRICCURRRENT Lists the current metrics for a particular objecttype. Syntax is LIST METRICCURRENT WHEREobjectType = 'CELLDISK'.
This command also allows for sorting andresults limits as seen in the following example:
LIST METRICCURRENT attributes name, metricObjectName ORDER BY metricObjectName asc, name desc LIMIT 5
METRICDEFINITION Lists metric definitions for the object thatyou can then get details for. With thecommand LIST metricDefinition WHEREobjectType=cell, you can get all the metricsfor that object type. You can then use themetric definition object again to get details forone of those specific metrics just listed:
LIST metricDefinition WHERE name= IORM_MODE DETAIL
METRICHISTORY List metrics over a specified period oftime. For example, with the command LISTMETRICHISTORY WHERE ageInMinutes <30, you can list all the metrics collected overthe past 30 minutes. You can also use thepredicate collectionTime to set a rangefrom a specific time.
Use collectionTime as shownin the follow example: LISTMETRICHISTORY WHERE collectionTime> '2018-04-01T21:12:00-10:00'. Themetric history object can also be used tosee a specific metric using the object’sname (for example, LIST METRICHISTORYCT_FD_IO_RQ_SM) or with a "where" clauseto get objects with similar attributes like name(for example, LIST METRICHISTORY WHEREname like 'CT_.*').
Chapter 18ExaCLI Command
18-5
Table 18-1 (Cont.) Command
Command Parameter Description
OFFLOADGROUP Lists the attributes for the offload groupthat are running on your storage servers.You can list all details for all groups withLIST OFFLOADGROUP DETAIL, or list theattributes for a specific group, as shown inthe following example: LIST OFFLOADGROUPoffloadgroup4. List specific attributes withLIST OFFLOADGROUP ATTRIBUTES name.
PHYSICALDISK Lists all physical disks. Use the results of LISTPHYSICALDISK to identify a specific disk forfurther investigation, then list the details ofthat disk using the command as follows: LISTPHYSICALDISK 20:10 DETAIL. To list thedetails of flash disks, use the command asfollows: LIST PHYSICALDISK FLASH_1_0DETAIL).
PLUGGABLEDATABASE Lists all PDBs. View the details of aspecific PDB with LIST PLUGGABLEDATABASEpdb_name.
QUARANTINE Lists all SQL statements that you preventedfrom using Smart Scans. The syntax is LISTQUARANTINE DETAIL. You can also usea "where" clause on any of the availableattributes.
DIAGPACK Use the ExaCLI CREATE, ALTER, DROP, andLIST commands with DIAGPACK to listthe diagnostic packages and their statusin your Exadata system. The syntax isLIST DIAGPACK [DETAIL], with DETAILbeing an optional attribute. Use CREATEDIAGPACK with the packStartTime attributeto gather logs and trace files into a singlecompressed file for downloading, as inthe following example: CREATE DIAGPACKpackStartTime=2019_12_15T00_00_00.You can also use the value nowwith packStartTime: CREATE DIAGPACKpackStartTime=now.
To download a diagnostic package, useDOWNLOAD DIAGPACK package_namelocal_directory. For example, the followingcommand downloads a diagnostic package tothe /tmp directory: DOWNLOAD DIAGPACKcfclcx2647_diag_2018_06_03T00_44_24_1 /tmp.
Usage Notes
• Notes for the --cookie-jar option:
Chapter 18ExaCLI Command
18-6
– The user name and password are sent to the remote node for authentication.On successful authentication, the remote node issues a cookie (the logincredentials) that is stored in the specified filename on the database node. Iffilename is not specified, the cookie is stored in a default cookie jar located atHOME/.exacli/cookiejar, where HOME is the home directory of the operatingsystem user running the ExaCLI command. For the opc user, the home is /home/opc.
– The operating system user running the ExaCLI command is the owner of thecookie jar file.
– A cookie jar can contain multiple cookies from multiple users on multiplenodes in parallel sessions.
– Cookies are invalidated after 24 hours.
– If the cookie is not found or is no longer valid, ExaCLI prompts for thepassword. The new cookie is stored in the cookie jar identified by filename, orthe default cookie jar if filename is not specified.
– Even without the --cookie-jar option, ExaCLI still checks for cookies fromthe default cookie jar. However, if the cookie does not exist or is no longervalid, the new cookie will not be stored in the default cookie jar if the --cookie-jar option is not specified.
• Notes for the -e option:
– ExaCLI exits after running the commands.
– If specifying multiple commands to run, be sure to enclose the commands insingle quotes to prevent the shell from interpreting the semi-colon.
– The batch file is a text file that contains one or more ExaCLI commands to run.
• Notes for the -n (--no-prompt) option:
– If ExaCLI needs additional information from the user, for example, if ExaCLIneeds to prompt the user for a password (possibly because there were novalid cookies in the cookie-jar) or to prompt the user to confirm the remotenode’s identity, then ExaCLI prints an error message and exits.
Examples
Example 18-1 Starting an Interactive ExaCLI Session on a Storage Server
This example shows the user on an Exadata compute node issuing the command tolog in to ExaCLI start an interactive ExaCLI session on a storage server:
[opc@exacs-node1 ~]$ exacli -l cloud_user_clustername -c 192.168.136.7
See "Finding the IP addresses of storage cells using the cellip.ora file" for informationabout how to determine your storage server IP address.
After you are logged in, run additional commands as follows:
exacli [email protected]> LIST DATABASEASMHRCDB
Chapter 18ExaCLI Command
18-7
Example 18-2 Issuing a Single Command on a Compute Node
This example shows a single command issued on a compute node that does thefollowing:
• Connects to a storage server
• Performs a LIST action
• Exits the session (specified with the -e option)
[opc@exacs-node1 ~]$ exacli -l cloud_user_clustername -c 192.168.136.7 --xml --cookie-jar -e list griddisk detail
Related Topics
• Finding the IP addresses of storage cells using the cellip.ora file
Connecting to a Storage Server with ExaCLITo use ExaCLI on storage servers, you will need to know your target storage server'sIP address.
If you do not know the IP address of the node you want to connect to, you can find itby viewing the contents of the cellip.ora file.
The following example illustrates how to do so on the UNIX command line for a quarterrack system. (Note that a quarter rack has three storage cells, and each cell has twoconnections, so a total of six IP addresses are shown.)
[root@exacs-node1 ~]# cat /etc/oracle/cell/network-config/cellip.oraclecell="192.168.136.5;cell="192.168.136.6"cell="192.168.136.7;cell="192.168.136.8"cell="192.168.136.9;cell="192.168.136.10"
If you are connecting to a storage cell for the first time using ExaCLI, you may beprompted to accept an SSL certificate. The ExaCLI output in this case will look like thefollowing:
[opc@exacs-node1 ~]$ exacli -l cloud_user_clustername -c 192.168.136.7 --cookie-jarNo cookies found for [email protected]: *********EXA-30016: This connection is not secure. You have asked ExaCLI to connect to cell 192.168.136.7 securely. The identity of 192.168.136.7 cannot be verified.Got certificate from server:C=US,ST=California,L=Redwood City,O=Oracle Corporation,OU=Oracle Exadata,CN=ed1cl03clu01-priv2.usdc2.oraclecloud.comDo you want to accept and store this certificate? (Press y/n)
Accept the self-signed Oracle certificate by pressing "y" to continue using ExaCLI.
Chapter 18Connecting to a Storage Server with ExaCLI
18-8
19Policy Details for ExadataCloud@Customer
Learn to write policies to control access to Exadata Cloud@Customer resources.
Note:
For more information on Policies, see "How Policies Work".
For a sample policy, see "Let database admins manage ExadataCloud@Customer instances".
• About Resource-TypesLearn about resource-types you can use in your policies.
• Resource-Types for Exadata Cloud@CustomerReview the list of resource-types specific to Exadata Cloud@Customer.
• Supported VariablesUse variables when adding conditions to a policy.
• Details for Verb + Resource-Type CombinationsReview the list of permissions and API operations covered by each verb.
• Permissions Required for Each API OperationReview the list of API operations for Exadata Cloud@Customer resources in alogical order, grouped by resource type.
Related Topics
• How Policies Work
• Let database admins manage Exadata Cloud@Customer instances
About Resource-TypesLearn about resource-types you can use in your policies.
An aggregate resource-type covers the list of individual resource-types that directlyfollow. For example, writing one policy to allow a group to have access to thedatabase-family is equivalent to writing eight separate policies for the groupthat would grant access to the exadata-infrastructures, vmcluster-networks,vmclusters, backups-destinations, db-nodes, and the rest of the individual resource-types. For more information, see Resource-Types.
19-1
Resource-Types for Exadata Cloud@CustomerReview the list of resource-types specific to Exadata Cloud@Customer.
Aggregate Resource-Type
database-family
Individual Resource-Types
exadata-infrastructures
vmcluster-networks
vmclusters
backups-destinations
db-nodes
db-homes
databases
backups
Supported VariablesUse variables when adding conditions to a policy.
Exadata Cloud@Customer supports only the general variables. For more information,see "General Variables for All Requests".
Related Topics
• General Variables for All Requests
Details for Verb + Resource-Type CombinationsReview the list of permissions and API operations covered by each verb.
For more information, see "Permissions", "Verbs", and "Resource-Types".
• Database-Family Resource TypesUnderstand the level of access of each verb.
Chapter 19Resource-Types for Exadata Cloud@Customer
19-2
• exadata-infrastructuresReview the list of permissions and API operations for exadata-infrastructuresresource-type.
• vmcluster-networksReview the list of permissions and API operations for vmcluster-networksresource-type.
• vmclustersReview the list of permissions and API operations for vmclusters resource-type.
• backup-destinationsReview the list of permissions and API operations for backup-destinationsresource-type.
• db-nodesReview the list of permissions and API operations for db-nodes resource-type.
• db-homesReview the list of permissions and API operations for db-homes resource-type.
• databasesReview the list of permissions and API operations for databases resource-type.
• backupsReview the list of permissions and API operations for backups resource-type.
• autonomous-vmclustersReview the list of permissions and API operations for autonomous-vmclustersresource-type.
• autonomous-container-databasesReview the list of permissions and API operations for autonomous-container-databases resource-type.
• autonomous-databasesReview the list of permissions and API operations for autonomous-container-databases resource-type.
• data-guard-associationReview the list of permissions and API operations for data-guard-associationresource-type.
• key-storesReview the list of permissions and API operations for key-store resource-type.
• autonomousContainerDatabaseDataguardAssociationsReview the list of permissions and API operations forautonomousContainerDatabaseDataguardAssociations resource-type.
• AutonomousDatabaseDataguardAssociationReview the list of permissions and API operations forAutonomousDatabaseDataguardAssociation resource-type.
Related Topics
• Permissions
• Verbs
• Resource-Types
Chapter 19Details for Verb + Resource-Type Combinations
19-3
Database-Family Resource TypesUnderstand the level of access of each verb.
The level of access is cumulative as you go from inspect > read > use > manage. Aplus sign (+) in a table cell indicates incremental access compared to the cell directlyabove it, whereas "no extra" indicates no incremental access.
For example, the read verb for the vmclusters resource-type covers no extrapermissions or API operations compared to the inspect verb. However, the use verbincludes one more permission, fully covers one more operation, and partially coversanother additional operation.
exadata-infrastructuresReview the list of permissions and API operations for exadata-infrastructuresresource-type.
Granting permissions on exadata-infrastructure resources grants permissions onassociated vmcluster-network resources.
Table 19-1 INSPECT
Permission APIs Fully Covered APIs Partially Covered
EXADATA_INFRASTRUCTURE_INSPECT
ListExadataInfrastructures
GetExadataInfrastructure
GenerateRecommendedNetworkDetails
ChangeExadataInfrastructureCompartment
Table 19-2 READ
Permissions APIs Fully Covered APIs Partially Covered
INSPECT +
EXADATA_INFRASTRUCTURE_CONTENT_READ
DownloadExadataInfrastructureConfigFile
none
Table 19-3 USE
Permissions APIs Fully Covered APIs Partially Covered
READ +
EXADATA_INFRASTRUCTURE_UPDATE
ActivateExadataInfrastructure
UpdateExadataInfrastructure
ChangeExadataInfrastructureCompartment
CreateVmCluster (alsoneeds manage vmclusters)
UpdateVmCluster (alsoneeds use vmclusters)
ChangeExadataInfrastructureCompartment
Chapter 19Details for Verb + Resource-Type Combinations
19-4
Table 19-4 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
EXADATA_INFRASTRUCTURE_CREATE
EXADATA_INFRASTRUCTURE_DELETE
CreateExadataInfrastructure
DeleteExadataInfrastructure
downloadExadataInfrastructureConfigFile
none
vmcluster-networksReview the list of permissions and API operations for vmcluster-networks resource-type.
vmcluster-network resources inherit permissions from the exadata-infrastructureresources with which they are associated. You cannot grant permissions tovmcluster-network resources explicitly.
Table 19-5 INSPECT
Permission APIs Fully Covered APIs Partially Covered
EXADATA_INFRASTRUCTURE_INSPECT
ListVmClusterNetworks
GetVmClusterNetwork
ValidateVmClusterNetwork
none
Table 19-6 READ
Permissions APIs Fully Covered APIs Partially Covered
INSPECT +
EXADATA_INFRASTRUCTURE_CONTENT_READ
DownloadVmClusterNetworkConfigFile
none
Table 19-7 USE
Permissions APIs Fully Covered APIs Partially Covered
READ +
EXADATA_INFRASTRUCTURE_UPDATE
CreateVmClusterNetwork
UpdateVmClusterNetwork
DeleteVmClusterNetwork
none
Chapter 19Details for Verb + Resource-Type Combinations
19-5
Table 19-8 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
EXADATA_INFRASTRUCTURE_CREATE
EXADATA_INFRASTRUCTURE_DELETE
none none
vmclustersReview the list of permissions and API operations for vmclusters resource-type.
Table 19-9 INSPECT
Permission APIs Fully Covered APIs Partially Covered
VM_CLUSTER_INSPECT ListVmClusters
GetVmCluster
ListVmClusterPatches
ListVmClusterPatchHistoryEntries
GetVmClusterPatch
GetVmClusterPatchHistoryEntry
none
Table 19-10 READ
Permissions APIs Fully Covered APIs Partially Covered
No extra No extra none
Chapter 19Details for Verb + Resource-Type Combinations
19-6
Table 19-11 USE
Permissions APIs Fully Covered APIs Partially Covered
READ +
VM_CLUSTER_UPDATE
ChangeVmClusterCompartment
UpdateVmCluster (alsoneeds use exadata-infrastructures)
CreateDbHome, (also needsmanage db-homes andmanage databases). Ifautomatic backups areenabled on the defaultdatabase, also needs managebackups
DeleteDbHome, (also needsmanage db-homes andmanage databases. Ifautomatic backups areenabled on the defaultdatabase, also needs managebackups
Table 19-12 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
VM_CLUSTER_CREATE
VM_CLUSTER_DELETE
No extra CreateVmCluster (alsoneeds use exadata-infrastructures)
DeleteVmCluster (alsoneeds use exadata-infrastructures)
backup-destinationsReview the list of permissions and API operations for backup-destinations resource-type.
Table 19-13 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
BACKUP_DESTINATION_INSPECT
ListBackupDestinations
GetBackupDestination
none
Table 19-14 READ
Permissions APIs Fully Covered APIs Partially Covered
no extra no extra none
Chapter 19Details for Verb + Resource-Type Combinations
19-7
Table 19-15 USE
Permissions APIs Fully Covered APIs Partially Covered
READ +
BACKUP_DESTINATION_UPDATE
UpdateBackupDestination
ChangeBackupDestinationCompartment
none
Table 19-16 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
BACKUP_DESTINATION_CREATE
BACKUP_DESTINATION_DELETE
CreateBackupDestination
DeleteBackupDestination
none
db-nodesReview the list of permissions and API operations for db-nodes resource-type.
Table 19-17 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
DB_NODE_INSPECT
DB_NODE_QUERY
GetDbNode none
Table 19-18 READ
Permissions APIs Fully Covered APIs Partially Covered
No extra No extra none
Table 19-19 USE
Permissions APIs Fully Covered APIs Partially Covered
No extra No extra none
Table 19-20 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
DB_NODE_POWER_ACTIONS
DbNodeAction none
Chapter 19Details for Verb + Resource-Type Combinations
19-8
db-homesReview the list of permissions and API operations for db-homes resource-type.
Table 19-21 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
DB_HOME_INSPECT ListDBHome
GetDBHome
ListDbHomePatches
ListDbHomePatchHistoryEntries
GetDbHomePatch
GetDbHomePatchHistoryEntry
none
Table 19-22 READ
Permissions APIs Fully Covered APIs Partially Covered
No extra No extra none
Table 19-23 USE
Permissions APIs Fully Covered APIs Partially Covered
DB_HOME_UPDATE UpdateDBHome none
Table 19-24 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
DB_HOME_CREATE
DB_HOME_DELETE
No extra CreateDbHome, (also needsuse vmclusters andmanage databases). Ifautomatic backups areenabled on the defaultdatabase, also needs managebackups
DeleteDbHome, (also needsuse vmclusters andmanage databases). Ifautomatic backups areenabled on the defaultdatabase, also needs managebackups.
databasesReview the list of permissions and API operations for databases resource-type.
Chapter 19Details for Verb + Resource-Type Combinations
19-9
Table 19-25 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
DATABASE_INSPECT ListDatabases
GetDatabase
none
Table 19-26 READ
Permissions APIs Fully Covered APIs Partially Covered
No extra No extra none
Table 19-27 USE
Permissions APIs Fully Covered APIs Partially Covered
READ +
DATABASE_UPDATE
UpdateDatabase If enabling automatic backups,also needs manage backups.
Table 19-28 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
DATABASE_CREATE
DATABASE_DELETE
No extra CreateDbHome, (also needsuse vmclusters andmanage db-homes). Ifautomatic backups areenabled on the defaultdatabase, also needs managebackups
DeleteDbHome, (also needsuse vmclusters andmanage db-homes). Ifautomatic backups areenabled on the defaultdatabase, also needs managebackups
backupsReview the list of permissions and API operations for backups resource-type.
Table 19-29 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
DB_BACKUP_INSPECT GetBackup
ListBackups
none
Chapter 19Details for Verb + Resource-Type Combinations
19-10
Table 19-30 READ
Permissions APIs Fully Covered APIs Partially Covered
INSPECT +
DB_BACKUP_CONTENT_READ
none RestoreDatabase (alsoneeds use databases)
Table 19-31 USE
Permissions APIs Fully Covered APIs Partially Covered
no extra no extra none
Table 19-32 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
DB_BACKUP_CREATE
DB_BACKUP_DELETE
no extra none
autonomous-vmclustersReview the list of permissions and API operations for autonomous-vmclustersresource-type.
Table 19-33 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
AUTONOMOUS_VM_CLUSTER_INSPECT
ListAutonomousVmClusters
GetAutonomousVmCluster
ChangeAutonomousVmClusterCompartment
Table 19-34 READ
Permissions APIs Fully Covered APIs Partially Covered
No extra No extra none
Table 19-35 USE
Permissions APIs Fully Covered APIs Partially Covered
READ +
AUTONOMOUS_VM_CLUSTER_UPDATE
ChangeAutonomousVmClusterCompartment
UpdateAutonomousVmCluster
CreateAutonomousContainerDatabase
TerminateAutonomousContainerDatabase
Chapter 19Details for Verb + Resource-Type Combinations
19-11
Table 19-36 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
AUTONOMOUS_VM_CLUSTER_CREATE +
AUTONOMOUS_VM_CLUSTER_DELETE
DeleteAutonomousVmCluster
CreateAutonomousVmCluster
autonomous-container-databasesReview the list of permissions and API operations for autonomous-container-databases resource-type.
Table 19-37 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
AUTONOMOUS_CONTAINER_DATABASE_INSPECT
ListAutonomousContainerDatabases,GetAutonomousContainerDatabase
none
Table 19-38 READ
Permissions APIs Fully Covered APIs Partially Covered
No extra No extra none
Table 19-39 USE
Permissions APIs Fully Covered APIs Partially Covered
AUTONOMOUS_CONTAINER_DATABASE_UPDATE
UpdateAutonomousContainerDatabase
ChangeAutonomousContainerDatabaseCompartment
CreateAutonomousDatabase (also needs manageautonomous-databases)
Table 19-40 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
AUTONOMOUS_CONTAINER_DATABASE_CREATE
AUTONOMOUS_CONTAINER_DATABASE_DELETE
No extra CreateAutonomousContainerDatabase,TerminateAutonomousContainerDatabase (both alsoneed use autonomous-VmCluster)
Chapter 19Details for Verb + Resource-Type Combinations
19-12
autonomous-databasesReview the list of permissions and API operations for autonomous-container-databases resource-type.
Table 19-41 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
AUTONOMOUS_DATABASE_INSPECT
GetAutonomousDatabase,ListAutonomousDatabases
no extra
Table 19-42 READ
Permissions APIs Fully Covered APIs Partially Covered
INSPECT +AUTONOMOUS_DATABASE_CONTENT_READ
no extra CreateAutonomousDatabaseBackup (also needs manageautonomous-backups)
Table 19-43 USE
Permissions APIs Fully Covered APIs Partially Covered
READ +AUTONOMOUS_DATABASE_CONTENT_WRITE +AUTONOMOUS_DATABASE_UPDATE
UpdateAutonomousDatabase
RestoreAutonomousDatabase (also needs readautonomous-backups)
ChangeAutonomousDatabaseCompartment (also needsread autonomous-backups)
Table 19-44 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
AUTONOMOUS_DATABASE_CREATE
AUTONOMOUS_DATABASE_DELETE
CreateAutonomousDatabase
none
data-guard-associationReview the list of permissions and API operations for data-guard-associationresource-type.
Chapter 19Details for Verb + Resource-Type Combinations
19-13
Table 19-45 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
DATABASE_INSPECT ListDataGuardAssociations,GetDataGuardAssociation
CreateDataGuardAssociation
Table 19-46 READ
Permissions APIs Fully Covered APIs Partially Covered
no extra no extra no extra
Table 19-47 USE
Permissions APIs Fully Covered APIs Partially Covered
READ + VM_CLUSTER_UPDATE+ DB_HOME_UPDATE
DATABASE_UPDATE
DeleteDatabase
SwitchoverDataGuardAssociation,FailoverDataGuardAssociation,ReinstateDataGuardAssociation
CreateDataGuardAssociation
Table 19-48 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +
DATABASE_DELETE
DeleteDatabase none
key-storesReview the list of permissions and API operations for key-store resource-type.
Table 19-49 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
KEY_STORE_INPSECT
AUTONOMOUS_CONTAINER_DATABASE_INSPECT
AUTONOMOUS_DATABASE_INSPECT
AUTONOMOUS_DB_BACKUP_INSPECT
GetKeyStore
GetAutonomousContainerDatabase
GetAutonomousDatabase
GetAutonomousDatabaseBackup
ChangeKeyStoreCompartment
RotateAutonomousContainerDatabaseKey
Chapter 19Details for Verb + Resource-Type Combinations
19-14
Table 19-50 READ
Permissions APIs Fully Covered APIs Partially Covered
no extra no extra no extra
Table 19-51 USE
Permissions APIs Fully Covered APIs Partially Covered
READ + KEY_STORE_UPDATE+
AUTONOMOUS_VM_CLUSTER_UPDATE +
AUTONOMOUS_CONTAINER_DATABASE_UPDATE
AUTONOMOUS_DATABASE_UPDATE
UpdateKeyStore
none
none
none
RotateAutonomousDatabaseKey
ChangeKeyStoreCompartment
CreateAutonomousContainerDatabase
RotateAutonomousContainerDatabaseKey
none
Table 19-52 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE + KEY_STORE_CREATE +
KEY_STORE_DELETE +
AUTONOMOUS_CONTAINER_DATABASE_CREATE
CreateKeyStore
DeleteKeyStore
CreateAutonomousContainerDatabase
none
none
none
autonomousContainerDatabaseDataguardAssociationsReview the list of permissions and API operations forautonomousContainerDatabaseDataguardAssociations resource-type.
Table 19-53 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
AUTONOMOUS_VM_CLUSTER_INSPECT
AUTONOMOUS_CONTAINER_DATABASE_INSPECT
none
GetAutonomousContainerDatabaseListAutonomousContainerDatabaseDataguardAssociationsGetAutonomousContainerDatabaseDataguardAssociation
CreateAutonomousContainerDatabase
FailoverAutonomousContainerDatabaseDataguardAssociationSwitchoverAutonomousContainerDatabaseDataguardAssociationReinstateAutonomousContainerDatabaseDataguardAssociation
Chapter 19Details for Verb + Resource-Type Combinations
19-15
Table 19-54 READ
Permissions APIs Fully Covered APIs Partially Covered
no extra no extra no extra
Table 19-55 USE
Permissions APIs Fully Covered APIs Partially Covered
READ +AUTONOMOUS_VM_CLUSTER_UPDATE +
AUTONOMOUS_CONTAINER_DATABASE_UPDATE
none
none
CreateAutonomousContainerDatabasedeleteAutonomouContainerDatabase
FailoverAutonomousContainerDatabaseDataguardAssociationSwitchoverAutonomousContainerDatabaseDataguardAssociationReinstateAutonomousContainerDatabaseDataguardAssociation
Table 19-56 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE +AUTONOMOUS_CONTAINER_DATABASE_CREATE +
AUTONOMOUS_CONTAINER_DATABASE_DELETE
none
none
CreateAutonomousContainerDatabase
deleteAutonomouContainerDatabase
AutonomousDatabaseDataguardAssociationReview the list of permissions and API operations forAutonomousDatabaseDataguardAssociation resource-type.
Table 19-57 INSPECT
Permissions APIs Fully Covered APIs Partially Covered
AUTONOMOUS_DATABASE_INSPECT
GetAutonomousDatabase none
Table 19-58 READ
Permissions APIs Fully Covered APIs Partially Covered
no extra no extra no extra
Chapter 19Details for Verb + Resource-Type Combinations
19-16
Table 19-59 USE
Permissions APIs Fully Covered APIs Partially Covered
READ + no extra no extra no extra
Table 19-60 MANAGE
Permissions APIs Fully Covered APIs Partially Covered
USE + no extra no extra no extra
Permissions Required for Each API OperationReview the list of API operations for Exadata Cloud@Customer resources in a logicalorder, grouped by resource type.
For information about permissions, see Permissions.
Table 19-61 Database API Operations
API Operation Permissions Required to Use theOperation
ListExadataInfrastructures EXADATA_INFRASTRUCTURE_INSPECT
GetExadataInfrastructure EXADATA_INFRASTRUCTURE_INSPECT
CreateExadataInfrastructure EXADATA_INFRASTRUCTURE_CREATE
UpdateExadataInfrastructure EXADATA_INFRASTRUCTURE_UPDATE
ChangeExadataInfrastructureCompartment
EXADATA_INFRASTRUCTURE_INSPECT andEXADATA_INFRASTRUCTURE_UPDATE
DeleteExadataInfrastructure EXADATA_INFRASTRUCTURE_DELETE
DownloadExadataInfrastructureConfigFile
EXADATA_INFRASTRUCTURE_CONTENT_READ
DownloadExadataInfrastructureConfigFile
EXADATA_INFRASTRUCTURE_CONTENT_READ
ActivateExadataInfrastructure EXADATA_INFRASTRUCTURE_UPDATE
GenerateRecommendedNetworkDetails EXADATA_INFRASTRUCTURE_INSPECT
ListVmClusterNetworks EXADATA_INFRASTRUCTURE_INSPECT
GetVmClusterNetwork EXADATA_INFRASTRUCTURE_INSPECT
CreateVmClusterNetwork EXADATA_INFRASTRUCTURE_INSPECT andEXADATA_INFRASTRUCTURE_UPDATE
UpdateVmClusterNetwork EXADATA_INFRASTRUCTURE_INSPECT andEXADATA_INFRASTRUCTURE_UPDATE
DeleteVmClusterNetwork EXADATA_INFRASTRUCTURE_UPDATE
DownloadVmClusterNetworkConfigFile EXADATA_INFRASTRUCTURE_INSPECT andEXADATA_INFRASTRUCTURE_CONTENT_READ
ValidateVmClusterNetwork EXADATA_INFRASTRUCTURE_INSPECT
Chapter 19Permissions Required for Each API Operation
19-17
Table 19-61 (Cont.) Database API Operations
API Operation Permissions Required to Use theOperation
ListVmClusters VM_CLUSTER_INSPECT
GetVmCluster VM_CLUSTER_INSPECT
CreateVmCluster EXADATA_INFRASTRUCTURE_INSPECT andEXADATA_INFRASTRUCTURE_UPDATE andVM_CLUSTER_CREATE
UpdateVmCluster EXADATA_INFRASTRUCTURE_INSPECT andEXADATA_INFRASTRUCTURE_UPDATE andVM_CLUSTER_UPDATE
ChangeVmClusterCompartment VM_CLUSTER_INSPECT andVM_CLUSTER_UPDATE
DeleteVmCluster VM_CLUSTER_DELETE
ListVmClusterPatches VM_CLUSTER_INSPECT
ListVmClusterPatchHistoryEntries VM_CLUSTER_INSPECT
GetVmClusterPatch VM_CLUSTER_INSPECT
GetVmClusterPatchHistoryEntry VM_CLUSTER_INSPECT
ListBackupDestinations BACKUP_DESTINATION_INSPECT
GetBackupDestination BACKUP_DESTINATION_INSPECT
CreateBackupDestination BACKUP_DESTINATION_CREATE
UpdateBackupDestination BACKUP_DESTINATION_UPDATE
DeleteBackupDestination BACKUP_DESTINATION_DELETE
ChangeBackupDestinationCompartment BACKUP_DESTINATION_INSPECT andBACKUP_DESTINATION_UPDATE
GetDbNode DB_NODE_INSPECT
DbNodeAction DB_NODE_POWER_ACTIONS
ListDbHomes DB_HOME_INSPECT
GetDbHome DB_HOME_INSPECT
CreateDbHome VM_CLUSTER_INSPECT andVM_CLUSTER_UPDATE and DB_HOME_CREATEand DATABASE_CREATE
To enable automatic backups for thedatabase, also need DB_BACKUP_CREATE andDATABASE_CONTENT_READ.
UpdateDbHome DB_HOME_UPDATE
DeleteDbHome VM_CLUSTER_UPDATE and DB_HOME_UPDATEand DATABASE_DELETE
ListDbHomePatches DB_HOME_INSPECT
ListDbHomePatchHistoryEntries DB_HOME_INSPECT
GetDbHomePatch DB_HOME_INSPECT
GetDbHomePatchHistoryEntry DB_HOME_INSPECT
Chapter 19Permissions Required for Each API Operation
19-18
Table 19-61 (Cont.) Database API Operations
API Operation Permissions Required to Use theOperation
CreateDatabase VM_CLUSTER_INSPECT,VM_CLUSTER_UPDATE, DB_HOME_INSPECT,DB_HOME_UPDATE, DATABASE_CREATE
DB_BACKUP_CREATE andDATABASE_CONTENT_READ
DB_BACKUP_INSPECT,DB_BACKUP_CONTENT_READ
ListDatabases DATABASE_INSPECT
GetDatabase DATABASE_INSPECT
UpdateDatabase DATABASE_UPDATE
To enable automatic backups,also need DB_BACKUP_CREATE andDATABASE_CONTENT_READ
DeleteDatabase VM_CLUSTER_UPDATE, DB_HOME_UPDATE,DATABASE_DELETE
DB_BACKUP_INSPECT, DB_BACKUP_DELETE
DB_BACKUP_CREATE andDATABASE_CONTENT_READ
ListDbVersions (no permissions required; available to anyone)
GetBackup DB_BACKUP_INSPECT
ListBackups DB_BACKUP_INSPECT
CreateBackup DB_BACKUP_CREATE andDATABASE_CONTENT_READ
DeleteBackup DB_BACKUP_DELETE andDB_BACKUP_INSPECT
RestoreDatabase DB_BACKUP_INSPECT andDB_BACKUP_CONTENT_READ andDATABASE_CONTENT_WRITE
CreateAutonomousVmCluster AUTONOMOUS_VM_CLUSTER_CREATE andEXADATA_INFRASTRUCTURE_INSPECT andEXADATA_INFRASTRUCTURE_UPDATE
ListAutonomousVmClusters AUTONOMOUS_VM_CLUSTER_INSPECT
GetAutonomousVmCluster AUTONOMOUS_VM_CLUSTER_INSPECT
UpdateAutonomousVmCluster AUTONOMOUS_VM_CLUSTER_UPDATE andEXADATA_INFRASTRUCTURE_INSPECT andEXADATA_INFRASTRUCTURE_UPDATE
ChangeAutonomousVmClusterCompartment AUTONOMOUS_VM_CLUSTER_INSPECT andAUTONOMOUS_VM_CLUSTER_UPDATE
DeleteAutonomousVmCluster AUTONOMOUS_VM_CLUSTER_DELETE
ListAutonomousContainerDatabases AUTONOMOUS_CONTAINER_DATABASE_INSPECT
Chapter 19Permissions Required for Each API Operation
19-19
Table 19-61 (Cont.) Database API Operations
API Operation Permissions Required to Use theOperation
GetAutonomousContainerDatabase AUTONOMOUS_CONTAINER_DATABASE_INSPECT
CreateAutonomousContainerDatabase AUTONOMOUS_VM_CLUSTER_UPDATE andAUTONOMOUS_CONTAINER_DATABASE_CREATE
TerminateAutonomousContainerDatabase AUTONOMOUS_VM_CLUSTER_UPDATE andAUTONOMOUS_CONTAINER_DATABASE_DELETE
UpdateAutonomousContainerDatabase AUTONOMOUS_CONTAINER_DATABASE_UPDATE
ChangeAutonomousContainerDatabaseCompartment
AUTONOMOUS_CONTAINER_DATABASE_INSPECT andAUTONOMOUS_CONTAINER_DATABASE_UPDATE
GetAutonomousDatabase AUTONOMOUS_DATABASE_INSPECT
ListAutonomousDatabases AUTONOMOUS_DATABASE_INSPECT
CreateAutonomousDatabase AUTONOMOUS_DATABASE_CREATE andAUTONOMOUS_CONTAINER_DATABASE_INSPECT
UpdateAutonomousDatabase AUTONOMOUS_DATABASE_UPDATE
ChangeAutonomousDatabaseCompartment AUTONOMOUS_DATABASE_UPDATE andAUTONOMOUS_DB_BACKUP_INSPECT andAUTONOMOUS_DB_BACKUP_CONTENT_READandAUTONOMOUS_DATABASE_CONTENT_WRITEand AUTONOMOUS_DB_BACKUP_CREATE
DeleteAutonomousDatabase AUTONOMOUS_DATABASE_DELETE
StartAutonomousDatabase AUTONOMOUS_DATABASE_UPDATE
StopAutonomousDatabase AUTONOMOUS_DATABASE_UPDATE
RestoreAutonomousDatabase AUTONOMOUS_DB_BACKUP_CONTENT_READandAUTONOMOUS_DATABASE_CONTENT_WRITE
CreateAutonomousDatabaseBackup AUTONOMOUS_DB_BACKUP_CREATE andAUTONOMOUS_DATABASE_CONTENT_READ
DeleteAutonomousDatabaseBackup AUTONOMOUS_DB_BACKUP_DELETE
ListAutonomousDatabaseBackups AUTONOMOUS_DB_BACKUP_DELETE
GetAutonomousDatabaseBackup AUTONOMOUS_DB_BACKUP_DELETE
CreateDataGuardAssociation VM_CLUSTER_INSPECT andDATABASE_INSPECT and DATABASE_UPDATE
GetDataGuardAssociation DATABASE_INSPECT
ListDataGuardAssociations DATABASE_INSPECT
SwitchoverDataGuardAssociation DATABASE_UPDATE
FailoverDataGuardAssociation DATABASE_UPDATE
ReinstateDataGuardAssociation DATABASE_UPDATE
Chapter 19Permissions Required for Each API Operation
19-20
Table 19-61 (Cont.) Database API Operations
API Operation Permissions Required to Use theOperation
DeleteDatabase VM_CLUSTER_UPDATE and DB_HOME_UPDATEand DATABASE_DELETE
CreateKeyStore KEY_STORE_CREATE
GetKeyStore KEY_STORE_INSPECT
UpdateKeyStore KEY_STORE_UPDATE
DeleteKeyStore KEY_STORE_DELETE
ChangeKeyStoreCompartment KEY_STORE_INPSECT andKEY_STORE_UPDATE
CreateAutonomousContainerDatabase AUTONOMOUS_VM_CLUSTER_UPDATE andAUTONOMOUS_CONTAINER_DATABASE_CREATE
GetAutonomousContainerDatabase AUTONOMOUS_CONTAINER_DATABASE_INSPECT
RotateAutonomousContainerDatabaseKey AUTONOMOUS_CONTAINER_DATABASE_UPDATEandAUTONOMOUS_CONTAINER_DATABASE_INSPECT
GetAutonomousDatabase AUTONOMOUS_DATABASE_INSPECT
RotateAutonomousDatabaseKey AUTONOMOUS_DATABASE_UPDATE
GetAutonomousDatabaseBackup AUTONOMOUS_DB_BACKUP_INSPECT
CreateAutonomousContainerDatabase No changes for Primary.
AUTONOMOUS_VM_CLUSTER_INSPECT,AUTONOMOUS_VM_CLUSTER_UPDATE andAUTONOMOUS_CONTAINER_DATABASE_CREATE
Standby:AUTONOMOUS_CONTAINER_DATABASE_CREATE
GetAutonomousContainerDatabase AUTONOMOUS_CONTAINER_DATABASE_INSPECT
deleteAutonomouContainerDatabase AUTONOMOUS_VM_CLUSTER_UPDATE andAUTONOMOUS_CONTAINER_DATABASE_DELETE
ListAutonomousContainerDatabaseDataguardAssociations
AUTONOMOUS_CONTAINER_DATABASE_INSPECT
GetAutonomousContainerDatabaseDataguardAssociation
AUTONOMOUS_CONTAINER_DATABASE_INSPECT
FailoverAutonomousContainerDatabaseDataguardAssociation
AUTONOMOUS_CONTAINER_DATABASE_INSPECT andAUTONOMOUS_CONTAINER_DATABASE_UPDATE
SwitchoverAutonomousContainerDatabaseDataguardAssociation
AUTONOMOUS_CONTAINER_DATABASE_INSPECT andAUTONOMOUS_CONTAINER_DATABASE_UPDATE
ReinstateAutonomousContainerDatabaseDataguardAssociation
AUTONOMOUS_CONTAINER_DATABASE_INSPECT andAUTONOMOUS_CONTAINER_DATABASE_UPDATE
Chapter 19Permissions Required for Each API Operation
19-21
Table 19-61 (Cont.) Database API Operations
API Operation Permissions Required to Use theOperation
ListAutonomousDatabaseDataguardAssociations
AUTONOMOUS_CONTAINER_DATABASE_INSPECT
GetAutonomousDatabaseDataguardAssociation
AUTONOMOUS_CONTAINER_DATABASE_INSPECT
GetAutonomousDatabase AUTONOMOUS_DATABASE_INSPECT
Chapter 19Permissions Required for Each API Operation
19-22
20Oracle Exadata Cloud@Customer Events
The Oracle Database resources emit events, which are structured messages thatindicate changes in resources.
• Exadata Infrastructure Event TypesReview the list of event types that Exadata Infrastructure instances emit.
• VM Cluster Network Event TypesReview the list of event types that VM cluster networks emit.
• VM Cluster Event TypesReview the list of event types that VM clusters emit.
• Backup Destination Event TypesReview the list of event types that backup destinations emit.
• Database Node Event Types (Cloud@Customer)Review the list of event types that database nodes emit.
• Database Home Event Types (Cloud@Customer)Review the list of event types that Database Homes emit.
• Database Event Types (Cloud@Customer)Review the list of event types that databases emit.
• Database and Grid Infrastructure Patching Event TypesReview the list of event types that Database and Grid Infrastructure Patching emit.
• Autonomous VM Cluster Event TypesReview the list of event types that Autonomous VM clusters emit.
• Autonomous Container Database Event TypesReview the list of event types that Autonomous Container Database emit.
• Autonomous Database Event TypesReview the list of event types that Autonomous Database emit.
• Data Guard Event TypesReview the list of event types that Data Guard associations emit.
• Autonomous Database Autonomous Data Guard Event TypesReview the list of event types that Autnomous Data Guard associations emit.
• Key Store Event TypesReview the list of event types that Key Store emits.
• Exadata Cloud@Customer Infrastructure Patching Event TypesReview the list of event types that Exadata Cloud@Customer Infrastructurepatching emits.
Exadata Infrastructure Event TypesReview the list of event types that Exadata Infrastructure instances emit.
20-1
Table 20-1 Exadata Infrastructure Event Types
Friendly Name Event Type
Activate Begin com.oraclecloud.databaseservice.activateexadatainfrastructure.begin
Activate End com.oraclecloud.databaseservice.activateexadatainfrastructure.end
Change Compartment com.oraclecloud.databaseservice.changeexadatainfrastructurecompartment
Configuration File Download com.oraclecloud.databaseservice.downloadexadatainfrastructureconfigfile
Create Begin com.oraclecloud.databaseservice.createexadatainfrastructure.begin
Create End com.oraclecloud.databaseservice.createexadatainfrastructure.end
Delete Begin com.oraclecloud.databaseservice.deleteexadatainfrastructure.begin
Delete End com.oraclecloud.databaseservice.deleteexadatainfrastructure.end
Update Begin com.oraclecloud.databaseservice.updateexadatainfrastructure.begin
Update End com.oraclecloud.databaseservice.updateexadatainfrastructure.end
Exadata Infrastructure -Connectivity Status
com.oraclecloud.databaseservice.exadatainfrastructureconnectstatus
Example 20-1 Exadata Infrastructure Example
This is a reference event for Exadata Infrastructure instances:
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.createexadatainfrastructure.begin", "source": "databaseservice", "eventTypeVersion": "version", "eventTime": "2019-08-29T21:16:04Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_exadata_infra", "resourceId": "ExadataInfra-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {},
Chapter 20Exadata Infrastructure Event Types
20-2
"additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-29T12:00:00.000Z", "timeUpdated": "2019-08-29T12:30:00.000Z", "lifecycleDetails": "detail message", "shape": "ExadataCC.Base3.48", "timeZone": "US/Pacific", "displayName": "testDisplayName" } } }
This is a reference event for Exadata Infrastructure - Connectivity Status:
{ "eventType" : "com.oraclecloud.databaseservice.exadatainfrastructureconnectstatus", "cloudEventsVersion" : "0.1", "eventTypeVersion" : "2.0", "source" : "DatabaseService", "eventTime" : "2020-06-02T06:07:40.141Z", "contentType" : "application/json", "data" : { "compartmentId" : "ocid1.compartment.oc1..aaaaaaaayrygl4guhplo5rtiumx3eh4mk7grrkrqspzaltmvbxecnbvhkrga", "compartmentName" : "DBaaSInteg20160918ExaccTest", "resourceName" : "MVM_HR", "resourceId" : "ocid1.exadatainfrastructure.oc1.ap-hyderabad-1.abuhsljrp2vzzenmqmctqciwro6euhhsmlrewiiemiktov5xyfsu5hiufjsq", "availabilityDomain" : "", "additionalDetails" : { "timeCreated" : "2020-05-28T00:23:18Z", "timeUpdated" : "2020-06-02T06:07:40Z", "lifecycleState" : "DISCONNECTED", "lifecycleDetails" : "Exadata Infrastructure is not reachable. Please lodge a Service Request (SR) with Oracle Support and provide Infrastructure-id: ocid1.exadatainfrastructure.oc1.ap-hyderabad-1.abuhsljrp2vzzenmqmctqciwro6euhhsmlrewiiemiktov5xyfsu5hiufjsq.", "shape" : "ExadataCC.Half3.200", "timeZone" : "UTC" }, "definedTags" : { "Oracle-Tags" : { "CreatedBy" : "[email protected]", "CreatedOn" : "2020-05-28T00:23:18.291Z" } } }, "eventID" : "cde92d45-a06b-4b69-a125-6005dd8c2f0c", "extensions" : {
Chapter 20Exadata Infrastructure Event Types
20-3
"compartmentId" : "ocid1.compartment.oc1..aaaaaaaayrygl4guhplo5rtiumx3eh4mk7grrkrqspzaltmvbxecnbvhkrga" }}
VM Cluster Network Event TypesReview the list of event types that VM cluster networks emit.
Table 20-2 VM Cluster Network Event Types
Friendly Name Event Type
Create Begin com.oraclecloud.databaseservice.createvmclusternetwork.begin
Create End com.oraclecloud.databaseservice.createvmclusternetwork.end
Network Validation File Download com.oraclecloud.databaseservice.downloadvmclusternetworkconfigfile
Terminate Begin com.oraclecloud.databaseservice.deletevmclusternetwork.begin
Terminate End com.oraclecloud.databaseservice.deletevmclusternetwork.end
Update Begin com.oraclecloud.databaseservice.createvmclusternetwork.begin
Update End com.oraclecloud.databaseservice.createvmclusternetwork.end
Validate Begin com.oraclecloud.databaseservice.validatevmclusternetwork.begin
Validate End com.oraclecloud.databaseservice.validatevmclusternetwork.end
Example 20-2 VM Cluster Network Example
This is a reference event for VM cluster networks:
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.createvmclusternetwork.begin", "source": "databaseservice", "eventTypeVersion": "version", "eventTime": "2019-08-29T21:16:04Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID",
Chapter 20VM Cluster Network Event Types
20-4
"compartmentName": "example_name", "resourceName": "my_vmcluster_network", "resourceId": "VmClusterNetwork-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-29T12:00:00.000Z", "timeUpdated": "2019-08-29T12:30:00.000Z", "lifecycleDetails": "detail message", "exadataInfrastructureId": "ExadataInfra-unique_ID", "displayName": "testDisplayName" } } }
VM Cluster Event TypesReview the list of event types that VM clusters emit.
Table 20-3 VM Cluster Event Types
Friendly Name Event Type
Change Compartment com.oraclecloud.databaseservice.changevmclustercompartment
Create Begin com.oraclecloud.databaseservice.createvmcluster.begin
Create End com.oraclecloud.databaseservice.createvmcluster.end
Terminate Begin com.oraclecloud.databaseservice.deletevmcluster.begin
Terminate End com.oraclecloud.databaseservice.deletevmcluster.end
Update Begin com.oraclecloud.databaseservice.updatevmcluster.begin
Update End com.oraclecloud.databaseservice.updatevmcluster.end
Example 20-3 VM Cluster Example
This is a reference event for VM clusters:
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.createvmclusternetwork.begin", "source": "databaseservice", "eventTypeVersion": "version",
Chapter 20VM Cluster Event Types
20-5
"eventTime": "2019-08-29T21:16:04Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_vmcluster_network", "resourceId": "VmClusterNetwork-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-29T12:00:00.000Z", "timeUpdated": "2019-08-29T12:30:00.000Z", "lifecycleDetails": "detail message", "exadataInfrastructureId": "ExadataInfra-unique_ID", "displayName": "testDisplayName" } } }
This is a reference event for VM Cluster Create Begin:
{ "cloudEventsVersion": "0.1", "eventId": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.createvmcluster.begin", "source": "databaseservice", "eventTypeVersion": "1.0", "eventTime": "2019-06-27T21:16:04.000Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_database", "resourceId": "Vmcluster-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-09-03T12:00:00.000Z", "timeUpdated": "2019-09-03T12:30:00.000Z", "displayName": "testDisplayName", "lifecycleDetails": "detail message", "exadataInfrastructureId": "ExatraInfra-unique_ID",
Chapter 20VM Cluster Event Types
20-6
"vmClusterNetworkId": "VmCluster-unique_ID", "cpuCoreCount": 2, "dataStorageSizeInTBs": 4, "dbVersion": "19.0.0.0", "licenseType": "BRING_YOUR_OWN_LICENSE", "giVersion": "19.0.0.0", "dbNodeIds": "[ocid1.dbnode.1, ocid1.dbnode.2,...]", "timeZone": "US/Pacific" } }}
Backup Destination Event TypesReview the list of event types that backup destinations emit.
Table 20-4 Backup Destination Event Types
Friendly Name Event Type
Change Compartment com.oraclecloud.databaseservice.changebackupdestinationcompartment
Create com.oraclecloud.databaseservice.createbackupdestination
Terminate com.oraclecloud.databaseservice.deletebackupdestination
Update com.oraclecloud.databaseservice.updatebackupdestination
Example 20-4 Backup Destination Example
This is a reference event for backup destinations:
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.createbackupdestination", "source": "databaseservice", "eventTypeVersion": "version", "eventTime": "2019-08-29T21:16:04Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_backupdestination", "resourceId": "BackupDestination-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}
Chapter 20Backup Destination Event Types
20-7
} }
Database Node Event Types (Cloud@Customer)Review the list of event types that database nodes emit.
Table 20-5 Database Node Event Types
Friendly Name Event Type
Update Begin com.oraclecloud.databaseservice.dbnodeaction.begin
Update End com.oraclecloud.databaseservice.dbnodeaction.end
Example 20-5 Database Node Example
This is a reference event for database nodes:
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.dbnodeaction.begin", "source": "databaseservice", "eventTypeVersion": "version", "eventTime": "2019-06-27T21:16:04Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_dbnode", "resourceId": "DbNode-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-26T12:00:00.000Z", "timeUpdated": "2019-08-26T12:30:00.000Z", "dbSystemId": "ocid1.dbsystem.oc1.phx.unique_ID", "lifecycleDetails": "detail message", "vmClusterId": "VmCluster-unique_ID", "dbHostId": "dbHost-unique_ID", "nodeNumber": 2, "powerAction": "HardReset", "hostName": "testHostName" }
Chapter 20Database Node Event Types (Cloud@Customer)
20-8
}}
Database Home Event Types (Cloud@Customer)Review the list of event types that Database Homes emit.
Table 20-6 Database Home Event Types
Friendly Name Event Type
Create Begin com.oraclecloud.databaseservice.createdbhome.begin
Create End com.oraclecloud.databaseservice.createdbhome.end
Terminate Begin com.oraclecloud.databaseservice.deletedbhome.begin
Terminate End com.oraclecloud.databaseservice.deletedbhome.end
Update Begin com.oraclecloud.databaseservice.updatedbhome.begin
Update End com.oraclecloud.databaseservice.updatedbhome.end
Example 20-6 Database Home Example
This is a reference event for Database Homes:
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.createdbhome.begin", "source": "databaseservice", "eventTypeVersion": "version", "eventTime": "2019-08-29T21:16:04Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_dbhome", "resourceId": "DbHome-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-29T12:00:00.000Z", "timeUpdated": "2019-08-29T12:30:00.000Z",
Chapter 20Database Home Event Types (Cloud@Customer)
20-9
"lifecycleDetails": "detail message", "dbSystemId": "DbSystem-unique_ID", "dbVersion": "19.0.0.0", "recordVersion": 4, "displayName": "testDisplayName" } } }
Database Event Types (Cloud@Customer)Review the list of event types that databases emit.
Table 20-7 Database Event Types
Friendly Name Event Type
Create Begin com.oraclecloud.databaseservice.createdatabase.begin
Create End com.oraclecloud.databaseservice.createdatabase.end
Delete Backup Begin com.oraclecloud.databaseservice.deletebackup.begin
Delete Backup End com.oraclecloud.databaseservice.deletebackup.end
Restore Begin com.oraclecloud.databaseservice.restoredatabase.begin
Restore End com.oraclecloud.databaseservice.restoredatabase.end
Terminate Begin com.oraclecloud.databaseservice.deletedatabase.begin
Terminate End com.oraclecloud.databaseservice.deletedatabase.end
Update Begin com.oraclecloud.databaseservice.updatedatabase.begin
Update End com.oraclecloud.databaseservice.updatedatabase.end
Example 20-7 Database Example
This is a reference event for databases:
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.restoredatabase.begin", "source": "databaseservice", "eventTypeVersion": "version", "eventTime": "2019-06-27T21:16:04Z", "contentType": "application/json", "extensions": {
Chapter 20Database Event Types (Cloud@Customer)
20-10
"compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_database", "resourceId": "Database-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-26T12:00:00.000Z", "timeUpdated": "2019-08-26T12:30:00.000Z", "dbSystemId": "dbSystem-unique_ID", "displayName": "testDisplayName", "lifecycleDetails": "detail message", "vmClusterId": "VmCluster-unique_ID", "backupType": "FULL", "dbHomeId": "dbHome-unique_ID", "dbVersion": "19.0.0.0", "databaseEdition": "ENTERPRISE_EDITION_EXTREME", "autoBackupsEnabled": "true", "recoveryWindow": 30, "backupDestinationId": "backupDestination-unique_ID", "backupDestinationType": "OBJECT_STORAGE", "backupDestinationName": "my_backup_destination_name", "exadataInfrastructureId": "ExadataInfrastructure-unique_ID", "dbUniqueName": "akv_tgh_unqna" } }}
Database and Grid Infrastructure Patching Event TypesReview the list of event types that Database and Grid Infrastructure Patching emit.
Table 20-8 Database and Grid Infrastructure Patching Events
Friendly Name Event Type
VM Cluster - Patch Begin com.oraclecloud.databaseservice.patchvmcluster.begin
VM Cluster - Patch End com.oraclecloud.databaseservice.patchvmcluster.end
DB Home - Patch Begin com.oraclecloud.databaseservice.patchdbhome.begin
DB Home - Patch End com.oraclecloud.databaseservice.patchdbhome.end
Database - Move Begin com.oraclecloud.databaseservice.movedatabase.end
Chapter 20Database and Grid Infrastructure Patching Event Types
20-11
Table 20-8 (Cont.) Database and Grid Infrastructure Patching Events
Friendly Name Event Type
Database - Move End com.oraclecloud.databaseservice.movedatabase.end
Example 20-8 Database Example
This is a reference event for VM Cluster - Patch Begin:
{ "cloudEventsVersion": "0.1", "eventId": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.patchvmcluster.begin", "source": "databaseservice", "eventTypeVersion": "1.0", "eventTime": "2019-06-27T21:16:04.000Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_database", "resourceId": "Vmcluster-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-09-03T12:00:00.000Z", "timeUpdated": "2019-09-03T12:30:00.000Z", "displayName": "testDisplayName", "lifecycleDetails": "detail message", "exadataInfrastructureId": "ExatraInfra-unique_ID", "vmClusterNetworkId": "VmCluster-unique_ID", "cpuCoreCount": 2, "dataStorageSizeInTBs": 4, "dbVersion": "19.0.0.0", "licenseType": "BRING_YOUR_OWN_LICENSE", "giVersion": "19.0.0.0", "dbNodeIds": "[ocid1.dbnode.1, ocid1.dbnode.2,...]", "timeZone": "US/Pacific" } } }
Chapter 20Database and Grid Infrastructure Patching Event Types
20-12
This is a reference event for DB Home - Patch Begin:
{ "cloudEventsVersion": "0.1", "eventId": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.patchdbhome.begin", "source": "databaseservice", "eventTypeVersion": "1.0", "eventTime": "2019-08-29T21:16:04.000Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_dbhome", "resourceId": "DbHome-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-29T12:00:00.000Z", "timeUpdated": "2019-08-29T12:30:00.000Z", "lifecycleDetails": "detail message", "dbSystemId": "DbSystem-unique_ID", "dbVersion": "19.0.0.0", "recordVersion": 4, "displayName": "testDisplayName" } } }
This is a reference event for Database - Move Begin:
{ "cloudEventsVersion": "0.1", "eventId": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.movedatabase.begin", "source": "databaseservice", "eventTypeVersion": "1.0", "eventTime": "2019-06-27T21:16:04.000Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_database", "resourceId": "Database-unique_ID", "availabilityDomain": "all",
Chapter 20Database and Grid Infrastructure Patching Event Types
20-13
"freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-26T12:00:00.000Z", "timeUpdated": "2019-08-26T12:30:00.000Z", "dbSystemId": "ocid1.dbsystem.oc1.phx.unique_ID", "displayName": "testDisplayName", "lifecycleDetails": "detail message", "vmClusterId": "VmCluster-unique_ID", "dbSystemId": "dbSystem-unique_ID", "backupType": "FULL", "dbHomeId": "dbHome-unique_ID", "dbVersion": "19.0.0.0", "databaseEdition": "ENTERPRISE_EDITION_EXTREME", "autoBackupsEnabled": "true", "recoveryWindow": 30, "backupDestinationId": "backupDestination-unique_ID", "backupDestinationType": "OBJECT_STORAGE", "backupDestinationName": "my_backup_destination_name", "exadataInfrastructureId": "ExadataInfrastructure-unique-ID", "dbUniqueName": "akv_tgh_unqna" } } }
Autonomous VM Cluster Event TypesReview the list of event types that Autonomous VM clusters emit.
Table 20-9 Autonomous VM Cluster Events
Friendly Name Event Type
Autonomous VM Cluster - ChangeCompartment
com.oraclecloud.databaseservice.changeautonomousvmclustercompartment
Autonomous VM Cluster - Create Begin com.oraclecloud.databaseservice.createautonomousvmcluster.begin
Autonomous VM Cluster - Create End com.oraclecloud.databaseservice.createautonomousvmcluster.end
Autonomous VM Cluster - TerminateBegin
com.oraclecloud.databaseservice.deleteautonomousvmcluster.begin
Autonomous VM Cluster - TerminateEnd
com.oraclecloud.databaseservice.deleteautonomousvmcluster.end
Autonomous VM Cluster - Update Begin com.oraclecloud.databaseservice.updateautonomousvmcluster.begin
Autonomous VM Cluster - Update End com.oraclecloud.databaseservice.updateautonomousvmcluster.end
Chapter 20Autonomous VM Cluster Event Types
20-14
Example 20-9 Autonomous VM Cluster Examples
This is a reference event for Autonomous VM Cluster - Change Compartment:
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.changeautonomousvmclustercompartment", "source": "databaseservice", "eventTypeVersion": "1.0", "eventTime": "2019-06-27T21:16:04Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_database", "resourceId": "AutonomousVmCluster-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-09-03T12:00:00.000Z", "timeUpdated": "2019-09-03T12:30:00.000Z", "displayName": "testDisplayName", "lifecycleDetails": "detail message", "exadataInfrastructureId": "ExatraInfra-unique_ID", "vmClusterNetworkId": "VmClusterNetwork-unique_ID", "cpuCoreCount": "2", "availableCpus": "1", "dataStorageSizeInTBs": "4", "availableDataStorageSizeInTBs": "1", "licenseType": "BRING_YOUR_OWN_LICENSE", "timeZone": "US/Pacific" } } }
This is a reference event for Autonomous VM Cluster - Create Begin
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.createautonomousvmcluster.begin", "source": "databaseservice", "eventTypeVersion": "1.0", "eventTime": "2019-06-27T21:16:04Z", "contentType": "application/json", "extensions": {
Chapter 20Autonomous VM Cluster Event Types
20-15
"compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_database", "resourceId": "AutonomousVmCluster-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-09-03T12:00:00.000Z", "timeUpdated": "2019-09-03T12:30:00.000Z", "displayName": "testDisplayName", "lifecycleDetails": "detail message", "exadataInfrastructureId": "ExatraInfra-unique_ID", "vmClusterNetworkId": "VmClusterNetwork-unique_ID", "cpuCoreCount": "2", "availableCpus": "1", "dataStorageSizeInTBs": "4", "availableDataStorageSizeInTBs": "1", "licenseType": "BRING_YOUR_OWN_LICENSE", "timeZone": "US/Pacific" } } }
This is a reference event for Autonomous VM Cluster - Terminate Begin
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.deleteautonomousvmcluster.begin", "source": "databaseservice", "eventTypeVersion": "1.0", "eventTime": "2019-06-27T21:16:04Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_database", "resourceId": "AutonomousVmCluster-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE",
Chapter 20Autonomous VM Cluster Event Types
20-16
"timeCreated": "2019-09-03T12:00:00.000Z", "timeUpdated": "2019-09-03T12:30:00.000Z", "displayName": "testDisplayName", "lifecycleDetails": "detail message", "exadataInfrastructureId": "ExatraInfra-unique_ID", "vmClusterNetworkId": "VmClusterNetwork-unique_ID", "cpuCoreCount": "2", "availableCpus": "1", "dataStorageSizeInTBs": "4", "availableDataStorageSizeInTBs": "1", "licenseType": "BRING_YOUR_OWN_LICENSE", "timeZone": "US/Pacific" } } }
This is a reference event for Autonomous VM Cluster - Update Begin
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.updateautonomousvmcluster.begin", "source": "databaseservice", "eventTypeVersion": "1.0", "eventTime": "2019-06-27T21:16:04Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_database", "resourceId": "AutonomousVmCluster-unique_ID", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.id..oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-09-03T12:00:00.000Z", "timeUpdated": "2019-09-03T12:30:00.000Z", "displayName": "testDisplayName", "lifecycleDetails": "detail message", "exadataInfrastructureId": "ExatraInfra-unique_ID", "vmClusterNetworkId": "VmClusterNetwork-unique_ID", "cpuCoreCount": "2", "availableCpus": "1", "dataStorageSizeInTBs": "4", "availableDataStorageSizeInTBs": "1", "licenseType": "BRING_YOUR_OWN_LICENSE", "timeZone": "US/Pacific" }
Chapter 20Autonomous VM Cluster Event Types
20-17
} }
Autonomous Container Database Event TypesReview the list of event types that Autonomous Container Database emit.
Table 20-10 Autonomous Container Database Events
Friendly Name Event Type
Change Compartment com.oraclecloud.databaseservice.changeautonomouscontainerdatabasecompartment
Create Backup Begin com.oraclecloud.databaseservice.autonomous.container.database.backup.begin
Create Backup End com.oraclecloud.databaseservice.autonomous.container.database.backup.end
Create Begin com.oraclecloud.databaseservice.autonomous.container.database.instance.create.begin
Create End com.oraclecloud.databaseservice.autonomous.container.database.instance.create.end
Maintenance Begin com.oraclecloud.databaseservice.autonomous.container.database.maintenance.begin
Maintenance End com.oraclecloud.databaseservice.autonomous.container.database.maintenance.end
Maintenance Reminder com.oraclecloud.databaseservice.autonomous.container.database.maintenance.reminder
Maintenance Scheduled com.oraclecloud.databaseservice.autonomous.container.database.maintenance.scheduled
Restart Begin com.oraclecloud.databaseservice.restartautonomouscontainerdatabase.begin
Restart End com.oraclecloud.databaseservice.restartautonomouscontainerdatabase.end
Restore Begin com.oraclecloud.databaseservice.autonomous.container.database.restore.begin
Restore End com.oraclecloud.databaseservice.autonomous.container.database.restore.end
Terminate Begin com.oraclecloud.databaseservice.terminateautonomouscontainerdatabase.begin
Chapter 20Autonomous Container Database Event Types
20-18
Table 20-10 (Cont.) Autonomous Container Database Events
Friendly Name Event Type
Terminate End com.oraclecloud.databaseservice.terminateautonomouscontainerdatabase.end
Update Begin com.oraclecloud.databaseservice.autonomous.container.database.instance.update.begin
Update End com.oraclecloud.databaseservice.autonomous.container.database.instance.update.begin
Example 20-10 Autonomous Container Database Examples
This is a reference event for create Autonomous Container Database:
{lifecycleState=AVAILABLE, autonomousVmClusterId=ocid1.autonomousvmcluster.oc1.sea.abzwkljrevsjcfuskw7mgi6ulzfg2epjjxhbnhwj63q7q3kzvuwg3djqnd2a,displayName=CDB2-NFS, dbName=wqxtzzfn, dbUniqueName=wqxtzzfn_sea1td, freeTags={}, autonomousContainerDatabaseId=ocid1.autonomouscontainerdatabase.oc1.sea.abzwkljrxkuruqe3qzgw432adr5ug7ridmwi4ifvjlsahcdqdhbhzbf543xa, compartmentId=ocid1.compartment.region1..aaaaaaaass5x4witduxzgrs7qmzqk3m5kmoguve7urwploqef6763w3o42ta, timeUpdated=2020-06-15 21:52:24.085,tenantId=ocid1.tenancy.region1..aaaaaaaagyw5okosjg54csr3u5qgaxvtjufz55537h44mjy2umiqur4z5w3a, timeCreated=2020-06-15 19:08:03.797,id=ocid1.autonomouscontainerdatabase.oc1.sea.abzwkljrxkuruqe3qzgw432adr5ug7ridmwi4ifvjlsahcdqdhbhzbf543xa,definedTags={}}
Autonomous Database Event TypesReview the list of event types that Autonomous Database emit.
Table 20-11 Autonomous Database Events
Friendly Name Event Type
Change Compartment Begin com.oraclecloud.databaseservice.changeautonomousdatabasecompartment.begin
Change Compartment End com.oraclecloud.databaseservice.changeautonomousdatabasecompartment.end
Create Backup Begin com.oraclecloud.databaseservice.autonomous.database.backup.begin
Chapter 20Autonomous Database Event Types
20-19
Table 20-11 (Cont.) Autonomous Database Events
Friendly Name Event Type
Create Backup End com.oraclecloud.databaseservice.autonomous.database.backup.end
Create Begin com.oraclecloud.databaseservice.autonomous.database.instance.create.begin
Create End com.oraclecloud.databaseservice.autonomous.database.instance.create.end
Restore Begin com.oraclecloud.databaseservice.autonomous.database.restore.begin
Restore End com.oraclecloud.databaseservice.autonomous.database.restore.end
Start Begin com.oraclecloud.databaseservice.startautonomousdatabase.begin
Start End com.oraclecloud.databaseservice.startautonomousdatabase.end
Stop Begin com.oraclecloud.databaseservice.stopautonomousdatabase.begin
Stop End com.oraclecloud.databaseservice.stopautonomousdatabase.end
Terminate Begin com.oraclecloud.databaseservice.deleteautonomousdatabase.begin
Terminate End com.oraclecloud.databaseservice.deleteautonomousdatabase.end
Update Begin com.oraclecloud.databaseservice.updateautonomousdatabase.begin
Update End com.oraclecloud.databaseservice.updateautonomousdatabase.end
Data Guard Event TypesReview the list of event types that Data Guard associations emit.
Table 20-12 Data Guard Association Events
Friendly Name Event Type
Data Guard Association - CreateBegin
com.oraclecloud.databaseservice.createdataguardassociation.begin
Data Guard Association - Create End com.oraclecloud.databaseservice.createdataguardassociation.end
Switchover Begin com.oraclecloud.databaseservice.switchoverdataguardassociation.begin
Switchover End com.oraclecloud.databaseservice.switchoverdataguardassociation.end
Chapter 20Data Guard Event Types
20-20
Table 20-12 (Cont.) Data Guard Association Events
Friendly Name Event Type
Failover Begin com.oraclecloud.databaseservice.failoverdataguardassociation.begin
Failover End com.oraclecloud.databaseservice.failoverdataguardassociation.end
Reinstate Begin com.oraclecloud.databaseservice.reinstatedataguardassociation.begin
Reinstate End com.oraclecloud.databaseservice.reinstatedataguardassociation.end
Example 20-11 Data Guard Associations Examples
This is a reference event for Data Guard Association - Create Begin:
{ "eventId": "022a63a4-ff77-11e9-a0af-f45c89b1cb17", "eventTime": "2019-11-05T02:50:21.000Z", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_id" }, "eventType": "com.oraclecloud.databaseservice.createdataguardassociation.begin", "eventTypeVersion": "2.0", "cloudEventsVersion": "0.1", "source": "databaseservice", "contentType": "application/json", "definedTags": {}, "data": { "compartmentId": "ocid1.compartment.oc1..unique_id", "compartmentName": "example_name", "resourceName": "my_container_database", "resourceId": "ocid1.dataguard.oc1.phx.unique_id", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.dataguard.oc1.phx.unique_id", "timeCreated": "2019-06-27T21:15:59.000Z", "timeUpdated": "2019-06-27T21:16:04.389Z", "lifecycleState": "ACTIVE", "lifecycleMessage": "", "dbSystemId": "ocid1.vmcluster.oc1.phx.unique_id", "DatabaseId": "ocid1.database.oc1.phx.unique_id", "DbHomeId": "ocid1.dbhome.oc1.phx.unique_id", "DGConfigId": "022a67c8-ff77-11e9-af6e-f45c89b1cb17", "DGConfigState": "SUCCESS", "LastSyncedTime": "2019-06-27T21:16:04.389Z", "ApplyLag": "2 hours", "SyncState": "SYNCED", "dcsDgUpdateTimestamp": "2019-06-27T21:16:04.389Z",
Chapter 20Data Guard Event Types
20-21
"lastUpdatedIdentifier": "022a6912-ff77-11e9-9e77-f45c89b1cb17", "displayName": "Data Guard Association - Create Begin", "licenseType": "BRING_YOUR_OWN_LICENSE", "workloadType": "Transaction Processing" } } }
This is a reference event for Data Guard Association - Create End:
{ "eventId": "022aa7cc-ff77-11e9-90cd-f45c89b1cb17", "eventTime": "2019-11-05T02:50:21.000Z", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_id" }, "eventType": "com.oraclecloud.databaseservice.createdataguardassociation.end", "eventTypeVersion": "2.0", "cloudEventsVersion": "0.1", "source": "databaseservice", "contentType": "application/json", "definedTags": {}, "data": { "compartmentId": "ocid1.compartment.oc1..unique_id", "compartmentName": "example_name", "resourceName": "my_container_database", "resourceId": "ocid1.dataguard.oc1.phx.unique_id", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.dataguard.oc1.phx.unique_id", "timeCreated": "2019-06-27T21:15:59.000Z", "timeUpdated": "2019-06-27T21:16:04.389Z", "lifecycleState": "ACTIVE", "lifecycleMessage": "", "dbSystemId": "ocid1.vmcluster.oc1.phx.unique_id", "DatabaseId": "ocid1.database.oc1.phx.unique_id", "DbHomeId": "ocid1.dbhome.oc1.phx.unique_id", "DGConfigId": "022aab34-ff77-11e9-b89c-f45c89b1cb17", "DGConfigState": "SUCCESS", "LastSyncedTime": "2019-06-27T21:16:04.389Z", "ApplyLag": "2 hours", "SyncState": "SYNCED", "dcsDgUpdateTimestamp": "2019-06-27T21:16:04.389Z", "lastUpdatedIdentifier": "022aac10-ff77-11e9-8041-f45c89b1cb17", "displayName": "Data Guard Association - Create End", "licenseType": "BRING_YOUR_OWN_LICENSE", "workloadType": "Transaction Processing" } } }
Chapter 20Data Guard Event Types
20-22
Autonomous Database Autonomous Data Guard EventTypes
Review the list of event types that Autnomous Data Guard associations emit.
Table 20-13 Autonomous Data Guard Association Events
Friendly Name Event Type
Autonomous Container Database -Create Autonomous Data Guard Begin
com.oraclecloud.DatabaseService.CreateAutonomousDataGuardAssociation.begin
Autonomous Container Database -Create Autonomous Data Guard End
com.oraclecloud.DatabaseService.CreateAutonomousDataGuardAssociation.end
Autonomous Container Database -Switchover Begin
com.oraclecloud.DatabaseService.SwitchoverAutonomousDataguardAssociation.begin
Autonomous Container Database -Switchover End
com.oraclecloud.DatabaseService.SwitchoverAutonomousDataguardAssociation.end
Autonomous Container Database -Failover Begin
com.oraclecloud.DatabaseService.FailoverAutonomousDataguardAssociation.begin
Autonomous Container Database -Failover End
com.oraclecloud.DatabaseService.FailoverAutonomousDataguardAssociation.end
Autonomous Container Database -Reinstate Begin
com.oraclecloud.DatabaseService.ReinstateAutonomousDataGuardAssociation.begin
Autonomous Container Database -Reinstate End
com.oraclecloud.DatabaseService.ReinstateAutonomousDataGuardAssociation.end
Example 20-12 Autonomous Data Guard Associations Examples
This is a reference event for Autonomous Container Database - Create AutonomousData Guard Begin:
{ "cloudEventsVersion": "0.1", "eventID": "<unique_ID>", "eventType": "com.oraclecloud.DatabaseService.CreateAutonomousDataGuardAssociation.begin", "source": "databaseservice", "eventTypeVersion": "2.0", "eventTime": "2019-06-27T21:16:04Z", "contentType": "application/json", "data": { "eventGroupingId": "<unique_ID>",
Chapter 20Autonomous Database Autonomous Data Guard Event Types
20-23
"eventName"="CreateAutonomousDataGuardAssociation" "compartmentId": "ocid1.compartment.oc1..<unique_ID>", "compartmentName": "example_name", "resourceVersion":null, "resourceName": "my_container_database", "resourceId": "<unique_ID>", "availabilityDomain": "all", "tagSlug": "<slug_ID>", "definedTags": {}, "additionalDetails": { "lifecycleState": "PROVISIONING", "DGConfigId"="91f298da-b890-42ce-935b-9b841e908756", "ApplyLag"=null, "LastRoleChangeTime"=null, "TransportLag"=null, "autonomousContainerDatabaseId"="ocid1.autonomouscontainerdatabase.oc1.sea.<unique_ID>", "DGConfigState"=null, "lifeCycleMessage"=null, "lastUpdatedIdentifier"=null, "SyncState"=null, "autonomousExadataInfrastructureId"="ocid1.autonomousvmcluster.oc1.sea.<unique_ID>", "timeUpdated"="2020-10-18 23:02:34.864", "timeCreated"="2020-10-18 23:02:34.864", "dbHomeId"="ocid1.autonomouspodhome.oc1.sea.<unique_ID>", "LastSyncedTime"=null, "dcsDgUpdateTimestamp"=null, } }}
This is a reference event for Autonomous Container Database - Switchover Begin:
{ "cloudEventsVersion": "0.1", "eventID": "<unique_ID>", "eventType": "com.oraclecloud.DatabaseService.CreateAutonomousDataGuardAssociation.begin", "source": "databaseservice", "eventTypeVersion": "2.0", "eventTime": "2019-06-27T21:16:04Z", "contentType": "application/json", "data": { "eventGroupingId": "<unique_ID>", "eventName"="SwitchoverAutonomousDataguardAssociation" "compartmentId": "ocid1.compartment.oc1..<unique_ID>", "compartmentName": "example_name", "resourceVersion":null, "resourceName": "my_container_database", "resourceId": "ocid1.autonomousdgassociation.oc1.sea.<unique_ID>",
Chapter 20Autonomous Database Autonomous Data Guard Event Types
20-24
"availabilityDomain": "all", "tagSlug": "<slug_ID>", "definedTags": {}, "stateChange": { "previous"=null, "current: { "lifecycleState"="ROLE_CHANGE_IN_PROGRESS } } "additionalDetails": { "lifecycleState": "ROLE_CHANGE_IN_PROGRESS", "DGConfigId"="<unique_ID>", "ApplyLag"="0 seconds computed 2 seconds ago", "LastRoleChangeTime"=null, "TransportLag"="0 seconds computed 2 seconds ago", "autonomousContainerDatabaseId"="ocid1.autonomouscontainerdatabase.oc1.sea.<unique_ID>", "DGConfigState"="SUCCESS", "lifeCycleMessage"=null, "lastUpdatedIdentifier"=null, "SyncState"="SYNCED", "autonomousExadataInfrastructureId"="ocid1.autonomousvmcluster.oc1.sea.<unique_ID>", "timeUpdated"="2020-10-18 23:02:34.864", "timeCreated"="2020-10-18 23:02:34.864", "dbHomeId"="ocid1.autonomouspodhome.oc1.sea.<unique_ID>", "LastSyncedTime"=null, "dcsDgUpdateTimestamp"=null, } }}
This is a reference event for Autonomous Container Database - Failover Begin:
{ "cloudEventsVersion": "0.1", "eventID": "<unique_ID>", "eventType": "com.oraclecloud.DatabaseService.CreateAutonomousDataGuardAssociation.begin", "source": "databaseservice", "eventTypeVersion": "2.0", "eventTime": "2019-06-27T21:16:04Z", "contentType": "application/json", "data": { "eventGroupingId": "<unique_ID>", "eventName"="FailoverAutonomousDataguardAssociation" "compartmentId": "ocid1.compartment.oc1..<unique_ID>", "compartmentName": "example_name", "resourceVersion":null, "resourceName": "my_container_database", "resourceId": "ocid1.autonomousdgassociation.oc1.sea.<unique_ID>",
Chapter 20Autonomous Database Autonomous Data Guard Event Types
20-25
"availabilityDomain": "all", "tagSlug": "<slug_ID>", "definedTags": {}, "stateChange": { "previous"=null, "current: { "lifecycleState"="ROLE_CHANGE_IN_PROGRESS } } "additionalDetails": { "lifecycleState": "ROLE_CHANGE_IN_PROGRESS", "DGConfigId"="<unique_ID>", "ApplyLag"="0 seconds computed 2 seconds ago", "LastRoleChangeTime"=null, "TransportLag"="0 seconds computed 2 seconds ago", "autonomousContainerDatabaseId"="ocid1.autonomouscontainerdatabase.oc1.sea.<unique_ID>", "DGConfigState"="SUCCESS", "lifeCycleMessage"=null, "lastUpdatedIdentifier"=null, "SyncState"="SYNCED", "autonomousExadataInfrastructureId"="ocid1.autonomousvmcluster.oc1.sea.<unique_ID>", "timeUpdated"="2020-10-18 23:02:34.864", "timeCreated"="2020-10-18 23:02:34.864", "dbHomeId"="ocid1.autonomouspodhome.oc1.sea.<unique_ID>", "LastSyncedTime"=null, "dcsDgUpdateTimestamp"=null, } }}
This is a reference event for Autonomous Container Database - Reinstate Begin:
{ "cloudEventsVersion": "0.1", "eventID": "<unique_ID>", "eventType": "com.oraclecloud.DatabaseService.CreateAutonomousDataGuardAssociation.begin", "source": "databaseservice", "eventTypeVersion": "2.0", "eventTime": "2019-06-27T21:16:04Z", "contentType": "application/json", "data": { "eventGroupingId": "<unique_ID>", "eventName"="ReinstateAutonomousDataGuardAssociation" "compartmentId": "ocid1.compartment.oc1..<unique_ID>", "compartmentName": "example_name", "resourceVersion":null, "resourceName": "my_container_database", "resourceId": "ocid1.autonomousdgassociation.oc1.sea.<unique_ID>",
Chapter 20Autonomous Database Autonomous Data Guard Event Types
20-26
"availabilityDomain": "all", "tagSlug": "<slug_ID>", "definedTags": {}, "stateChange": { "previous"=null, "current: { "lifecycleState"="ROLE_CHANGE_IN_PROGRESS } } "additionalDetails": { "lifecycleState": "ROLE_CHANGE_IN_PROGRESS", "DGConfigId"="<unique_ID>", "ApplyLag"="0 seconds computed 2 seconds ago", "LastRoleChangeTime"=null, "TransportLag"="0 seconds computed 2 seconds ago", "autonomousContainerDatabaseId"="ocid1.autonomouscontainerdatabase.oc1.sea.<unique_ID>", "DGConfigState"="SUCCESS", "lifeCycleMessage"=null, "lastUpdatedIdentifier"=null, "SyncState"="SYNCED", "autonomousExadataInfrastructureId"="ocid1.autonomousvmcluster.oc1.sea.<unique_ID>", "timeUpdated"="2020-10-18 23:02:34.864", "timeCreated"="2020-10-18 23:02:34.864", "dbHomeId"="ocid1.autonomouspodhome.oc1.sea.<unique_ID>", "LastSyncedTime"=null, "dcsDgUpdateTimestamp"=null, } }}
Key Store Event TypesReview the list of event types that Key Store emits.
Table 20-14 Key Store Events
Friendly Name Event Type
Key Store - Create com.oraclecloud.databaseservice.createkeystore
Key Store - Update com.oraclecloud.databaseservice.updatekeystore
Key Store - Terminate com.oraclecloud.databaseservice.deletekeystore
Key Store - Change Compartment com.oraclecloud.databaseservice.changekeystorecompartment
Chapter 20Key Store Event Types
20-27
Table 20-14 (Cont.) Key Store Events
Friendly Name Event Type
Autonomous Container Database -Rotate Key Begin
com.oraclecloud.databaseservice.rotatekeyautonomouscontainerdatabase.begin
Autonomous Container Database -Rotate Key End
com.oraclecloud.databaseservice.rotatekeyautonomouscontainerdatabase.end
Autonomous Database - Rotate KeyBegin
com.oraclecloud.databaseservice.rotatekeyautonomousdatabase.begin
Autonomous Database - Rotate Key End com.oraclecloud.databaseservice.rotatekeyautonomousdatabase.end
Example 20-13 Key Store Example
This is a reference event for Create Key Store:
{ "cloudEventsVersion": "0.1", "eventID": "60600c06-d6a7-4e85-b56a-1de3e6042f57", "eventType": "com.oraclecloud.databaseservice.createkeystore", "source": "databaseservice", "eventTypeVersion": "version", "eventTime": "2020-10-27T21:16:04Z", "contentType": "application/json", "extensions": { "compartmentId": "ocid1.compartment.oc1..unique_ID" }, "data": { "compartmentId": "ocid1.compartment.oc1..unique_ID", "compartmentName": "example_name", "resourceName": "my_keystore", "resourceId": "KeyStore-unique_ID", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "timeUpdated"="2020-10-27 21:16:34.864", "timeCreated"="2020-10-27 21:16:34.864", "keyStoreType": "all", "connectionIps": "ip1,ip2", "adminUsername": "username", } } }
Exadata Cloud@Customer Infrastructure Patching EventTypes
Review the list of event types that Exadata Cloud@Customer Infrastructure patchingemits.
Chapter 20Exadata Cloud@Customer Infrastructure Patching Event Types
20-28
Table 20-15 Exadata Cloud@Customer Infrastructure Patching Events
Friendly Name Event Type Event Message
Exadata Infrastructure- Virtual MachinesMaintenance Begin
com.oraclecloud.databaseservice.exaccinfrastructuremaintenancevm.begin
This is an Oracle CloudOperations notice regardingthe quarterly maintenanceupdate of Virtual Machinescomponent of your ExaCCInfrastructure instance %s,ocid %s has started. A follow-up notice will be sent whenVirtual Machines maintenanceoperation has completed.
Exadata Infrastructure- Virtual MachinesMaintenance End
com.oraclecloud.databaseservice.exaccinfrastructuremaintenancevm.end
This is an OracleCloud Operations noticethat quarterly maintenanceupdate of Virtual Machinescomponent of your ExaCCInfrastructure instance %s,ocid %s has completed.
Exadata Infrastructure- Maintenance Scheduled
com.oraclecloud.databaseservice.exaccinfrastructuremaintenancescheduled
Oracle Cloud Operations isannouncing the availabilityof a new quarterlymaintenance update forExaCC Infrastructure. Oraclehas scheduled the installationof this new update on yourservice instance %s, ocid %son %s.
Exadata Infrastructure- Maintenance Reminder
com.oraclecloud.databaseservice.exaccinfrastructuremaintenancereminder
This is an Oracle CloudOperations reminder notice.Oracle has scheduleda quarterly maintenanceupdate installation for ExaCCInfrastructure instance %s,ocid %s in approximately %dweeks on %s.
Exadata Infrastructure- Maintenance Begin
com.oraclecloud.databaseservice.exaccinfrastructuremaintenance.begin
This is an Oracle CloudOperations notice regardingthe quarterly maintenanceupdate installation for yourExaCC Infrastructure instance%s, ocid %s. The updateinstallation for the servicestarted at %s. A follow-upnotice will be sent when themaintenance update operationhas completed.
Chapter 20Exadata Cloud@Customer Infrastructure Patching Event Types
20-29
Table 20-15 (Cont.) Exadata Cloud@Customer Infrastructure Patching Events
Friendly Name Event Type Event Message
Exadata Infrastructure- Maintenance End
com.oraclecloud.databaseservice.exaccinfrastructuremaintenance.end
Success: This is an OracleCloud Operations notice thatyour ExaCC Infrastructurequarterly maintenance updateinstallation for service instance%s, ocid %s which startedat %s is now successfullycomplete.
Failure: This is an OracleCloud Operations notice thatyour ExaCC Infrastructurequarterly maintenance updateinstallation for service instance%s, ocid %s which startedat %s has failed to completedue to technical reasons andwill be rescheduled for a laterdate. You will receive regularnotifications to track progressof this maintenance.
Example 20-14 Exadata Cloud@Customer Infrastructure Maintenance EventsExamples
This is a reference event for Exadata Infrastructure - Virtual Machines MaintenanceBegin:
"exampleEvent": { "cloudEventsVersion": "0.1", "eventID": "b28fcda6-3d7b-4044-aa8e-7c21cde84b44", "eventType": "com.oraclecloud.databaseservice.exaccinfrastructuremaintenancevm.begin", "source": "databaseservice", "eventTypeVersion": "2.0", "eventTime": "2019-06-27T21:16:04.000Z", "contentType": "application/json", "data": { "eventGroupingId": "4976b940-2c2d-4380-a669-1d70d071b187", "eventName": "ExaccInfrastructureMaintenanceVM", "compartmentId": "ocid1.compartment.oc1.......unique_id", "compartmentName": "example_compartment", "resourceName": "my_exacc_infrastructure", "resourceId": "ocid1.exadatainfrastructure.oc1.....unique_id", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.dbmaintenancerun.oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-29T12:00:00.000Z", "timeScheduled": "2019-08-29T12:30:00.000Z",
Chapter 20Exadata Cloud@Customer Infrastructure Patching Event Types
20-30
"timeStarted": "2019-08-29T12:30:00.000Z", "description": "ExaCC Infrastructure Maintenance Notifications", "message": "detailed message", "shape": "ExadataCC.Base3.48", "displayName": "testDisplayName" } }}
This is a reference event for Exadata Infrastructure - Virtual Machines MaintenanceEnd:
"exampleEvent": { "cloudEventsVersion": "0.1", "eventID": "b28fcda6-3d7b-4044-aa8e-7c21cde84b44", "eventType": "com.oraclecloud.databaseservice.exaccinfrastructuremaintenancevm.end", "source": "databaseservice", "eventTypeVersion": "2.0", "eventTime": "2019-06-27T21:16:04.000Z", "contentType": "application/json", "data": { "eventGroupingId": "4976b940-2c2d-4380-a669-1d70d071b187", "eventName": "ExaccInfrastructureMaintenanceVM", "compartmentId": "ocid1.compartment.oc1.......unique_id", "compartmentName": "example_compartment", "resourceName": "my_exacc_infrastructure", "resourceId": "ocid1.exadatainfrastructure.oc1.....unique_id", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.dbmaintenancerun.oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-29T12:00:00.000Z", "timeScheduled": "2019-08-29T12:30:00.000Z", "timeEnded": "2019-08-29T12:30:00.000Z", "description": "ExaCC Infrastructure Maintenance Notifications", "message": "detailed message", "shape": "ExadataCC.Base3.48", "displayName": "testDisplayName" } }}
This is a reference event for Exadata Infrastructure - Maintenance Scheduled:
"exampleEvent": { "cloudEventsVersion": "0.1", "eventID": "b28fcda6-3d7b-4044-aa8e-7c21cde84b44", "eventType": "com.oraclecloud.databaseservice.exaccinfrastructuremaintenancescheduled
Chapter 20Exadata Cloud@Customer Infrastructure Patching Event Types
20-31
", "source": "databaseservice", "eventTypeVersion": "2.0", "eventTime": "2019-06-27T21:16:04.000Z", "contentType": "application/json", "data": { "eventGroupingId": "4976b940-2c2d-4380-a669-1d70d071b187", "eventName": "ExaccInfrastructureMaintenanceScheduled", "compartmentId": "ocid1.compartment.oc1.......unique_id", "compartmentName": "example_compartment", "resourceName": "my_exacc_infrastructure", "resourceId": "ocid1.exadatainfrastructure.oc1.....unique_id", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.dbmaintenancerun.oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-29T12:00:00.000Z", "timeScheduled": "2019-08-29T12:30:00.000Z", "description": "ExaCC Infrastructure Maintenance Notifications", "message": "detailed message", "shape": "ExadataCC.Base3.48", "displayName": "testDisplayName" } }}
This is a reference event for Exadata Infrastructure - Maintenance Reminder:
"exampleEvent": { "cloudEventsVersion": "0.1", "eventID": "b28fcda6-3d7b-4044-aa8e-7c21cde84b44", "eventType": "com.oraclecloud.databaseservice.exaccinfrastructuremaintenancereminder", "source": "databaseservice", "eventTypeVersion": "2.0", "eventTime": "2019-06-27T21:16:04.000Z", "contentType": "application/json", "data": { "eventGroupingId": "4976b940-2c2d-4380-a669-1d70d071b187", "eventName": "ExaccInfrastructureMaintenanceReminder", "compartmentId": "ocid1.compartment.oc1.......unique_id", "compartmentName": "example_compartment", "resourceName": "my_exacc_infrastructure", "resourceId": "ocid1.exadatainfrastructure.oc1.....unique_id", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.dbmaintenancerun.oc1...unique_ID", "lifecycleState": "AVAILABLE",
Chapter 20Exadata Cloud@Customer Infrastructure Patching Event Types
20-32
"timeCreated": "2019-08-29T12:00:00.000Z", "timeScheduled": "2019-08-29T12:30:00.000Z", "description": "ExaCC Infrastructure Maintenance Notifications", "message": "detailed message", "shape": "ExadataCC.Base3.48", "displayName": "testDisplayName" } }}
This is a reference event for Exadata Infrastructure - Maintenance Begin:
"exampleEvent": { "cloudEventsVersion": "0.1", "eventID": "b28fcda6-3d7b-4044-aa8e-7c21cde84b44", "eventType": "com.oraclecloud.databaseservice.exaccinfrastructuremaintenance.begin", "source": "databaseservice", "eventTypeVersion": "2.0", "eventTime": "2019-06-27T21:16:04.000Z", "contentType": "application/json", "data": { "eventGroupingId": "4976b940-2c2d-4380-a669-1d70d071b187", "eventName": "ExaccInfrastructureMaintenance", "compartmentId": "ocid1.compartment.oc1.......unique_id", "compartmentName": "example_compartment", "resourceName": "my_exacc_infrastructure", "resourceId": "ocid1.exadatainfrastructure.oc1.....unique_id", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.dbmaintenancerun.oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-29T12:00:00.000Z", "timeScheduled": "2019-08-29T12:30:00.000Z", "timeStarted": "2019-08-29T12:30:00.000Z", "description": "ExaCC Infrastructure Maintenance Notifications", "message": "detailed message", "shape": "ExadataCC.Base3.48", "displayName": "testDisplayName" } }}
This is a reference event for Exadata Infrastructure - Maintenance End:
"exampleEvent": { "cloudEventsVersion": "0.1", "eventID": "b28fcda6-3d7b-4044-aa8e-7c21cde84b44", "eventType": "com.oraclecloud.databaseservice.exaccinfrastructuremaintenance.end",
Chapter 20Exadata Cloud@Customer Infrastructure Patching Event Types
20-33
"source": "databaseservice", "eventTypeVersion": "2.0", "eventTime": "2019-06-27T21:16:04.000Z", "contentType": "application/json", "data": { "eventGroupingId": "4976b940-2c2d-4380-a669-1d70d071b187", "eventName": "ExaccInfrastructureMaintenance", "compartmentId": "ocid1.compartment.oc1.......unique_id", "compartmentName": "example_compartment", "resourceName": "my_exacc_infrastructure", "resourceId": "ocid1.exadatainfrastructure.oc1.....unique_id", "availabilityDomain": "all", "freeFormTags": {}, "definedTags": {}, "additionalDetails": { "id": "ocid1.dbmaintenancerun.oc1...unique_ID", "lifecycleState": "AVAILABLE", "timeCreated": "2019-08-29T12:00:00.000Z", "timeScheduled": "2019-08-29T12:30:00.000Z", "timeEnded": "2019-08-29T12:30:00.000Z", "description": "ExaCC Infrastructure Maintenance Notifications", "message": "detailed message", "shape": "ExadataCC.Base3.48", "displayName": "testDisplayName" } }}
Chapter 20Exadata Cloud@Customer Infrastructure Patching Event Types
20-34
21Troubleshooting ExadataCloud@Customer Systems
These topics cover some common issues you might run into and how to address them.
• Patching Failures on Exadata Cloud@Customer SystemsYou can patch Oracle Database and Oracle Grid Infrastructure using the dbaascliutility and update the Cloud Tooling on Exadata Cloud@Customer.
• Determining the ProblemIn the Console, you can identify a failed patching operation by viewing the patchhistory of an Exadata Cloud@Customer system or an individual database.
• Troubleshooting and DiagnosisDiagnose the most common issues that can occur during the patching process ofany of the Exadata Cloud@Customer components.
• Obtaining Further AssistanceIf you were unable to resolve the problem using the information in this topic, followthe procedures below to collect relevant database and diagnostic information.After you have collected this information, contact Oracle Support.
• Failed Patch Modifies the Home Name in oraInventory with the Suffix "_PIP"
• Database is Down While Performing Downgrade to Release 11.2 or 12.1
• After Database Upgrade, the Standby Database Remains in Mounted State inOracle Data Guard Configurations
• Primary Database Fails to Downgrade to 18c in Oracle Data Guard Configurations
• Patching Primary and Standby Databases Configured with Oracle Data GuardFails
Patching Failures on Exadata Cloud@Customer SystemsYou can patch Oracle Database and Oracle Grid Infrastructure using the dbaascliutility and update the Cloud Tooling on Exadata Cloud@Customer.
Patching operations can fail for various reasons. Typically, an operation fails becausea database node is down, there is insufficient space on the file system, or thedatabase host cannot access the object store.
Determining the ProblemIn the Console, you can identify a failed patching operation by viewing the patchhistory of an Exadata Cloud@Customer system or an individual database.
A patch that was not successfully applied displays a status of Failed and includesa brief description of the error that caused the failure. If the error message does notcontain enough information to point you to a solution, you can use the database CLI
21-1
and log files to gather more data. Then, refer to the applicable section in this topic for asolution.
Troubleshooting and DiagnosisDiagnose the most common issues that can occur during the patching process of anyof the Exadata Cloud@Customer components.
• Host IssuesOne or more of the following conditions on the database host can cause patchingoperations to fail.
• Oracle Grid Infrastructure IssuesOne or more of the following conditions on Oracle Grid Infrastructure can causepatching operations to fail.
• Oracle Databases IssuesAn improper database state can lead to patching failures.
• Oracle Cloud Tooling Issues
Host IssuesOne or more of the following conditions on the database host can cause patchingoperations to fail.
File System is Full
Patching operations require a minimum of 25 GB for Oracle Grid Infrastructurepatching or 15 GB for Oracle Database patching. If the required Oracle home locationsdo not not meet the storage requirements, then an error message like the followingcan be observed during the patching pre-check operation:
[FATAL] [DBAAS-31009] - One or more Oracle patching pre-checks resulted in error conditions that needs to be addressed before proceeding: not enough space for s/w backups ACTION: Verify the logs at /var/opt/oracle/log/exadbcpatch.
Use the df -h command on the host to check the available space. If the file systemhas insufficient space, you can remove old log or trace files to free up space.
Nodes Connectivity Problems
Cloud tooling relies on the proper networking and connectivity configuration betweennodes of a given cluster. If the configuration is not set properly, this may incur infailures on all the operations that require cross-node processing. One example can benot being able to download the required files to apply a given patch. In such case anderror like the following one would be observed upon a given patch precheck or applyrequest:
[FATAL] [DBAAS-31009] - One or more Oracle patching pre-checks resulted in error conditions that needs to be addressed before proceeding: % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed0 0 0 0 0 0 0 0 --:--:--
Chapter 21Troubleshooting and Diagnosis
21-2
--:--:-- --:--:-- 0 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0curl: (7) Failed connect to [host address]
Given the case, you can perform the following actions:
• Verify that the node or the URL is reachable by using the following commands:
ping hostname
curl target url
• Verify that your DNS configuration is correct so that the relevant nodes addressesare resolvable within the VM cluster.
• Refer to the relevant Cloud Tooling logs as instructed in the Obtaining FurtherAssistance section and contact Oracle Support for further assistance.
Oracle Grid Infrastructure IssuesOne or more of the following conditions on Oracle Grid Infrastructure can causepatching operations to fail.
Oracle Grid Infrastructure is Down
Oracle Clusterware enables servers to communicate with each other so that they canfunction as a collective unit. The cluster software program must be up and running onthe VM Cluster for patching operations to complete. Occasionally you might need torestart the Oracle Clusterware to resolve a patching failure.
In such cases, verify the status of the Oracle Grid Infrastructure as follows:
[grid@host:$GRID_HOME/bin]$ ./crsctl check clusterCRS-4537: Cluster Ready Services is onlineCRS-4529: Cluster Synchronization Services is onlineCRS-4533: Event Manager is online
If Oracle Grid Infrastructure is down, then restart by running the following commands:
crsctl start cluster -all
crsctl check cluster
Oracle Grid Infrastructure Upgrade Pre-check Failures
During the pre-check operation, many failures can be reported as the requesteddatabases to be patched, fails in meeting the minimum requirements to perform thepatching operation. An example of the required command is shown as it follows:
[root@host:~][0]# dbaascli patch db prereq --patchid <patch id> --dbnames GRIDDBAAS CLI version 19.4.4.2.0Executing command patch db prereq --patchid LATEST --dbnames grid
Chapter 21Troubleshooting and Diagnosis
21-3
INFO: DBCS patching...
Patch ID not being recognized
If Cloud tooling fails to identify the specified patch ID to verify, then an error like thefollowing one will be observed:
[FATAL] [DBAAS-10002] - The provided value for the parameter patchnum is invalid: Incorrect patchnum.ACTION: Verify the corresponding application usage and/or logs at /var/opt/oracle/log/exadbcpatchmulti and try again.
To verify that the specified patch ID is correct, confirm that the specified patch ID islisted as an available patch on the Console.
If the specified patch ID is listed and if the prerequisite operation still fails torecognize the patch ID, then refer to the relevant Cloud Tooling logs as instructedin the Obtaining Further Assistance section and contact Oracle Support for furtherassistance.
Specific Pre-check Validation Failed
Once that the pre-check validation starts, Cloud tooling will perform a series ofvalidations to determine whether or not the minimum requirements to perform therequested patching operation are met. If any of this minimum requirements are notmet, then a failure of the following will be observed:
[FATAL] [DBAAS-31009] - One or more Oracle patching pre-checks resulted in error conditions that needs to be addressed before proceeding: <Specific Pre-check Validation Failure>
Depending on the specific failed prerequisite validation, the corresponding correctionscan be performed on the environment or the Oracle home if required. Once that thosecorrections have been performed, then the operation can be reattempted.
If the failure persist, then refer to the relevant Cloud Tooling logs as instructedin the Obtaining Further Assistance section and contact Oracle Support for furtherassistance.
Oracle Grid Infrastructure Patch Apply Failures
During the actual installation of the requested patch for the corresponding OracleGrid Infrastructure, the procedure may fall into error or unexpected conditions as thefollowing example:
[root@host:~][0]# dbaascli patch db apply --patchid <patch id> --dbnames GRID...ERROR: Grid upgrade failed. Please check corresponding log in /var/opt/oracle/log/exadbcpatch
If a failure is detected on a given node during the patch installation process, then dothe following:
Chapter 21Troubleshooting and Diagnosis
21-4
• Address the issue that originated the failure if its evident and then re-try the samecommand so that the operation can be resumed from the failure point.
• If after retrying the command the issue persists or if its not possible to identify theroot cause of the failure, then refer to the relevant Cloud Tooling logs as instructedin the Obtaining Further Assistance section and contact Oracle Support for furtherassistance.
Oracle Databases IssuesAn improper database state can lead to patching failures.
Oracle Database is Down
The database must be active and running on all the active nodes so the patchingoperations can be completed successfully across the cluster.
Use the following command to check the state of your database, and ensure that anyproblems that might have put the database in an improper state are resolved:
srvctl status database -d db_unique_name -verbose
The system returns a message including the database instance status. The instancestatus must be Open for the patching operation to succeed.
If the database is not running, use the following command to start it:
srvctl start database -d db_unique_name -o open
Oracle Database Patching Pre-check Failures
During the pre-check operation, many failures can be reported as the requesteddatabases to be patched, fails in meeting the minimum requirements to perform thepatching operation. An example of the required command is shown as it follows:
[root@host:~][0]# dbaascli patch db prereq --patchid <patch id> --dbnames <database 1,...,database n>DBAAS CLI version 19.4.4.2.0Executing command patch db prereq --patchid LATEST --dbnames gridINFO: DBCS patching...
Patch ID not being recognized
If Cloud tooling fails to identify the specified patch ID to verify, then an error like thefollowing one will be observed:
[FATAL] [DBAAS-10002] - The provided value for the parameter patchnum is invalid: Incorrect patchnum.ACTION: Verify the corresponding application usage and/or logs at /var/opt/oracle/log/exadbcpatchmulti and try again.
To verify that the specified patch ID is correct, confirm that the specified patch ID islisted as an available patch on the Console.
Chapter 21Troubleshooting and Diagnosis
21-5
Alternatively, you can verify the installed patch level into a given home by using thefollowing command as well:
dbaascli dbhome info
If the specified patch ID is listed and if the prerequisite operation still fails torecognize the patch ID, then refer to the relevant Cloud Tooling logs as instructedin the Obtaining Further Assistance section and contact Oracle Support for furtherassistance.
Specific Prereq Validation Failed
Once that the prerequisite validation starts, Cloud tooling will perform a series ofvalidations to determine whether or not the minimum requirements to perform therequested patching operation are met. If any of this minimum requirements are notmet, then a failure of the following will be observed:
[FATAL] [DBAAS-31009] - One or more Oracle patching pre-checks resulted in error conditions that needs to be addressed before proceeding: <Specific Prereq Validation Failure>
Depending on the specific failed prereq validation, the corresponding corrections canbe performed on the environment or the Oracle home if required. Once that thosecorrections have been performed, then the operation can be re-attempted.
If the failure persist, then refer to the relevant Cloud Tooling logs as instructedin the Obtaining Further Assistance section and contact Oracle Support for furtherassistance.
Oracle Database Patch Apply Failures
During the actual installation of the requested patch for the corresponding OracleGrid Infrastructure, the procedure may fall into error or unexpected conditions as thefollowing example:
[root@host:~][0]# dbaascli patch db apply --patchid <patch id> --dbnames <database 1,...,database n>...ERROR: Error during creation, empty dbhome patching failed. Check the corresponding logs
If its not possible to identify the root cause of the failure and its corresponding solution,then refer to the relevant Cloud Tooling logs as instructed in the Obtaining FurtherAssistance section and contact Oracle Support for further assistance.
Chapter 21Troubleshooting and Diagnosis
21-6
Oracle Cloud Tooling Issues
Not Applicable Cloud Tooling Patches Available
One issue that may happen if the Cloud patch installation is tried right away is that theoperation fails because there are no applicable RPMs to install. An example of suchcondition is shown as it follows:
[root@host:~]# dbaascli patch tools apply --patchid LATESTDBAAS CLI version 19.4.4.2.0Executing command patch tools apply --patchid LATEST...[FATAL] [DBAAS-33032] - An error occurred while performing the installation of the Oracle DBAAS tools: No applicable dbaastools rpms found.ACTION: Verify the logs at /var/opt/oracle/log/exadbcpatch.
To confirm that indeed there are no applicable patches to be installed for Cloud toolingyou can run the following command:
dbaascli patch tools list
If the patch level for the Cloud tooling is eligible for patch application and Cloud toolingis not able to disclose any applicable patch ID, then refer to the relevant Cloud Toolinglogs as instructed in the Obtaining Further Assistance section and contact OracleSupport for further assistance.
Obtaining Further AssistanceIf you were unable to resolve the problem using the information in this topic, follow theprocedures below to collect relevant database and diagnostic information. After youhave collected this information, contact Oracle Support.
• Collecting Cloud Tooling LogsUse the relevant log files that could assist Oracle Support for further investigationand resolution of a given issue.
• Collecting Configuration Tools Logs
• Collecting Oracle Diagnostics
Related Topics
• Oracle Support
Collecting Cloud Tooling LogsUse the relevant log files that could assist Oracle Support for further investigation andresolution of a given issue.
DBAASAPI Logs
These logs are applicable for actions that are performed from the Console.
Chapter 21Obtaining Further Assistance
21-7
/var/opt/oracle/log/dbaasapi/db/db
• Job HASH.log corresponding to the Backend API request
Note:
All the log files are timestamped records so that the issues can be tracedback to some point in the past during the DBSystem operation.
DBAASCLI Logs
/var/opt/oracle/log/dbaascli
• dbaascli.log
DBAAS ExaPatch Logs
/var/opt/oracle/log/exadbcpatchmulti:
• exadbcpatchmulti.log
• exadbcpatchmulti-cmd.log
/var/opt/oracle/log/exadbcpatchsm:
• exadbcpatchsm.log
/var/opt/oracle/log/exadbcpatch:
• exadbcpatch.log
• exadbcpatch-cmd.log
• exadbcpatch-dmp.log
• exadbcpatch-sql.log
Note:
All the log files are timestamped records so that the issues can be tracedback to some point in the past during the DBSystem operation.
Collecting Configuration Tools Logs
$GRID_BASE/cfgtoollogs$ORACLE_BASE/cfgtoollogs
Collecting Oracle Diagnostics
To collect the relevant Oracle diagnostic information and logs, run thedbaas_diag_tool.pl script.
/var/opt/oracle/misc/dbaas_diag_tool.pl
Chapter 21Obtaining Further Assistance
21-8
For more information about the usage of this utility, see My Oracle Support note2219712.1.
Related Topics
• https://support.oracle.com/rs?type=doc&id=2219712.1
Failed Patch Modifies the Home Name in oraInventory withthe Suffix "_PIP"
Description: The image-based patching process temporarily changes the name of theHome that is being patched in the oraInventory adding the suffix '_pip' for patching inprogress. For example, changing OraDB19Home1 to OraDB19Home1_pip.
When a patch fails on node 2, the name is not reverted to the original name.This causes subsequent Home installed on node 2 to use the Home nameOraDB19Home1.
Action: On the failing node run the following command to clear the inventory from thecorresponding _pip entrance:
/var/opt/oracle/exapatch/exadbcpatchmulti -rollback_async patch id -instance1=hostname:ORACLE_HOME path -dbname=dbname1 -run_datasql=1
After performing the local rollback, resume applying the corresponding patching.
Database is Down While Performing Downgrade to Release11.2 or 12.1
Description: Error is thrown as follows while running the database upgrade commandwith the –revert flag.
[FATAL] [DBAAS-54007] - An error occurred whenopen the a121db database with resetlog options: ORA-01034: ORACLE notavailable.
Action: Apply one-off patching for bug 31561819 prior to attempting the downgrade ifrequired for Oracle Database releases 11.2 and 12.1.
If the issue persists and impacts a given database, then, per a similar bug 31762303filed by MAA team, Oracle recommends that you run the following commands after thefailure to complete database downgrade:
/u02/app/oracle/product/19.0.0.0/dbhome_3/bin/srvctl downgrade database -d<DB_UNIQUE_NAME> -o /u02/app/oracle/product/11.2.0/dbhome_2 -t 11.2.0.4
/u02/app/oracle/product/11.2.0/dbhome_2/bin/srvctl setenv database -d <DB_UNIQUE_NAME> -T
Chapter 21Failed Patch Modifies the Home Name in oraInventory with the Suffix "_PIP"
21-9
"TNS_ADMIN=/u02/app/oracle/product/11.2.0/dbhome_2/network/admin/<DB_NAME>"
After Database Upgrade, the Standby Database Remains inMounted State in Oracle Data Guard Configurations
Description: After performing the upgrade as recommended in Oracle MOS note2628228.1, the standby database is left opened in MOUNT state.
Action: If it is required to bring the standby database back to read-only mode, thenproceed with the following steps:
Run the following query on the primary database:
SELECT DEST_ID,THREAD#,sequence#,RESETLOGS_CHANGE#,STANDBY_DEST,ARCHIVED,APPLIED,status,to_char(completion_time,'DD-MM-YYYY:hh24:mi') from v$archived_log;
Ensure that all the logs have been replicated successfully to the standby databaseafter the upgrade operation.
Then on the standby database, run the following commands:
# dbaascli database stop --dbname standby dbname# dbaascli database start --dbname standby dbname
Then the database should be open in read-only mode again.
Primary Database Fails to Downgrade to 18c in Oracle DataGuard Configurations
Description: The following failure is observed while downgrading a primary DataGuard database from 19c to 18c:
[FATAL] [DBAAS-54007]- An error occurred when open the db163 database with resetlog options:ORA-16649: possible failover to another database prevents this database frombeing opened.
Action: Follow these steps to fix the issue:
1. Open the initdbname.ora file:
/var/opt/oracle/dbaas_acfs/upgrade_backup/dbname/initdbname.ora
2. Set the *.dg_broker_start parameters to false and save the changes:
*.dg_broker_start=FALSE
Chapter 21After Database Upgrade, the Standby Database Remains in Mounted State in Oracle Data Guard Configurations
21-10
3. Bring down the local instance and open it back in mount mode:
startup mount pfile=’/var/opt/oracle/dbaas_acfs/upgrade_backup/dbname/initdbname.ora’;
4. Then open it with the following command:
alter database open resetlogs;
5. Re-enable the Data Guard broker.
alter system set dg_broker_start=true scope=BOTH;
6. Restore the spfile.
create spfile=’DATA DISKGROUP/db_unique_name/spfiledbname.ora’ from pfile=’ /var/opt/oracle/dbaas_acfs/upgrade_backup/dbname/initdbname.ora’
7. Shut down the local instance.
shutdown immediate;
8. Manually downgrade the service.
19c Oracle home/bin/srvctl downgrade database –d db_unique_name -oraclehome 18c Oracle home path -targetversion 18.0.0.0.0
9. Restore the TNS_ADMIN variable.
19c Oracle home/bin/srvctl setenv database –d db_unique_name -t oraclehome “18c Oracle home/network/admin/dbname”
10. Bounce the database across the cluster.
18c Oracle home/bin/srvctl stop database –d db_unique_name18c Oracle home/bin/srvctl start database –d db_unique_name
Patching Primary and Standby Databases Configured withOracle Data Guard Fails
Description: In OCI environments, patching primary or secondary nodes using theexadbcpatchmulti tool fails if there's no SSH connectivity between the primary andstandby nodes.
Action: Depending on the node you're patching, add the -primary or -secondaryflag. You can add flags to identify the nodes only if you're patching using theexadbcpatchmulti tool.
For example:
Chapter 21Patching Primary and Standby Databases Configured with Oracle Data Guard Fails
21-11
To patch standby nodes, use -secondary flag.
/var/opt/oracle/exapatch/exadbcpatchmulti action [patchid] dbname|instance_num -secondary
To patch primary nodes, use -primary flag.
/var/opt/oracle/exapatch/exadbcpatchmulti action [patchid] dbname|instance_num -primary
Note:
Always patch standby nodes first and then proceed to primary nodes.
Chapter 21Patching Primary and Standby Databases Configured with Oracle Data Guard Fails
21-12
22Introduction to Autonomous Database onExadata Cloud@Customer
Oracle Autonomous Database on Oracle Exadata Cloud@Customer combines thebenefits of a self-driving, self-securing, and self-repairing database managementsystem and the security and control offered by having it deployed securely on premisebehind your firewall.
After purchasing Autonomous Database on Oracle Exadata Cloud@Customerand creating, provisioning and activating its Exadata Infrastructure hardwareand Oracle Cloud resource, several additional resource types become availablein the Exadata Cloud@Customer section of the Oracle Cloud Infrastructureconsole: Autonomous Exadata VM Clusters, Autonomous Container Databases andAutonomous Databases. You use these resources to create and manage your secure,on-premise deployment of Oracle Autonomous Database.
• Database System Architecture Overview
• User Roles
• Available Exadata Infrastructure Hardware Shapes
• Oracle Exadata Cloud@Customer X8M-2 System SpecificationsReview the technical specifications for each system configuration option for ADB-D on Oracle Exadata Cloud@Customer.
• Access Control Lists (ACLs) for Autonomous Databases on ExadataCloud@Customer
Database System Architecture OverviewOracle Autonomous Database on Oracle Exadata Cloud@Customer has a four-level database architecture model that makes use of Oracle multitenant databasearchitecture.
• Resource Types
• Deployment Order
Resource TypesEach level of the architecture model corresponds to one of the following resourcestypes:
• Oracle Exadata Cloud@Customer infrastructure: Hardware rack that includescompute nodes and storage servers, tied together by a high-speed, low-latencyInfiniBand network and intelligent Exadata software.
Oracle Exadata Cloud@Customer infrastructure is common for both Autonomousand Non-Autonomous resources.
22-1
For a list of the hardware and Oracle Cloud resource characteristics of OracleExadata Cloud@Customer infrastructure resources that support AutonomousDatabases, see Available Exadata Infrastructure Hardware Shapes.
– Only the Oracle Exadata Cloud@Customer Infrastructures deployed beforeOracle announced support for Autonomous Databases on Oracle ExadataCloud@Customer do not support Autonomous resources listed below. Pleasecontact your Oracle sales representative to understand the infrastructureupgrades required for supporting Oracle Autonomous Databases.
– You can create only one Autonomous VM cluster in an Exadata Infrastructure.
– Oracle Exadata Cloud@Customer infrastructure cannot simultaneously haveboth Autonomous and Exadata VM clusters.
• Autonomous VM clusters on Exadata Cloud@Customer infrastructure: VMcluster is a set of symmetrical VMs across all Compute nodes. AutonomousContainer and Database run all the VMs across all nodes enabling highavailability. It consumes all the resources of the underlying Exadata Infrastructure.
Before you can create any Autonomous Databases on your ExadataCloud@Customer infrastructure, you must create an Autonomous VM clusternetwork, and you must associate it with a VM cluster.
• Autonomous Container Database: Provides a container for multipleAutonomous Databases.
• Autonomous Database: You can create multiple autonomous databases withinthe same autonomous container database. You can configure Oracle AutonomousDatabase for either transaction processing or data warehouse workloads.
Deployment OrderYou must create the dedicated Exadata infrastructure resources in the following order:
1. Exadata Infrastructure. See Preparing for Exadata Cloud@Customer andProvisioning Exadata Cloud@Customer Systems for more information.
2. Autonomous Exadata VM cluster. See Managing Autonomous Exadata VMClusters for more information.
3. Autonomous Container Database. See Managing Autonomous ContainerDatabases for more information.
4. Autonomous Database. See Managing Autonomous Databases for moreinformation.
User RolesYour organization may choose to split the administration of the Oracle AutonomousDatabase on Oracle Exadata Cloud@Customer into the following roles:
• Fleet Administrator. Fleet administrators create, monitor and manageAutonomous Exadata Infrastructure and Autonomous Container Databaseresources. They must also setup customer managed Backup Destinations, suchas Recovery Appliance and NFS to be used by Autonomous Databases. Afleet administrator must have permissions for using the networking resourcesrequired by the Oracle Exadata Cloud@Customer infrastructure, and permissionsto manage the infrastructure and container database resources.
Chapter 22User Roles
22-2
• Database Administrator. Database administrators create, monitor and manageAutonomous Databases. They also create and manage users within the database.Database administrators must have permissions for using container databases,for managing autonomous databases and backups, and for using the relatednetworking resources. At the time of provisioning an Autonomous Database,the administrator provides user credentials for the automatically created ADMINaccount, which provides administrative rights to the new database.
• Database User. Database users are the developers who write applications thatconnect to and use an Autonomous Database to store and access the data.Database users do not need Oracle Cloud Infrastructure accounts. They gainnetwork connectivity to and connection authorization information for the databasefrom the database administrator.
Available Exadata Infrastructure Hardware ShapesOracle Autonomous Database on Oracle Exadata Cloud@Customer supports thefollowing shapes of Exadata Infrastructure resources.
The following table lists the Exadata Infrastructure resource shapes that OracleAutonomous Database on Oracle Exadata Cloud@Customer supports.
Specification Exadata X8-2Quarter Rack
Exadata X8-2 HalfRack
Exadata X8-2 FullRack
Shape Name Exadata.Quarter3.100
Exadata.Half3.200 Exadata.Full3.400
Number of Compute Nodes 2 4 8
Total Maximum Number of Enabled CPU Cores 100 200 400
Total RAM Capacity 1440 GB 2880 GB 5760 GB
Number of Exadata Storage Servers 3 6 12
Total Raw Flash Storage Capacity 76.8 TB 153.6 TB 307.2 TB
Total Usable Storage Capacity 149.7 TB 299.4 TB 598.7 TB
Maximum Number of Autonomous ContainerDatabases
12 (See note) 12 (See note) 12 (See note)
Maximum Number of Autonomous Databasesper Autonomous Container Database
100 (See note) 200 (See note) 400 (See note)
Note:
Oracle Autonomous Database does not currently support over-provisioning,the ability for multiple autonomous databases to share a single CPUcore. Therefore, an Exadata Infrastructure resource can currently support,across all its autonomous container databases, up to as many autonomousdatabases as it has CPU cores.
Chapter 22Available Exadata Infrastructure Hardware Shapes
22-3
Oracle Exadata Cloud@Customer X8M-2 SystemSpecifications
Review the technical specifications for each system configuration option for ADB-D onOracle Exadata Cloud@Customer.
Tip:
X8M-2 support is available only in the ashburn-1 region.
Table 22-1 Oracle Exadata Cloud@Customer X8M-2 System Specifications
Property Quarter Rack Half Rack Full Rack
Number of ComputeNodes
2 4 8
Total MaximumNumber of EnabledCPU Cores
100 200 400
Total RAM Capacity 2780 GB 5560 GB 11120 GB
Persistent Memory 4.6 TB 9.2 TB 18.4 TB
Number of ExadataStorage Servers
3 6 12
Total Raw FlashStorage Capacity
76.8 TB 153.6 TB 307.2 TB
Total Usable StorageCapacity**
149 TB 299 TB 598 TB
Max number of VMs 8 8 8
** TB=1024^4
Access Control Lists (ACLs) for Autonomous Databases onExadata Cloud@Customer
An access control list (ACL) provides additional protection to your database byallowing only the clients with specific IP addresses to connect to the database. Youcan add IP addresses individually, or in CIDR blocks.
You can optionally create an ACL during database provisioning, or at any timethereafter. You can also edit an ACL at any time. Enabling an access control list withan empty list of IP addresses makes the database inaccessible. For more information,see "Manage Access Control List of an Autonomous Database".
Note the following about using an ACL with your Autonomous Database:
• The Autonomous Database Service console is not subject to ACL rules.
Chapter 22Oracle Exadata Cloud@Customer X8M-2 System Specifications
22-4
• Oracle Application Express (APEX), RESTful services, and SQL Developer Webare not subject to ACLs. Choosing to enable an ACL disables these featuresautomatically.
• Performance Hub is not subject to ACL rules.
• While creating a database, if setting ACL fails, then provisioning the database alsofails.
• Updating ACL is allowed if the database is in Available andAvailableNeedsAttention states.
• Restoring a database does not overwrite the existing ACLs.
• Cloning a database, full and metadata, will have the same access control settingsas the source database. You can make changes as necessary.
• All CDB operations are allowed during ACL update. However, ADB operations arenot allowed during ACL update.
Related Topics
• Manage Access Control List of an Autonomous Database
Chapter 22Access Control Lists (ACLs) for Autonomous Databases on Exadata Cloud@Customer
22-5
23Managing Autonomous Exadata VMClusters
An Autonomous Exadata VM Cluster is a set of symmetrical VMs across all Computenodes. Autonomous Container and Database run all the VMs across all nodesenabling high availability. It consumes all the resources of the underlying ExadataInfrastructure.
After you have created the Autonomous Exadata VM Cluster, you can create up to12 Autonomous Container Database resources on it, depending on the capacity ofyour Exadata Infrastructure hardware, as described in Available Exadata InfrastructureHardware Shapes.
• Create an Autonomous Exadata VM Cluster
• View a List of Autonomous Exadata VM Clusters
• View Details of an Autonomous Exadata VM Cluster
• Change the License Type on an Autonomous VM Cluster
• Move an Autonomous Exadata VM Cluster to Another Compartment
• Terminate an Autonomous Exadata VM Cluster
• Using the API to Manage Autonomous Exadata VM Clusters
Create an Autonomous Exadata VM ClusterFollow these steps to create an Autonomous Exadata VM cluster on an OracleExadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Exadata VM Clusters.
3. Click Create Autonomous Exadata VM Cluster.
4. In the Create Autonomous Exadata VM Cluster dialog, enter the following generalinformation:
• Compartment: Specify the compartment in which the Autonomous ExadataVM Cluster will be created.
• Display Name: A user-friendly description or other information that helps youeasily identify the infrastructure resource. The display name does not have tobe unique. Avoid entering confidential information.
• Exadata Infrastructure: Select an Exadata Infrastructure.
• VM Cluster Network: Select a VM Cluster Network.
• Configure the Exadata Storage: Optionally, you can Allocate Storage forLocal Backups.
5. Choose the license type you wish to use.
23-1
Your choice affects metering for billing. You have the following options:
• Bring your own license: If you choose this option, make sure you haveproper entitlements to use for new service instances that you create.
• License included: With this choice, the cost of the cloud service includes alicense for the Database service.
6. The following Advanced Options are available:
• Time zone: The default time zone for the Exadata Infrastructure is UTC,but you can specify a different time zone. The time zone options are thosesupported in both the Java.util.TimeZone class and the Oracle Linux operatingsystem.
Note:
If you want to set a time zone other than UTC or thebrowser-detected time zone, then select the Select another timezone option, select a Region or contry, and then select thecorresponding Time zone.
If you do not see the region or country you want, then selectMiscellaneous, and then select an appropriate Time zone.
• Tags: Optionally, you can apply tags. If you have permissions to create aresource, you also have permissions to apply free-form tags to that resource.To apply a defined tag, you must have permissions to use the tag namespace.For more information about tagging, see Resource Tags. If you are not sure ifyou should apply tags, skip this option (you can apply tags later) or ask youradministrator. Avoid entering confidential information.
7. Click Create Autonomous Exadata VM Cluster.
View a List of Autonomous Exadata VM ClustersFollow these steps to view a list of autonomous Exadata VM clusters on an OracleExadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Exadata VM Clusters.
View Details of an Autonomous Exadata VM ClusterFollow these steps to view detailed information about an autonomous Exadata VMcluster on an Oracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Exadata VM Clusters.
3. In the list of Autonomous Exadata VM Clusters, click the display name of theExadata VM cluster you wish to view details.
Chapter 23View a List of Autonomous Exadata VM Clusters
23-2
Change the License Type on an Autonomous VM ClusterFollow these steps to update the license type of an autonomous Exadata VM clusteron an Oracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Exadata VM Clusters.
3. In the list of Autonomous Exadata VM Clusters, click the display name of theExadata VM cluster you wish to administer.
4. Click Update License Type.
5. On the Update License Type dialog box, choose one of the following license types.
• Bring Your Own License (BYOL): Select this option if your organizationalready owns Oracle Database software licenses that you want to use on theVM cluster.
• License Included: Select this option to subscribe to Oracle Databasesoftware licenses as part of Exadata Cloud@Customer.
Updating the license type does interrupt the operation of the VM cluster.
6. Click Save Changes.
Move an Autonomous Exadata VM Cluster to AnotherCompartment
Follow these steps to move an autonomous Exadata VM cluster on an Oracle ExadataCloud@Customer system from one compartment to another compartment.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Exadata VM Clusters.
3. In the list of Autonomous Exadata VM Clusters, click the display name of theExadata VM cluster you wish to administer.
4. Click Move Resource.
5. Select the new compartment.
6. Click Move Resource.
Terminate an Autonomous Exadata VM ClusterFollow these steps to terminate an autonomous Exadata VM cluster on an OracleExadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. In the list of Autonomous Exadata VM Clusters, click the display name of theExadata VM cluster you wish to administer.
3. Click Terminate.
4. Confirm that you wish to terminate your Autonomous Exadata VM Cluster in theconfirmation dialog.
Chapter 23Change the License Type on an Autonomous VM Cluster
23-3
5. Click Terminate VM Cluster.
Using the API to Manage Autonomous Exadata VM ClustersFor information about using the API and signing requests, see REST APIs andSecurity Credentials. For information about SDKs, see Software Development Kits andCommand Line Interface.
The following table lists the REST API endpoints to manage Autonomous Exadata VMClusters.
Operation REST API Endpoint
Create an Autonomous Exadata VM Cluster CreateAutonomousVmCluster
View a list of Autonomous Exadata VMClusters
ListAutonomousVmClusters
View details of an Autonomous Exadata VMCluster
GetAutonomousVmCluster
Change the license type of an AutonomousVM Cluster
UpdateAutonomousVmCluster
Move an Autonomous Exadata VM Cluster toanother compartment
ChangeAutonomousVmClusterCompartment
Terminate an Autonomous Exadata VMCluster
DeleteAutonomousVmCluster
Chapter 23Using the API to Manage Autonomous Exadata VM Clusters
23-4
24Managing Encryption Keys on ExternalDevices
There are two options to store and manage database encryption keys for yourautonomous databases on Exadata Cloud@Customer:
1. In the DomU on the Exadata Infrastructure
2. On an external key management device. Oracle Key Vault is the currentlysupported device.
• About Oracle Key VaultOracle Key Vault is a full-stack, security-hardened software appliance built tocentralize the management of keys and security objects within the enterprise.
• Overview of Key StoreIntegrate your on-premises Oracle Key Vault (OKV) with Autonomous Databaseon Exadata Cloud@Customer to secure your critical data on-premises.
• Required IAM Policy for Managing OKV on Oracle Exadata Cloud@CustomerReview the identity access management (IAM) policy for managing OKV on OracleExadata Cloud@Customer Systems.
• Tagging ResourcesYou can apply tags to your resources to help you organize them according to yourbusiness needs.
• Moving Resources to a Different CompartmentYou can move vaults from one compartment to another.
• Setting Up Your Exadata Cloud@Customer to Work With Oracle Key Vault
• Managing Your Key Store
About Oracle Key VaultOracle Key Vault is a full-stack, security-hardened software appliance built tocentralize the management of keys and security objects within the enterprise.
Note:
The Oracle Key Vault is a customer-provisioned and managed system and itis not part of Oracle Cloud Infrastructure managed services.
Related Topics
• Oracle Key Vault
24-1
Overview of Key StoreIntegrate your on-premises Oracle Key Vault (OKV) with Autonomous Database onExadata Cloud@Customer to secure your critical data on-premises.
Oracle Key Vault integration enables you to take complete control of your encryptionkeys and store them securely on an external, centralized key management device.
OKV is optimized for Oracle wallets, Java keystores, and Oracle Advanced SecurityTransparent Data Encryption (TDE) master keys. Oracle Key Vault supports theOASIS KMIP standard. The full-stack, security-hardened software appliance usesOracle Linux and Oracle Database technology for security, availability, and scalability,and can be deployed on your choice of compatible hardware.
OKV also provides a REST interface for clients to auto-enroll endpoints and setupwallets and keys. For Autonomous Databases on Exadata Cloud@Customer toconnect to OKV REST interface, create a key store in your tenancy to store the IPaddress and administrator credentials of your OKV. Exadata Cloud@Customer will notstore the admin password required to connect to the OKV appliance. Ensure that youcreate a secret with Oracle's Vault Service, which will store the password required forautonomous databases to connect to OKV for key management.
For more information, see "Oracle Key Vault".
Related Topics
• Oracle Key Vault
Required IAM Policy for Managing OKV on Oracle ExadataCloud@Customer
Review the identity access management (IAM) policy for managing OKV on OracleExadata Cloud@Customer Systems.
A policy is an IAM document that specifies who has what type of access to yourresources. It is used in different ways: to mean an individual statement written inthe policy language; to mean a collection of statements in a single, named "policy"document (which has an Oracle Cloud ID (OCID) assigned to it), and to mean theoverall body of policies your organization uses to control access to resources.
A compartment is a collection of related resources that can be accessed onlyby certain groups that have been given permission by an administrator in yourorganization.
To use Oracle Cloud Infrastructure, you must be given the required type of access ina policy written by an administrator, whether you're using the Console, or the RESTAPI with a software development kit (SDK), a command-line interface (CLI), or someother tool. If you try to perform an action, and receive a message that you don’thave permission, or are unauthorized, then confirm with your administrator the type ofaccess you've been granted, and which compartment you should work in.
For administrators: The policy in "Let database admins manage DB systems" lets thespecified group do everything with databases and related database resources.
Chapter 24Overview of Key Store
24-2
If you're new to policies, then see "Getting Started with Policies" and "CommonPolicies". If you want to dig deeper into writing policies for databases, then see "Detailsfor the Database Service".
Related Topics
• Let database admins manage DB systems
• Getting Started with Policies
• Common Policies
• Details for the Database Service
Tagging ResourcesYou can apply tags to your resources to help you organize them according to yourbusiness needs.
You can apply tags at the time you create a resource, or you can update the resourcelater with the desired tags. For general information about applying tags, see "ResourceTags".
Related Topics
• Resource Tags
Moving Resources to a Different CompartmentYou can move vaults from one compartment to another.
After you move a vault to a new compartment, inherent policies apply immediatelyand affect access to the vault. Moving a vault doesn't affect access to any keys orsecrets that the vault contains. You can move a key or secret from one compartmentto another independently of moving the vault it's associated with. For more information,see "Managing Compartments".
Related Topics
• Managing Compartments
Setting Up Your Exadata Cloud@Customer to Work WithOracle Key Vault
Prerequisites
1. Ensure OKV is setup and network accessible from the Exadata client network
2. Gather OKV administrator credentials and IP address, which is required to connectto OKV
• Step 1: Create a Vault in OCI Vault Service and Add a Secret to the Vault to StoreOKV REST Administrator Password
• Step 2: Create a Dynamic Group and a Policy Statement for Key Store to AccessSecret in OCI Vault
• Step 3: Create a Dynamic Group and a Policy Statement for ExadataInfrastructure to Key Store
Chapter 24Tagging Resources
24-3
• Step 4: Create a Policy Statement for Database Service to Use Secret from OCIVault Service
• Step 5: Create Key Store
Step 1: Create a Vault in OCI Vault Service and Add a Secret to theVault to Store OKV REST Administrator Password
Your Exadata Cloud@Customer infrastructure communicates with OKV over RESTeach time an Autonomous Container Database is provisioned to register theAutonomous Container Database and request a wallet on OKV. Therefore, Exadatainfrastructure needs access to the REST admin credentials.
These credentials can be stored securely in the Oracle Vault Service in OCI as aSecret and accessed by your Exadata Cloud@Customer infrastructure only whenneeded. These credentials are not accessible by a human operator administering theExadata infrastructure.
To store OKV administrator password in OCI Vault service, create a vault by followingthe instructions outlined in "Managing Vaults" and create a Secret in that vault byfollowing the instructions outlined in "Managing Secrets".
Related Topics
• Managing Vaults
• Managing Secrets
Step 2: Create a Dynamic Group and a Policy Statement for Key Storeto Access Secret in OCI Vault
To grant your Key Store resources permission to access Secret in OCI Vault, youcreate an IAM dynamic group that identifies these resources and then create an IAMpolicy that grants this dynamic group access to the Secret you created in the OCIVaults and Secrets.
When defining the dynamic group, you identify your Key Store resources by specifyingthe OCID of the compartment containing your Key Store.
1. Copy the OCID of the compartment containing your Key Store resource.
You can find this OCID on the Compartment Details page of the compartment.
2. Create a dynamic group by following the instructions in "To create a dynamicgroup" in Oracle Cloud Infrastructure Documentation. When following theseinstructions, enter a matching rule of this format:
ALL {resource.compartment.id ='<compartment-ocid>'}
where <compartment-ocid> is the OCID of the compartment containing your KeyStore resource.
Chapter 24Setting Up Your Exadata Cloud@Customer to Work With Oracle Key Vault
24-4
3. After creating the dynamic group, navigate to (or create) an IAM policy in acompartment higher up in your compartment hierarchy than the compartmentcontaining your vaults and secrets. Then, add a policy statement of this format:
allow dynamic-group <dynamic-group> to use secret-family in compartment <vaults-and-secrets-compartment>
where <dynamic-group> is the name of the dynamic group you created and<vaults-and-secrets-compartment> is the name of the compartment in whichyou created your vaults and secrets.
Related Topics
• To create a dynamic group
Step 3: Create a Dynamic Group and a Policy Statement for ExadataInfrastructure to Key Store
To grant your Exadata infrastructure resources permission to access Key Store, youcreate an IAM dynamic group that identifies these resources and then create an IAMpolicy that grants this dynamic group access to the Key Store you created.
When defining the dynamic group, you identify your Exadata infrastructure resourcesby specifying the OCID of the compartment containing your Exadata infrastructure.
1. Copy the OCID of the compartment containing your Exadata infrastructureresource.
You can find this OCID on the Compartment Details page of the compartment.
2. Create a dynamic group by following the instructions in "To create a dynamicgroup" in Oracle Cloud Infrastructure Documentation. When following theseinstructions, enter a matching rule of this format:
ALL {resource.compartment.id ='<compartment-ocid>'}
where <compartment-ocid> is the OCID of the compartment containing yourExadata infrastructure resource.
3. After creating the dynamic group, navigate to (or create) an IAM policy in acompartment higher up in your compartment hierarchy than the compartmentcontaining your Key Store. Then, add a policy statement of this format:
Allow dynamic-group <dynamic-group> to use keystores in compartment <key-store-compartment>
where <dynamic-group> is the name of the dynamic group you created and<key-store-compartment> is the name of the compartment in which you createdyour Key Store.
Chapter 24Setting Up Your Exadata Cloud@Customer to Work With Oracle Key Vault
24-5
Step 4: Create a Policy Statement for Database Service to Use Secretfrom OCI Vault Service
To grant the Autonomous Database service permission to use the secret in OCIVault to log in to the OKV REST interface, navigate to (or create) an IAM policyin a compartment higher up in your compartment hierarchy than the compartmentcontaining your OCI Vaults and Secrets. Then, add a policy statement of this format:
allow service database to read secret-family in compartment <vaults-and-secrets-compartment>
where <vaults-and-secrets-compartment> is the name of the compartment in whichyou created your OCI Vaults and Secrets.
Once the OCI Vault is set up and the IAM configuration is in place, you are now readyto deploy your Oracle Key Vault 'Key Store' in OCI and associate it with your ExadataCloud@Customer VM Cluster.
Step 5: Create Key Store
Follow these steps to create a Key Store to connect to an on-premises encryption keyappliance such as Oracle Key Vault (OKV).
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose your Compartment.
3. Click Key Stores.
Key Stores page displays the list name of key stores, the number of databasesassociated with each database, and the date on which each key store wascreated.
4. Click Create Key Store.
5. In the Create Key Store dialog, enter the following general information:
• Name your key store: A user-friendly description or other information thathelps you easily identify the Key Store resource. Avoid entering confidentialinformation.
• Oracle Key Vault connection settings
– Connection IP addresses: Enter the IP address of the OKV appliance.You can specify a comma-delimited list of IP addresses, for example,193.10.20.1, 193.10.20.1.
– Administrator username: Enter the user name of the OKV RESTadministrator.
– Administrator Password Secret: The administrator password is storedwith the secret management service within OCI. Select the OCI Vault inyour tenancy that contains OKV REST administrator password stored asSecret.
• Tags: Optionally, you can apply tags. If you have permission to create aresource, you also have permission to apply free-form tags to that resource.
Chapter 24Setting Up Your Exadata Cloud@Customer to Work With Oracle Key Vault
24-6
To apply a defined tag, you must have permission to use the tag namespace.For more information about tagging, see Resource Tags. If you are not sure ifyou should apply tags, skip this option (you can apply tags later) or ask youradministrator. Avoid entering confidential information.
6. Click Create Key Store.
For more information, see "Managing Vaults", "Managing Keys", and "ManagingSecrets".
Related Topics
• Managing Vaults
• Managing Keys
• Managing Secrets
Managing Your Key Store• View Key Store Details
Follow these steps to view Key Store details that include Oracle Key Vault (OKV)connection details and the list of associated databases.
• Edit Key Store DetailsYou can edit a Key Store only if it is not associated with any CDBs.
• Move a Key Store to Another CompartmentFollow these steps to move a Key Store on an Oracle Exadata Cloud@Customersystem from one compartment to another compartment.
• Delete a Key StoreYou can delete a Key Store only if it is not associated with any CDBs.
• View Key Store Associated Autonomous Container Database DetailsFollow these steps to view details of the Autonomous Container Databaseassociated with a Key Store.
• Using the API to Manage Key StoreLearn how to use the API to manage key store.
View Key Store DetailsFollow these steps to view Key Store details that include Oracle Key Vault (OKV)connection details and the list of associated databases.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose your Compartment.
3. Click Key Stores.
Key Stores page displays the list name of Key Stores, the number of databasesassociated with each database, and the date on which each Key Store wascreated.
4. Click the name of the Key Store or click the Actions icon (three dots), and thenclick View Details.
5. Click the link in the Administrator Password Secret field to view secret details.
Chapter 24Managing Your Key Store
24-7
Edit Key Store DetailsYou can edit a Key Store only if it is not associated with any CDBs.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose your Compartment.
3. Click Key Stores.
4. Click the name of the Key Store or click the Actions icon (three dots), and thenclick View Details.
5. On the Key Store Details page, click Edit.
6. On the Edit Key Store page, make changes as needed, and then click SaveChanges.
Move a Key Store to Another CompartmentFollow these steps to move a Key Store on an Oracle Exadata Cloud@Customersystem from one compartment to another compartment.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose your Compartment.
3. Click Key Stores.
4. Click the name of the Key Store or click the Actions icon (three dots), and thenclick View Details.
5. On the Key Store Details page, click Move Resource.
6. On the Move Resource to a Different Compartment page, select the newcompartment.
7. Click Move Resource.
Delete a Key StoreYou can delete a Key Store only if it is not associated with any CDBs.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose your Compartment.
3. Click Key Stores.
4. Click the name of the Key Store or click the Actions icon (three dots), and thenclick View Details.
5. On the Key Store Details page, click Delete.
6. On the Delete Key Store dialog, click Delete.
View Key Store Associated Autonomous Container Database DetailsFollow these steps to view details of the Autonomous Container Database associatedwith a Key Store.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
Chapter 24Managing Your Key Store
24-8
2. Choose your Compartment.
3. Click Key Stores.
Key Stores page displays the list name of Key Stores, the number of databasesassociated with each database, and the date on which each Key Store wascreated.
4. Click the name of the Key Store or click the Actions icon (three dots), and thenclick View Details.
5. Click the name of the associated database or click the Actions icon (three dots),and then click View Details.
Using the API to Manage Key StoreLearn how to use the API to manage key store.
For information about using the API and signing requests, see "REST APIs" and"Security Credentials". For information about SDKs, see "Software Development Kitsand Command Line Interface".
The following table lists the REST API endpoints to manage key store.
Operation REST API Endpoint
Create OKV Key Store CreateKeyStore
View OKV Key Store GetKeyStore
Update OKV Key Store UpdateKeyStore
Delete OKV Key Store DeleteKeyStore
Change Key store compartment ChangeKeyStoreCompartment
Choose between customer-managed andOracle-managed encryption
CreateAutonomousContainerDatabase
Get the Key Store (OKV or Oracle-managed)and OKV wallet name
GetAutonomousContainerDatabase
Rotate OKV and Oracle-managed key RotateAutonomousContainerDatabaseKey
Get the Key store (OKV or Oracle-managed)and OKV wallet name
GetAutonomousDatabase
Rotate OKV and Oracle-managed key RotateAutonomousDatabaseKey
Get the Key Store (OKV or Oracle-managed)and OKV wallet name
GetAutonomousDatabaseBackup
Related Topics
• REST APIs
• Security Credentials
• Software Development Kits and Command Line Interface
Chapter 24Managing Your Key Store
24-9
25Managing Autonomous ContainerDatabases
Learn how you can create, view, move, change backup policies, manage maintenanceschedules, and perform other Oracle Autonomous Container Database management.
An Autonomous Container Database resource provides a container for yourAutonomous Databases. You can create multiple Autonomous Container Databaseresources in a single Autonomous Exadata VM Cluster resource, but you must createat least one before you can create any Autonomous Databases.
• Create an Autonomous Container Database
• View a List of Autonomous Container Databases
• View Details of an Autonomous Container Database
• Rotate CDB Encryption Key
• Change the Backup Retention Policy of an Autonomous Container Database
• Change the Maintenance Schedule of an Autonomous Container Database
• Restart an Autonomous Container Database
• Move an Autonomous Container Database to Another Compartment
• Terminate an Autonomous Container Database
• Using the API to Manage Autonomous Container Databases
Create an Autonomous Container DatabaseFollow these steps to create an autonomous container database on an Oracle ExadataCloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. Click Create Autonomous Container Database.
The Create Autonomous Container Database page is displayed.
4. Provide the following basic information:
• Compartment: Choose the compartment in which your autonomous containerdatabase will be created.
• Display Name: Enter a user-friendly description or other information that helpsyou easily identify the autonomous container database. The display namedoes not have to be unique. Avoid entering confidential information.
5. Select the Autonomous Exadata VM Cluster you wish to use to create yourautonomous container database.
6. Optionally, you can configure an automatic maintenance schedule.
25-1
a. Click Modify Maintenance.
b. To configure the maintenance schedule, select Specify a schedule.
Choose your preferred month, week, weekday, and start time for autonomouscontainer database maintenance.
• Under Week of the month, specify which week of the month maintenancewill take place. Weeks start on the 1st, 8th, 15th, and 22nd days of themonth, and have a duration of 7 days. Weeks start and end based oncalendar dates, not days of the week. Maintenance cannot be scheduledfor the fifth week of months that contain more than 28 days.
• Under Day of the week, specify the day of the week on which themaintenance will occur.
• Under Start hour, specify the hour during which the maintenance run willbegin.
c. Click Save Changes.
7. Select a Backup Destination Type:
• Object Storage: Stores backups in an Oracle-managed object storagecontainer on Oracle Cloud Infrastructure. Optionally, you can use this fieldto specify your corporate HTTP proxy. We recommend using an HTTP proxywhen possible for enhanced security.
• Network File System (NFS): Stores backups in one of your previouslydefined backup destinations that uses Network File System (NFS) storage.
– Select a Backup Destination.
• Recovery Appliance: Stores backups in one of your previously definedbackup destinations that uses Oracle Zero Data Loss Recovery Appliance.
– Select a Backup Destination.
– Provide a unique name for the database.
– Provide a VPC user name and password.
8. The following Advanced Options are available:
• Backup retention period: Customize the retention period for automaticbackups. For Recovery Appliance, you cannot select the retention period.
• Encryption Key: Choose an encryption option, Encrypt using Oracle-managed keys or Encrypt using customer-managed keys. The defaultoption is Oracle-managed keys.To use customer-managed keys, select the Encrypt using customer-managed keys option, select the compartment where you have created theKey Store, and then select the Key Store. As part of the CDB creation, a newwallet is created for the CDB in Oracle Key Vault (OKV). Also, a TDE MasterKey is generated for the CDB and added to the wallet in OKV.
Chapter 25Create an Autonomous Container Database
25-2
Note:
– Autonomous Container Databases and Autonomous Databasesonly support 256-bit Hardware Security Module (HSM) Vaultkeys.
– Validate OKV Key encryption post restart: OKV TDE Maser Keyis validated every time you start or restart your ACD. Start orrestart fails if the key is not validated. Work requests and lifecycle states indicate the reason for failure.
– View OKV keys post database restore: When you restore aCDB, the master key associated with that backup is restoredas well.
– Enable CDB backups to capture wallet name: CDB backupsinformation about the wallet associated with the backup.
– OKV Wallet or TDE Master Key on CDB deletion: If you delete aCDB, then the wallet and TDE Master Key remains in OKV andwill not be deleted.
• Tags: Optionally, you can apply tags. If you have permissions to create aresource, you also have permissions to apply free-form tags to that resource.To apply a defined tag, you must have permissions to use the tag namespace.For more information about tagging, see Resource Tags. If you are not sure ifyou should apply tags, skip this option (you can apply tags later) or ask youradministrator. Avoid entering confidential information.
9. Click Create Autonomous Container Database.
View a List of Autonomous Container DatabasesThere are two ways to view a list of autonomous container databases on an OracleExadata Cloud@Customer system.
• View the List of Autonomous Container Databases in an Autonomous Exadata VMCluster
• View the List of Autonomous Container Databases in a Compartment
View the List of Autonomous Container Databases in an AutonomousExadata VM Cluster
Follow these steps to view a list of an autonomous container databases in a givenautonomous Exadata VM cluster on an Oracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Exadata VM Clusters.
3. Click the display name of the Autonomous Exadata VM Cluster that you interestedin.
In the Autonomous Exadata VM Clusters Details page, a list of AutonomousContainer Databases is displayed under Resources.
Chapter 25View a List of Autonomous Container Databases
25-3
You can also filter out to view Autonomous Container Databases in a particularcompartment. Under List Scope, select a compartment from the Compartmentdrop-down list.
View the List of Autonomous Container Databases in a CompartmentFollow these steps to view a list of an autonomous container databases in a givencompartment on an Oracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. Under List Scope, select a compartment from the Compartment drop-down list.
View Details of an Autonomous Container DatabaseFollow these steps to view detailed information about an autonomous containerdatabase on an Oracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of thedatabase you wish to view details.
On the Autonomous Container Database Details page encryption details aredisplayed under Encryption.
If you have chosen customer-managed keys while creating the database, then youwill see a link to the Encryption Key Store and OKV Wallet Name.
Note:
OKV Wallet Name represents the name of the wallet in which keys forthis CDB are generated on the OKV.
Click the Key Store link to view details.
If you have chosen Oracle-managed keys while creating the database, then youwill not see the link to Encryption Key Store and OKV Wallet Name.
Rotate CDB Encryption KeyFollow these steps to rotate the TDE Master key. On key rotation, the ACD life cyclegoes through the regular updating state and returns to available.
You can rotate the TDE Master key as many times as you want. The new TDE MasterKey is stored in the same wallet in which the previous key was stored. Rotating theTDE Master Key leads to the new key being generated in OKV and assigned to thisdatabase. You can view all of the keys in OKV.
Chapter 25View Details of an Autonomous Container Database
25-4
Note:
You can rotate both Oracle-managed and customer-managed encryptionkeys.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of thedatabase you wish to view details.
4. On the Autonomous Container Database Details page, click Rotate EncryptionKey.
5. On the Rotate Encryption Key dialog, click Rotate Encryption Key.
Change the Backup Retention Policy of an AutonomousContainer Database
Follow these steps to update the backup retention policy of an autonomous containerdatabase on an Oracle Exadata Cloud@Customer system.
Note:
By default, database backups are retained for 30 days if you have chosenObject Storage or NFS as a backup destination. You have the option ofretaining backups for 7, 15, 30, or 60 days. If you have chosen Local storageas a backup destination, then by default, database backups are retained fora maximum of 7 days. If you have chosen Recovery Appliance as a backupdestination, then you cannot update the backup retention policy.
The current backup retention policy for an Autonomous Container Databaseis displayed on the Autonomous Container Database details page.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of thecontainer database you are interested in.
4. On the Autonomous Container Database details page, under Backup, click theEdit link in the Backup retention policy field.
5. Specify a backup retention period from the list of choices.
6. Click Update.
Chapter 25Change the Backup Retention Policy of an Autonomous Container Database
25-5
Change the Maintenance Schedule of an AutonomousContainer Database
Follow these steps to change the maintenance schedule of an autonomous containerdatabase on an Oracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of thecontainer database you are interested in.
4. On the Autonomous Container Database details page, under Maintenance, clickthe edit link in the Maintenance Details field.
5. In the Edit Automatic Maintenance dialog that opens, configure automaticmaintenance schedule.
• No preference: The system assigns a date and start time for containerdatabase maintenance.
• Specify a schedule: Choose your preferred month, week, weekday, and starttime for container database maintenance.
6. Click Save Changes.
Restart an Autonomous Container DatabaseFollow these steps to restart an autonomous container database on an OracleExadata Cloud@Customer system.
The restart of an autonomous container database occurs in a rolling fashion, firststopping and starting one of the container database's database instances and thenstopping and starting its other database instance.
Note:
You cannot restart an autonomous container database if a backup is inprogress on any of its autonomous databases.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of thecontainer database you are interested in.
4. On the Autonomous Container Database details page, click Restart.
5. In the confirmation dialog, type the name of the Autonomous Container Database.
6. Click Restart.
Chapter 25Change the Maintenance Schedule of an Autonomous Container Database
25-6
Move an Autonomous Container Database to AnotherCompartment
Follow these steps to move an autonomous container database on an Oracle ExadataCloud@Customer system from one compartment to another compartment.
Note:
• To move an autonomous container database you must have the right tomanage it in its current compartment and in the compartment you aremoving it to.
• As soon as you move an autonomous container database to a differentcompartment, the policies that govern the new compartment applyimmediately and affect access to the autonomous container database.Therefore, both your and other Oracle Cloud users' access to it maychange, depending on the policies governing the user account's accessto resources. For example, a user may lose the ability to createautonomous databases in the autonomous container database, given itsnew compartment.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of thecontainer database you wish to move.
4. Click Move Resource.
5. Select the new compartment.
6. Click Move Resource.
Terminate an Autonomous Container DatabaseFollow these steps to terminate an autonomous container database on an OracleExadata Cloud@Customer system.
Note:
You must terminate all Autonomous Databases within a container databasebefore you can terminate the container database itself.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of theinfrastructure resource you are interested in.
Chapter 25Move an Autonomous Container Database to Another Compartment
25-7
4. Click Terminate.
5. In the confirmation dialog, type the name of the Autonomous Container Database,and then click Terminate Autonomous Container Database.
Using the API to Manage Autonomous Container DatabasesFor information about using the API and signing requests, see REST APIs andSecurity Credentials. For information about SDKs, see Software Development Kits andCommand Line Interface.
The following table lists the REST API endpoints to manage Autonomous ContainerDatabases.
Operation REST API Endpoint
Create an Autonomous Container Database CreateAutonomousContainerDatabase
View a list of Autonomous ContainerDatabases
ListAutonomousContainerDatabases
View details of an Autonomous ContainerDatabase
GetAutonomousContainerDatabase
Change the backup retention policy of anAutonomous Container Database
UpdateAutonomousContainerDatabase
Change the maintenance schedule of anAutonomous Container Database
UpdateAutonomousContainerDatabase
Restart an Autonomous Container Database RestartAutonomousContainerDatabase
Move an Autonomous Container Database toanother compartment
ChangeAutonomousContainerDatabaseCompartment
Terminate an Autonomous ContainerDatabase
TerminateAutonomousContainerDatabase
Chapter 25Using the API to Manage Autonomous Container Databases
25-8
26Managing Autonomous Databases
An Autonomous Database resource is a user database. When you create anAutonomous Database, you choose the Autonomous Container Database for it andyou specify "Data Warehouse" or "Transaction Processing" as its workload type tocreate an Autonomous Data Warehouse database or an Autonomous TransactionProcessing database.
You can create up to 400 Autonomous Databases in each Autonomous ContainerDatabase, depending on the capacity of your Exadata Infrastructure hardware, asdescribed in Available Exadata Infrastructure Hardware Shapes.
• Create an Autonomous Database
• Manage Access Control List of an Autonomous Database
• View a List of Autonomous Databases
• View Details of an Autonomous Database
• Rotate ADB Encryption Key
• Set the Password of an Autonomous Database's ADMIN User
• Scale the CPU Core Count or Storage of an Autonomous Database
• Enable or Disable Auto Scaling for an Autonomous Database
• Move an Autonomous Database to Another Compartment
• Stop or Start an Autonomous Database
• Restart an Autonomous Database
• Back Up an Autonomous Database Manually
• Restore an Autonomous Database
• Clone an Autonomous Database
• Terminate an Autonomous Database
• Using the API to Manage Autonomous Databases
• Monitor Performance with Autonomous Database Metrics
Create an Autonomous DatabaseFollow these steps to create an autonomous database on an Oracle ExadataCloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. Click Create Autonomous Database.
4. In the Create Autonomous Database dialog, enter the following:
Basic Database Information
26-1
• Compartment: Select the compartment of the Autonomous Database.
• Display Name: A user-friendly description or other information that helps youeasily identify the resource. The display name does not have to be unique.Avoid entering confidential information.
• Database Name: The database name must consist of letters and numbersonly, starting with a letter. The maximum length is 14 characters. Avoidentering confidential information.
Workload Type
Select the desired workload type. See About Autonomous Database forinformation about each workload type.
Autonomous Container Database: Select an Autonomous Container Database.
Compartment: Specify the compartment containing the Autonomous ContainerDatabase you wish to use.
Database CPU Core Count and Storage Configuration
• OCPU Count: The total number of cores available to all database within theAutonomous Exadata Infrastructure depends on the infrastructure shape andwhat is already allocated to other Autonomous Databases.Deselect Auto Scaling to disable auto scaling. By default auto scaling isenabled to allow the system to automatically use up to three times more CPUand IO resources to meet workload demand.
• Storage (TB): Specify the storage you wish to make available to yourAutonomous Database, in terabytes. The available storage depends on theinfrastructure shape and what is already consumed by other AutonomousDatabases.
Administrator Credentials
Set the password for the Autonomous Database Admin user by entering apassword that meets the following criteria. You use this password when accessingthe Autonomous Database service console and when using an SQL client tool.
• Contains from 12 to 30 characters
• Contains at least one lowercase letter
• Contains at least one uppercase letter
• Contains at least one number
• Does not contain the double quotation mark (")
• Does not contain the string "admin", regardless of casing
Configure network access
You can optionally create an ACL during database provisioning, or at any timethereafter.
Select the Enable database level access control checkbox.
Click Access Control Rule.
Chapter 26Create an Autonomous Database
26-2
Note:
The database-level access control will be enabled without any IPaddresses in the access control list. Enabling an access control list withan empty list of IP addresses makes the database inaccessible to allclients
Specify the following types of addresses in your list by using the IP notation typedrop-down selector:
• IP Address allows you to specify one or more individual public IP addresses.Use commas to separate your addresses in the input field.
• CIDR Block allows you to specify one or more ranges of public IP addressesusing CIDR notation. Use commas to separate your CIDR block entries in theinput field.
Advanced Options
Encryption Key: ADB inherits encryption settings from the parent ACD. If theparent ACD is configured for customer-managed OKV based encryption, then thechild ADB will also have TDE Master Key generated and managed in the sameOKV wallet used to store ACD master keys. Additionally, any backups taken onthe Autonomous Database will have the OKV based key associated with it.
Tags: Optionally, you can apply tags. If you have permissions to create a resource,you also have permissions to apply free-form tags to that resource. To apply adefined tag, you must have permissions to use the tag namespace. For moreinformation about tagging, see Resource Tags. If you are not sure if you shouldapply tags, skip this option (you can apply tags later) or ask your administrator.Avoid entering confidential information.
5. Click Create Autonomous Database.
Note:
The following naming restrictions apply to Autonomous TransactionProcessing and Autonomous Data Warehouse databases:
• Names associated with databases terminated within the last 60 dayscannot be used when creating a new database.
• A database name cannot be used concurrently for both anAutonomous Data Warehouse and an Autonomous TransactionProcessing database.
Manage Access Control List of an Autonomous DatabaseEnabling an access control list with an empty list of IP addresses makes the databaseinaccessible.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Choose your Compartment.
Chapter 26Manage Access Control List of an Autonomous Database
26-3
3. In the list of Autonomous Databases, click the display name of the database youwant to administer.
4. Under Network in the database details, find the Access Control List field andclick Edit to enable or disable your database-level access control and makechanges to the ACL rules.
Note:
Autonomous Data Guard enabled Automonous databases:
• You can only view ACLs for standby databases.
• You can reset ACL for both the primary and standby databases fromthe primary database details page. You cannot configure ACL fromthe standby database details page.
5. In the Access Control List dialog, add or modify entries, as applicable.
If you are editing an ACL, the ACL's existing entries display in the Access ControlList dialog. Do not overwrite the existing values unless you intend to replace oneor more entries. To add new ACL entries, click + Access Control Rule.
You can specify the following types of addresses in your list by using the IPnotation type drop-down selector:
• IP Address allows you to specify one or more individual public IP addresses.Use commas to separate your addresses in the input field.
• CIDR Block allows you to specify one or more ranges of public IP addressesusing CIDR notation. Use commas to separate your CIDR block entries in theinput field.
Click + Access Control Rule to add additional access rules to your list.
To remove an access control rule, simply delete the entry from the list. Deleting allaccess control rules from the ACL will render the database inaccessible becausethe allow list is empty.
To disable the database-level access control configuration, clear the Enabledatabase level access control checkbox. Once ACL is disabled and theconfiguration is saved, all the access control rules are removed from the ACLand no longer applicable.
6. Click Save Changes.
If the Lifecycle State is Available when you click Save, the Lifecycle Statechanges to Updating until the ACL update is complete. The database is still upand accessible, there is no downtime. When the update is complete the LifecycleState returns to Available and the network ACL rules from the access control listare in effect.
View a List of Autonomous DatabasesFollow these steps to view a list of autonomous databases on an Oracle ExadataCloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
Chapter 26View a List of Autonomous Databases
26-4
2. Click Autonomous Databases.
View Details of an Autonomous DatabaseFollow these steps to view detailed information about an autonomous database on anOracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to view details.
On the Autonomous Container Database Details page encryption details aredisplayed under Encryption.
If you have chosen customer-managed keys while creating the database, then youwill see a link to the Encryption Key Store and OKV Wallet Name. Click the KeyStore link to view details.
If you have chosen Oracle-managed keys while creating the database, then youwill not see the link to Encryption Key Store and OKV Wallet Name.
Rotate ADB Encryption KeyFollow these steps to rotate the TDE Master key. On key rotation, the ADB life cyclegoes through the regular updating state and returns to available.
You can rotate the TDE Master key as many times as you want. The new TDE MasterKey is stored in the same wallet in which the previous key was stored. Rotating theTDE Master Key leads to the new key being generated in OKV and assigned to thisdatabase. You can view all of the keys in OKV.
Note:
You can rotate both Oracle-managed and customer-managed encryptionkeys.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to view details.
4. On the Autonomous Database Details page, from the More Actions drop-downlist, select Rotate Encryption Key.
5. On the Rotate Encryption Key dialog, click Rotate Encryption Key.
Chapter 26View Details of an Autonomous Database
26-5
Set the Password of an Autonomous Database's ADMINUser
Follow these steps to set the ADMIN database user's password for an autonomousdatabase on an Oracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to administer.
4. From the More Actions drop-down list, select Admin Password.
The Admin Password dialog opens.
5. Enter a password for the Autonomous Database.
The password must meet the following criteria:
• Contains from 12 to 30 characters
• Contains at least one lowercase letter
• Contains at least one uppercase letter
• Contains at least one number
• Does not contain the double quotation mark (")
• Does not contain the string "admin", regardless of case
• Is not one of the last four passwords used for the database
• Is not a password you previously set within the last 24 hours
6. Enter the password again in the Confirm Password field.
7. Click Update.
Scale the CPU Core Count or Storage of an AutonomousDatabase
Follow these steps to scale the CPU core count or storage an autonomous databaseon an Oracle Exadata Cloud@Customer system up or down.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to view details.
4. Click Scale Up/Down.
5. Enter a new value for CPU Core Count or Storage between 1 and 128. Thenumber you enter represents the desired total (final) value for your database'sCPU core count or storage.
Chapter 26Set the Password of an Autonomous Database's ADMIN User
26-6
The maximum number of CPU Core Count or Storage depends on theinfrastructure shape and what is already consumed by other AutonomousDatabases.
6. Click Update.
Related Topics
• Service Limits
Enable or Disable Auto Scaling for an AutonomousDatabase
Oracle Autonomous Database on Oracle Exadata Cloud@Customer systems providesan auto scaling feature that automatically increases the number of cores anautomonomous database during periods of increased demand and, as demand returnsto normal, automatically decreases the number of cores down to the databases's basenumber.
Note the following points regarding the auto scaling feature:
• With auto scaling enabled, the database can use up to three times more CPU andIO resources than specified by the number of OCPUs currently shown in the ScaleUp/Down dialog.
• If auto scaling is disabled while more CPU cores are in use than the database'scurrently assigned number of cores, then Autonomous Database scales thenumber of CPU cores in use down to the assigned number.
• Enabling auto scaling does not change the concurrency and parallelism settingsfor the predefined services.
Follow these steps to enable or disable auto scaling for an autonomous database.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to view details.
4. Click Scale Up/Down.
5. Check Auto Scaling to enable the auto scaling feature, or uncheck Auto Scalingto disable the feature.
6. Click Update.
Move an Autonomous Database to Another CompartmentFollow these steps to move an autonomous database on an Oracle ExadataCloud@Customer system from one compartment to another compartment.
Chapter 26Enable or Disable Auto Scaling for an Autonomous Database
26-7
Note:
• To move an autonomous database you must have the right to manage itin its current compartment and in the compartment you are moving it to.
• As soon as you move an autonomous database to a differentcompartment, the policies that govern the new compartment applyimmediately and affect access to the autonomous database. Therefore,both your and other Oracle Cloud users' access to it may change,depending on the policies governing the user account's access toresources. For example, a user may lose the ability to manage theautonomous databae, given its new compartment.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to move.
4. From the More Actions drop-down list, select Move Resource.
5. Select the new compartment.
6. Click Move Resource.
Stop or Start an Autonomous DatabaseFollow these steps to stop or start an autonomous database on an Oracle ExadataCloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to view details.
4. Click Stop (or Start).
When you stop your Autonomous Database, billing stops for CPU usage. Billingfor storage continues when the database is stopped.
5. Confirm that you want to stop or start your Autonomous Database in theconfirmation dialog.
Note:
Stopping your database has the following consequences:
• On-going transactions are rolled back.
• You will not be able to connect to your database using database clientsor tools.
Chapter 26Stop or Start an Autonomous Database
26-8
Restart an Autonomous DatabaseTo resolve some autonomous database issues with minimal downtime on ExadataCloud@Customer systems, you can restart the database.
Restarting an autonomous database on an Oracle Exadata Cloud@Customer systemis equivalent to manually stopping and then starting the database. Using restart allowsyou to minimize downtime and requires only a single action.
Follow these steps to restart an autonomous database.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to restart.
4. Click Restart.
5. Confirm that you want to restart your Autonomous Database in the confirmationdialog.
The system stops and then immediately starts your database.
Back Up an Autonomous Database ManuallyOracle Autonomous Database automatically backs up autonomous databases on anOracle Exadata Cloud@Customer system. In addition, you can manually back up anautonomous database should the need arise.
Note:
During the backup operation, your autonomous database remains available.However, lifecycle management operations such as stopping it, scaling it, orterminating it are disabled.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to back up.
4. On the Details page, under Resources, click Backups.
5. Click Create Manual Backup.
6. In the Create Manual Backup dialog, enter a name for your backup. Avoid enteringconfidential information.
7. Click Update.
The backup operation begins. This operation may take several hours to complete,depending on the size of the database.
Optionally, you can check the state of your backup in the list of backups on thedatabase details page. For some states, an information icon is displayed to provide
Chapter 26Restart an Autonomous Database
26-9
additional details regarding the state or ongoing operations like deletions. The backuphas one of the following states:
• Creating
• Active
• Deleting
• Deleted
• Failed
Restore an Autonomous DatabaseYou can use any existing manual or automatic backup to restore and recover anautonomous database on an Oracle Exadata Cloud@Customer system, or you canrestore and recover the database to any point in time during the retention period of itsautomatic backups.
Note:
Restoring an autonomous database puts the database in the unavailablestate during the restore operation. You cannot connect to a database in thisstate. The only lifecycle management operation supported in the unavailablestate is terminate.
• Restore from a Backup
• Restore to a Point in Time
Restore from a BackupFollow these steps to restore an autonomous database on an Oracle ExadataCloud@Customer system from a specific backup.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwant to clone.
4. From the More Actions drop-down list, select Restore.
5. Specify the date range for a list of backups to display.
6. Select the backup.
7. Click Restore.
Restore to a Point in TimeFollow these steps to restore an autonomous database on an Oracle ExadataCloud@Customer system to a specific point in time.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
Chapter 26Restore an Autonomous Database
26-10
3. In the list of Autonomous Databases, click the display name of the database youwant to restore.
4. From the More Actions drop-down list, select Restore.
5. Click Specify Timestamp.
6. Enter a timestamp.
Your Autonomous Database decides which backup to use for faster recovery. Thetimestamp input allows you to specify precision to the seconds level (YYYY-MM-DDHH:MM:SS GMT).
7. Click Restore.
Clone an Autonomous DatabaseFollow these steps to clone an autonomous database on an Oracle ExadataCloud@Customer system.You can use the cloning feature to create a point-in-time copy of your AutonomousDatabase for purposes such as testing, development, or analytics. To clone only thedatabase schema of your source database, choose the metadata clone option.
Clone Types
The clone feature offers the following two types of Autonomous Database clones:
• The full-clone option creates a database that includes the metadata and data fromthe source database.
• The metadata-clone option creates a database that includes only the metadatafrom the source database.
Steps
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwant to clone.
4. From the More Actions drop-down list, select Create Clone.
5. On the Clone Autonomous Database page, provide the following information:
In the Clone Type section, select the type of clone you want to create. Chooseeither Full Clone or Metadata Clone.
Provide basic information for the Autonomous Database.
• Choose a compartment: Your current compartment is the default selectionbut you can select a different compartment in which to create the clone fromthe drop-down list.
• Source database name: The name of the source database displays in theread-only Source database name field.
• Display name: Enter a description or other information to identify thedatabase clone. You can change the display name any time and it does nothave to be unique. Avoid entering confidential information.
Chapter 26Clone an Autonomous Database
26-11
• Database name: Enter a database name for the clone that contains onlyletters and numbers, begins with a letter, and does not exceed 14 characters.Avoid entering confidential information.
• Choose autonomous container database in compartment: You can chooseto create the database clone in the same compartment and containerdatabase as the source database, or you can choose a different compartmentby clicking CHANGE COMPARTMENT, and a different container database bychoosing one from the drop-down list.
Configure the database.
• OCPU Count: You can enable up to the number of cores available for yourcloned Autonomous Database.
• Storage (TB): Specify the amount of storage, in terabytes, that you wantto make available to your cloned Autonomous Database, and it depends onthe storage available to use. For full clones, the size of the source databasedetermines the minimum amount of storage you can make available.
• Auto scaling: Enabling auto scaling allows Oracle to use upto 3 times thenumber of OCPUs for processing workload if required.
Create administrator credentials.
Set the password for the Autonomous Database administrator user by entering apassword that meets the following criteria.
• Password cannot be one of the three most recently used passwords of thesource database
• Between 12 and 30 characters long
• Contains at least one lowercase letter
• Contains at least one uppercase letter
• Contains at least one number
• Does not contain the double quotation mark (")
• Does not contain the string "admin", regardless of casing
Use this password when accessing the service console and when using a SQLclient tool.
Access control list: Add or modify entries, as applicable.
Access control list will automatically initialize with the same settings configured onthe source Autonomous Database from which the clone is being created. You canchange the access control list to enable or disable database level access controlor add or modify entries to the access control list.
Advanced Options:
Encryption Key: ADB inherits encryption settings from the parent ACD. If theparent ACD is configured for customer-managed OKV based encryption, then thechild ADB will also have TDE Master Key generated and managed in the sameOKV wallet used to store ACD master keys.
Additionally, any backups taken on the Autonomous Database will have the vaultkey associated with it.
Tags: Optionally, you can apply tags. If you have permissions to create a resource,you also have permissions to apply free-form tags to that resource. To apply adefined tag, you must have permissions to use the tag namespace. For more
Chapter 26Clone an Autonomous Database
26-12
information about tagging, see Resource Tags. If you are not sure if you shouldapply tags, skip this option (you can apply tags later) or ask your administrator.Avoid entering confidential information.
6. Click Clone Autonomous Database.
The Console displays the details page for the new clone of your database and theservice begins provisioning the Autonomous Database. Note the following:
• The new clone displays the Provisioning lifecycle state until the provisioningprocess completes.
• The source database remains in the Available lifecycle state.
• Backups associated with the source database are not cloned for either the full-clone or the metadata-clone option.
Terminate an Autonomous DatabaseFollow these steps to terminate an Autonomous Database on an Oracle ExadataCloud@Customer system.
WARNING:
Terminating an Autonomous Database permanently deletes it. The databasedata will be lost when the system is terminated. However, automatic backupsare not deleted if you have chosen Recovery Appliance or NFS as a backupdestination. You can delete automatic backups directly from the RecoveryAppliance or NFS.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to terminate.
4. From the More Actions drop-down list, select Terminate.
5. Confirm that you wish to terminate your Autonomous Database in the confirmationdialog.
6. Click Terminate Autonomous Database.
Using the API to Manage Autonomous DatabasesFor information about using the API and signing requests, see REST APIs andSecurity Credentials. For information about SDKs, see Software Development Kits andCommand Line Interface.
The following table lists the REST API endpoints to manage Autonomous Databases.
Operation REST API Endpoint
Create an Autonomous Database CreateAutonomousDatabase
Chapter 26Terminate an Autonomous Database
26-13
Operation REST API Endpoint
View a list of Autonomous Databases ListAutonomousDatabases
View details of an Autonomous Database GetAutonomousDatabase
Set the password of an AutonomousDatabase's ADMIN user
UpdateAutonomousDatabase
Scale the CPU core count or storage of anAutonomous Database
UpdateAutonomousDatabase
Enable or disable auto scaling for anAutonomous Database
UpdateAutonomousDatabase
Move an Autonomous Database to anothercompartment
ChangeAutonomousDatabaseCompartment
Stop or start an Autonomous Database StartAutonomousDatabase
Stop or start an Autonomous Database StopAutonomousDatabase
Restart an Autonomous Database RestartAutonomousDatabase
Back up an Autonomous Database manually CreateAutonomousDatabaseBackup
View the list of Autonomous Databasebackups
ListAutonomousDatabaseBackups
Restore an Autonomous Database RestoreAutonomousDatabase
Clone an Autonomous Database CreateAutonomousDatabase
Terminate an Autonomous Database DeleteAutonomousDatabase
Monitor Performance with Autonomous Database MetricsYou can monitor the health, capacity, and performance of your AutonomousDatabases with metrics, alarms, and notifications. You can use Oracle CloudInfrastructure console or Monitoring APIs to view metrics.
• View Top Six Metrics for an Autonomous DatabaseDisplays the top six metrics that are available in the metrics section on theAutonomous Database details page.
• View Aggregated Metrics for Autonomous Databases in a CompartmentLearn to view aggregated metrics for Autonomous Databases in a compartment.
• Autonomous Database Metrics and DimensionsYou can limit the instances where you see metrics with dimensions. The availabledimensions include: workload type, instance display name, region, and theinstance OCID.
View Top Six Metrics for an Autonomous DatabaseDisplays the top six metrics that are available in the metrics section on theAutonomous Database details page.
To view metrics you must have the required access as specified in an Oracle CloudInfrastructure policy (whether you're using the Console, the REST API, or other tools).See Getting Started with Policies for information on policies.
Perform the following prerequisite steps as necessary:
Chapter 26Monitor Performance with Autonomous Database Metrics
26-14
• Open the Oracle Cloud Infrastructure console by clicking the hamburger menunext to Oracle Cloud.
• From the Oracle Cloud Infrastructure left navigation list click Oracle Database >Exadata Cloud@Customer.
• On the Autonomous Databases page select an Autonomous Database from thelinks under the Name column.
To view metrics for an Autonomous Database instance:
1. On the Autonomous Database Details page, under Resources, click Metrics.
2. There is a chart for each metric. In each chart, you can select the Interval andStatistic or use the default values.
3. To create an alarm on a metric, click Options and select Create an Alarm on thisQuery.
See Managing Alarms for information on setting and using alarms.
For more information about metrics see Database Metrics.
You can also use the Monitoring API to view metrics. See Monitoring API for moreinformation.
View Aggregated Metrics for Autonomous Databases in aCompartment
Learn to view aggregated metrics for Autonomous Databases in a compartment.
To view metrics you must have the required access as specified in an Oracle CloudInfrastructure policy (whether you're using the Console, the REST API, or other tool).See Getting Started with Policies for information on policies
Perform the following prerequisite steps as necessary:
• Open the Oracle Cloud Infrastructure console by clicking the hamburger menunext to Oracle Cloud.
• From the left navigation list click Solutions and Platform > Monitoring > ServiceMetrics.
To use the metrics service to view Autonomous Database metrics:
1. On the Service Metrics page, under Compartment select your compartment.
2. On the Service Metrics page, under Metric Namespace selectoci_autonomous_database.
3. If there are multiple Autonomous Databases in the compartment you can showmetrics aggregated across the Autonomous Databases by selecting AggregateMetric Streams.
4. If you want to limit the metrics you see, next to Dimensions click Add (click Edit ifyou have already added dimensions).
a. In the Dimension Name field select a dimension.
b. In the Dimension Value field select a value.
c. Click Done.
Chapter 26Monitor Performance with Autonomous Database Metrics
26-15
d. In the Edit dimensions dialog click +Additional Dimension to add an additionaldimension. Click x to remove a dimension.
To create an alarm on a specific metric, click Options and select Create an Alarm onthis Query. See Managing Alarms for information on setting and using alarms.
Autonomous Database Metrics and DimensionsYou can limit the instances where you see metrics with dimensions. The availabledimensions include: workload type, instance display name, region, and the instanceOCID.
Use dimensions by selecting values in the Oracle Cloud Infrastructure ConsoleService Metrics page or by setting dimension values with the API. See ViewAggregated Metrics for Autonomous Databases in a Compartment to view metricsand to select metric dimensions.
See Database Metrics for a list of the database metrics and dimensions.
Chapter 26Monitor Performance with Autonomous Database Metrics
26-16
27Connecting to Autonomous Databases
Applications and tools connect to an autonomous database using Oracle Net Services(also known as SQL*Net). Oracle Net Services enables a network session from aclient application to an Oracle Database server.
When a network session is established, Oracle Net Services acts as the data courierfor both the client application and the database. It is responsible for establishing andmaintaining the connection between the client application and the database, as wellas exchanging messages between them. It supports a variety of connection types toautonomous databases, including:
• Oracle Call Interface (OCI), which is used by many applications written inC language. Examples include Oracle utilities such as Oracle SQL*Plus,SQL*Loader, and Oracle Data Pump.
• ODBC drivers, which can be used by applications running on Microsoft Windows,are layered over Oracle Call Interface (OCI).
• JDBC OCI, which can be used by Java language applications, is layered overOracle Call Interface (OCI). The Oracle SQLcl command-line interface uses JDBCOCI.
• JDBC Thin Driver, also for Java applications, is a pure Java driver. Oracle SQLDeveloper supports JDBC Thin Driver connections.
Third-party products and custom applications can use any of these connection types.
Oracle Autonomous Database provides several pairs of database services to usewhen connecting to autonomous databases. In each pair, one of the pair providesa secure TCP (TCPS) connection using the TLS protocol, and the other provides aTCP connection. In all other respects, the two members of a pair are the same. Toensure security of data in transit, Oracle strongly recommends that you use a secureconnection, even if the database is only available through a private network. If you arefamiliar with using an Oracle Database within your own data center, you may not havepreviously used these secure connections.
To provide the secure TCPS connection, certification authentication uses an encryptedkey stored in a wallet on both the client (where the application is running) and theserver (where the autonomous database is running). The key on the client must matchthe key on the server to make a connection. A wallet contains a collection of files,including the key and other information needed to connect to your database . Allcommunications between the client and the server are encrypted.
• Download the Wallet for an Autonomous Database
• Get the APEX and SQL Developer Web URLs for an Autonomous Database
Download the Wallet for an Autonomous DatabaseFollow these steps to download the wallet for an autonomous database on an OracleExadata Cloud@Customer system.
27-1
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the databasewhose wallet you wish to download.
4. Click DB Connections.
5. Select the DB Connection option.
6. In the Download Wallet dialog, enter a wallet password in the Password field andconfirm the password in the Confirm Password field.
The password must be at least 8 characters long and must include at least 1 letterand either 1 numeric character or 1 special character.
Note:
This password protects the downloaded Client Credentials wallet. Thiswallet is not the same as the Transparent Data Encryption (TDE) walletfor the database; therefore, use a different password to protect the ClientCredentials wallet.
7. Click Download to save the client security credentials zip file.
By default the filename is Wallet_databasename.zip. You can save this file as anyfilename you want.
You must protect this file to prevent unauthorized database access.
The zip file includes the following:
• tnsnames.ora and sqlnet.ora: Network configuration files storing connectdescriptors and SQL*Net client side configuration.
• cwallet.ora and ewallet.p12: Auto-open SSO wallet and PKCS12 file. PKCS12file is protected by the wallet password provided in the UI.
• keystore.jks and truststore.jks: Java keystore and truststore files. They areprotected by the wallet password provided while downloading the wallet.
• ojdbc.properties: Contains the wallet related connection property required forJDBC connection. This should be in the same path as tnsnames.ora.
Note:
Wallet files, along with the Database user ID and password, provide accessto data in your autonomous database. Store wallet files in a secure location.Share wallet files only with authorized users. If wallet files are transmittedin a way that might be accessed by unauthorized users (for example, overpublic email), transmit the wallet password separately and securely.
Chapter 27Download the Wallet for an Autonomous Database
27-2
Get the APEX and SQL Developer Web URLs for anAutonomous Database
Follow these steps to get the URLs to use to connect to APEX (Oracle ApplicationExpress) and Oracle SQL Developer Web in an autonomous database on an OracleExadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the databasewhose APEX and SQL URLs you wish to get.
4. Click DB Connections.
5. Select the Application Connection option.
6. Application URLs are displayed in plain text in the Application URL field. Copythe URL string using the Copy link.
Paste the URL into a browser running on a system with network access to yourautonomous database.
Chapter 27Get the APEX and SQL Developer Web URLs for an Autonomous Database
27-3
28Using Autonomous Data Guard withAutonomous Database on ExadataCloud@Customer
Learn how to enable a Data Guard association between databases, change the roleof a database in a Data Guard association using either a switchover or a failoveroperation, and reinstate a failed database.
• Enabling Autonomous Data Guard on an Autonomous Container DatabaseWhen you enable Data Guard, a separate Data Guard association is created forthe primary and the standby database.
• Enabling Autonomous Data Guard on an Autonomous DatabaseAutonomous Databases inherit Data Guard settings from the parent containerdatabase.
• Maintenance Scheduling and Patching Data Guard Enabled AutonomousContainer DatabaseFollow these steps to change the maintenance schedule of a Data Guard enabledAutonomous Container Database.
Enabling Autonomous Data Guard on an AutonomousContainer Database
When you enable Data Guard, a separate Data Guard association is created for theprimary and the standby database.
• Create an Autonomous Data Guard Enabled Autonomous Container DatabaseFollow these steps to create an Autonomous Data Guard Enabled AutonomousContainer Database on an Oracle Exadata Cloud@Customer system.
• View Details of a Data Guard Enabled Primary or Standby Autonomous ContainerDatabaseFollow these steps to view detailed information about a primary or standbyAutonomous Container Database on an Oracle Exadata Cloud@Customersystem.
• Perform a Failover to Standby Autonomous Container DatabaseInitiate a failover operation by using the Data Guard association of the standbydatabase.
• Perform a Switchover to Standby or Primary Autonomous Container DatabaseInitiate a switchover operation by using the Data Guard association of the primarydatabase.
• Reinstate Data Guard Enabled Standby Autonomous Container DatabaseAfter you fail over a primary database to its standby, the standby assumes theprimary role and the old primary is identified as a disabled standby.
28-1
• Terminate a Data Guard Enabled Primary Autonomous Container DatabaseFollow these steps to terminate an autonomous container database on an OracleExadata Cloud@Customer system.
• Terminate a Data Guard Enabled Standby Autonomous Container DatabaseFollow these steps to terminate an autonomous container database on an OracleExadata Cloud@Customer system.
• Operations Performed Using the APIsLearn how to use the API to manage Autonomous Data Guard EnabledAutonomous Container Database.
Create an Autonomous Data Guard Enabled Autonomous ContainerDatabase
Follow these steps to create an Autonomous Data Guard Enabled AutonomousContainer Database on an Oracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. Click Create Autonomous Container Database.
The Create Autonomous Container Database page is displayed.
4. Provide the following basic information:
• Compartment: Choose the compartment in which your autonomous containerdatabase will be created.
• Display Name: Enter a user-friendly description or other information that helpsyou easily identify the autonomous container database. The display namedoes not have to be unique. Avoid entering confidential information.
5. Select the Autonomous Exadata VM Cluster you wish to use to create yourautonomous container database.
6. Under Configure Autonomous Data Guard, select the Enable AutonomousData Guard checkbox and provide the following details.
• Peer Autonomous Container Database Compartment: Choose thecompartment in which your standby autonomous container database will becreated.
• Display Name: Enter a user-friendly description or other information thathelps you easily identify the autonomous container database. The displayname does not have to be unique. Avoid entering confidential information.
• Select peer Autonomous Exadata VM Cluster: Specify the following valuesfor the standby:
– Peer Region: Currently, the peer region is auto-populated and youcannot change it. The primary and secondary databases must run on twoAutonomous Exadata VM Cluster on two separate Exadata infrastructureseven if they are in the same region.
– Peer Exadata: Select the Exadata Cloud@Customer infrastructurewhere the standby database will be created. Click the CHANGECOMPARTMENT hyperlink to choose a compartment.
Chapter 28Enabling Autonomous Data Guard on an Autonomous Container Database
28-2
– Peer Autonomous Exadata VM Cluster: Select the Autonomous VMCluster in which the standby ACD must be created. Click the CHANGECOMPARTMENT hyperlink to choose a compartment.
• Data Protection Mode: Specify the protection mode used for this Data Guardassociation.
– Maximum Performance: Provides the highest level of data protection thatis possible without compromising the availability of a primary database.
– Maximum Availability: Provides the highest level of data protection thatis possible without affecting the performance of a primary database. Thisis the default protection mode.See Oracle Data Guard Concepts and Administration for more informationabout protection modes.
7. Optionally, you can configure an automatic maintenance schedule.
a. Click Modify Schedule.
b. Optionally, you can change the maintenance patch type. Select eitherRelease Update (RU) or Release Update Revision (RUR).
Note:
You can set maintenance type only for primary.
Release Update (RU): Autonomous Database installs only the most currentrelease update.
Release Update Revision (RUR): Autonomous Database installs the releaseupdate plus additional fixes.
For more information, see "management operations.
c. To configure the maintenance schedule, select Specify a schedule.
Choose your preferred month, week, weekday, and start time for autonomouscontainer database maintenance.
• Under Week of the month, specify which week of the month maintenancewill take place. Weeks start on the 1st, 8th, 15th, and 22nd days of themonth, and have a duration of 7 days. Weeks start and end based oncalendar dates, not days of the week. Maintenance cannot be scheduledfor the fifth week of months that contain more than 28 days.
• Under Day of the week, specify the day of the week on which themaintenance will occur.
• Under Start hour, specify the hour during which the maintenance run willbegin.
d. Click Save Changes.
8. Select a Backup Destination Type:
• Object Storage: Stores backups in an Oracle-managed object storagecontainer on Oracle Cloud Infrastructure. Optionally, you can use this fieldto specify your corporate HTTP proxy. We recommend using an HTTP proxywhen possible for enhanced security.
Chapter 28Enabling Autonomous Data Guard on an Autonomous Container Database
28-3
• Network File System (NFS): Stores backups in one of your previouslydefined backup destinations that uses Network File System (NFS) storage.
– Select a Backup Destination.
• Recovery Appliance: Not Supported.
9. The following Advanced Options are available:
• Backup retention period: Customize the retention period for automaticbackups.
• Encryption Key: The customer-managed encryption key is not available forAutonomous Container Databases with Data Guard feature enabled, andtherefore ACDs use the default Oracle-managed encryption keys.
• Tags: Optionally, you can apply tags. If you have permissions to create aresource, you also have permissions to apply free-form tags to that resource.To apply a defined tag, you must have permissions to use the tag namespace.For more information about tagging, see Resource Tags. If you are not sure ifyou should apply tags, skip this option (you can apply tags later) or ask youradministrator. Avoid entering confidential information.
10. Click Create Autonomous Container Database.
View Details of a Data Guard Enabled Primary or StandbyAutonomous Container Database
Follow these steps to view detailed information about a primary or standbyAutonomous Container Database on an Oracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of thedatabase you wish to view details.
4. In the Autonomous Container Database Details page, check the Autonomous DataGuard association status and peer database state.
5. Under Resources, click Autonomous Data Guard to view association details.
Perform a Failover to Standby Autonomous Container DatabaseInitiate a failover operation by using the Data Guard association of the standbydatabase.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of theinfrastructure resource you are interested in.
4. Click the name of the standby database.
5. Under Resources, click Data Guard Associations.
6. For the Data Guard association on which you want to perform a failover, click theActions icon (three dots), and then click Failover.
Chapter 28Enabling Autonomous Data Guard on an Autonomous Container Database
28-4
7. In the Confirm Manual Failover to Standby dialog box, enter the name of theAutonomous Container Database you want to failover, and then click Failover.
Note:
After successful completion of failover, the standby ACDs role willchange to primary and the primay's role will become disabled-standby.
Perform a Switchover to Standby or Primary Autonomous ContainerDatabase
Initiate a switchover operation by using the Data Guard association of the primarydatabase.
• You can perform Switchover only when both primary and standby are in availablestate.
• You cannot perform switchover if patching or maintenance is in progress onprimary or standby.
• After switchover, the maintenance preference for new standby and primary willremain same as old standby and primary.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of theinfrastructure resource you are interested in.
4. Click the name of the primary or secondary database.
5. Under Resources, click Data Guard Associations.
6. For the Data Guard association on which you want to perform a switchover, clickthe Actions icon (three dots), and then click Switchover.
7. In the Confirm Switchover to Standby dialog box, click Swichover.
This database should now assume the role of the standby, and the standby shouldassume the role of the primary in the Data Guard association.
Reinstate Data Guard Enabled Standby Autonomous ContainerDatabase
After you fail over a primary database to its standby, the standby assumes the primaryrole and the old primary is identified as a disabled standby.
After the operations team correct the cause of failure, you can reinstate the faileddatabase as a functioning standby for the current primary by using its Data Guardassociation. you can reinstate the failed database as a functioning standby for thecurrent primary by using its Data Guard association.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
Chapter 28Enabling Autonomous Data Guard on an Autonomous Container Database
28-5
3. In the list of Autonomous Container Databases, click the display name of theinfrastructure resource you are interested in.
4. Click the name of the failed database.
5. Under Resources, click Data Guard Associations.
6. For the Data Guard association on which you want to reinstate this database, clickthe Actions icon (three dots), and then click Reinstate.
7. In the Reinstate Database dialog box, click Reinstate.
This database should now be reinstated as the standby in the Data Guardassociation.
Terminate a Data Guard Enabled Primary Autonomous ContainerDatabase
Follow these steps to terminate an autonomous container database on an OracleExadata Cloud@Customer system.
You must terminate all Autonomous Databases within a container database beforeyou can terminate the container database itself. Terminating Autonomous ContainerDatabase will disable Autonomous Data Guard, which affects high availability anddisaster recovery of your Autonomous Databases.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
3. In the list of Autonomous Container Databases, click the display name of theinfrastructure resource you are interested in.
4. In the Autonomous Container Database Details page, select Terminate from theMore Actions drop-down list.
5. Click Terminate.
6. In the confirmation dialog, type the name of the Autonomous Container Database,and then click Terminate Autonomous Container Database.
Terminate a Data Guard Enabled Standby Autonomous ContainerDatabase
Follow these steps to terminate an autonomous container database on an OracleExadata Cloud@Customer system.
You can terminate a standby Autonomous Container Database even if there arestandby Autonomous Databases inside it. However, you cannot terminate standbyAutonomous Databases inside a standby Autonomoous Container Database. Toterminate a standby Autonomoous Database, you must first terminate the primaryAutonomous Database. Terminating Autonomous Container Database will disableAutonomous Data Guard, which affects high availability and disaster recovery of yourAutonomous Databases.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
Chapter 28Enabling Autonomous Data Guard on an Autonomous Container Database
28-6
3. In the list of Autonomous Container Databases, click the display name of theinfrastructure resource you are interested in.
4. In the Autonomous Container Database Details page, select Terminate from theMore Actions drop-down list.
5. Click Terminate.
6. In the confirmation dialog, type the name of the Autonomous Container Database,and then click Terminate Autonomous Container Database.
Operations Performed Using the APIsLearn how to use the API to manage Autonomous Data Guard Enabled AutonomousContainer Database.
For information about using the API and signing requests, see "REST APIs" and"Security Credentials". For information about SDKs, see "Software Development Kitsand Command Line Interface".
The following table lists the REST API endpoints to manage Autonomous Data GuardEnabled Autonomous Container Database.
Operation REST API Endpoint
Creates Autonomous Container Databases(update to the existing API)
CreateAutonomousContainerDatabase
View details of the specified AutonomousContainer Database
GetAutonomousContainerDatabase
(update to the existing API) deleteAutonomousContainerDatabase
View a list of Autonomous ContainerDatabases with Autonomous Data Guardassociations
ListAutonomousContainerDatabaseDataguardAssociations
Fetch details of an Autonomous ContainerDatabase Autonomous Data Guardassociations
GetAutonomousContainerDatabaseDataguardAssociation
Fail over the standby AutonomousContainer Database identified bythe autonomousContainerDatabaseIdparameter to the primary AutonomousContainer Database after the existing primaryAutonomous Container Database fails orbecomes unreachable.
FailoverAutonomousContainerDatabaseDataguardAssociation
Switch over the primary AutonomousContainer Database of an Autonomous DataGuard peer association to standby role. Thestandby Autonomous Container Databaseassociated withautonomousContainerDatabaseDataguardAssociationId assumes the primaryAutonomous Container Database role.
SwitchoverAutonomousContainerDatabaseDataguardAssociation
Reinstate a disabled standby AutonomousContainer Database identified bythe autonomousContainerDatabaseIdparameter to an active standby AutonomousContainer Database.
ReinstateAutonomousContainerDatabaseDataguardAssociation
Chapter 28Enabling Autonomous Data Guard on an Autonomous Container Database
28-7
Operation REST API Endpoint
View a list of the Autonomous Data Guard-enabled databases associated with thespecified Autonomous Database.
ListAutonomousDatabaseDataguardAssociations
Fetch details of an Autonomous DatabaseAutonomous Data Guard associations
GetAutonomousDatabaseDataguardAssociation
Fetches details such as peer database role,lag time, transport lag, and state
GetAutonomousDatabase
Related Topics
• REST APIs
• Security Credentials
• Software Development Kits and Command Line Interface
Enabling Autonomous Data Guard on an AutonomousDatabase
Autonomous Databases inherit Data Guard settings from the parent containerdatabase.
• View Autonomous Data Guard EnablementAutonomous Data Guard settings are configured on the Autonomous ContainerDatabases in which the databases are running.
• Create an Autonomous Data Guard Enabled Autonomous Database
• View Details of a Data Guard Enabled Primary or Standby Autonomous DatabaseFollow these steps to view detailed information about a primary or standbyAutonomous Database on an Oracle Exadata Cloud@Customer system.
View Autonomous Data Guard EnablementAutonomous Data Guard settings are configured on the Autonomous ContainerDatabases in which the databases are running.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Container Databases.
This page displays if an autonomous database is Data Guard enabled or not, andif enabled, then the role of the database in the Data Guard association.
Create an Autonomous Data Guard Enabled Autonomous DatabaseFollow these steps to create an autonomous database on an Oracle ExadataCloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. Click Create Autonomous Database.
Chapter 28Enabling Autonomous Data Guard on an Autonomous Database
28-8
4. In the Create Autonomous Database dialog, enter the following:
Basic Database Information
• Compartment: Select the compartment of the Autonomous Database.
• Display Name: A user-friendly description or other information that helps youeasily identify the resource. The display name does not have to be unique.Avoid entering confidential information.
• Database Name: The database name must consist of letters and numbersonly, starting with a letter. The maximum length is 14 characters. Avoidentering confidential information.
Workload Type
Select the desired workload type. See About Autonomous Data Warehouse andAbout Autonomous Transaction Processing for information about each workloadtype.
Autonomous Container Database: Select the Autonomous Data Guard-enabled Autonomous Container Databases checkbox, and then select anAutonomous Container Database.
Compartment: Specify the compartment containing the Autonomous ContainerDatabase you wish to use.
Database CPU Core Count and Storage Configuration
• OCPU Count: The total number of cores available to all databases within theAutonomous Exadata Infrastructure depends on the infrastructure shape andwhat is already allocated to other Autonomous Databases.Deselect Auto Scaling to disable auto-scaling. By default, auto-scaling isenabled to allow the system to automatically use up to three times more CPUand IO resources to meet workload demand.
• Storage (TB): Specify the storage you wish to make available to yourAutonomous Database, in terabytes. The available storage depends on theinfrastructure shape and what is already consumed by other AutonomousDatabases.
Administrator Credentials
Set the password for the Autonomous Database Admin user by entering apassword that meets the following criteria. You use this password when accessingthe Autonomous Database service console and when using an SQL client tool.
• Contains from 12 to 30 characters
• Contains at least one lowercase letter
• Contains at least one uppercase letter
• Contains at least one number
• Does not contain the double quotation mark (")
• Does not contain the string "admin", regardless of casing
Configure network access
You can optionally create an ACL during database provisioning, or at any timethereafter.
a. Cick Modify Access Control.
Chapter 28Enabling Autonomous Data Guard on an Autonomous Database
28-9
b. In the Edit Access Control List dialog, select the Enable database levelaccess control checkbox.
c. Under the Primary database access control list, specify the following typesof addresses in your list by using the IP notation type drop-down selector:IP Address allows you to specify one or more individual public IP addresses.Use commas to separate your addresses in the input field.
CIDR Block allows you to specify one or more ranges of public IP addressesusing CIDR notation. Use commas to separate your CIDR block entries in theinput field.
d. Under Standby database access control, do the following:(Default) Same as primary database: Leave as is if you want the same accesscontrol list for the secondary database.
Define standby database access control: Initialized with the same details asprimary. Add or modify entries, as applicable.
Advanced Options
Tags: Optionally, you can apply tags. If you have permission to create a resource,then you also have permissions to apply free-form tags to that resource. To applya defined tag, you must have permissions to use the tag namespace. For moreinformation about tagging, see Resource Tags. If you are not sure if you shouldapply tags, skip this option (you can apply tags later) or ask your administrator.Avoid entering confidential information.
Encryption Key: ADB inherits encryption settings from the parent ACD.
5. Click Create Autonomous Database.
Note:
The following naming restrictions apply to Autonomous TransactionProcessing and Autonomous Data Warehouse databases:
• Names associated with databases terminated within the last 60 dayscannot be used when creating a new database.
• A database name cannot be used concurrently for both anAutonomous Data Warehouse and an Autonomous TransactionProcessing database.
View Details of a Data Guard Enabled Primary or StandbyAutonomous Database
Follow these steps to view detailed information about a primary or standbyAutonomous Database on an Oracle Exadata Cloud@Customer system.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Databases, click the display name of the database youwish to view details.
Chapter 28Enabling Autonomous Data Guard on an Autonomous Database
28-10
4. In the Autonomous Database Details page, check the Autonomous Data Guardassociation status and peer database state.
5. Under Resources, click Autonomous Data Guard to view association details.
Maintenance Scheduling and Patching Data Guard EnabledAutonomous Container Database
Follow these steps to change the maintenance schedule of a Data Guard enabledAutonomous Container Database.
• Configure Automatic Maintenance Schedule for a Data Guard EnabledAutonomous Container Database
• View the Next Scheduled Maintenance Run of a Data Guard Enabled AutonomousContainer Database
• View the Maintenance History of a Data Guard Enabled Autonomous ContainerDatabase
• Immediately Patch a Data Guard Enabled Autonomous Container Database
• Reschedule or Skip scheduled Maintenance for Data Guard Enabled AutonomousContainer Database
Configure Automatic Maintenance Schedule for a Data Guard EnabledAutonomous Container Database
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Container Databases, click the display name of thecontainer database you are interested in.
4. On the Autonomous Container Database details page, under Maintenance, clickthe edit link in the Maintenance Details field. In the Edit Automatic Maintenancedialog that opens, you can configure both the maintenance schedule and the patchtype.
Note:
The standby database will have No preference by default. StandbyMaintenance depends on the primary maintenance schedule.
5. Optionally, you can change the maintenance patch type. To edit this setting, selecteither Release Update (RU) or Release Update Revision (RUR).
Release Update (RU): Autonomous Database installs only the most currentrelease update.
Release Update Revision (RUR): Autonomous Database installs the releaseupdate plus additional fixes.
Chapter 28Maintenance Scheduling and Patching Data Guard Enabled Autonomous Container Database
28-11
Note:
Standby will be always patched before primary and the default gapbetween standby and primary is 7 days. You have have an option tochange the default gap to anytime between 1 - 7 days.
6. To configure the maintenance schedule, select Specify a schedule in the Configurethe automatic maintenance schedule section. Choose your preferred month, week,weekday, and start time for container database maintenance.
• Under Maintenance months, specify at least one month for each maintenancequarter during which you want Autonomous Exadata Infrastructuremaintenance to occur.
Note:
Maintenance quarters begin in February, May, August, andNovember, with the first maintenance quarter of the year beginningin February.
• Under Week of the month, specify which week of the month maintenance willtake place. Weeks start on the 1st, 8th, 15th, and 22nd days of the month,and have a duration of 7 days. Weeks start and end based on calendar dates,not days of the week. Maintenance cannot be scheduled for the fifth week ofmonths that contain more than 28 days.
• Under Day of the week, specify the day of the week on which the maintenancewill occur.
• Under Start hour, specify the hour during which the maintenance run willbegin.
• Choose the buffer period between primary and standby maintenanceexecution. Buffer period is the number of days before which the standbyAutonomous Container Database Maintenance will be scheduled beforeprimary Autonomous Container Database Maintenance
7. Click Save Changes.
View the Next Scheduled Maintenance Run of a Data Guard EnabledAutonomous Container Database
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Container Databases, click the display name of thecontainer database you are interested in.
4. On the Autonomous Container Database details page, under Maintenance, clickthe View link in the Next Maintenance field.
5. On the Maintenance page, under Autonomous Database Maintenance, clickMaintenance.
Chapter 28Maintenance Scheduling and Patching Data Guard Enabled Autonomous Container Database
28-12
In the list of maintenance events, you can the details of scheduled maintenanceruns. Maintenance event details include the following:
• The status of the scheduled maintenance run
• The type of maintenance run (quarterly software maintenance or a criticalpatch)
• The OCID of the maintenance event
• The start time and date of the maintenance
View the Maintenance History of a Data Guard Enabled AutonomousContainer Database
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Container Databases, click the display name of thecontainer database you are interested in.
4. On the Autonomous Container Database details page, under Maintenance, clickthe View link in the Next Maintenance field.
5. On the Maintenance page, under Autonomous Database Maintenance, clickMaintenance History.
In the list of past maintenance events, you can click on an individual event titleto read the details of the maintenance that took place. Maintenance event detailsinclude the following:
• The category of maintenance (quarterly software maintenance or a criticalpatch)
• Whether the maintenance was scheduled or unplanned
• The OCID of the maintenance event
• The start time and date of the maintenance
Immediately Patch a Data Guard Enabled Autonomous ContainerDatabase
Note:
Patching primary immediately will result in standby being patched first, ifstandby is not already patched.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Container Databases, click the display name of theAutonomous Container Database that you want to patch.
4. On the Autonomous Container Database Details page, in the Maintenancesection, click the View link in the Next Maintenance field to display the
Chapter 28Maintenance Scheduling and Patching Data Guard Enabled Autonomous Container Database
28-13
Maintenance page for the Autonomous Container Database that you want topatch.
5. In the Autonomous Container Database section, click Patch Now in theScheduled Start Time field to display the Run Maintenance dialog.
6. Click Patch Now to start the patching operation.
Reschedule or Skip scheduled Maintenance for Data Guard EnabledAutonomous Container Database
Note:
Skipping primary will skip standby also. If standby is patched, then skippingon primary is not allowed.
1. Open the navigation menu. Under Database, click Exadata Cloud@Customer.
2. Click Autonomous Databases.
3. In the list of Autonomous Container Databases, click the display name of thecontainer database that you want to manage.
4. On the Autonomous Container Database details page, in the Maintenancesection, click the View link in the Next Maintenance field.
5. On the Maintenance page, any container database maintenance events plannedfor the next 15 days will appear in the list of maintenance events.
To skip scheduled maintenance for a container database, click Skip.
Note:
You cannot skip scheduled maintenance more than twice, consecutively.
To reschedule maintenance, click Edit and enter a start time for theupdate in the Edit Maintenance dialog. Ensure that your specifiedcontainer database maintenance window is later in the quarter than yourscheduled Exadata infrastructure maintenance.
Chapter 28Maintenance Scheduling and Patching Data Guard Enabled Autonomous Container Database
28-14
29Using Performance Hub to AnalyzeDatabase Performance
Use the Performance Hub tool to analyze and tune the performance of a selectedOracle Exadata Cloud@Customer Autonomous Database.
With this tool, you can view real-time and historical performance data. When you viewhistorical data in the Performance Hub, you are viewing statistics collected as part ofthe hourly snapshots of your database.
Note:
Performance Hub supports only Autonomous Databases.
• Performance Hub Features
• Time Range Selector
• Time Zone Selector
• ASH Analytics Tab
• SQL Monitoring Tab
• Blocking Sessions Tab
• Using the Oracle Cloud Infrastructure Console
Performance Hub FeaturesThe Performance Hub window consists of a graphical Time Range display that youuse to select the time period of all data to be displayed. It includes the following tabsthat display performance data:
• ASH Analytics
• SQL Monitoring
• Blocking Sessions
These tabs, described in detail below, provide information that you can use to analyzethe performance of a selected database, including the following:
• How much of the database is waiting for a resource, such as CPU or disk I/O
• Whether database performance degraded over a given time period and what couldbe the likely cause.
• Which specific modules may be causing a load on the system, and where most ofdatabase time is being spent on this module.
29-1
• Which SQL statements are the key contributors to changes in databaseperformance, and which executions are causing them.
• Which user sessions are causing performance bottlenecks.
• Which sessions are currently blocking and if there are outstanding requests for alock.
Time Range SelectorThe time range selector is displayed at the top of the Performance Hub page. Itconsists of a graphically displayed time field as shown in the following illustration. Notethat the selected time range applies to all charts and graphs in the Performance Hubwindow.
Figure 29-1 Time Range Selector
The time range field (#1 in the above illustration) shows database activity in chartform for the specified Time Range period. The time range is the amount of time beingmonitored.
Use the Quick Select selector to set the time range. The menu includes five timechoices, Last Hour, Last 8 Hours, Last 24 Hours, Last Week, and Custom. The defaulttime range is Last Hour. To specify a custom time range, you can also click the TimeRange field. This opens the Custom Time Range dialog, allowing you to specify acustom range.
The Activity graph displays the average number of active sessions broken down byCPU, User I/O, and Wait. Maximum threads are shown as a red line above the timefield.
The sliding box (circled at right in the above illustration) on the time range chart isknown as the time slider. The time slider selects a section of the time range (#2 in theabove illustration) shown in the time range field. It shows the time being analyzed. Inthe illustration, the arrows inside the time slider point to the vertical 'handle' elementson the left and right boundaries of the slider box. The time slider works as follows:
• To change the start and end time of the analysis while keeping the same amountof time between them, left click anywhere inside the box. Then slide the box leftor right along the time range without changing its size. The selected times aredisplayed below the time graph.
• To increase or decrease the length of time being analyzed, left click either one ofthe handles and drag it left or right to expand or contract the box.
• To refresh the data in Performance Hub according to the time range chosen, clickRefresh (upper right corner of the window).
Chapter 29Time Range Selector
29-2
Note:
The time slider provides an extra display feature in the Workload tab. Seethe description in the Workload section of this page.
Use the Quick Select menu to set the time duration. The menu includes thefollowing five time choices: Last Hour, Last 8 Hours, Last 24 Hours, LastWeek, and Custom. The default Time Range is Last Hour. The time sliderselects the time period of the data displayed in Performance Hub. The timeslider has a different default time period based on the selected Time Range.
Time Zone SelectorThe Time Zone selector is located above the time range field, beside the Quick Selectand Time Range selectors. By default, when you open Performance Hub, the tooldisplays data in UTC (Coordinated Universal Time) time. You can use the time zoneselector to change the time zone to either your local web browser time, or the timezone setting of the database you are working with. When you change the time zone,Performance Hub's reports display data in your specified time zone.
ASH Analytics TabDisplayed by default, the ASH (Active Session History) Analytics tab shows ASHanalytics charts to explore ASH data. You use it to drill down into databaseperformance across multiple dimensions such as Consumer Group, Wait Class, SQLID, and User Name. In the ASH Analytics tab, you can select an Average ActiveSessions dimension and view the top activity for that dimension for the selected timeperiod. For more information on ASH, see Active Session History (ASH) in OracleDatabase Concepts.
SQL Monitoring TabThe SQL Monitoring tab is not displayed by default. To view it, click SQL Monitoringon the Performance Hub page.
SQL statements are only monitored if they have been running for at least fiveseconds or if they are run in parallel. The table in this section displays monitoredSQL statement executions by dimensions including Last Active Time, CPU Time,and Database Time. The table displays currently running SQL statements and SQLstatements that completed, failed, or were terminated. The columns in the tableprovide information for monitored SQL statements including Status, Duration, and SQLID.
The Status column has the following icons:
• A spinning icon indicates that the SQL statement is executing.
• A green check mark icon indicates that the SQL statement completed its executionduring the specified time period.
Chapter 29Time Zone Selector
29-3
• A red cross icon indicates that the SQL statement did not complete. The icondisplays when an error occurs because the session was terminated.
• A clock icon indicates that the SQL statement is queued.
To terminate a running or queued SQL statement, click Kill Session.
You can also click an SQL ID to go to the corresponding Real-time SQL Monitoringpage. This page provides extra details to help you tune the selected SQL statement.
Blocking Sessions TabThe Performance Hub blocking sessions tab displays the current blocking and waitingsessions in a hierarchical display. You can view detailed information about eachblocking session, and can view the sessions blocked by each blocking session. Youcan also use the tab to inspect or drill down into the SQL involved, to determine thecause of the blocking. You can perform several operations in the tab, including killingone or more of the listed sessions to resolve a waiting session problem.
The hierarchical display nests waiting sessions underneath the session that they areblocked by in an easily viewable parent-child relationship. The hierarchy can containany number of levels to correctly represent the structure of the sessions involved.
The sessions listed include sessions that are waiting for a resource and sessions thathold a resource that is being waited on that creates the blocking condition.
Using the Oracle Cloud Infrastructure Console• Navigate to Performance Hub in the Oracle Cloud Infrastructure Console Interface
of an Autonomous Database
• View the Average Active Sessions Data by a Selected Dimension
• Filter Average Active sessions Data
• View the SQL Monitoring Report
• View the Blocking and Waiting Sessions
Navigate to Performance Hub in the Oracle Cloud InfrastructureConsole Interface of an Autonomous Database
1. Open the navigation menu. Under Database, click Exadata Cloud at Customer.
2. Choose your Compartment.
3. Click Autonomous Databases.
4. In the list of Autonomous Databases, click the display name of the database youwant to analyze using Performance Hub reports.
5. Click Performance Hub.
Chapter 29Blocking Sessions Tab
29-4
View the Average Active Sessions Data by a Selected Dimension1. Go to the Performance Hub page of the Oracle Cloud Infrastructure Console for
the database which you want to manage.
See To navigate to Performance Hub in the Oracle Cloud Infrastructure Consoleinterface of an Autonomous Database for more information.
• The database name is displayed at the top of the Performance Hub page.
• The time period for which information is available on the Performance Hub isdisplayed in the Time Range field. The selected time period is indicated onthe time slider graph by the adjustable time slider box.
The ASH Analytics tab is displayed with the top activity for a selected dimensionin the selected time period.
2. Use the Quick Select selector to set the exact time period for which data isdisplayed in the ASH Analytics tables and graphs.
By default, the last hour is selected. The time range is the total amount of timeavailable for analysis.
3. Use the box on the time slider to further narrow down the time period for whichperformance data is displayed on the ASH Analytics tab.
4. Select a dimension in the Average Active Sessions drop-down list to displayASH analytics by that dimension.
When the Consumer Group dimension is selected, the data is categorized bydefault to the High, Medium, or Low service name that is associated with theAutonomous Database.
Optionally, you can:
• Click the Maximum Threads check box to view the number of Max CPUThreads. The red line on the chart shows this limit.
• Click the Total Activity check box to view a black border that denotes totalactivity of all the components of the selected dimension on the chart. Thisoption is selected by default when you use the filtering capabilities to onlyview the data for a particular component within a dimension. For informationon filtering Average Active Sessions data, see Filter Average Active SessionsData.
5. For the dimension selected in the Average Active Sessions drop-down list, youcan further drill down into session details by selecting dimensions in the twosections at the bottom of the ASH Analytics tab.
By default, the following dimensions are selected:
• SQL ID by Consumer Group, which displays the SQL statements with thetop average active sessions activity for consumer groups for the selectedtime period. You can right-click the bar charts to sort the SQL statements inascending or descending order or click the SQL ID to go the SQL Detailspage.
• User Session by Consumer Group, which displays the user sessions withthe top average active sessions activity for consumer groups for the selectedtime period. You can right-click the bar charts to sort the user sessions inascending or descending order or click the user session to go to the UserSession page.
Chapter 29Using the Oracle Cloud Infrastructure Console
29-5
Filter Average Active sessions Data1. Go to the Performance Hub page of the Oracle Cloud Infrastructure Console for
the database which you want to manage.
See To navigate to Performance Hub in the Oracle Cloud Infrastructure Consoleinterface of an Autonomous Database for more information.
• The database name is displayed at the top of the Performance Hub page.
• The time period for which information is available on the Performance Hub isdisplayed in the Time Range field. The selected time period is indicated onthe time slider graph by the adjustable time slider box.
The ASH Analytics tab is displayed with the top activity for a selected dimensionin the selected time period.
2. Use the Quick Select selector to set the exact time period for which data isdisplayed in the ASH Analytics tables and graphs.
By default, the last hour is selected. The time range is the total amount of timeavailable for analysis.
3. Use the adjustable time slider box to further narrow down the time period for whichperformance data is displayed on the ASH Analytics tab.
4. In the ASH Analytics tab, select a dimension in the Average Active Sessions bydrop-down list.
By default, Consumer Group is selected.
The chart is displayed. Each color in the chart denotes a component of theselected dimension.For example, the Consumer Group dimension has High,Medium, and Low, which are predefined service names assigned to yourAutonomous Database to provide different levels of concurrency and performance.
5. Click a component in the legend.
The selected component is displayed in the Applied Filters field and the chart isupdated to only display data pertaining to that component. The total activity, whichincludes all the components of the dimension, is defined by a black outline and isdisplayed by default when you filter data.
View the SQL Monitoring Report1. Go to the Performance Hub page of the Oracle Cloud Infrastructure Console for
the database which you want to manage.
See To navigate to Performance Hub in the Oracle Cloud Infrastructure Consoleinterface of an Autonomous Database for more information.
• The database name is displayed at the top of the Performance Hub page.
• The time period for which information is available on the Performance Hub isdisplayed in the Time Range field. The selected time period is indicated onthe time slider graph by the adjustable time slider box.
2. Click SQL Monitoring to display the SQL monitoring tab.
3. Optionally, you can get detailed information on a specific SQL statement byclicking an ID number in the SQL ID column.
Chapter 29Using the Oracle Cloud Infrastructure Console
29-6
When you click an ID number, the Real-time SQL Monitoring page is displayed.
4. Click Download Report to download the report data for your selected SQLstatement.
View the Blocking and Waiting Sessions1. Go to the Performance Hub page of the Oracle Cloud Infrastructure Console for
the database which you want to manage.
See To navigate to Performance Hub in the Oracle Cloud Infrastructure Consoleinterface of an Autonomous Database for more information.
• The database name is displayed at the top of the Performance Hub page.
• The time period for which information is available on the Performance Hub isdisplayed in the Time Range field. The selected time period is indicated onthe time slider graph by the adjustable time slider box.
2. Click Blocking Sessions to display details about current blocking and waitingsessions.
Analysis of historical sessions is not supported.
3. Click the link in each column of the table to view the details of the listed blockingand waiting sessions, as shown in the following table.
Note:
If you see an error message that says the server failed to getperformance details for the selected session at the selected time, try theselection again. If the same error message is displayed, try a differenttime selection. If that fails, contact Oracle Support.
Table 29-1 Blocking and Waiting Sessions
Tab Column Description
User Name This is the name of the user.
Status The status indicates whether the session isactive, inactive, or expired.
Lock This is the lock type for the session.Click the lock type to display a table withmore information about the session lock.It lists the Lock Type, Lock Mode, LockRequest, Object Type, Subobject Type,Time, ID1, ID2, Lock Object Address,and Lock Address of the selected session.
User Session The user session lists the Instance, SID,and Serial number.
SQL ID This is the ID of the SQL associated with thesession.
Chapter 29Using the Oracle Cloud Infrastructure Console
29-7
Table 29-1 (Cont.) Blocking and Waiting Sessions
Tab Column Description
Wait Event This is the wait event for the session. Clickthe wait event to show additional wait eventdetails.
Object Name This is the name of the locked databaseobject.
Blocking Time This is the time that a blocking session hasbeen blocking a session.
Wait Time This is the time that a session has beenwaiting.
• Setting the Minimum Wait Time
• Killing a Session
• Displaying Lock Details
• Displaying Wait Event Information
• Displaying Session Details
• Displaying SQL Details
Setting the Minimum Wait Time
The minimum wait time works like a filter for the Blocking Sessions information. Itsets the minimum time that a session must wait before it is displayed in the tab. Forexample, if the minimum wait time is set to three seconds, and a session has waitedonly two seconds, it is not displayed in the table. But if you change the minimum waittime to one second, the session that waited only two seconds is added to the display.
Note:
The minimum wait time default setting is three seconds.
Killing a Session
1. Click the check box at the left of the session User Name to select a session.
The Kill Session button is enabled.
2. Click Kill Session.
The Kill Session confirmation dialog box is displayed.
3. Click Kill Session to end the session.
Displaying Lock Details
1. In the session Lock column, click the name of the lock type (Lock or ExclusiveLock) for the session.
Chapter 29Using the Oracle Cloud Infrastructure Console
29-8
The Wait Event Details message box is displayed.
2. Note the information in the table and use as needed to determine any action totake.
Displaying Wait Event Information
1. In the session Wait Event column, click the name of the wait event for theselected session.
The Session Lock Information table is displayed.
2. Note the information in the message box and use as needed to determine anyaction to take.
Displaying Session Details
1. In the session User Session column, click the session identifier for thesession.The Performance Hub Session Details page is displayed.
2. Optionally, move the time slider to display a specific time range of the session.
3. Use the Session Details page to explore additional details about the session.
Displaying SQL Details
1. In the session SQL ID column, click the SQL ID associated with the session.
The Performance Hub SQL Details page is displayed.
2. Optionally, move the time slider to display a specific time range of the session.
3. Select one or more of the following tabs, note the information in them, and takeany action needed.
• Summary. This tab displays the SQL Overview and Source details.
• ASH Analytics. This tab displays the SQL average active sessions.
• Execution Statistics. This tab displays the SQL plans and plan details.
• SQL Monitoring. This tab displays information about monitored SQLexecutions.
• SQL Text. This tab displays the SQL.
Chapter 29Using the Oracle Cloud Infrastructure Console
29-9
Index
Index-1