Oracle Cloud. Using Oracle Database Cloud - Database as a Service E

Transcription

1 Oracle Cloud Using Oracle Database Cloud - Database as a Service E November 2015

2 Oracle Cloud Using Oracle Database Cloud - Database as a Service, E Copyright 2014, 2015, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license 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. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you 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 on behalf 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 installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. 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 that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark 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 expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be 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.

3 Contents Preface... Audience... Related Documents... Conventions... ix ix ix ix 1 Getting Started with Database as a Service About Oracle Database Cloud Service Offerings About Oracle Database Cloud - Database as a Service About Database as a Service Instances Service Level Billing Frequency Oracle Database Release Version Oracle Database Edition Computing Power Database Storage Automatic Backup Configuration Before You Begin with Database as a Service How to Begin with Database as a Service Subscriptions About Database as a Service Roles and Users Accessing the Oracle Database Cloud Service Console Typical Workflow for Using Database as a Service Managing the Life Cycle of Database as a Service Instances Creating a Database as a Service Instance Viewing All Database as a Service Instances Viewing Detailed Information for a Database as a Service Instance Stopping, Starting and Restarting a Database as a Service Instance Restarting a Database as a Service Compute Node Deleting a Database as a Service Instance Tracking the Number of Database as a Service Instances in an Account iii

4 3 Managing Network Access to a Database as a Service Instance About Network Access to a Database as a Service Instance Generating a Secure Shell (SSH) Public/Private Key Pair Generating an SSH Key Pair on UNIX and UNIX-Like Platforms Using the ssh-keygen Utility Generating an SSH Key Pair on Windows Using the PuTTYgen Program Creating an SSH Tunnel to a Compute Node Port Creating an SSH Tunnel Using the ssh Utility on Linux Creating an SSH Tunnel Using the PuTTY Program on Windows Enabling Access to a Compute Node Port Defining a Custom Host Name or Domain Name for Database as a Service Using Network Encryption and Integrity Administering Database as a Service Instances Scaling a Database as a Service Instance Updating the Cloud Tooling on a Database as a Service Instance Updating the Cloud Tooling on Service Instances Hosting Single-Instance Databases Updating the Cloud Tooling on Service Instances Hosting Oracle RAC Databases Maintaining the Manageability of Your Database as a Service Instance Administering Oracle REST Data Services (formerly Oracle APEX Listener) Administering Oracle GlassFish Server Loading Data into the Oracle Database in a Database as a Service Instance Tuning Performance of the Oracle Database in a Database as a Service Instance Monitoring and Managing the Database in a Database as a Service Instance Creating a Database on a Virtual Image Service Instance Creating a Database on a Virtual Image Service Instance: Example Accessing a Database as a Service Instance Connecting to a Compute Node Through Secure Shell (SSH) Connecting to a Compute Node Using the ssh Utility on UNIX and UNIX-Like Platforms Connecting to a Compute Node Using the PuTTY Program on Windows Accessing Enterprise Manager Database Express 12c Accessing Enterprise Manager 11g Database Control Accessing the Oracle Pluggable Database Self-Service Provisioning Application Connecting Remotely to the Database by Using Oracle Net Services Accessing the Oracle GlassFish Server Administration Console Backing Up and Restoring a Database as a Service Instance About Backing Up a Database as a Service Instance Creating an On-Demand Backup of a Database as a Service Instance iv

5 Creating an On-Demand Backup on Service Instances Hosting Single-Instance Databases Creating an On-Demand Backup on Service Instances Hosting Oracle RAC Databases Deleting a Backup of a Database as a Service Instance Updating the Password for Backing Up to the Storage Cloud Updating the Password on Service Instances Hosting Single-Instance Databases Updating the Password on Service Instances Hosting Oracle RAC Databases Customizing the Current Backup Configuration Customizing the Current Backup Configuration on Service Instances Hosting Single- Instance Databases Customizing the Current Backup Configuration on Service Instances Hosting Oracle RAC Databases Changing the Backup Configuration to a Different Backup Destination Changing the Backup Configuration on Service Instances Hosting Single-Instance Databases Changing the Backup Configuration on Service Instances Hosting Oracle RAC Databases Increasing Local Storage for Backups on Older Service Instances Disabling and Re-enabling Scheduled Backups Restoring a Database as a Service Instance from a Backup Restoring from a Backup on Service Instances Hosting Single-Instance Databases Restoring from the Most Recent Backup Restoring from a Specific Backup Restoring from a Specific Long-Term Backup Restoring an Instance Using the mrec Utility Restoring from a Backup on Service Instances Hosting Oracle RAC Databases Restoring from the Most Recent Backup Restoring to a Specific Point in Time Patching Database as a Service Checking Prerequisites Before Applying a Patch Checking Prerequisites by Using the Oracle Database Cloud Service Console Checking Prerequisites by Using the dbpatchm Subcommand Applying a Patch Applying a Patch by Using the Oracle Database Cloud Service Console Applying a Patch on Service Instances Hosting Single-Instance Databases Applying a Patch on Service Instances Hosting Oracle RAC Databases Rolling Back a Patch or Failed Patch Rolling Back a Patch or Failed Patch by Using the Oracle Database Cloud Service Console Rolling Back a Patch or Failed Patch by Using the dbpatchm Subcommand Applying a Patch to a Test Instance The dbpatchm Subcommand v

6 The dbpatchm.cfg Configuration File Configuring Database Features, Database Options, and Companion Products Using Oracle Real Application Clusters (RAC) in Database as a Service Using Hybrid Columnar Compression (HCC) in Database as a Service Using Tablespace Encryption in Database as a Service Creating Encrypted Tablespaces Managing Tablespace Encryption Using Oracle Application Express in Database as a Service Accessing the Oracle Application Express Administration Console Accessing the Oracle Application Express Home Page Upgrading from Oracle Application Express 4.2 to 5.0 in Database as a Service Migrating from Oracle Database Cloud - Database as a Service to Oracle Database Cloud - Database Schema Service Migrating from Oracle Database Cloud - Database Schema Service to Oracle Database Cloud - Database as a Service Using Oracle Enterprise Manager Cloud Control with Database as a Service Using the Oracle Pluggable Database Self-Service Provisioning Application Migrating an On-Premises Oracle Database to Oracle Database Cloud Choosing a Migration Method Migrating from Oracle Database 11g to Oracle Database 11g in the Cloud Migrating from Oracle Database 11g to Oracle Database 12c in the Cloud Migrating from Oracle Database 12c CDB to Oracle Database 12c in the Cloud Migrating from Oracle Database 12c Non-CDB to Oracle Database 12c in the Cloud Migration Methods Data Pump Conventional Export/Import Data Pump Full Transportable Data Pump Transportable Tablespace Remote Cloning a PDB Remote Cloning Non-CDB RMAN Cross-Platform Transportable PDB RMAN Cross-Platform Transportable Tablespace Backup Sets RMAN Transportable Tablespace with Data Pump RMAN CONVERT Transportable Tablespace with Data Pump SQL Developer and INSERT Statements to Migrate Selected Objects SQL Developer and SQL*Loader to Migrate Selected Objects Unplugging/Plugging a PDB Unplugging/Plugging Non-CDB Using Oracle DBaaS Monitor About Oracle DBaaS Monitor Accessing Oracle DBaaS Monitor vi

7 Filtering the Display on DBaaS Monitor Pages Starting and Stopping the Database Instance Starting the Database Instance Stopping the Database Instance Viewing and Modifying Initialization Parameters Viewing Alert Log Entries and Checking for Errors Viewing Tablespace and Segment Space Usage Administering the Listener Viewing Listener Status Information Starting the Listener Stopping the Listener Verifying that the Listener Knows of a Service Frequently Asked Questions for Database as a Service 12 Troubleshooting Database as a Service Problems Creating Instances Problems Accessing Instances Problems with Scaling Problems with Patching and Rollback Problems with Backing Up and Restoring A B Characteristics of a Newly Created Database as a Service Instance Characteristics of an Oracle Database Cloud Service Instance... A-1 Virtual Machine and System Characteristics... A-1 Oracle Database Characteristics... A-4 Oracle GlassFish Server Characteristics... A-4 Location of Diagnostic and Log Files... A-4 Oracle Compute Cloud Service Resources... A-5 Characteristics of an Oracle Database Cloud Service Instance Using Oracle RAC... A-7 Characteristics of an Oracle Database Cloud Service - Virtual Image Instance... A-12 Virtual Machine and System Characteristics... A-12 Oracle Compute Cloud Service Resources... A-14 Oracle Cloud Pages for Administering Database as a Service Oracle Database Cloud Service Services Page... B-1 Oracle Database Cloud Service Instance Overview Page... B-3 Oracle Database Cloud Service Instance Administration Page... B-5 Create Database Cloud Service Instance: Subscription Type Page... B-6 Create Database Cloud Service Instance: Software Release Page... B-7 Create Database Cloud Service Instance: Software Edition Page... B-7 Create Database Cloud Service Instance: Service Details Page... B-8 Create Database Cloud Service Instance: Confirmation Page... B-11 vii

8 C D E The oracle-dbcs-cli Utility Downloading and Installing the oracle-dbcs-cli Utility... C-1 Running the oracle-dbcs-cli Utility... C-2 The Configuration File for oracle-dbcs-cli Subcommands... C-7 The Data File for the oracle-dbcs-cli create Subcommand... C-7 The raccli Utility raccli apply patch... D-2 raccli create backup... D-2 raccli create recovery... D-3 raccli describe job... D-4 raccli describe system... D-5 raccli list backup... D-6 raccli list backupconfig... D-7 raccli list jobs... D-8 raccli list recovery... D-8 raccli update backupconfig... D-9 raccli update netsec... D-11 raccli update rdk... D-13 raccli update tde... D-13 REST API for Database as a Service Using the REST API... E-1 URL Structure... E-1 Supported REST Methods... E-2 Security, Authentication and Authorization... E-2 Status Codes... E-3 curl Examples... E-4 Alphabetical Listing of Endpoints in the REST API... E-4 REST API Reference... E-5 Create a Service Instance... E-5 View All Service Instances... E-10 View a Service Instance... E-12 Stop, Start or Restart a Service Instance... E-16 Scale Up a Service Instance... E-18 Delete a Service Instance... E-20 View the Job Status of an Operation... E-22 viii

9 Preface This document describes how to manage and monitor Oracle Database Cloud - Database as a Service and provides references to related documentation. Topics Audience Related Documents Conventions Audience This document is intended for Oracle Cloud users who want to manage and monitor Oracle Database Cloud - Database as a Service. Related Documents Conventions For more information, see these Oracle resources: Getting Started with Oracle Cloud Using Oracle Database Cloud Service (Database Schema) Using Oracle Compute Cloud Service The following text conventions are used in this document: Convention boldface italic monospace Meaning Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. ix

10

11 1 Getting Started with Database as a Service This section describes how to get started with Oracle Database Cloud - Database as a Service for administrators and developers. Topics About Oracle Database Cloud Service Offerings About Oracle Database Cloud - Database as a Service About Database as a Service Instances Before You Begin with Database as a Service How to Begin with Database as a Service Subscriptions About Database as a Service Roles and Users Accessing the Oracle Database Cloud Service Console Typical Workflow for Using Database as a Service About Oracle Database Cloud Service Offerings Oracle Database Cloud Service provides the power and flexibility of the Oracle Database in the cloud with your choice of a dedicated schema with a complete development and deployment platform managed by Oracle, or dedicated database instances with full administrative control: Oracle Database Cloud - Database Schema Service Oracle Database Cloud - Database as a Service About Oracle Database Cloud Database Schema Service Oracle Database Cloud Database Schema Service provides a complete platform for database application development. All the infrastructure for the underlying Oracle Database is inside the cloud; you do not have to perform any standard database maintenance operations. Oracle Database Cloud Database Schema Service subscriptions are based on schemas within an Oracle Database. Your service is limited to a single schema. Because of this schema-level isolation, you do not have the ability to perform instance-wide modifications of configuration settings. In addition, some capabilities of the Oracle Database have been disabled in order to guarantee schema-level isolation. Since the overall database server environment is shared between multiple tenants, you do not have access to the underlying hardware and operating system infrastructure, so Getting Started with Database as a Service 1-1

12 About Oracle Database Cloud - Database as a Service you cannot load additional applications, store files in the file system or access the operating system environment in any way. Finally, access to the underlying Oracle Database is through the SQL and PL/SQL programmatic interfaces. You cannot connect to a Database Schema Service service by using Oracle Net Services. You can access SQL statements and PL/SQL code through the use of RESTful Web Services, which you can define with either the RESTful Web Services wizard in Oracle Application Express or with SQL Developer. Oracle Database Cloud Database Schema Service provides convenient access to the following features: Oracle SQL Developer: a graphical tool that enables you to browse, create, edit, and delete database objects; run SQL statements and scripts; edit and debug PL/SQL code; manipulate and export data; migrate third-party databases to Oracle; view metadata and data in third-party databases; and view and create reports. Oracle Application Express: a robust rapid application development system. RESTful web Services - the ability to use RESTful web services to access data in your Oracle Database. (Both Application Express and SQL Developer include a RESTful web service wizard, which makes it easy for you to create services which implement any SQL statement or PL/SQL procedure to supply data to applications.) For further information about Oracle Database Cloud Database Schema Service, including how to use its most attractive features, see Using Oracle Database Cloud - Database Schema Service. About Oracle Database Cloud - Database as a Service Oracle Database Cloud - Database as a Service provides you the ability to create service instances that contain Oracle databases, with each service instance containing a single Oracle database. You have full access to the features and operations available with Oracle Database, but with Oracle providing the computing power, physical storage and (optionally) tooling to simplify routine database maintenance and management operations. When you create service instances, Database as a Service creates compute nodes to host the database, using computing and storage resources provided by Oracle Compute Cloud Service. Additionally, it provides access to the compute nodes (and thus to the database) using networking resources provided by Oracle Compute Cloud Service. Because each service instance provides a complete Oracle database and provides you direct access to it, you can avoid many of the restrictions associated with Database Schema Service. For example, you can define multiple schemas in the database, and you can connect to the database using Oracle Net Services. Two service levels of Database as a Service instances are available: The Oracle Database Cloud Service - Virtual Image level includes Oracle Database and supporting software on the service instance. You have to install this software yourself, and you are responsible for all maintenance operations for this software. You have root privilege, so you can load and run software in the compute environment. You have full administrative privileges for the Oracle database. The Oracle Database Cloud Service level also includes Oracle Database and supporting software on the service instance. However, the software is installed for 1-2 Using Oracle Database Cloud - Database as a Service

13 About Database as a Service Instances you, an Oracle database is created using values you provide when creating the service instance, and the database is started. Additionally, you can direct Database as a Service to set up automatic backups when creating the service instance. Finally, the service instance includes cloud tooling that simplifies backup, recovery, patching and upgrade operations. You have root privilege, so you can load and run software in the compute environment. You have full administrative privileges for the Oracle database. You are responsible for making any changes to the automated maintenance setup, and you are responsible for recovery operations in the event of a failure. About Database as a Service Instances When you create an Oracle Database Cloud - Database as a Service instance, you use the Create Database Cloud Service Instance wizard, which steps you through the process of making the choices that produce a service instance tailored to your needs. These choices include: Service Level Billing Frequency Oracle Database Release Version Oracle Database Edition Computing Power Database Storage Automatic Backup Configuration Service Level When creating an Oracle Database Cloud - Database as a Service instance, you choose one of the following service levels: Oracle Database Cloud Service - Virtual Image a compute environment with pre-installed virtual machine images that include all software needed to create and run an Oracle Database. You connect to the virtual machine and run the Oracle Database Configuration Assistant (DBCA) to create your database. All subsequent maintenance operations, including backup, patching and upgrades, are performed by you. Oracle Database Cloud Service everything in Virtual Image, plus a database created according to specifications you provide in the Create Database Cloud Service Instance wizard, plus cloud tooling that provides automatic and ondemand backups, patching and upgrading, and point-in-time recovery for your Oracle Databases. Cloud Tooling for Database as a Service In addition to the capabilities of the web-based Oracle Database Cloud Service console, Database as a Service offers the following tools on the compute nodes of service instances created using the Oracle Database Cloud Service service level: Simple Automated Backups: use the bkup_api utility (raccli on service instances that use Oracle Real Application Clusters) to perform on-demand Getting Started with Database as a Service 1-3

14 About Database as a Service Instances Billing Frequency backups and to change how automatic backups are configured. See Backing Up and Restoring a Database as a Service Instance. Simple Automated Recovery: use the orec subcommand of the dbaascli utility (raccli on service instances that use Oracle Real Application Clusters) to restore from backups. See Backing Up and Restoring a Database as a Service Instance. Simple Automated Patching: use the dbpatchm subcommand of the dbaascli utility (raccli on service instances that use Oracle Real Application Clusters) to apply patches. See Patching Database as a Service. New DBaaS Monitor: use the Oracle DBaaS Monitor web application to monitor the Oracle database and the Oracle GlassFish Server domain on the service instance. See Accessing Oracle DBaaS Monitor. Oracle DBaaS Monitor is not available on service instances that use Oracle Real Application Clusters. When creating an Oracle Database Cloud - Database as a Service instance, you choose one of the following billing frequencies: Hourly Pay only for the number of hours used during your billing period. You cannot switch a service instance from hourly to monthly billing frequency after it is created. Monthly Pay one price for the full month irrespective of the number of hours used. Oracle Database Release Version Oracle Database Edition For service instances that are started in the middle of a month, the price is prorated; you pay only for the partial month from the day the instance is created. You cannot switch a service instance from monthly to hourly billing frequency after it is created. When creating an Oracle Database Cloud - Database as a Service instance, you choose one of the following Oracle Database software release versions: Oracle Database 11g Release 2 Oracle Database 12c Release 1 When creating an Oracle Database Cloud - Database as a Service instance, you choose one of the following Oracle Database editions: Standard Edition delivers unprecedented ease of use, power, and performance for workgroup, department-level, and Web applications. Oracle Database Standard Edition includes all the facilities necessary to build business-critical applications. This edition is only available for Oracle Database 11g Release 2. Enterprise Edition provides the performance, availability, scalability, and security required for mission-critical applications such as high-volume online transaction processing (OLTP) applications, query-intensive data warehouses, and demanding Internet applications. 1-4 Using Oracle Database Cloud - Database as a Service

15 About Database as a Service Instances Enterprise Edition contains all the components of Oracle Database. Enterprise Edition - High Performance provides all the features of Enterprise Edition, plus all the database enterprise management packs and all the Enterprise Edition options except: Active Data Guard In-Memory Database Oracle RAC One Node Real Application Clusters (Oracle RAC) Enterprise Edition - Extreme Performance provides all the features of Enterprise Edition, plus all the database enterprise management packs and all the Enterprise Edition options except: Oracle RAC One Node Note: Regardless of which Enterprise Edition variation you choose, all available database enterprise management packs and Enterprise Edition options are included in the Database as a Service instance that is created. The packs and options that are not part of the Enterprise Edition variation you chose are available to you for use on a trial basis. Computing Power When creating an Oracle Database Cloud - Database as a Service instance, you choose the computing power for the service instance's compute node (or compute nodes in the case of service instances that use Oracle Real Application Clusters) from a list of supported OCPU (Oracle CPU) and processor RAM combinations. These combinations fall into two categories: General Purpose: OC3-1 OCPU, 7.5 GB RAM OC4-2 OCPU, 15 GB RAM OC5-4 OCPU, 30 GB RAM OC6-8 OCPU, 60 GB RAM OC7-16 OCPU, 120 GB RAM High Memory: OC1M - 1 OCPU, 15 GB RAM OC2M - 2 OCPU, 30 GB RAM OC3M - 4 OCPU, 60 GB RAM OC4M - 8 OCPU, 120 GB RAM Getting Started with Database as a Service 1-5

16 Before You Begin with Database as a Service Database Storage OC5M - 16 OCPU, 240 GB RAM When creating an Oracle Database Cloud - Database as a Service instance, you choose the amount of usable data storage you want for your database in gigabyte (GB) increments up to a maximum of 1 TB. After you create the service instance, you can add more data storage as needed. For information, see Scaling Up the Storage of a Service Instance. Automatic Backup Configuration When creating a new Oracle Database Cloud - Database as a Service instance, you choose whether you want automatic backups to be configured for the instance. Your choices are: Back up to cloud storage and VM block storage 30 days' worth of backups are kept, with the 7 most recent days' worth available directly on VM block storage. If you choose this option, you must specify an existing Oracle Storage Cloud container for the cloud storage. This container becomes associated with Oracle Database Backup Cloud Service, which Database as a Service uses to perform backups to cloud storage. Once associated with Oracle Database Backup Cloud Service, this container becomes part of your Oracle Database Public Cloud Services subscription (or trial) rather than part of an Oracle IaaS Public Cloud Services subscription (or trial). Note: Do not use the Oracle Storage Cloud container that you are using to back up Database as a Service instances to cloud storage for any other purpose. For example, do not also use it to back up Oracle Java Cloud Service instances to cloud storage. Using the container for multiple purposes can result in billing errors. Back up to VM block storage only 7 days' worth of backups are kept on VM block storage. No backups automatic backups are not configured. Before You Begin with Database as a Service Before you begin using Oracle Database Cloud - Database as a Service, you should be familiar with the following technologies: Oracle Cloud See Getting Started with Oracle Cloud for information about Oracle Cloud, especially the topic Buying a Metered Subscription to an Oracle Cloud Service. Oracle Compute Cloud Service Database as a Service compute nodes use a variety of Oracle Compute Cloud Service resources. See Using Oracle Compute Cloud Service for information about its instances and the disk images, compute shapes, storage volumes, IP reservations, security lists, security rules, and secure shell (SSH) public keys that underlie them. 1-6 Using Oracle Database Cloud - Database as a Service

17 How to Begin with Database as a Service Subscriptions Oracle Storage Cloud Service containers Database as a Service uses Oracle Database Backup Cloud Service to back up to cloud storage. Oracle Database Backup Cloud Service, in turn, uses Oracle Storage Cloud Service containers as repositories for backups to the cloud. Before you can create a container, you must have an active subscription to Oracle Storage Cloud Service. For more information, see How to Begin with Oracle Storage Cloud Service Subscriptions in Using Oracle Storage Cloud Service. Before you create your first Database as a Service instance: Procure a Database as a Service subscription. Without an active subscription, you cannot create a Database as a Service instance. Create a Secure Shell (SSH) public/private key pair so you can provide the public key when you create the instance. See Generating a Secure Shell (SSH) Public/ Private Key Pair. (Optional) Create a container in Oracle Storage Cloud Service to store backups on cloud storage. See Creating Containers in Using Oracle Storage Cloud Service. Note: Do not use an Oracle Storage Cloud container that you use to back up Database as a Service instances for any other purpose. For example, do not also use it to back up Oracle Java Cloud Service instances. Using the container for multiple purposes can result in billing errors. How to Begin with Database as a Service Subscriptions Here s how to get started with Oracle Database Cloud - Database as a Service trials and paid subscriptions: 1. Request a trial environment or purchase a subscription to Oracle Database Public Cloud Services. See Subscribing to an Oracle Cloud Service Trial or Buying a Metered Subscription to an Oracle Cloud Service in Getting Started with Oracle Cloud. 2. Set up your Oracle Database Public Cloud Services account. See Setting Up a Metered Oracle Cloud Services Account in Getting Started with Oracle Cloud. 3. Verify Database as a Service is ready to use. See Verifying That Metered Oracle Cloud Services Are Running in Getting Started with Oracle Cloud. 4. Learn about Database as a Service users and roles. See About Database as a Service Roles and Users. 5. Create accounts for your users and assign them appropriate privileges and roles. See Managing User Accounts and Managing User Roles in Managing and Monitoring Oracle Cloud. 6. Be sure to review the prerequisites described in Before You Begin with Database as a Service before you create your first Database as a Service instance. Note that an Oracle Database Public Cloud Services trial environment or purchased subscription comes with Oracle IaaS Public Cloud Services, which provides you access to: Getting Started with Database as a Service 1-7

18 About Database as a Service Roles and Users Oracle Compute Cloud Service, which Database as a Service relies on Oracle Storage Cloud Service, which Database Backup Service and, in turn, Database as a Service rely on Despite the fact that these services are part of the Oracle IaaS Public Cloud Services subscription, use of their features by Database as a Service or Database Backup Service are billed to the Oracle Database Public Cloud Services subscription. About Database as a Service Roles and Users In addition to the roles and privileges described in Oracle Cloud User Roles and Privileges in Getting Started with Oracle Cloud, the following role is created for Oracle Database Cloud - Database as a Service: DBaaS Database Administrator. When the Database as a Service account is first set up, the service administrator is given this role. User accounts with this role must be added before anyone else can access and use Database as a Service. The identity domain administrator can create more Database as a Service administrators by creating user accounts and assigning the role to user. For information about how to add user accounts in Oracle Cloud, see Managing User Accounts and Managing and Monitoring Oracle Cloud. The following table summarizes the privileges given to the DBaaS Database Administrator role: Description of Privilege Can create and delete service instances Can scale, patch, and back up or restore service instances Can monitor and manage service usage in Oracle Cloud More Information Creating a Database as a Service Instance Deleting a Database as a Service Instance Scaling a Database as a Service Instance Patching Database as a Service Backing Up and Restoring a Database as a Service Instance Managing and Monitoring Oracle Cloud Services in Managing and Monitoring Oracle Cloud Accessing the Oracle Database Cloud Service Console To access the Oracle Database Cloud Service console: 1. Display the Sign In to Oracle Cloud page by clicking the My Services URL link in your Welcome or by following these instructions: a. Open your web browser and go to the Oracle Cloud website: cloud.oracle.com. b. Click Sign In. c. In the My Services box, select the data center where your services are located: Public Cloud Services - NA or Public Cloud Services - EMEA. d. Click Sign In to My Services. 1-8 Using Oracle Database Cloud - Database as a Service

19 Typical Workflow for Using Database as a Service 2. On the Sign In to Oracle Cloud page, enter your user name, your password and the name of your identity domain. Then, click Sign In. The My Services Dashboard opens. 3. In the list of services, locate the entry for Oracle Database Cloud Service and then click Service Console. The Oracle Database Cloud Service opens. 4. If a Welcome page is displayed, view the list of service instances by clicking Services next to Database Cloud Service. For information about the details provided on the Oracle Database Cloud Service console, see Oracle Database Cloud Service Services Page. Typical Workflow for Using Database as a Service To start using Oracle Database Cloud - Database as a Service, refer to the following tasks as a guide: Task Description More Information Get a trial environment or purchase a subscription to Oracle Database Public Cloud Services Add and manage users and roles Create an SSH key pair Create a service instance Enable network access to the service instance Load data into the service instance Monitor service instances Monitor the service Provide your information, and sign up for a free trial or purchase a subscription to Oracle Database Public Cloud Services. Create accounts for your users and assign them appropriate privileges. Assign the necessary Database as a Service roles. Create an SSH public/private key pair for use when creating service instances. Use a wizard to create a new service instance. Permit access to network services associated with the service instance. Use standard Oracle Database tools to load data into the service instance's database. Check on the health and performance of individual service instances. Check on the day-to-day operation of your service, monitor performance, and review important notifications. How to Begin with Database as a Service Subscriptions Managing User Accounts and Managing User Roles in Managing and Monitoring Oracle Cloud, and About Database as a Service Roles and Users Generating a Secure Shell (SSH) Public/ Private Key Pair Creating a Database as a Service Instance About Network Access to a Database as a Service Instance Loading Data into the Oracle Database in a Database as a Service Instance Monitoring and Managing the Database in a Database as a Service Instance Managing and Monitoring Oracle Cloud Services in Managing and Monitoring Oracle Cloud Patch a service instance Apply a patch or roll back a patch. Patching Database as a Service Back up a service instance Back up a service instance or restore a service instance from a backup. Backing Up and Restoring a Database as a Service Instance Getting Started with Database as a Service 1-9

20 Typical Workflow for Using Database as a Service 1-10 Using Oracle Database Cloud - Database as a Service

21 2 Managing the Life Cycle of Database as a Service Instances This section describes tasks to manage the life cycle of Oracle Database Cloud - Database as a Service instances. Topics Creating a Database as a Service Instance Viewing All Database as a Service Instances Viewing Detailed Information for a Database as a Service Instance Stopping, Starting and Restarting a Database as a Service Instance Restarting a Database as a Service Compute Node Deleting a Database as a Service Instance Tracking the Number of Database as a Service Instances in an Account Creating a Database as a Service Instance To create an Oracle Database Cloud - Database as a Service instance, use the Create Database Cloud Service Instance wizard as described in the following procedure. Before You Begin Before you create a Database as a Service instance, ensure you have created the following: An SSH public/private key pair When creating a Database as a Service instance, you must associate an SSH public key with the service instance. You can upload a new public key during the service creation process, or you can specify the name of a public key that has been uploaded previously. A public key might have been uploaded previously during creation of another service instance or manually using the Oracle Compute Cloud Service console. An SSH public key is used for authentication when you use an SSH client to connect to a compute node associated with the service instance. When you connect, you must provide the private key that matches the public key. You generate an SSH public/private key pair using a standard SSH key generation tool. For more information, see Generating a Secure Shell (SSH) Public/Private Key Pair. An Oracle Storage Cloud Service container (Optional) Managing the Life Cycle of Database as a Service Instances 2-1

22 Creating a Database as a Service Instance To back up your new instance to the cloud, you first must create an Oracle Storage Cloud Service container. For information about creating a container, see Creating Containers in Using Oracle Storage Cloud Service. This container becomes associated with Oracle Database Backup Cloud Service, which Database as a Service uses to perform backups to cloud storage. Once associated with Oracle Database Backup Cloud Service, this container becomes part of your Oracle Database Public Cloud Services subscription (or trial) rather than part of an Oracle IaaS Public Cloud Services subscription (or trial). Note: Do not use the Oracle Storage Cloud container that you are using to back up Database as a Service instances for any other purpose. For example, do not also use it to back up Oracle Java Cloud Service instances. Using the container for multiple purposes can result in billing errors. When creating a Database as a Service instance, you are prompted for the following information about the container: The name of the container The user name and password of a user who has read/write access to the container Procedure To create a Database as a Service instance: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. Click Create Service. The Create Database Cloud Service Instance wizard starts and the Subscription Type page is displayed. 3. On the Subscription Type page, select the service level and billing frequency that you want to define. Then, click Next. Your choices for service level are: Oracle Database Cloud Service everything in Virtual Image, plus a database created according to specifications you provide in the wizard, plus cloud tooling that provides automatic and on-demand backups, patching and upgrading, and point-in-time recovery for your Oracle Databases. Oracle Database Cloud Service - Virtual Image a compute environment with pre-installed virtual machine images that include all software needed to create and run an Oracle Database. You connect to the virtual machine and run the Oracle Database Configuration Assistant (DBCA) to create your database. All subsequent maintenance operations, including backup, patching and upgrades, are performed by you. Your choices for billing frequency are: 2-2 Using Oracle Database Cloud - Database as a Service

23 Creating a Database as a Service Instance Hourly Pay only for the number of hours used during your billing period. You cannot switch a service instance from hourly to monthly billing frequency after it is created. Monthly Pay one price for the full month irrespective of the number of hours used. For service instances that are started in the middle of a month, the price is prorated; you pay only for the partial month from the day the instance is created. You cannot switch a service instance from monthly to hourly billing frequency after it is created. 4. On the Software Release page, select the Oracle Database software release that you want to run on your instance. Then, click Next. Your choices for software release are: Oracle Database 11g Release 2 Oracle Database 12c Release 1 5. On the Software Edition page, select the Oracle Database software edition that you want to run on your instance. Then, click Next. Your choices for software edition are: Standard Edition delivers unprecedented ease of use, power, and performance for workgroup, department-level, and Web applications. Oracle Database Standard Edition includes all the facilities necessary to build business-critical applications. This edition is only available for Oracle Database 11g Release 2. Enterprise Edition provides the performance, availability, scalability, and security required for mission-critical applications such as high-volume online transaction processing (OLTP) applications, query-intensive data warehouses, and demanding Internet applications. Enterprise Edition contains all the components of Oracle Database. Enterprise Edition - High Performance provides all the features of Enterprise Edition, plus all the database enterprise management packs and all the Enterprise Edition options except: Active Data Guard In-Memory Database Oracle RAC One Node Real Application Clusters (Oracle RAC) Enterprise Edition - Extreme Performance provides all the features of Enterprise Edition, plus all the database enterprise management packs and all the Enterprise Edition options except: Oracle RAC One Node Managing the Life Cycle of Database as a Service Instances 2-3

24 Creating a Database as a Service Instance Note: If you choose one of the Enterprise Edition variations, all available database enterprise management packs and Enterprise Edition options are included in the service instance that is created. The packs and options that are not part of the Enterprise Edition variation you chose are available to you for use on a trial basis. 6. On the Service Details page, configure details for your service instance. Then, click Next. Note: An asterisk adjacent to a field name indicates that the field is required. a. In the Instance Configuration section, select the name, description, and compute shape of your service instance and provide an SSH public key to access the instance. Instance Name enter a name for your service instance. This name: Must not exceed 50 characters (15 characters for a service instance that uses Oracle RAC). Must start with a letter. Must contain only letters, numbers, or hyphens. Must not contain any other special characters. Must be unique within the identity domain. Description enter a description for your service instance. (Optional) Compute Shape select a compute shape from the list of supported OCPU (Oracle CPU) and RAM combinations. These combinations fall into two categories: General Purpose: OC3-1 OCPU, 7.5 GB RAM OC4-2 OCPU, 15 GB RAM OC5-4 OCPU, 30 GB RAM OC6-8 OCPU, 60 GB RAM OC7-16 OCPU, 120 GB RAM High Memory: OC1M - 1 OCPU, 15 GB RAM OC2M - 2 OCPU, 30 GB RAM OC3M - 4 OCPU, 60 GB RAM 2-4 Using Oracle Database Cloud - Database as a Service

25 Creating a Database as a Service Instance OC4M - 8 OCPU, 120 GB RAM OC5M - 16 OCPU, 240 GB RAM VM Public Key provide the SSH public key to be used for authentication when using an SSH client to connect to a compute node VM that is associated with your service instance. Click Edit to specify the public key, either by uploading a key file or by entering the name of a key that was uploaded earlier. To specify the name of a key that was uploaded earlier, use the full hierarchical name of the key: /domain/user/keyname To discover the full hierarchical name of a key, view the list of keys on the Oracle Compute Cloud Service SSH Public Keys page and hover over the short name of the key. For more information, see Viewing an SSH Public Key in Using Oracle Compute Cloud Service. b. In the Database Configuration section, select the amount of data storage, administrator password, database name (SID), PDB name (for Oracle Database 12c), inclusion of Demos PDB (for Oracle Database 12c), and whether to set up Oracle Real Application Clusters (RAC) (for Oracle Database 12c) for the Oracle Database to be created in your service instance. Note: The Database Configuration section does not appear if you chose the Oracle Database Cloud Service - Virtual Image service level. Usable Database Storage (GB) enter the amount of storage you want for actual database data (in GB). Total Data File Storage (GB) the computed amount of storage in GB that will be allocated to your instance, including space for operating system and product binaries, supporting files, database data and configuration files, and so on. Administration Password and Confirm Password enter and then reenter a password for administrative access to the database and to other components of your service instance, specifically: Oracle Database SYS and SYSTEM users Oracle Application Express ADMIN user Oracle GlassFish Server admin user Cloud database monitor access The password you enter: Must be 8 to 30 characters in length. Must contain at least one lowercase letter Must contain at least one uppercase letter Managing the Life Cycle of Database as a Service Instances 2-5

26 Creating a Database as a Service Instance Must contain at least one number Must contain at least one of these symbols: _ (underscore), # (hash sign), or $ (dollar sign). DB Name (SID) enter a name for the database instance. This name: Must not exceed 8 characters. Must start with a letter. Must contain only letters, numbers, or these symbols: _ (underscore), # (hash sign), or $ (dollar sign). PDB Name (Available only for Oracle Database 12c) enter a name for the default PDB (pluggable database). This name: Must not exceed 8 characters. Must start with a letter. Must contain only letters, numbers, or these symbols: _ (underscore), # (hash sign), or $ (dollar sign). Include Demos PDB include the "Demos" PDB in the database, which contains demos for many new features of 12c such as in-memory and multitenant. Usable Data File Storage must to be at least 25 GB to include this PDB. This option is available only for Oracle Database 12c. RAC Database controls whether a two-node Oracle Real Application Clusters (RAC) database is created. This option is available only if you choose a shape with two OCPUs for trial accounts or a shape with four or more OCPUs for subscription accounts. c. In the Backup and Recovery Configuration section, choose a backup option for the database in your service and, depending on your choice, provide information about the Oracle Storage Cloud Service container where cloud backups are to be stored. Note: The Backup and Recovery Configuration section does not appear if you chose the Oracle Database Cloud Service - Virtual Image service level. Backup Destination select how backups are to be configured: Both Cloud Storage and Block Storage backups are configured to be created automatically and stored both on block storage and on an Oracle Storage Cloud Service container. If this choice is selected, the Cloud Storage Container, User Name and Password fields are displayed: Cloud Storage Container enter the name of an existing Oracle Storage Cloud Service container in the format: instance-id_domain/container 2-6 Using Oracle Database Cloud - Database as a Service

27 Viewing All Database as a Service Instances where instance is the name of the Oracle Storage Cloud Service instance, id_domain is the name of the identity domain, and container is the name of the container. Note: Do not use the Oracle Storage Cloud Service container that you are using to back up Database as a Service instances to cloud storage for any other purpose. For example, do not also use it to back up Oracle Java Cloud Service instances to cloud storage. Using the container for multiple purposes can result in billing errors. Cloud Storage User Name enter the user name of a user who has read/write access to the container specified in Cloud Storage Container. Cloud Storage Password enter the password of the user specified in Cloud Storage User Name. Block Store Only backups are configured to be created automatically and stored on block storage. None backups are not configured for your service instance. 7. On the Confirmation page, review the information listed. If you are satisfied with the information, click Create. If you need to change the information, use the navigation bar or Back button at the top of the wizard to step back through the pages in the wizard. Click Cancel to cancel out of the wizard without creating a new instance. Viewing All Database as a Service Instances From the Oracle Database Cloud Service Console, you can: View the total resources allocated across all Oracle Database Cloud - Database as a Service instances. View the details for each service instance. Use the search field to filter the list to include only the service instances that contain a given string in their name. To view all Database as a Service instances: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. The Oracle Database Cloud Service console is displayed, showing a list of all service instances. For information about the details provided on the Oracle Database Cloud Service console, see Oracle Database Cloud Service Console Page. Managing the Life Cycle of Database as a Service Instances 2-7

28 Viewing Detailed Information for a Database as a Service Instance Viewing Detailed Information for a Database as a Service Instance From the Oracle Database Cloud Service Instance Overview page, you can: View a summary of details for the Oracle Database Cloud - Database as a Service instance, such as description, subscription mode, and so on. View the total resources allocated for the Database as a Service instance. View the details and status information for each node. To view detailed information for a Database as a Service instance: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. Click on the service instance for which you want to view more information. The Oracle Database Cloud Service Instance page is displayed with the Overview tile foremost. For more information about the details provided on the Oracle Database Cloud Service Instance Overview page, see Oracle Database Cloud Service Instance Overview Page. Stopping, Starting and Restarting a Database as a Service Instance You can stop, start and restart an Oracle Database Cloud - Database as a Service instance from the Oracle Database Cloud Service console. Topics About Stopping, Starting and Restarting a Service Instance Stopping a Service Instance Starting a Stopped Service Instance Restarting a Service Instance Viewing Past Stop, Start and Restart Activity About Stopping, Starting and Restarting a Service Instance About Stopping a Service Instance When you stop a Database as a Service instance, no access to it is possible and you can perform no management operations on it except to start it or to delete it. Stopping a service instance is similar to turning off your personal computer: it has no computing capabilities because the CPU and RAM have no power, but all its other resources disk drives and the data they contain, static IP reservations, and so on remain and are ready to be put back into use when power is restored. When a Database as a Service instance is stopped, its CPU and RAM (an Oracle Compute Cloud Service instance) are stopped. As a consequence, it consumes no OCPU or memory resources and so metering and billing of these resources stop. However, all the other resources of the service instance continue to exist and so continue to be metered and billed, including: 2-8 Using Oracle Database Cloud - Database as a Service

29 Stopping, Starting and Restarting a Database as a Service Instance Oracle Compute Cloud Service resources such as storage volumes and IP address reservations Oracle Storage Cloud Service storage space used by the service instance s backups to the Oracle Cloud (if the service instance was being backed up to cloud storage) Additionally, when a Database as a Service instance is stopped, backups of the service instance are not performed. About Starting a Stopped Service Instance When you start a stopped Database as a Service instance, access to it becomes possible again and you can perform management operations on it such as scaling and patching. Starting a stopped service instance is similar to turning your personal computer back on: its computing capabilities are restored because the CPU and RAM again have power, and all its other resources are put back into use. When a Database as a Service instance is started: 1. An Oracle Compute Cloud Service instance of the appropriate compute shape (OCPU and memory) is allocated to it. 2. All other Compute Cloud Service resources associated with it at instance creation or as the result of a scaling operation are reattached to it. 3. The allocated Oracle Compute Cloud Service instance is started. After these steps complete, the Database as a Service instance is running and available. Because the started service instance again consumes OCPU and memory resources, metering and billing of these resources resume. Note: Only those Compute Cloud Service resources that became associated with the Database as a Service instance when the instance was initially created or as the result of a scaling operation are reattached when the Database as a Service instance is started. As a result, you must manually reattach the following kinds of Compute Cloud Service resources: Storage volumes you created and attached using the Oracle Compute Cloud Service console. You must attach such storage volumes to the new Oracle Compute Cloud Service instance (the compute node) once the Database as a Service instance is started, and then connect to the compute node and mount them. Security lists to which you added the Database as a Service instance s previous Oracle Compute Cloud Service instance (the compute node). You must add such security lists to the new Oracle Compute Cloud Service instance once the Database as a Service instance is started. About Restarting a Service Instance When you restart a Database as a Service instance, the service instance is stopped and then immediately started again. Thus, the information about what happens when stopping and starting a service instance applies to restarting a service instance as well, just in immediate succession. Managing the Life Cycle of Database as a Service Instances 2-9

30 Stopping, Starting and Restarting a Database as a Service Instance Note: Restarting a service instance is different from rebooting a compute node of a service instance. Rebooting a compute node, as described in Restarting a Database as a Service Compute Node, does not restart the service instance. It simply reboots the compute node. Stopping a Service Instance In general, you stop a Database as a Service instance for one of these reasons: To prohibit access to it. To reduce its cost of operation, especially if its billing frequency is hourly. Before You Begin To learn what happens when you stop a Database as a Service instance, review About Stopping, Starting and Restarting a Service Instance. Procedure To stop a service instance: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. In the list of instances, click the name of the service instance you want to stop. The Oracle Database Cloud Service Instance Overview page is displayed. 3. From the menu, select Stop, and then confirm the action. The instance first has a status of Maintenance and then Stopped in the Oracle Database Cloud Service console. Note that you cannot scale a stopped instance. Starting a Stopped Service Instance Before You Begin To learn what happens when you start a stoppeddatabase as a Service instance, review About Stopping, Starting and Restarting a Service Instance. Procedure To start a stopped service instance: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. In the list of instances, click the name of the stopped service instance you want to start. The Oracle Database Cloud Service Instance Overview page is displayed. 3. From the menu, select Start, and then confirm the action Using Oracle Database Cloud - Database as a Service

31 Stopping, Starting and Restarting a Database as a Service Instance The instance has a status of Maintenance in the Oracle Database Cloud Service console until it is fully started. Restarting a Service Instance Note: Restarting a service instance is different from rebooting a compute node of a service instance. Rebooting a compute node, as described in Restarting a Database as a Service Compute Node, does not restart the service instance. It simply reboots the compute node. Before You Begin To learn what happens when you restart a Database as a Service instance, review About Stopping, Starting and Restarting a Service Instance. Procedure To restart a service instance: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. In the list of instances, click the name of the service instance you want to restart. The Oracle Database Cloud Service Instance Overview page is displayed. 3. From the menu, select Restart, and then confirm the action. The instance has a status of Maintenance in the Oracle Database Cloud Service console until it is fully restarted. Viewing Past Stop, Start and Restart Activity You can see information about past stop, start and restart activity by viewing a service instance s activity log: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Oracle Database Cloud Service. 2. In the list of instances, click the name of the service instance whose past activity you want to view. The Oracle Database Cloud Service Instance Overview page is displayed. 3. Click the triangle icon to the left of the Activity title to expand the service instance s activity log. The activity log shows information about past operations performed on the service instance, with the most recent activity first. 4. Click the icon next to a particular operation to see details about that operation. If an operation failed, the details include information about why it failed. Managing the Life Cycle of Database as a Service Instances 2-11

32 Restarting a Database as a Service Compute Node Restarting a Database as a Service Compute Node On occasion, you might find it necessary to restart a compute node associated with an Oracle Database Cloud - Database as a Service instance. Follow these steps to perform the operation. 1. Connect to the compute node as the opc user. Unlike the oracle user, the opc user has the privileges required to perform operations that require root-user access. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. Enter the command to reboot the compute node: # reboot Caution: Do not use the halt, shutdown or shutdown h commands to shut down the compute node. Doing so will stop the compute node indefinitely and will require manual intervention by Oracle Cloud system administrators to restart the compute node. Your connection to the compute node is closed and the compute node reboots. Deleting a Database as a Service Instance When you no longer require an Oracle Database Cloud - Database as a Service instance, you can delete it. To delete a Database as a Service instance: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. From the menu for the instance, select Delete. You are prompted to confirm the deletion. Once deleted, the Database as a Service instance is removed from the list of instances displayed on the Database as a Service Console. Tracking the Number of Database as a Service Instances in an Account You can track the number of Oracle Database Cloud - Database as a Service instances across all identity domains using the My Account Dashboard page. Note that the My Account Dashboard page is different from the My Services Dashboard page: My Account Dashboard shows information for your entire account, while My Services Dashboard shows information limited to one identity domain in your account Using Oracle Database Cloud - Database as a Service

33 Tracking the Number of Database as a Service Instances in an Account To open the My Account Dashboard page, sign in to My Account. By default, the Dashboard page is in focus. You can also click Dashboard at any time to display the page. The list of services is displayed using the following naming convention: servicename (service-type). Click the service name to go to the details page, which displays status history, availability history, usage metrics, and additional information for the selected service. For information about the details provided on the Dashboard page, see Exploring the My Account Dashboard Page in Getting Started with Oracle Cloud. Managing the Life Cycle of Database as a Service Instances 2-13

34 Tracking the Number of Database as a Service Instances in an Account 2-14 Using Oracle Database Cloud - Database as a Service

35 3 Managing Network Access to a Database as a Service Instance By default, network access to an Oracle Database Cloud - Database as a Service instance is provided by using SSH. The SSH connection uses the SSH key specified during service instance creation. By default, port 22 is used for SSH connections. To access other ports you must perform additional configuration tasks, such as creating an SSH tunnel or enabling access to the port. Topics About Network Access to a Database as a Service Instance Generating a Secure Shell (SSH) Public/Private Key Pair Creating an SSH Tunnel to a Compute Node Port Enabling Access to a Compute Node Port Defining a Custom Host Name or Domain Name for Database as a Service Using Network Encryption and Integrity About Network Access to a Database as a Service Instance When an Oracle Database Cloud - Database as a Service instance is created, network access to the compute nodes of the service instance is provided by Secure Shell (SSH) connections on port 22. SSH Access on Port 22 SSH is a cryptographic network protocol that uses two keys, one public and one private, to provide secure communication between two networked computers. Port 22 is the standard TCP/IP port that is assigned to SSH servers. When a service instance is being created, the public key is specified on the Details page of the Create Database Cloud Service Instance wizard by: Uploading the public key file. When the public key file is uploaded during the service instance creation process, the key is added to the Oracle Compute Cloud Service environment that supports Database as a Service and given a unique name. Entering the full hierarchical name of an existing public key using the format / domain/user/keyname. An existing public key is one that has already been added to the Oracle Compute Cloud Service environment that supports Database as a Service, either as the result of an earlier service instance creation process or by manual addition to Oracle Managing Network Access to a Database as a Service Instance 3-1

36 Generating a Secure Shell (SSH) Public/Private Key Pair Compute Cloud Service. To discover the full hierarchical name of a key, view the list of keys on the Oracle Compute Cloud Service SSH Public Keys page and hover over the short name of the key. For more information, see Viewing an SSH Public Key in Using Oracle Compute Cloud Service. For information on manually adding a public key to Oracle Compute Cloud Service, see Adding an SSH Public Key in Using Oracle Compute Cloud Service. When you access any compute node of a Database as a Service instance using SSH, you must provide the private key that matches the public key specified when the service instance was created. To generate the SSH public/private key pairs needed to create and access Database as a Service instances, see Generating a Secure Shell (SSH) Public/Private Key Pair. Access to Other Ports To access network protocols and services on a compute node by using a port other than port 22, you must either: Enable network access to the port You use the Oracle Compute Cloud Service console to enable access to a port on a compute node. For more information, see Enabling Access to a Compute Node Port Create an SSH tunnel to the port Creating an SSH tunnel enables you to access a specific compute node port by using an SSH connection as the transport mechanism. To create the tunnel, you must have the SSH private key file that matches the public key specified when the service instance was created. For more information, see Creating an SSH Tunnel to a Compute Node Port. Generating a Secure Shell (SSH) Public/Private Key Pair Several tools exist to generate SSH public/private key pairs. The following sections show how to generate an SSH key pair on UNIX, UNIX-like and Windows platforms. Generating an SSH Key Pair on UNIX and UNIX-Like Platforms Using the ssh-keygen Utility UNIX and UNIX-like platforms (including Solaris and Linux) include the ssh-keygen utility to generate SSH key pairs. To generate an SSH key pair on UNIX and UNIX-like platforms using the ssh-keygen utility: 1. Navigate to your home directory: $ cd $HOME 2. Run the ssh-keygen utility, providing as filename your choice of file name for the private key: $ ssh-keygen -b t rsa -f filename The ssh-keygen utility prompts you for a passphrase for the private key. 3. Enter a passphrase for the private key, or press Enter to create a private key without a passphrase: 3-2 Using Oracle Database Cloud - Database as a Service

37 Generating a Secure Shell (SSH) Public/Private Key Pair Enter passphrase (empty for no passphrase): passphrase Note: While a passphrase is not required, you should specify one as a security measure to protect the private key from unauthorized use. When you specify a passphrase, a user must enter the passphrase every time the private key is used. The ssh-keygen utility prompts you to enter the passphrase again. 4. Enter the passphrase again, or press Enter again to continue creating a private key without a passphrase: Enter the same passphrase again: passphrase 5. The ssh-keygen utility displays a message indicating that the private key has been saved as filename and the public key has been saved as filename.pub. It also displays information about the key fingerprint and randomart image. Generating an SSH Key Pair on Windows Using the PuTTYgen Program The PuTTYgen program is part of PuTTY, an open source networking client for the Windows platform. To generate an SSH key pair on Windows using the PuTTYgen program: 1. Download and install PuTTY or PuTTYgen. To download PuTTY or PuTTYgen, go to and click the You can download PuTTY here link. 2. Run the PuTTYgen program. The PuTTY Key Generator window is displayed. 3. Set the Type of key to generate option to SSH-2 RSA. 4. In the Number of bits in a generated key box, enter Click Generate to generate a public/private key pair. As the key is being generated, move the mouse around the blank area as directed. 6. (Optional) Enter a passphrase for the private key in the Key passphrase box and reenter it in the Confirm passphrase box. Note: While a passphrase is not required, you should specify one as a security measure to protect the private key from unauthorized use. When you specify a passphrase, a user must enter the passphrase every time the private key is used. 7. Click Save private key to save the private key to a file. To adhere to file-naming conventions, you should give the private key file an extension of.ppk (PuTTY private key). Managing Network Access to a Database as a Service Instance 3-3

38 Creating an SSH Tunnel to a Compute Node Port 8. Select all of the characters in the Public key for pasting into OpenSSH authorized_keys file box. Make sure you select all the characters, not just the ones you can see in the narrow window. If a scroll bar is next to the characters, you aren't seeing all the characters. 9. Right click somewhere in the selected text and select Copy from the menu. 10. Open a text editor and paste the characters, just as you copied them. Start at the first character in the text editor, and do not insert any line breaks. 11. Save the text file in the same folder where you saved the private key, using the.pub extension to indicate that the file contains a public key. 12. If you or others are going to use an SSH client that requires the OpenSSH format for private keys (such as the ssh utility on Linux), export the private key: a. On the Conversions menu, choose Export OpenSSH key. b. Save the private key in OpenSSH format in the same folder where you saved the private key in.ppk format, using an extension such as.openssh to indicate the file's content. Creating an SSH Tunnel to a Compute Node Port To create an SSH tunnel to a port on a compute node associated with an Oracle Database Cloud - Database as a Service instance, you use Secure Shell (SSH) client software that supports tunneling. Several SSH clients that support tunneling are freely available. The following sections show how to use SSH clients on the Linux and Windows platforms to connect to a compute node associated with a Database as a Service instance. Creating an SSH Tunnel Using the ssh Utility on Linux The Linux platform includes the ssh utility, an SSH client that supports SSH tunneling. Before you use the ssh utility to create an SSH tunnel, you need the following: The IP address of the target compute node. The IP addresses associated with an Oracle Database Cloud - Database as a Service instance are listed on the service instance s details page. For instructions to display this page, see Viewing Detailed Information for an Oracle Database Cloud - Database as a Service Instance. The SSH private key file that pairs with the public key used when the service instance was created. The port number for which you want to create an SSH tunnel. To create an SSH tunnel for a port using the ssh utility on Linux: 1. In a command shell, set the file permissions of the private key file so that only you have access to it: $ chmod 600 private-key-file private-key-file is the path to the SSH private key file that matches the public key used when the service instance was created. 3-4 Using Oracle Database Cloud - Database as a Service

39 Creating an SSH Tunnel to a Compute Node Port 2. Run the ssh utility: $ ssh -i private-key-file -L local-port:target-ip-address:target-port opc@targetip-address where: private-key-file is the path to the SSH private key file. local-port is the number of an available port on your Linux system. Specify a port number greater than 1023 and less than to avoid conflicts with ports that are reserved for the system. As a good practice, and for the sake of simplicity, you should specify the same port number as the one to which you are creating a tunnel. target-ip-address is the IP address of the target compute node in x.x.x.x format. target-port is the port number to which you want to create a tunnel. 3. If this is the first time you are connecting to the target compute node, the ssh utility prompts you to confirm the public key. In response to the prompt, enter yes. After the SSH tunnel is created, you can access the port on the target compute node by specifying localhost:local-port on your Linux system. Creating an SSH Tunnel Using the PuTTY Program on Windows PuTTY is a freely available SSH client program for Windows that supports SSH tunneling. Before you use the ssh utility to create an SSH tunnel, you need the following: The IP address of the target compute node. The IP addresses associated with an Oracle Database Cloud - Database as a Service instance are listed on the service instance s details page. For instructions to display this page, see Viewing Detailed Information for an Oracle Database Cloud - Database as a Service Instance. The SSH private key file that pairs with the public key used when the service instance was created. The port number for which you want to create an SSH tunnel. To create an SSH tunnel for a port using the PuTTY program on Windows: 1. Download and install PuTTY. To download PuTTY, go to and click the You can download PuTTY here link. 2. Run the PuTTY program. The PuTTY Configuration window is displayed, showing the Session panel. 3. Configure SSH connectivity: a. In Host Name (or IP address) box, enter the IP address of the target compute node. Managing Network Access to a Database as a Service Instance 3-5

40 Creating an SSH Tunnel to a Compute Node Port b. Confirm that the Connection type option is set to SSH. c. In the Category tree, expand Connection if necessary and then click Data. The Data panel is displayed. d. In Auto-login username box, enter oracle. e. Confirm that the When username is not specified option is set to Prompt. f. In the Category tree, expand SSH and then click Auth. The Auth panel is displayed. g. Click the Browse button next to the Private key file for authentication box. Then, in the Select private key file window, navigate to and open the private key file that matches the public key used when the service instance was created. 4. Add a forwarded port: a. In the Category tree, click Tunnels. The Tunnels panel is displayed. b. In the Source Port box, enter the number of an available port on your system. Specify a port number greater than 1023 and less than to avoid conflicts with ports that are reserved for the system. As a good practice, and for the sake of simplicity, you should specify the same port number as the one to which you are creating a tunnel. c. In the Destination box, enter the IP address of the target compute node, a colon, and the port number to which you want to create a tunnel; for example, :1521. d. Confirm that the Local and Auto options are set. e. Click Add to add the forwarded port. The new forwarded port appears in the Forwarded ports list. 5. In the Category tree, click Session. The Session panel is displayed. 6. In the Saved Sessions box, enter a name for this connection configuration. Then, click Save. 7. Click Open to open the connection. The PuTTY Configuration window is closed and the PuTTY window is displayed. 8. If this is the first time you are connecting to the target compute node, the PuTTY Security Alert window is displayed, prompting you to confirm the public key. Click Yes to continue connecting. After the SSH tunnel is created, you can access the port on the target compute node by specifying localhost:local-port on your system, where local-port is the source port you specfied when creating the tunnel. 3-6 Using Oracle Database Cloud - Database as a Service

41 Enabling Access to a Compute Node Port Enabling Access to a Compute Node Port Oracle Database Cloud - Database as a Service relies on Oracle Compute Cloud Service to provide secure network access to Database as a Service instances. Therefore, you use the Oracle Compute Cloud Service console to perform network access operations such as enabling access to a port on a compute node associated with a Database as a Service instance. When a Database as a Service instance is created, the following Oracle Compute Cloud Service security rules are created, but set to a disabled status. ora_p2_dbconsole, which controls access to port 1158, the port used by Enterprise Manager 11g Database Control. ora_p2_dbexpress, which controls access to port 5500, the port used by Enterprise Manager Database Express 12c. ora_p2_dblistener, which controls access to port 1521, the port used by SQL*Net. ora_p2_http, which controls access to port 80, the port used for HTTP connections to the instance. ora_p2_httpadmin, which controls access to port 4848, the port used by the Oracle GlassFish Server administration console. ora_p2_httpssl, which controls access to port 443, the port used for HTTPS connections to the instance, including Oracle REST Data Services, Oracle Application Express, and the Oracle Cloud on-instance database monitor. To enable access to a compute node port, you enable the appropriate security rule. When you enable one of the predefined security rules, the given port on the compute node is opened to the public internet. If you wish to enable access to a compute node port that is not associated with an existing security rule, you must perform some additional steps to define the protocol associated with the port number and create a security rule. If you wish to restrict access to a compute node port, to only permit connections from specific IP addresses, you must create a Security IP List and associate it to the security rule. Enabling Port Access by Enabling an Automatically Created Security Rule To enable one of the automatically created Oracle Compute Cloud security rules: 1. Display the Network Security Rules page of the Oracle Compute Cloud Service console: a. Open the Oracle Compute Cloud Service console. For instructions, see Accessing Oracle Compute Cloud Service in Using Oracle Compute Cloud Service. When you open the Oracle Compute Cloud Service console, the Instance Overview page is displayed. b. Click Network. The Network page displays with the Security Rules tile foremost. 2. Locate the security rule you want to enable. Managing Network Access to a Database as a Service Instance 3-7

42 Enabling Access to a Compute Node Port 3. From the menu for the located security rule, select Update. The Update Security Rule window is displayed. 4. Change the Status from Disabled to Enabled. 5. Click Update. The Update Security Rule window closes, and a message indicating that you successfully updated the security rule is displayed above the list of security rules. Enabling Port Access by Creating a Security Rule To enable a compute node port, or range of ports, that is not associated with one of the automatically created Oracle Compute Cloud security rules: 1. Display the Network Security Applications page of the Oracle Compute Cloud Service console: a. Open the Oracle Compute Cloud Service console. For instructions, see Accessing Oracle Compute Cloud Service in Using Oracle Compute Cloud Service. When you open the Oracle Compute Cloud Service console, the Overview page is displayed with the Instances tile foremost. b. Click Network. The Network page displays with the Security Rules tile foremost. c. Click the Security Applications tile. The Network page refreshes with the Security Applications tile foremost. 2. Click Create Security Application. In the Create Security Application dialog, enter the following information. Name: Any name to identify the new port; for example, mynetport. Port Type: tcp Port Range Start: The number of the port you wish to open, or the lowest number in the range of ports that you want to open. Port Range End: The number of the port you wish to open, or the highest number in the range of ports that you want to open. Description: Any description of your choice. 3. Click Create. 4. Click the Security Rules tile on the left side of the page, and then click Create Security Rule. In the Create Security Rule dialog, enter the following information. Name: Any name to identify the security rule. Status: Enabled Security Application: Select the name of the security application you created in the steps above; for example mynetport. 3-8 Using Oracle Database Cloud - Database as a Service

43 Defining a Custom Host Name or Domain Name for Database as a Service Source: Select Security IP Lists, and then select public-internet from the list. Destination: Select the name of the security list to use as the target for this security rule. By default, Database as a Service instances are assigned to security lists named ora-db. Description: Any description of your choice. 5. Click Create. The port is opened to the public internet. Restricting Port Access to Specific IP Addresses If you wish to restrict access to a compute node port, to only permit connections from specific IP addresses: 1. Create a Security IP List that describes the IP addresses of the computers that are to be granted access to the compute node, as described in Creating a Security IP List in Using Oracle Compute Cloud Service. 2. Create a Security Rule that links your Security IP List to the compute node Security List on the Security Application (port) you want to open by setting fields in the Create Security Rule dialog as follows: Security Application: set to the name of the Security Application (port) on the compute node to which you want to provide access. Source: set to the name of the Security IP List you created. Destination: set to the ora_db security list for the compute node. Tip: You can use the above procedure Enabling Port Access by Creating a Security Rule to help you create a security rule. For more information about creating security rules, see Creating a Security Rule in Using Oracle Compute Cloud Service Defining a Custom Host Name or Domain Name for Database as a Service You can associate a custom host name or domain name to the public IP address of a compute node associated with an Oracle Database Cloud - Database as a Service instance. To associate a custom host name to the public IP address of a compute node, contact the administrator of your DNS (Domain Name Service) and request a custom DNS record for the compute node s public IP address. For example, if your domain is example.com and you wanted to use clouddb1 as the custom host name for a compute node, you would request a DNS record that associates clouddb1.example.com to your compute node's public IP address. To associate a custom domain name to the public IP address of a compute node: 1. Register your domain name through a third-party domain registration vendor, such as Register.com, Namecheap, and so on. For example, example.com. 2. Resolve your domain name to the IP address of the Database as a Service compute node, using the third-party domain registration vendor console. For more information, refer to the third-party domain registration documentation. Managing Network Access to a Database as a Service Instance 3-9

44 Using Network Encryption and Integrity You can obtain the public IP address of a compute node by viewing details as described in Viewing Detailed Information for a Database as a Service Instance. Using Network Encryption and Integrity To secure connections to your Oracle Database Cloud - Database as a Service databases, you can use native Oracle Net encryption and integrity capabilities. Encryption of network data provides data privacy so that unauthorized parties are not able to view data as it passes over the network. In addition, integrity algorithms protect against data modification and illegitimate replay. Oracle Database provides the Advanced Encryption Standard (AES), DES, 3DES, and RC4 symmetric cryptosystems for protecting the confidentiality of Oracle Net traffic. It also provides a keyed, sequenced implementation of the Message Digest 5 (MD5) algorithm or the Secure Hash Algorithm (SHA-1 and SHA-2) to protect against integrity attacks. By default, Database as a Service instances are configured to enable native Oracle Net encryption and integrity. Also, by default, Oracle Net clients are configured to enable native encryption and integrity when they connect to an appropriately configured server. If your Oracle Net client is configured to explicitly reject the use of native encryption and integrity then connection attempts will fail. You can check your configuration and verify the use of native Oracle Net encryption and integrity as follows. For more general information about configuring native Oracle Net encryption and integrity, see Configuring Network Data Encryption and Integrity in Oracle Database Security Guide. Checking your Database as a Service environment The following procedure outlines the basic steps required to confirm that native Oracle Net encryption and integrity are enabled in your Database as a Service environment. 1. In a command shell, connect to the compute node as the oracle user. See Connecting to a Compute Node Through Secure Shell (SSH). 2. Change directories to the location of the Oracle Net configuration files listener.ora and sqlnet.ora, for example: $ cd $ORACLE_HOME/network/admin $ ls *.ora listener.ora sqlnet.ora tnsnames.ora 3. View the sqlnet.ora file and confirm that it contains the following parameter settings: SQLNET.ENCRYPTION_SERVER = required SQLNET.CRYPTO_CHECKSUM_SERVER = required The required setting enables the encryption or integrity service and disallows the connection if the client side is not enabled for the security service. This is the default setting for Database as a Service instances. Checking your Oracle Net Client Configuration The following procedure outlines the basic steps required to confirm that native encryption and integrity are enabled in your Oracle Net client configuration Using Oracle Database Cloud - Database as a Service

45 Using Network Encryption and Integrity 1. In a command shell, connect to the Oracle Net client. 2. Change directories to the location of the Oracle Net configuration files tnsnames.ora and sqlnet.ora, for example: $ cd $ORACLE_HOME/network/admin $ ls *.ora sqlnet.ora tnsnames.ora 3. View the sqlnet.ora file and confirm that it does not contain the following parameter settings: SQLNET.ENCRYPTION_CLIENT = rejected SQLNET.CRYPTO_CHECKSUM_CLIENT = rejected The rejected setting explicitly disables the encryption or integrity service, even if the server requires it. When a client with an encryption or integrity service setting of rejected connects to a server with the required setting, the connection fails with the following error: ORA-12660: Encryption or crypto-checksumming parameters incompatible. Because native Oracle Net encryption and integrity are enabled in your Database as a Service environment by default, any parameter setting other than rejected, or no setting at all, would result in the use of native encryption and integrity. Verifying the use of Native Encryption and Integrity You can verify the use of native Oracle Net encryption and integrity by connecting to your Oracle database and examining the network service banner entries associated with each connection. This information is contained in the NETWORK_SERVICE_BANNER column of the V$SESSION_CONNECT_INFO view. The following example shows the SQL command used to display the network service banner entries associated with current connection: SQL> select network_service_banner from v$session_connect_info where sid in (select distinct sid from v$mystat); The following example output shows banner information for the available encryption service and the crypto-checksumming (integrity) service, including the algorithms in use: NETWORK_SERVICE_BANNER TCP/IP NT Protocol Adapter for Linux: Version Production Encryption service for Linux: Version Production AES256 Encryption service adapter for Linux: Version Production Crypto-checksumming service for Linux: Version Production SHA1 Crypto-checksumming service adapter for Linux: Version Production If native Oracle Net encryption and integrity was not in use, the banner entries would still include entries for the available security services; that is, the services linked into the Oracle Database software. However, there would be no entries indicating the specific algorithms in use for the connection. The following output shows an example: NETWORK_SERVICE_BANNER TCP/IP NT Protocol Adapter for Linux: Version Production Encryption service for Linux: Version Production Crypto-checksumming service for Linux: Version Production Managing Network Access to a Database as a Service Instance 3-11

46 Using Network Encryption and Integrity 3-12 Using Oracle Database Cloud - Database as a Service

47 4 Administering Database as a Service Instances This section describes tasks for administering an Oracle Database Cloud - Database as a Service instance and the Oracle database it contains. Topics Scaling a Database as a Service Instance Updating the Cloud Tooling on a Database as a Service Instance Maintaining the Manageability of Your Database as a Service Instance Administering Oracle REST Data Services (formerly Oracle APEX Listener) Administering Oracle GlassFish Server Loading Data into the Oracle Database in a Database as a Service Instance Tuning Performance of the Oracle Database in a Database as a Service Instance Monitoring and Managing the Database in a Database as a Service Instance Creating a Database on a Virtual Image Service Instance Scaling a Database as a Service Instance If an Oracle Database Cloud - Database as a Service instance is performing poorly or is running out of storage, you can scale up the instance. Usually, the need to scale an instance arises as the result of analyzing database performance, as described in Tuning Performance of the Oracle Database in a Database as a Service Instance. Occasionally, the need to scale an instance arises from some change made to the database or backup configuration after the instance was created. For example, if the decision to use the In-Memory Database option available in Enterprise Edition Extreme Performance was made after the instance was created, you might need to scale up the instance's compute shape to one of the high-memory options, such as scaling from "OC4-2 OCPU, 15 GB RAM" to "OC2M - 2 OCPU, 30 GB RAM". Administering Database as a Service Instances 4-1

48 Scaling a Database as a Service Instance Scaling the Compute Shape of a Service Instance Note: When you scale the compute shape of a Database as a Service instance, the service instance is put into Maintenance status during the operation and it is restarted. As a result of the restarting, any resources you ve manually added to the service instance using the Compute Cloud Service console become detached from the service instance. For more information and for instructions on reattaching such resources, see About Stopping, Starting and Restarting a Service Instance. To scale the compute shape of a service instance: 1. View the instance overview page for the service instance: a. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. b. Click the name of the instance you want to scale. The Oracle Database Cloud Service Instance Overview page is displayed. 2. Choose the scaling command: For service instances that use Oracle RAC, click the next to the service instance name and choose Scale Up/Down. For other service instances, click the menu in the box for the compute node and choose Scale Up/Down. The Scale Up/Down Service overlay is displayed. Note that the overlay includes information about the instance's current compute shape. 3. Select a new compute shape. 4. Click Yes, Scale Up/Down Service to scale the service instance. The scaling operation begins. The service instance is in Maintenance status and unavailable while the scaling operation is in progress. Scaling Up the Storage of a Service Instance Note: When you scale up the storage of a Database as a Service instance, the service instance is put into Maintenance status during the operation and it is restarted. As a result of the restarting, any resources you ve manually added to the service instance using the Compute Cloud Service console become detached from the service instance. For more information and for instructions on reattaching such resources, see About Stopping, Starting and Restarting a Service Instance. 4-2 Using Oracle Database Cloud - Database as a Service

49 Scaling a Database as a Service Instance When you scale up the storage of a service instance, a Compute Cloud Service storage volume is created and attached to the service instance. This storage volume remains attached and available to the service instance even after the service instance is restarted or is stopped and then started. Also, this storage volume exists until you delete the service instance, at which time the storage volume is also deleted. Note: A compute node in a service instance can have a maximum of ten storage volumes attached to it. To scale up the storage of a service instance: 1. View the instance overview page for the service instance: a. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. b. Click the name of the service instance you want to scale. The Oracle Database Cloud Service Instance page is displayed. 2. Choose the scaling command: For service instances that use Oracle RAC, click the next to the service instance name and choose Scale Up/Down. For other service instances, click the menu in the box for the compute node and choose Scale Up/Down. The Scale Up/Down Service overlay is displayed. 3. In the Additional Storage (GB) box, enter an amount raw storage to add to the service instance, from 1 to 1000 GB in increments of 1 GB. An Oracle Compute Cloud Service storage volume of the indicated size will be created. Note that a small percentage of this raw storage will be used for file system constructs and other overhead. Note: When adding storage to a service instance that uses Oracle Real Application Clusters (RAC), you should specify the same size as the other storage volume or volumes already in the Oracle ASM disk group you want to scale up: Data or Backup. 4. Specify how the additional storage should be allocated in the Add Storage to list: Create New Storage Volume: adds a new storage volume to the service instance and mounts it as the next available /u0n mount point. This option is not available for service instances that use Oracle Real Application Clusters. Administering Database as a Service Instances 4-3

50 Updating the Cloud Tooling on a Database as a Service Instance Extend Data Storage Volume: adds the storage volume to the existing Linux LVM disk group (or Oracle ASM disk group on service instances that use Oracle Real Application Clusters) for database data storage. Extend Backup Storage Volume: adds the storage volume to the existing Linux LVM disk group (or Oracle ASM disk group on service instances that use Oracle Real Application Clusters) for backup and FRA storage. Note: The Add Storage to list is not available for service instances created using the Oracle Database Cloud Service - Virtual Image service level. In this case, the Oracle Compute Cloud Service storage volume is added as a raw block device to the service instance. You need to format it, mount it, and update the /etc/ fstab file to make it usable in the service instance. 5. Click Yes, Scale Up/Down Service to scale the service instance. The scaling operation begins. The service instance is in Maintenance status and unavailable while the scaling operation is in progress. Updating the Cloud Tooling on a Database as a Service Instance How you update the cloud tooling on a Oracle Database Cloud - Database as a Service instance depends on the type of database running on the service instance. Topics Updating the Cloud Tooling on Service Instances Hosting Single-Instance Databases Updating the Cloud Tooling on Service Instances Hosting Oracle RAC Databases Updating the Cloud Tooling on Service Instances Hosting Single-Instance Databases To update the cloud-specific tooling on a compute node: 1. Connect to the compute node as the opc user. See Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. Navigate to the /tmp directory: # cd /tmp 4. Display information about the installed cloud tooling and note down the information: # rpm -qa grep -i dbaastools dbaastools-version_number-release_number 5. Download the RPM file containing the latest version of the cloud tooling: 4-4 Using Oracle Database Cloud - Database as a Service

51 Maintaining the Manageability of Your Database as a Service Instance # wget dbaas_patch/dbaastools.rpm 6. Get information about the cloud tooling in the downloaded RPM file: # rpm -qpi./dbaastools.rpm Name : dbaastools Relocations: (not relocatable) Version : version_number Vendor: Oracle Release : release_number Build Date: If the cloud tooling in the downloaded RPM file is newer than the installed cloud tooling, remove the installed tooling and install the new tooling: a. Remove the installed cloud tooling: # rpm -ev installed-info where installed-info is the information you noted down about the installed cloud tooling; that is, the output from the rpm -qa grep -i dbaastools command you entered earlier. b. Install the cloud tooling tooling in the downloaded RPM file: # rpm -ivh./dbaastools.rpm 8. Exit the root-user command shell: # exit $ Updating the Cloud Tooling on Service Instances Hosting Oracle RAC Databases To update the cloud-specific tooling on a compute node: 1. Connect to the compute node as the opc user. See Connecting to a Compute Node Through Secure Shell (SSH). 2. Execute the raccli update rdk subcommand: $ raccli update rdk $ Maintaining the Manageability of Your Database as a Service Instance The following best practices will ensure that your Oracle Database Cloud - Database as a Service instances stay manageable. To keep your Database as a Service manageable, follow these guidelines: Do not disable or close access to the SSH port (port 22). You can open other ports and protocols. See About Network Access to a Database as a Service Instance for information about the available options. Do not detach, change file access permissions for, or change the mount point of any storage volume attached to a compute node during the creation of your Database as a Service instance. In particular, do not unmount or change the file access permissions of /u01 through /u05. Administering Database as a Service Instances 4-5

52 Administering Oracle REST Data Services (formerly Oracle APEX Listener) For details about these volumes, see Oracle Compute Cloud Service Resources. Do not change compute node OS users and SSH key settings that were configured during the creation of your Database as a Service instance. Apply only patches that are available through the Database as a Service. Do not apply patches from any other source unless directed to by Oracle Support. Apply the quarterly Patch Set Updates (PSUs) regularly, every quarter if possible. Do not change the ports for the Oracle Cloud DBaaS Monitor, Oracle Application Express, Oracle GlassFish Server Administration Console, Oracle Net Listener, Enterprise Manager Database Express 12c, or Enterprise Manager 11g Database Control. Administering Oracle REST Data Services (formerly Oracle APEX Listener) When an Oracle Database Cloud - Database as a Service instance is created, Oracle REST Data Services is deployed to Oracle GlassFish Server and started. Note: This section does not apply to service instances that use Oracle Real Application Clusters. Such instances do not include Oracle REST Data Services. Stopping Oracle REST Data Services To stop Oracle REST Data Services, you disable the apex application in Oracle GlassFish Server: 1. Log into the Oracle GlassFish Server Administration Console. See Accessing the Oracle GlassFish Server Administration Console. 2. In the navigation tree, click Applications. The Applications page for is displayed, showing a table of deployed applications. 3. Check the box next to apex in the Applications table. 4. Click Disable Oracle GlassFish Server disables the application and then reports that it has been disabled. Starting Oracle REST Data Services To start Oracle REST Data Services, you enable the apex application in Oracle GlassFish Server: 1. Log into the Oracle GlassFish Server Administration Console. See Accessing the Oracle GlassFish Server Administration Console. 2. In the navigation tree, click Applications. 4-6 Using Oracle Database Cloud - Database as a Service

53 Administering Oracle GlassFish Server The Applications page for is displayed, showing a table of deployed applications. 3. Check the box next to apex in the Applications table. 4. Click Enable Oracle GlassFish Server enables the application and then reports that it has been enabled. Administering Oracle GlassFish Server When an Oracle Database Cloud - Database as a Service instance is created, Oracle GlassFish Server is configured and started as the application host for Oracle REST Data Services and the Oracle Cloud Database Monitor. Note: This section does not apply to service instances that use Oracle Real Application Clusters. Such instances do not currently include Oracle GlassFish Server. In general, you should not have to perform any administrative activities for Oracle GlassFish Server. The following topics are provided for the commonest operations you might need to perform. To perform other operations, see Oracle GlassFish Server Administration Guide. Topics Restarting the Oracle GlassFish Server Domain Stopping the Oracle GlassFish Server Domain Starting the Oracle GlassFish Server Domain Viewing the Oracle GlassFish Server Log Restarting the Oracle GlassFish Server Domain To restart the Oracle GlassFish Server domain: 1. Log into the Oracle GlassFish Server Administration Console. See Accessing the Oracle GlassFish Server Administration Console. 2. In the navigation tree, click server (Admin Server). The General Information page for the server is displayed. 3. Click Restart, and then click OK when prompted to restart the GlassFish Server instance. The restart page is displayed, indicating that the restart process has begun. 4. Wait a short period and then click the indicated link on the restart page. The Administration Console login page is displayed. Administering Database as a Service Instances 4-7

54 Administering Oracle GlassFish Server Stopping the Oracle GlassFish Server Domain To stop the Oracle GlassFish Server domain: 1. Log into the Oracle GlassFish Server Administration Console. See Accessing the Oracle GlassFish Server Administration Console. 2. In the navigation tree, click server (Admin Server). The General Information page for the server is displayed. 3. Click Stop, and then click OK when prompted to stop the GlassFish Server instance The shutdown page is displayed, providing information about how to start again. Starting the Oracle GlassFish Server Domain To start the Oracle GlassFish Server domain after it has been stopped, you must connect to the service instance and use the asadmin utility: 1. Connect to the compute node where you wish to start the Oracle GlassFish Server Domain. See Connecting to a Compute Node Through Secure Shell (SSH). 2. Run the asadmin utility: $ /u01/app/oracle/product/glassfish3/bin/asadmin The asadmin utility starts: Use "exit" to exit and "help" for online help. asadmin> 3. Confirm that domain1 is not running by using the list-domains subcommand: asadmin> list-domains domain1 not running Command list-domains executed successfully. asadmin> 4. Start the domain by using the start-domain subcommand: asadmin> start-domain domain1 Waiting for domain1 to start... Successfully started the domain : domain1 domain Location: /u01/app/oracle/product/glassfish3/glassfish/domains/domain1 Log File: /u01/app/oracle/product/glassfish3/glassfish/domains/domain1/logs/ server.log Admin Port: 4848 Command start-domain executed successfully. asadmin> 5. Exit asadmin: asadmin> exit Command multimode executed successfully. $ Viewing the Oracle GlassFish Server Log To view the Oracle GlassFish Server log: 4-8 Using Oracle Database Cloud - Database as a Service

55 Loading Data into the Oracle Database in a Database as a Service Instance 1. Log into the Oracle GlassFish Server Administration Console. See Accessing the Oracle GlassFish Server Administration Console. 2. In the navigation tree, click server (Admin Server). The General Information page for the server is displayed. 3. Click View Log Files. The Log Viewer is displayed in a new browser window. Loading Data into the Oracle Database in a Database as a Service Instance You load data into the Oracle database in an Oracle Database Cloud - Database as a Service instance using the same tools you would use for an Oracle database on your system or in your data center. The fact that the database is housed in the Oracle Cloud does not place any restrictions on data-loading. However, transmission speeds across the Internet tend to be slower, sometimes much slower, than on internal networks, and any data loading approach that you use should factor this in. For the sake of efficiency, therefore, it typically makes sense to move the operating system files containing the data on to a compute node associated with the service instance using a single bulk transfer before the data-loading operation is performed. Consequently, the processing associated with the data loading operation occurs within the service instance and proceeds more rapidly. The following sections outline several common tools and techniques used to load data into an Oracle database, providing links to further documentation about using the tool or technique. Using SQL*Loader to Load Data into the Database SQL*Loader is a high-speed data loading utility that loads data from external files into tables in an Oracle database. SQL*Loader accepts input data in a variety of formats, can perform filtering, and can load data into multiple Oracle database tables during the same load session. SQL*Loader provides three methods for loading data: Conventional Path Load, Direct Path Load, and External Table Load. For information, see SQL Loader in Oracle Database 12c Utilities or Oracle Database 11g Utilities. Using Oracle Data Pump Import to Load Data into the Database Oracle Data Pump is an Oracle Database feature that offers very fast bulk data and metadata movement between Oracle databases. Oracle Data Pump provides two highspeed, parallel utilities: Export (expdp) and Import (impdp). Data Pump automatically manages multiple, parallel streams for maximum throughput of unload and load operations. The degree of parallelism can be adjusted on-the-fly. For information, see Data Pump Import in Oracle Database 12c Utilities or Oracle Database 11g Utilities. Using Transportable Tablespaces to Load Data into the Database Transportable Tablespaces is an Oracle Database feature that copies a set of tablespaces from one Oracle database to another. Moving data using transportable tablespaces can be much more efficient than performing either an export/import or Administering Database as a Service Instances 4-9

56 Tuning Performance of the Oracle Database in a Database as a Service Instance unload/load of the same data. This is because the tablespace datafiles are copied to the destination location, which avoids the cost of formatting the data into Oracle blocks. Also, in some circumstances your Transportable Tablespace can contain previously encrypted or compressed data, which avoids the cost of decrypting and re-encrypting, or expanding and re-compressing the data. For information, see Transporting Tablespaces Between Databases in Oracle Database 12c Administrator's Guide or Oracle Database 11g Administrator's Guide. Using Pluggable Databases (PDBs) to Load Data into the Database The multitenant architecture of Oracle Database 12c supports the moving of a pluggable database (PDB) from one container database (CDB) to another. This capability makes it easy to load data into a Database as a Service instance, provided that the source data is already inside a PDB on Oracle Database 12c. For information about PDBs and how to unplug, move, and plug them, see Overview of Managing a Multitenant Environment in Oracle Database 12c Administrator's Guide. Tuning Performance of the Oracle Database in a Database as a Service Instance You tune the performance of the Oracle database in an Oracle Database Cloud - Database as a Service instance using the same tools you would use for an Oracle database running on any system in your data center. The fact that the database is housed in the Oracle Cloud does not place any restrictions on performance tuning. The Oracle Database 12c Performance Tuning Guide and Oracle Database 11g Performance Tuning Guide provide extensive information about how to use Oracle Database performance tools to optimize database performance. They also describe performance best practices and include performance-related reference information. Additionally, the Enterprise Manager Tuning and Performance option packs are included in service instances created using the Enterprise Edition High Performance edition of Oracle Database. These option packs provide several utilities to assist in maintaining performance and identifying and correcting performance issues. If your performance tuning activities indicate that you need more computing power or more storage, you can scale your service instance to satisfy the need. For information, see Scaling a Database as a Service Instance. Monitoring and Managing the Database in a Database as a Service Instance To monitor and manage the Oracle database hosted in an Oracle Database Cloud - Database as a Service instance, you can use the standard management tool provided with the version of the database: For Oracle Database 12c, use Enterprise Manager Database Express 12c. To access this manager, see Accessing Enterprise Manager Database Express 12c. For Oracle Database 11g, use Enterprise Manager 11g Database Control. To access this manager, see Accessing Enterprise Manager 11g Database Control. Beyond these standard tools, Database as a Service provides Oracle DBaaS Monitor. This monitor, unique to Oracle Database Cloud Services, supports monitoring and 4-10 Using Oracle Database Cloud - Database as a Service

57 Creating a Database on a Virtual Image Service Instance management of both versions of Oracle Database and of Oracle GlassFish Server. For more information, see Using the Oracle DBaaS Monitor. Creating a Database on a Virtual Image Service Instance When you create an Oracle Database Cloud - Database as a Service instance using the Virtual Image service level, Oracle Database is not automatically installed, nor is a database created. You perform these steps manually after the instance is created. The Virtual Image service level is provided for experienced Oracle Database administrators to create custom database configurations. Consequently, the characteristics and of the database and the specific method used to create the database can vary widely. The following procedure lists the general tasks you need to perform. For a worked example that presents a simple case of performing the procedure, see Creating a Database on a Virtual Image Service Instance: Example. Procedure To create a database on a Virtual Image service instance, you perform these tasks: 1. Create and attach Oracle Compute Cloud Service storage volumes for the Oracle Database software and for the database, and then format and mount them. 2. Expand the Oracle Database software stored on the service instance to the mount point you created for it. 3. Create a database and start the database instance. 4. Start the listener for the database instance. 5. Create Oracle Compute Cloud Service security rules to permit access to services of the database from outside the Oracle Cloud. Creating a Database on a Virtual Image Service Instance: Example This example provides a step-by-step demonstration of the tasks required to create a database on a Virtual Image service instance. Because this example shows only the most simplistic techniques for many of the steps, you should not use it exactly as it is presented. Instead, consider it a recipe that you adapt and extend to suit your needs. This example uses an Oracle Database Cloud - Database as a Service instance named example-vi, created using the Virtual Image service level and specifying Oracle Database 12c Enterprise Edition. This example performs the following tasks: 1. Determine the minimum space needed for the Oracle Database software. 2. Create one storage volume for the Oracle Database software and one storage volume for all database files, and prepare them for use. 3. Expand the Oracle Database software to the storage prepared for it. 4. Create a database and start the database instance using the Database Configuration Assistant (DBCA) silent mode. 5. Start the listener for the database instance. 6. Confirm local access to the database. Administering Database as a Service Instances 4-11

58 Creating a Database on a Virtual Image Service Instance 7. Create an security rule to enable remote access to the database. 8. Confirm remote access to the database. Determine the space needed for the Oracle Database software 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Determine the name of the zip file containing the Oracle Database software by displaying the contents of the /scratch/db directory: $ ls /scratch/db db12102_bits.tar.gz 3. Compute the expanded size of the zip file: $ zcat /scratch/db/db12102_bits.tar.gz wc --bytes Divide the listed result by 1,000,000,000 to get an approximate size in Gigabytes (GB). In this example, the approximate size is 7.5 GB. 5. Close your connection to the compute node: $ exit Create storage volumes and prepare them for use 1. Create a 10 GB storage volume for the Oracle Database software. (Note that this 10 GB value is larger than the minimum 7.5 GB determined earlier to allow for additional software to be added later.) Use the scaling feature of the Oracle Database Cloud Service console to add a 10 GB volume to the example-vi service instance. For instructions, see Scaling a Database as a Service Instance 2. Create a 15 GB storage volume for all database files. (Note that this example creates a single volume for all database-related files. In actual usage, you would create separate volumes for database data, for the fast recovery area and for the redo logs.) Use the scaling feature of the Oracle Database Cloud Service console to add a 15 GB volume to the example-vi service instance. For instructions, see Scaling a Database as a Service Instance 3. Start a root user command shell on the Virtual Image service instance's compute node: a. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). b. Start a root user command shell: $ sudo -s # 4-12 Using Oracle Database Cloud - Database as a Service

59 Creating a Database on a Virtual Image Service Instance 4. Display the list of block devices, noting the presence of the two volumes you created, xvdc and xvdd: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT xvdb 202: G 0 disk xvdb1 202: M 0 part /boot xvdb2 202: G 0 part / xvdb3 202:19 0 4G 0 part [SWAP] xvdc 202: G 0 disk xvdd 202: G 0 disk 5. Format the volume for the Oracle Database software and mount it as /u01: a. Use the fdisk command to create a single, primary partition that occupies the entire volume. In the following use of fdisk, the responses you enter are highlighted. These responses are: c and then u to switch off DOS-compatible mode and change display units to sectors, respectively. n and then p and then 1 to create a new partition, make it the primary partition, and make it partition number 1, respectively. Pressing Enter twice to accept the first available sector as the start of the partition and then to accept the last available sector as the end of the partition. p to print the partition table. (Note the name of the new partition as displayed in the Device column.) w to write the partition table to disk and exit fdisk. # fdisk /dev/xvdc Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel with disk identifier 0xf770fc66. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) WARNING: DOS-compatible mode is deprecated. It's strongly recommended to switch off the mode (command 'c') and change display units to sectors (command 'u'). Command (m for help): c DOS Compatibility flag is not set Command (m for help): u Changing display/entry units to sectors Command (m for help): Command (m for help): n Command action e extended p primary partition (1-4) p Administering Database as a Service Instances 4-13

60 Creating a Database on a Virtual Image Service Instance Partition number (1-4): 1 First sector ( , default 2048): (Press Enter) Using default value 2048 Last sector, +sectors or +size{k,m,g} ( , default ): (Press Enter) Using default value Command (m for help): p Disk /dev/xvdc: 10.7 GB, bytes 255 heads, 63 sectors/track, 1305 cylinders, total sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xf770fc66 Device Boot Start End Blocks Id System /dev/xvdc Linux Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. b. Use the mkfs command to make a filesystem of type ext4 on the partition: # mkfs -t ext4 /dev/xvdc1 mke2fs (17-May-2010) Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks inodes, blocks blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks= block groups blocks per group, fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, , , , , , Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 29 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. c. Create a directory to use as the mount point: # mkdir /u01 d. Use the mount command to mount the partition to the directory: # mount /dev/xvdc1 /u01 e. Use the chown and chmod commands to set the ownership and permissions of /u01: 4-14 Using Oracle Database Cloud - Database as a Service

61 Creating a Database on a Virtual Image Service Instance # chown oracle:oinstall /u01 # chmod 755 /u01 6. Format the volume for the database and its related files, and mount it as /u02: a. Use the fdisk command to create a single, primary partition that occupies the entire volume. # fdisk /dev/xvdd Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel with disk identifier 0xa0e1ae04. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable. Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite) WARNING: DOS-compatible mode is deprecated. It's strongly recommended to switch off the mode (command 'c') and change display units to sectors (command 'u'). Command (m for help): c DOS Compatibility flag is not set Command (m for help): u Changing display/entry units to sectors Command (m for help): n Command action e extended p primary partition (1-4) p Partition number (1-4): 1 First sector ( , default 2048): (Press Enter) Using default value 2048 Last sector, +sectors or +size{k,m,g} ( , default ): (Press Enter) Using default value Command (m for help): p Disk /dev/xvdd: 16.1 GB, bytes 255 heads, 63 sectors/track, 1958 cylinders, total sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xa0e1ae04 Device Boot Start End Blocks Id System /dev/xvdd Linux Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. Syncing disks. b. Use the mkfs command to make a filesystem of type ext4 on the partition: # mkfs -t ext4 /dev/xvdd1 mke2fs (17-May-2010) Administering Database as a Service Instances 4-15

62 Creating a Database on a Virtual Image Service Instance Filesystem label= OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) Stride=0 blocks, Stripe width=0 blocks inodes, blocks blocks (5.00%) reserved for the super user First data block=0 Maximum filesystem blocks= block groups blocks per group, fragments per group 8192 inodes per group Superblock backups stored on blocks: 32768, 98304, , , , , , , Writing inode tables: done Creating journal (32768 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 26 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. c. Create a directory to use as the mount point: # mkdir /u02 d. Use the mount command to mount the partition to the directory: # mount /dev/xvdd1 /u02 e. Use the chown and chmod commands to set the ownership and permissions of /u02: # chown oracle:oinstall /u02 # chmod 755 /u02 7. Display the list of block devices again, this time displaying the UUID, mount point, and filesystem for each device : # lsblk -o NAME,UUID,MOUNTPOINT,FSTYPE NAME UUID MOUNTPOINT FSTYPE xvdb xvdb c-7bf0-45f6-a2b7-d53d3f3bcfa7 /boot ext4 xvdb2 d69d8e28-fbdf-4e98-93cf-1f8d4bf52ae3 / ext4 xvdb3 f913a5e3-8bc bdc8-a3266b0a609f [SWAP] swap xvdc xvdc1 6843a9df-fc64-4c9e b7c2bd8b75f /u01 ext4 xvdd xvdd1 cc5340a8-2b72-4bed-920d-5a4ac5e9193c /u02 ext4 Note the addition and mounting of the two partitions you created, xvdc1 and xvdd1. 8. Add entries for the two new partitions to the /etc/fstab file so that they get mounted whenever the VM is rebooted. To add the entries, use an editor such as vim and the UUID, mount point and filesystem information from the lsblk command you just ran. Here is an example of the /etc/fstab file with entries for the new partitions highlighted at the end: 4-16 Using Oracle Database Cloud - Database as a Service

63 Creating a Database on a Virtual Image Service Instance # # /etc/fstab # Created by anaconda on Mon Jun 10 07:01: # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=d69d8e28-fbdf-4e98-93cf-1f8d4bf52ae3 / ext4 defaults,barrier=0 1 1 UUID= c-7bf0-45f6-a2b7-d53d3f3bcfa7 /boot ext4 defaults 1 2 UUID=f913a5e3-8bc bdc8-a3266b0a609f swap swap defaults 0 0 /tmp /var/tmp none bind 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode= sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 UUID=6843a9df-fc64-4c9e b7c2bd8b75f /u01 ext4 defaults 0 0 UUID=cc5340a8-2b72-4bed-920d-5a4ac5e9193c /u02 ext4 defaults End the root user command shell and close your connection to the compute node: # exit $ exit Expand the Oracle Database software 1. Expand the zip file into the /u01 directory: a. Connect as the oracle user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). b. Change to the /u01 directory: $ cd /u01 c. Determine the name of the zip file containing the Oracle Database software by displaying the contents of the /scratch/db directory: $ ls /scratch/db db12102_bits.tar.gz d. Expand the zip file into the current directory (/u01): $ tar -vxzf /scratch/db/db12102_bits.tar.gz e. Close your connection to the compute node: $ exit 2. Run the set-up scripts as the root user: a. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). Administering Database as a Service Instances 4-17

64 Creating a Database on a Virtual Image Service Instance b. Start the root user command shell: $ sudo -s # c. Run the orainstroot.sh script: # /u01/app/orainventory/orainstroot.sh Changing permissions of /u01/app/orainventory. Adding read,write permissions for group. Removing read,write,execute permissions for world. Changing groupname of /u01/app/orainventory to oinstall. The execution of the script is complete. d. Run the root.sh script: # /u01/app/oracle/product/12.1.0/dbhome_1/root.sh Check /u01/app/oracle/product/12.1.0/dbhome_1/install/root_examplevi_timestamp.log for the output of root script e. End the root user command shell and close your connection to the compute node: # exit $ exit Create a database 1. Connect as the oracle user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Define and export the environment variables necessary to run DBCA: $ export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1 $ export PATH=$ORACLE_HOME/OPatch:$ORACLE_HOME/bin:$PATH $ export ORACLE_BASE=/u02/app/oracle Note that ORACLE_BASE is set to /u02/app/oracle instead of the more common /u01/app/oracle. This deviation from common practice causes all of the created database s files to reside under /u02/app/oracle. 3. Run the DBCA utility in silent mode to create the database and start the database instance: $ dbca -silent -createdatabase -templatename General_Purpose.dbc \ > -gdbname ORCL -sid ORCL -syspassword Pa55_WoRd \ > -systempassword Pa55_WoRd -createascontainerdatabase true \ > -numberofpdbs 1 -pdbname PDB1 -pdbadminpassword Pa55_WoRd \ > -emconfiguration NONE -storagetype FS \ > -memorypercentage 10 -automaticmemorymanagement true Copying database files 1% complete 2% complete 27% complete Creating and starting Oracle instance 29% complete 32% complete 33% complete 34% complete 4-18 Using Oracle Database Cloud - Database as a Service

65 Creating a Database on a Virtual Image Service Instance 38% complete 42% complete 43% complete 45% complete Completing Database Creation 48% complete 51% complete 53% complete 62% complete 70% complete 72% complete Creating Pluggable Databases 78% complete 100% complete Look at the log file "/u02/app/oracle/cfgtoollogs/dbca/orcl/orcl.log" for further details. Start the listener While still connected to the compute node as the oracle user, use the lsnrctl command to start the database listener: $ lsnrctl START Confirm local access 1. While still connected to the compute node as the oracle user, set and export the ORACLE_SID environment variable: $ export ORACLE_SID=ORCL 2. Use SQL*Plus to connect to the database and confirm local access: $ sqlplus SQL*Plus: Release Production on timestamp Copyright (c) 1982, 2014, Oracle. All rights reserved. Enter user-name: SYSTEM Enter password: (Type Pa55_WoRd and then press Enter) Connected to: Oracle Database 12c Enterprise Edition Release bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options SQL> select * from dual; D - X SQL> exit; Disconnected from Oracle Database 12c Enterprise Edition Release bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options Administering Database as a Service Instances 4-19

66 Creating a Database on a Virtual Image Service Instance Create an security rule for remote access 1. Display the Network Security Applications page of the Oracle Compute Cloud Service console: a. Open the Oracle Compute Cloud Service console. For instructions, see Accessing Oracle Compute Cloud Service in Using Oracle Compute Cloud Service. When you open the Oracle Compute Cloud Service console, the Overview page is displayed with the Instances tile foremost. b. Click Network. The Network page displays with the Security Rules tile foremost. c. Click the Security Applications tile. The Network page refreshes with the Security Applications tile foremost. 2. Click Create Security Application. The Create Security Application window displays. 3. Fill out the fields as follows: Name: enter example-vi-sqlnet Port Type: select tcp. Port Range Start: enter Port Range End: enter Click Create. The Create Security Application window closes and the new security application is added to the list of security applications. 5. Click the Security Rules tile. The Network page refreshes with the Security Rules tile foremost. 6. Click Create Security Rule. The Create Security Rule window displays. 7. Fill out the fields as follows: Name: enter example-vi-sqlnet-1521 rule. Status: select Enabled. Security application: select example-vi-sqlnet Source: select Security IP Lists and then select public-internet. Destination: display the list of choices. Then, select the ora_db entry that includes example-vi. 8. Click Create Using Oracle Database Cloud - Database as a Service

67 Creating a Database on a Virtual Image Service Instance The Create Security Rule window closes and the new security rule is added to the list of security rules. Confirm remote access To confirm remote access to the database through the SQL*Net security rule, create a connection to the database in Oracle SQL Developer. When creating the connection, fill out the fields as follows: Username: enter SYSTEM. Password: enter Pa55_WoRd. Hostname: enter the Public IP address of the compute node associated with the service instance. To find out this address, display details of the service as described in Viewing Detailed Information for a Database as a Service Instance. Port: enter SID: enter ORCL. After entering values, click Test to test the connection. Administering Database as a Service Instances 4-21

68 Creating a Database on a Virtual Image Service Instance 4-22 Using Oracle Database Cloud - Database as a Service

69 5 Accessing a Database as a Service Instance This section describes how to access tools, utilities and interfaces available in an Oracle Database Cloud - Database as a Service instance. Topics Connecting to a Compute Node Through Secure Shell (SSH) Accessing Enterprise Manager Database Express 12c Accessing Enterprise Manager 11g Database Control Accessing the Oracle Pluggable Database Self-Service Provisioning Application Accessing the Oracle Application Express Administration Console Accessing the Oracle Application Express Home Page Connecting Remotely to the Database by Using Oracle Net Services Accessing the Oracle GlassFish Server Administration Console Connecting to a Compute Node Through Secure Shell (SSH) To gain local access the tools, utilities and other resources on a compute node associated with an Oracle Database Cloud - Database as a Service instance, you use Secure Shell (SSH) client software to establish a secure connection and log in as the user oracle or the user opc. Several SSH clients are freely available. The following sections show how to use SSH clients on UNIX, UNIX-like and Windows platforms to connect to a compute node associated with a Database as a Service instance. Connecting to a Compute Node Using the ssh Utility on UNIX and UNIX-Like Platforms UNIX and UNIX-like platforms (including Solaris and Linux) include the ssh utility, an SSH client. Before You Begin Before you use the ssh utility to connect to a compute node, you need the following: The IP address of the compute node The IP address of a compute node associated with an Oracle Database Cloud - Database as a Service instance is listed on the instance's Oracle Database Cloud Service Instance page. For instructions to display this page, see Viewing Detailed Information for a Database as a Service Instance. Accessing a Database as a Service Instance 5-1

70 Connecting to a Compute Node Through Secure Shell (SSH) The SSH private key file that pairs with the public key that is associated with the service instance. Procedure To connect to a compute node using the ssh utility on UNIX and UNIX-like platforms: 1. In a command shell, set the file permissions of the private key file so that only you have access to it: $ chmod 600 private-key-file private-key-file is the path to the SSH private key file that matches the public key that is associated with the service instance. 2. Run the ssh utility: $ ssh -i private-key-file user-name@node-ip-address where: private-key-file is the path to the SSH private key file. user-name is the operating system user you want to connect as: Connect as the user oracle to perform most operations; this user does not have root access to the compute node. On service instances that use Oracle RAC, you cannot by default connect as the oracle user. You must add the public key to the user s $HOME/.ssh/authorized_keys file to grant SSH access. Connect as the user opc to perform operations that require root access to the compute node, such as backing up or patching; this user can use the sudo command to gain root access to the compute node. node-ip-address is the IP address of the compute node in x.x.x.x format. 3. If this is the first time you are connecting to the compute node, the ssh utility prompts you to confirm the public key. In response to the prompt, enter yes. Connecting to a Compute Node Using the PuTTY Program on Windows PuTTY is a freely available SSH client program for Windows. Before You Begin Before you use the PuTTY program to connect to a compute node, you need the following: The IP address of the compute node The IP address of a compute node associated with an Oracle Database Cloud - Database as a Service instance is listed on the instance's Oracle Database Cloud Service Instance page. For instructions to display this page, see Viewing Detailed Information for a Database as a Service Instance. The SSH private key file that pairs with the public key that is associated with the service instance. This private key file must of the PuTTY.ppk format. If the private 5-2 Using Oracle Database Cloud - Database as a Service

71 Connecting to a Compute Node Through Secure Shell (SSH) key file was originally created on the Linux platform, you can use the PuTTYgen program to convert it to the.ppk format. Procedure To connect to a compute node using the PuTTY program on Windows: 1. Download and install PuTTY. To download PuTTY, go to and click the You can download PuTTY here link. 2. Run the PuTTY program. The PuTTY Configuration window is displayed, showing the Session panel. 3. In Host Name (or IP address) box, enter the IP address of the compute node. 4. Confirm that the Connection type option is set to SSH. 5. In the Category tree, expand Connection if necessary and then click Data. The Data panel is displayed. 6. In Auto-login username box, enter the user you want to connect as: Connect as the user oracle to perform most operations; this user does not have root access to the compute node. On service instances that use Oracle RAC, you cannot by default connect as the oracle user. You must add the public key to the user s $HOME/.ssh/authorized_keys file to grant SSH access. Connect as the user opc to perform operations that require root access to the compute node, such as backing up or patching; this user can use the sudo command to gain root access to the compute node. 7. Confirm that the When username is not specified option is set to Prompt. 8. In the Category tree, expand SSH and then click Auth. The Auth panel is displayed. 9. Click the Browse button next to the Private key file for authentication box. Then, in the Select private key file window, navigate to and open the private key file that matches the public key that is associated with the service instance. 10. In the Category tree, click Session. The Session panel is displayed. 11. In the Saved Sessions box, enter a name for this connection configuration. Then, click Save. 12. Click Open to open the connection. The PuTTY Configuration window is closed and the PuTTY window is displayed. 13. If this is the first time you are connecting to the VM, the PuTTY Security Alert window is displayed, prompting you to confirm the public key. Click Yes to continue connecting. Accessing a Database as a Service Instance 5-3

72 Accessing Enterprise Manager Database Express 12c Accessing Enterprise Manager Database Express 12c Enterprise Manager Database Express 12c (EM Express), a web-based tool for managing Oracle Database 12c, is available on Oracle Database Cloud - Database as a Service instances created using Oracle Database 12c Release 1. How you access EM Express depends on whether the EM Express port (5500) been unblocked. When a Database as a Service instance is first created, the EM Express port is blocked to ensure network security. For information about unblocking a specific port, see Enabling Access to a Compute Node Port. Accessing EM Express When Its Port Is Unblocked To access EM Express when its port is unblocked: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. From the menu for the instance, select Open EM Console. The EM Express login page is displayed. 3. Enter SYSTEM as the user name, enter the password specified when the service instance was created, and then click Login. To connect with SYSDBA privileges, select the check box next to as sysdba, enter SYS as the user name, enter the password specified when the service instance was created, and then click Login. This option is also available from the Instance Overview page. menu on the Oracle Database Cloud Service Alternatively, you can access EM Express by directing your browser to the URL where node-ip-address is the public IP address of the compute node. Note: On a service instance hosting an Oracle RAC database, the link Open EM Console opens EM Express on node 1 of the service instance. To open EM Express on node 2 of the service instance, direct your browser to the URL where node-ip-address is the public IP address of node 2. Accessing EM Express When Its Port Is Blocked To access EM Express when its port is blocked, you must create an SSH tunnel to port 5500 on the compute node hosting EM Express. For information about creating an SSH tunnel, see Creating an SSH Tunnel to a Compute Node Port. After the SSH tunnel is created, you can access EM Express by directing your browser to the URL After the EM Express login page is displayed, enter SYSTEM as the user name, enter the password specified when the service instance was created, and then click Login. To connect with SYSDBA privileges, select the check box next to as sysdba, enter SYS 5-4 Using Oracle Database Cloud - Database as a Service

73 Accessing Enterprise Manager 11g Database Control as the user name, enter the password specified when the service instance was created, and then click Login. Accessing Enterprise Manager 11g Database Control Enterprise Manager 11g Database Control (Database Control), a web-based tool for managing Oracle Database 11g, is available on Oracle Database Cloud - Database as a Service instances created using Oracle Database 11g Release 2. How you access Database Control depends on whether the Database Control port (1158) has been unblocked. When a Database as a Service instance is first created, the Database Control port is blocked to ensure network security. For information about unblocking a port, see Enabling Access to a Compute Node Port. Accessing Database Control When Its Port Is Unblocked To access Database Control when its port on the instance is unblocked: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. From the menu for the instance, select Open EM Console. The Database Control login page is displayed. 3. Enter SYSTEM as the user name, enter the password specified when the service instance was created, and then click Login. To connect with SYSDBA privileges, select SYSDBA from the drop-down list, enter SYS as the user name, enter the password specified when the service instance was created, and then click Login. This option is also available from the Instance page. menu on the Oracle Database Cloud Service Alternatively, you can access Database Control by directing your browser to the URL where node-ip-address is the public IP address of the compute node. Note: On a service instance hosting an Oracle RAC database, the link Open EM Console opens Database Control on node 1 of the service instance. To open Database Control on node 2 of the service instance, direct your browser to the URL where node-ip-address is the public IP address of node 2. Accessing Database Control When Its Port Is Blocked To access Database Control when its port on the instance is blocked, you must create an SSH tunnel to port 1158 on the compute node hosting Database Control. For information about creating an SSH tunnel, see Creating an SSH Tunnel to a Compute Node Port. After the SSH tunnel is created, you can access Database Control by directing your browser to the URL Accessing a Database as a Service Instance 5-5

74 Accessing the Oracle Pluggable Database Self-Service Provisioning Application After the Database Control login page is displayed, enter SYSTEM as the user name, enter the password specified when the service instance was created, and then click Login. To connect with SYSDBA privileges, select SYSDBA from the drop-down list, enter SYS as the user name, enter the password specified when the service instance was created, and then click Login. Accessing the Oracle Pluggable Database Self-Service Provisioning Application The Oracle Pluggable Database Self-Service Provisioning application provides an interface to Oracle Database 12c Multitenant option and allows for the provisioning of Pluggable Databases (PDBs). You can perform PDB operations including create, clone, open/close, plug/unplug, and drop. Additionally, you can grant others access to the application, giving them rights to create and manage their own PDBs within the quota limits you set. Note: This section does not apply to service instances that use Oracle Real Application Clusters. Such instances do not currently include the Oracle Pluggable Database Self-Service Provisioning application. How you access the Pluggable Database Self-Service Provisioning application depends on whether the HTTP port (80) has been unblocked. When an Oracle Database Cloud - Database as a Service instance is first created, the HTTP port is blocked to ensure network security. For information about unblocking a port, see Enabling Access to a Compute Node Port. Accessing the Application When the HTTP Port Is Unblocked To access the Oracle Pluggable Database Self-Service Provisioning application when the HTTP port on the instance is unblocked: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. From the menu for the service instance, select Open PDB Provisioning Console. The Oracle Pluggable Database Self-Service Provisioning login page is displayed. 3. Enter admin as the user name and the password specified when the instance was created as the password, and then click Login. This option is also available from the Instance Overview page. menu on the Oracle Database Cloud Service Alternatively, you can access the Oracle Pluggable Database Self-Service Provisioning login page by directing your browser to the URL apex/f?p=pdbss, where node-ip-address is the public IP address of the compute node hosting the application. 5-6 Using Oracle Database Cloud - Database as a Service

75 Connecting Remotely to the Database by Using Oracle Net Services Accessing the Application When the HTTP Port Is Blocked To access the Oracle Pluggable Database Self-Service Provisioning application when the HTTP port on the instance is blocked, you must create an SSH tunnel to port 80 on the compute node hosting the application. For information about creating an SSH tunnel, see Creating an SSH Tunnel to a Compute Node Port. After the SSH tunnel is created, you can access the Pluggable Database Self-Service Provisioning application by directing your browser to the URL apex/f?p=pdbss. After the Oracle Pluggable Database Self-Service Provisioning login page is displayed, enter admin as the user name, enter the password specified when the service instance was created, and then click Login. Connecting Remotely to the Database by Using Oracle Net Services Note: How you connect to an Oracle RAC database on a Database as a Service instance differs from how you connect to a non-clustered database. For information, see Creating an Oracle Net Connection to an Oracle RAC Database. Oracle Database Cloud - Database as a Service instances support access to the Oracle Database on the standard Oracle Net Listener port (1521). How you make a Oracle Net connection to the Oracle Database depends on whether the Oracle Net Listener port has been unblocked. When a Database as a Service instance is first created, the Oracle Net Listener port is blocked to ensure network security. For information about unblocking a port, see Enabling Access to a Compute Node Port. Before You Can Connect In order to make a remote database connection by using Oracle Net Services, you require pieces of information: The IP address for the compute node that you wish to connect to. You can obtain this information by viewing details as described in Viewing Detailed Information for a Database as a Service Instance. The database identifier, either the database SID or service name. For service instances running Oracle Database 11g, you can identify the database by using the SID. For service instances running Oracle Database 12c, connecting to the database by specifying the database SID connects you to the CDB (container database). To connect to a PDB (pluggable database), specify the service name of the pluggable database. In Database as a Service, the format of a database service name is: pdb.identity-domain.oraclecloud.internal where pdb is the name of the PDB and identity-domain is the name of the identity domain housing your Database as a Service subscription; for example: PDB1.usexample5822.oraclecloud.internal Accessing a Database as a Service Instance 5-7

76 Connecting Remotely to the Database by Using Oracle Net Services You can obtain the required information by viewing details as described in Viewing Detailed Information for a Database as a Service Instance. Creating an Oracle Net Connection When the Listener Port Is Unblocked To create an Oracle Net connection when the listener port is unblocked, you can use the easy connect method to specify a connect identifier with the following format: node-ip-address:1521/sid-or-service-name For example: :1521/ORCL or :1521/PDB1.usexample5822.oraclecloud.internal Creating an Oracle Net Connection When the Listener Port Is Blocked To create an Oracle Net connection when the listener port is blocked, you must create an SSH tunnel from your client (localhost) to port 1521 of the compute node hosting the Oracle Net Listener. For information about creating an SSH tunnel, see Creating an SSH Tunnel to a Compute Node Port. To create an Oracle Net connection that uses the SSH tunnel, you can use the easy connect method to specify a connect identifier with the following format: localhost:1521/sid-or-service-name For example: localhost:1521/orcl or localhost:1521/pdb1.usexample5822.oraclecloud.internal Note: Some database access products, such as Oracle SQL Developer or later, include functionality to connect to a database through an SSH tunnel. When using these products, you create the SSH tunnel to port 1521 within the product and do not need to follow the instructions in Creating an SSH Tunnel to a Compute Node Port. Creating an Oracle Net Connection to an Oracle RAC Database On an Oracle RAC database on a Database as a Service instance, the SCAN listeners on each compute node listen on port 1521, the standard Oracle Net Services port. By default, this port is disabled on the compute nodes. Therefore, you must first enable access to the port by following the instructions Enabling Access to a Compute Node Port. Then, on the client, specify a connect descriptor that references the SCAN listeners on both compute nodes; for example: alias-name = (DESCRIPTION = (ENABLE = BROKEN) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = node1-ip-address)(port = 1521)) 5-8 Using Oracle Database Cloud - Database as a Service

77 Accessing the Oracle GlassFish Server Administration Console (ADDRESS = (PROTOCOL = TCP)(HOST = node2-ip-address)(port = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = service-name) ) ) where: alias-name is the name you use to identify the alias. node1-ip-address and node2-ip-address are the public IP addresses of the two compute nodes for the service instance. service-name is the service name in the form: pdb.identity-domain.oraclecloud.internal For example: PDB1.usexample5822.oraclecloud.internal Accessing the Oracle GlassFish Server Administration Console Oracle Database Cloud - Database as a Service instances include Oracle GlassFish Server to host Oracle Application Express and the Oracle Cloud Database Monitor. The Oracle GlassFish Server Administration Console is available on port Note: This section does not apply to service instances that use Oracle Real Application Clusters. Such instances do not currently include Oracle GlassFish Server. How you access the administration console depends on whether port 4848 has been unblocked. When a Database as a Service instance is first created, port 4848 is blocked to ensure network security. For information about unblocking a port, see Enabling Access to a Compute Node Port. Accessing the Administration Console When Port 4848 Is Unblocked To access the administration console when port 4848 is unblocked: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. From the menu for the instance, select Open GlassFish Administration Console. The Administration Console login page is displayed. 3. Enter admin as the user name, enter the password specified when the service instance was created, and then click Login. This option is also available from the Instance Overview page. menu on the Oracle Database Cloud Service Accessing a Database as a Service Instance 5-9

78 Accessing the Oracle GlassFish Server Administration Console Accessing the Administration Console When Port 4848 Is Blocked To access the administration console when the port 4848 is blocked, you must create an SSH tunnel to port 4848 on the compute node hosting the administration console. For information about creating an SSH tunnel, see Creating an SSH Tunnel to a Compute Node Port. After creating an SSH tunnel to port 4848, you can access the administration console by directing your browser to the URL After the Administration Console login page is displayed, enter admin as the user name, enter the password specified when the service instance was created, and then click Login Using Oracle Database Cloud - Database as a Service

79 6 Backing Up and Restoring a Database as a Service Instance This section explains how to back up and restore an Oracle Database Cloud - Database as a Service instance. Note: This section does not apply to instances created at the Database Cloud Service - Virtual Image service level. Such instances do not include the cloud tooling described in this section. To back up and restore the Oracle Database in such instances, use the Oracle Database utilities and techniques described in Oracle Database 12c Backup and Recovery User's Guide or Oracle Database 11g Backup and Recovery User's Guide. To back up data in such instances to the Oracle Cloud, use Oracle Database Backup Service, as described in Using Oracle Database Backup Service. Topics About Backing Up a Database as a Service Instance Creating an On-Demand Backup of a Database as a Service Instance Deleting a Backup of a Database as a Service Instance Updating the Password for Backing Up to the Storage Cloud Customizing the Current Backup Configuration Changing the Backup Configuration to a Different Backup Destination Disabling and Re-enabling Scheduled Backups Restoring a Database as a Service Instance from a Backup Restoring from a Backup on Service Instances Hosting Single-Instance Databases Restoring from a Backup on Service Instances Hosting Oracle RAC Databases About Backing Up a Database as a Service Instance By backing up your Oracle Database Cloud - Database as a Service instances, you can protect these instances' software, configuration and database against loss if a failure occurs. By restoring an instance from a backup, you can restore the instance's software, configuration, and database to their state at the time of the backup. Database as a Service provides a backup feature that backs up: Backing Up and Restoring a Database as a Service Instance 6-1

80 About Backing Up a Database as a Service Instance The database Database configuration files Grid Infrastructure configuration files (on service instances hosting an Oracle RAC database) Important system and cloud tooling files To provide this backup feature, Database as a Service relies on system utilities and on Oracle Database Backup Cloud Service, which is installed on the service instance. Default Backup Configuration When you create a Database as a Service instance, you have to choose from the following backup configuration options: Both Cloud Storage and Local Storage. Backups are configured to be created automatically and stored both on local storage on the compute node associated with the service instance and on an Oracle Storage Cloud Service container. The container must have been created before creating the Database as a Service instance. Local Storage Only. Backups are configured to be created automatically and stored only on local storage on the compute node associated with the service instance. None. No backup configuration is created. The default backup configuration follows a set of Oracle best-practice guidelines: Full (level 0) backup of the database followed by rolling incremental (level 1) backups on a seven-day cycle Full backup of selected database configuration files Full backup of selected system files Automatic backups daily at 1:01 AM Retention period: Local Storage Only: 7 days Both Cloud Storage and Local Storage: 30 days, with the 7 most recent days' backups available on local storage Encryption: Cloud storage: All backups to cloud storage are encrypted. Local storage: Backups of Enterprise Edition databases to local storage are encrypted. Backups of Standard Edition databases to local storage are not encrypted. If the defaults do not suit your needs, you can customize the backup configuration for your service instance. For information, see Customizing the Current Backup Configuration. You can also change the entire backup configuration from the one used when your service instance was created. For information, see Changing the Backup Configuration to a Different Backup Destination. 6-2 Using Oracle Database Cloud - Database as a Service

81 Creating an On-Demand Backup of a Database as a Service Instance About Local Storage for Backups When a Database as a Service instance is created, Oracle Compute Cloud Service storage volumes are created on the compute node or nodes associated with the service instance, and resources are allocated to the service instance. The storage volume reserved for database backup is named fra. On service instances hosting Oracle RAC databases, this storage volume is shared by the compute nodes. You can see details about fra (as well as other storage volumes) in the Compute Cloud Service console. See Viewing a Storage Volume in Using Oracle Compute Cloud Service. The space allocated for the local storage used for backups on fra is 1.7 times the space allocated for data storage. For example, if you chose 100 GB for Usable Database Storage when creating the service instance, 170 GB are allocated for backups. Note: If you examine an instance configured for 10 GB data storage, you may see a slightly different size reported, for example 11 GB reserved for data storage and 18 GB reserved for backup. The size increase is due to space reserved for system operations. Creating an On-Demand Backup of a Database as a Service Instance How you create an on-demand backup on a Oracle Database Cloud - Database as a Service instance depends on the type of database running on the service instance. Topics Creating an On-Demand Backup on Service Instances Hosting Single-Instance Databases Creating an On-Demand Backup on Service Instances Hosting Oracle RAC Databases Creating an On-Demand Backup on Service Instances Hosting Single-Instance Databases Use the bkup_api utility to create an on-demand backup. If automatic backup of the service is enabled, you must disable it first, as described below. To create an on-demand backup: 1. Connect to the compute node as the opc user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. You can choose to have the backup follow the current retention policy, or you can choose to create a long-term backup that persists until you delete it: To create a backup that follows the current retention policy, enter the following bkup_api command: Backing Up and Restoring a Database as a Service Instance 6-3

82 Deleting a Backup of a Database as a Service Instance # /var/opt/oracle/bkup_api/bkup_api bkup_start To create a long-term backup, enter the following bkup_api command: # /var/opt/oracle/bkup_api/bkup_api bkup_start --keep 4. Exit the root-user command shell: # exit $ By default, the backup is given a timestamp-based tag. To specify a custom backup tag, add the --tag option to the bkup_api command; for example, to create a longterm backup with the tag "monthly", enter the following command: # /var/opt/oracle/bkup_api/bkup_api bkup_start --keep --tag=monthly After you enter a bkup_api bkup_start command, the bkup_api utility starts the backup process, which runs in the background. To check the progress of the backup process, enter the following bkup_api command: # /var/opt/oracle/bkup_api/bkup_api bkup_status Creating an On-Demand Backup on Service Instances Hosting Oracle RAC Databases Use the raccli utility to create an on-demand backup. To create an on-demand backup: 1. Connect to the compute node as the opc user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Enter the raccli create backup subcommand: $ raccli create backup $ By default, the backup is given a timestamp-based tag. To specify a custom backup tag, add the -tag option to the raccli command; for example, to create a long-term backup with the tag "monthly", enter the following command: $ raccli create backup -tag monthly After you enter a raccli create backup command, the raccli utility starts the backup process, which runs in the background. To check the progress of the backup process, enter the following raccli command: $ raccli describe job Deleting a Backup of a Database as a Service Instance Note: Currently, deleting a backup is not supported for Database as a Service instances that use Oracle Real Application Clusters (RAC). To delete a backup of an Oracle Database Cloud - Database as a Service instance, you use the bkup_api utility. 6-4 Using Oracle Database Cloud - Database as a Service

83 Updating the Password for Backing Up to the Storage Cloud 1. Connect to the compute node as the opc user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. List the available backups: # /var/opt/oracle/bkup_api/bkup_api recover_list A list of available backups is displayed. 4. Delete the backup you want: # /var/opt/oracle/bkup_api/bkup_api bkup_delete --bkup=backup-tag where backup-tag is the tag of the backup you want to delete. 5. Exit the root-user command shell: # exit $ Updating the Password for Backing Up to the Storage Cloud Whenever the password is changed for an Oracle Cloud user whose credentials are used for backing up to an Oracle Storage Cloud container, you need to update the user s password in the Oracle Wallet file stored on affected service instances. Because Oracle Cloud requires users to change their passwords on a regular basis, you need to perform this task regularly. How you update the password on an Oracle Database Cloud - Database as a Service instance depends on the type of database running on the service instance. Topics Updating the Password on Service Instances Hosting Single-Instance Databases Updating the Password on Service Instances Hosting Oracle RAC Databases Updating the Password on Service Instances Hosting Single-Instance Databases You use the bkup_api utility to update the Oracle Wallet file containing the backup user s password: 1. Connect to the compute node as the opc user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. Update the password: Backing Up and Restoring a Database as a Service Instance 6-5

84 Customizing the Current Backup Configuration # /var/opt/oracle/bkup_api/bkup_api update_wallet --password=new-password where new-password is the user's new password. If the update succeeds, output from the command indicates that the wallet was successfully created and the credentials are valid. If you could not authenticate, you entered the wrong password and need to try again with the correct credentials. If you get a message stating that there is no such option as --password, the bkup_api utility is out of date. Update it by following the instructions in Updating the Cloud Tooling on a Database as a Service Instance, and then try the bkup_api command again. 4. Exit the root-user command shell: # exit $ Updating the Password on Service Instances Hosting Oracle RAC Databases You use the raccli utility to update the Oracle Wallet file containing the backup user s password: 1. Connect to the compute node as the opc user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Update the password: $ raccli update backupconfig -params '{"cloudstoragepwd" : new-password}' where new-password is the user's new password. If the update succeeds, output from the command indicates that the wallet was successfully created and the credentials are valid. If you could not authenticate, you entered the wrong password and need to try again with the correct credentials. Customizing the Current Backup Configuration How you customize the current backup configuration on an Oracle Database Cloud - Database as a Service instance depends on the type of database running on the service instance. Topics Customizing the Current Backup Configuration on Service Instances Hosting Single-Instance Databases Customizing the Current Backup Configuration on Service Instances Hosting Oracle RAC Databases 6-6 Using Oracle Database Cloud - Database as a Service

85 Customizing the Current Backup Configuration Customizing the Current Backup Configuration on Service Instances Hosting Single- Instance Databases You can customize many of the characteristics of a service instance s current backup configuration. Topics Customizing How the Database Is Backed Up Customizing Which System Files Are Backed Up Customizing Which Database Configuration Files Are Backed Up Customizing the Retention Period for Backups Customizing the Cycle Period for Backups Customizing the Frequency of Automatic Backups Customizing How the Database Is Backed Up To change how the Oracle database is backed up, you use the RMAN utility. For information about using RMAN, see Oracle Database 12c Backup and Recovery User's Guide or Oracle Database 11g Backup and Recovery User's Guide. Caution: Do not use the RMAN utility to change the retention period. To view the current RMAN configuration, use the RMAN command SHOW ALL: 1. Connect as the oracle user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start an RMAN session: $ rman target=/... RMAN> 3. Enter the SHOW ALL command: RMAN> show all;... A listing of your configuration is displayed. 4. Use RMAN commands to make any changes to your configuration. 5. Exit the RMAN session: RMAN> exit; $ Backing Up and Restoring a Database as a Service Instance 6-7

86 Customizing the Current Backup Configuration Customizing Which System Files Are Backed Up To change which system files and directories are backed up: 1. Connect as the oracle user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Edit the contents of the /home/oracle/bkup/oscfg.spec file. The backup feature provided by Oracle Database Cloud - Database as a Service backs up the files and folders listed in this specification file. An example of an oscfg.spec file with a default configuration is as follows: ## OS Configuration Files # # Doc Spec oscfg.spec # # Directories /etc/rc.d /home/oracle/bkup # # Single files /home/oracle/.bashrc /etc/crontab /etc/sysctl.conf /etc/passwd /etc/group /etc/orainst.loc /etc/oratab /etc/fstab Customizing Which Database Configuration Files Are Backed Up To change which database configuration files are backed up: 1. Connect as the oracle user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Edit the contents of the /home/oracle/bkup/dbcfg.spec file: The backup feature provided by Oracle Database Cloud - Database as a Service backs up the files and folders listed in this specification file. An example of a dbcfg.spec file with a default configuration is as follows: ### Oracle_Home configuration files. # # Doc Spec dbcfg.spec # DB id dbid # # Directories /u01/app/oracle/product/12.1.0/dbhome_1/admin/orcl/xdb_wallet /u01/app/oracle/admin/orcl/xdb_wallet /u01/app/oracle/admin/orcl/opc_wallet # Note: tde_wallet must be backed up in a different location than DATA bkup. 6-8 Using Oracle Database Cloud - Database as a Service

87 Customizing the Current Backup Configuration /u01/app/oracle/admin/orcl/tde_wallet /u01/app/oracle/admin/orcl/cat_wallet #/u01/app/oracle/product/12.1.0/dbhome_1/dbs #/u01/app/oracle/product/12.1.0/dbhome_1/network/admin #/u01/app/orainventory # # Single files /u01/app/oracle/product/12.1.0/dbhome_1/dbs/opcorcl.ora /u01/app/oracle/product/12.1.0/dbhome_1/dbs/orapworcl /u01/app/oracle/product/12.1.0/dbhome_1/network/admin/listener.ora /u01/app/oracle/product/12.1.0/dbhome_1/network/admin/sqlnet.ora /u01/app/oracle/product/12.1.0/dbhome_1/network/admin/tnsnames.ora /u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/env_rdbms.mk /u01/app/oracle/product/12.1.0/dbhome_1/rdbms/lib/ins_rdbms.mk Customizing the Retention Period for Backups To change the retention period for backups, use the bkup_api utility: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. Enter this bkup_api command. # /var/opt/oracle/bkup_api/bkup_api bkup_chgcfg --retention_days=days where days is the number of days for which you want to retain backups. 4. Exit the root-user command shell: # exit $ Customizing the Cycle Period for Backups To change the cycle period for backups, use the bkup_api utility: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. Enter this bkup_api command. # /var/opt/oracle/bkup_api/bkup_api bkup_chgcfg --bkup_cycle=days where days is the number of days you want for the cycle period. 4. Exit the root-user command shell: Backing Up and Restoring a Database as a Service Instance 6-9

88 Customizing the Current Backup Configuration # exit $ Customizing the Frequency of Automatic Backups The backup feature provided by Oracle Database Cloud - Database as a Service uses the Linux cron job scheduler to perform automatic backups. If automatic backups are enabled, the following job entry is defined: * * * root /var/opt/oracle/bkup_api/bkup_api bkup_start This entry causes the bkup_api script to be run daily at 1:01 AM by the root user. The bkup_api script sends log messages to the file /home/oracle/bkup/log/ obkup.log. To change this frequency, or to add the entry if automatic backups were not enabled when the service instance was created, use the crontab -e command. You must be logged in as the root user to use this command. Customizing the Current Backup Configuration on Service Instances Hosting Oracle RAC Databases You can customize many of the characteristics of a service instance s current backup configuration. Topics Customizing How the Database Is Backed Up Customizing Which System Files Are Backed Up Customizing Which Database Configuration Files Are Backed Up Customizing Which Grid Infrastructure Configuration Files Are Backed Up Customizing the Recovery Window for Backups to Local Storage Customizing the Recovery Window for Backups to Cloud Storage Customizing the Time of Automatic Daily Backups Customizing How the Database Is Backed Up To change how the Oracle database is backed up, you use the RMAN utility. For information about using RMAN, see Oracle Database 12c Backup and Recovery User's Guide or Oracle Database 11g Backup and Recovery User's Guide. Caution: Do not use the RMAN utility to change the retention period. To view the current RMAN configuration, use the RMAN command SHOW ALL: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH) Using Oracle Database Cloud - Database as a Service

89 Customizing the Current Backup Configuration 2. Change to the oracle user: $ sudo -s # su - oracle 3. Start an RMAN session: $ rman target=/... RMAN> 4. Enter the SHOW ALL command: RMAN> show all;... A listing of your configuration is displayed. 5. Use RMAN commands to make any changes to your configuration. 6. Exit the RMAN session: RMAN> exit; $ Customizing Which System Files Are Backed Up To change which system files and directories are backed up: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Edit the contents of the /opt/oracle/dcs/rdbaas/config/oscfg.spec file. The backup feature provided by Oracle Database Cloud - Database as a Service backs up the files and folders listed in this specification file. Customizing Which Database Configuration Files Are Backed Up To change which database configuration files are backed up: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Edit the contents of the /opt/oracle/dcs/rdbaas/config/dbcfg.spec file. The backup feature provided by Oracle Database Cloud - Database as a Service backs up the files and folders listed in this specification file. Customizing Which Grid Infrastructure Configuration Files Are Backed Up To change which grid infrastructure configuration files are backed up: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Edit the contents of the /opt/oracle/dcs/rdbaas/config/gicfg.spec file. Backing Up and Restoring a Database as a Service Instance 6-11

90 Changing the Backup Configuration to a Different Backup Destination The backup feature provided by Oracle Database Cloud - Database as a Service backs up the files and folders listed in this specification file. Customizing the Recovery Window for Backups to Local Storage To change the recovery window for backups to local storage: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Enter this raccli command: $ raccli update backupconfig -params '{"diskrecoverywindow" : days}' where days is the number of days for which you want to retain backups. Customizing the Recovery Window for Backups to Cloud Storage To change the recovery window for backups to the Oracle Storage Cloud container: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Enter this raccli command: $ raccli update backupconfig -params '{"ossrecoverywindow" : days}' where days is the number of days for which you want to retain backups. Customizing the Time of Automatic Daily Backups To change the time of day when daily automatic backups are performed: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Enter this raccli command: $ raccli update backupconfig -params '{"crondate" : "time"}' where time is the time (using 24-hour, HH:MM format) when daily backups are to occur. For example, "02:45" is 2:45 AM, and "14:45" is 2:45 PM. Changing the Backup Configuration to a Different Backup Destination You can change the backup destination option of your Oracle Database Cloud - Database as a Service instance after creating it. When a service instance is created, it is configured with one of the following backup destination options: Both Cloud Storage and Local Storage Local Storage Only None 6-12 Using Oracle Database Cloud - Database as a Service

91 Changing the Backup Configuration to a Different Backup Destination The instructions in this topic describe how to switch from one of these options to another in an existing Database as a Service instance. For background information on the options, see About Backing Up a Database as a Service Instance. Prerequisites If you are switching from the backup option None to one of the other options, you must increase the size of the local storage used for backups. Use the Extend Backup Storage Volume option of the Oracle Database Cloud Service console s scaling feature to add storage such that the backup storage is 1.7 times the size of your database storage. For instructions, see Scaling a Database as a Service Instance. Note: Older service instances do not support the Extend Backup Storage Volume option, and an error is displayed when you try to use it. In this case, you must manually add backup storage. For instructions, see Increasing Local Storage for Backups on Older Service Instances. Use the scaling feature of the Oracle Database Cloud Service console to add a storage volume of the appropriate size to the service instance. If you are switching to the backup option Both Cloud Storage and Local Storage, you must have an Oracle Storage Cloud Service container in your account that is reserved for backups. If you don t have one, you must create one. See Creating Containers in Using Oracle Storage Cloud Service, or see the tutorial Oracle Storage Cloud Service: Creating Containers Using the REST API. How you change the backup configuration to a different backup destination on a Database as a Service instance depends on the type of database running on the service instance. Topics Changing the Backup Configuration on Service Instances Hosting Single-Instance Databases Changing the Backup Configuration on Service Instances Hosting Oracle RAC Databases Changing the Backup Configuration on Service Instances Hosting Single-Instance Databases You can change the backup destination option of your Oracle Database Cloud - Database as a Service instance after creating it. Before changing the backup configuration, make sure you have performed applicable Prerequisites. 1. Connect as the oracle user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start an RMAN session: Backing Up and Restoring a Database as a Service Instance 6-13

92 Changing the Backup Configuration to a Different Backup Destination $ rman target=/... RMAN> 3. Delete any existing backups. RMAN> delete backup; All backups for this database recorded in the RMAN repository are deleted. (This process may take several minutes.) 4. Exit the RMAN session and log out: RMAN> exit;... $ exit 5. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 6. Start a root-user command shell: $ sudo -s # 7. If you are switching to a backup configuration for both Cloud storage and local storage, and this is the first time you have done so, you must configure Transparent Data Encryption (TDE). Run the following command: /var/opt/oracle/dbaascli/dbaascli tde config --ks_login auto TDE provides encryption of database files at the file level. For information about TDE, including auto login, see Oracle 12c Database Advanced Security Guide or Oracle 11g Database Advanced Security Administrator's Guide. 8. Change to the location for the backup configuration file: # cd /var/opt/oracle/ocde/assistants/bkup/ 9. If a bkup.cfg file already exists and contains configuration details, you may want to copy with to a new name, in case you want to recover that configuration later, for example: $ ls bkup*.cfg bkup.cfg $ mv bkup.cfg bkup_bak.cfg $ ls bkup*.cfg bkup_bak.cfg 10. Open bkup.cfg in an editor, for example: # vim bkup.cfg 11. Enter configuration information for the backup destination you want to use: For local storage only, enter: # The bkup.cfg file will hold all the config info for BKUP bkup_disk=yes 6-14 Using Oracle Database Cloud - Database as a Service

93 Changing the Backup Configuration to a Different Backup Destination bkup_disk_recovery_window=days bkup_oss=no For both Cloud storage and local storage, enter: # The bkup.cfg file will hold all the config info for BKUP bkup_disk=yes bkup_disk_recovery_window=days bkup_oss=yes bkup_oss_url=oss_url bkup_oss_user=username bkup_oss_passwd=password bkup_oss_recovery_window=days where days (for bkup_disk_recovery_window) is the number of days for which backups and archived redo logs of the local storage are maintained. The interval always ends with the current time and extends back in time for the number of days specified for the window. oss_url is the REST endpoint of the storage container. username is the username for your account. password is the password for your account. days (for bkup_oss_recovery_window) is the number of days for which backups and archived redo logs of the cloud storage are maintained. The interval always ends with the current time and extends back in time for the number of days specified for the window 12. Prepare bkup.cfg to be used as follows. # chown root bkup.cfg # chmod 0600 bkup.cfg 13. Execute the backup assistant with the bkup.cfg file: # sudo./bkup -cfg bkup.cfg Changing the Backup Configuration on Service Instances Hosting Oracle RAC Databases You can change the backup destination option of your Oracle Database Cloud - Database as a Service instance after creating it. Before changing the backup configuration, make sure you have performed applicable Prerequisites. 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Use the raccli update backupconfig command to update the configuration. To change the backup destination to local storage only, enter the following command: Backing Up and Restoring a Database as a Service Instance 6-15

94 Changing the Backup Configuration to a Different Backup Destination $ raccli update backupconfig -params '{"diskenabled" : true, "ossenabled" : false}' To change the backup destination to both cloud storage and local storage, enter the following command. Line breaks have been added for clarity; you must enter the command on a single line. $ raccli update backupconfig -params '{"diskenabled" : true, "ossenabled" : true, "cloudstorageservicename" : "servicename", "cloudstorageidentitydomain" : "identity-domain", "cloudstorageuser" : "username", "StoragePwd" : "password", "cloudstoragehost" : "service-url", "cloudstorecontainer" : "container-name"}' where: servicename is the root name of the Oracle Storage Cloud service. identity-domain is the identity domain of the Oracle Storage Cloud service. username is the user name of an Oracle Cloud user who has read/write access to the container. password is the password of the user specified in cloudstorageuser. service-url is the service URL of the Oracle Storage Cloud service. container-name is the name of the Oracle Storage Cloud container. Increasing Local Storage for Backups on Older Service Instances Older Oracle Database Cloud - Database as a Service instances do not support the Extend Backup Storage Volume feature, so you must manually add backup storage. To create a larger storage volume and use it for backups: 1. Create a storage volume for backups. Its size should be 1.7 times the space allocated for data storage. Use the Create New Storage Volume option of the Oracle Database Cloud Serviceconsole s scaling feature to add a storage volume of the appropriate size to the service instance. For instructions, see Scaling a Database as a Service Instance. 2. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 3. Confirm the addition of the storage volume by listing the devices: $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT xvdb 202: G 0 disk xvdb1 202: M 0 part /boot xvdb2 202: G 0 part / xvdb3 202:19 0 4G 0 part [SWAP] xvdc 202: G 0 disk xvdc1 202: G 0 part /u04 xvdd 202:48 0 7G 0 disk xvdd1 202:49 0 7G 0 part /u03 xvde 202: G 0 disk xvde1 202: G 0 part /u01 xvdf 202: G 0 disk 6-16 Using Oracle Database Cloud - Database as a Service

95 Changing the Backup Configuration to a Different Backup Destination xvdf1 202: G 0 part /u02 xvdg 202: G 0 disk xvdg1 202: G 0 part /u05 4. Change from the opc user to the oracle user: $ sudo su - oracle 5. As the oracle user, use RMAN to shut down the database instance: $ rman target=/... RMAN> shutdown immediate; using target database control file instead of recovery catalog database closed database dismounted Oracle instance shut down Quit RMAN and exit the oracle user session: RMAN> quit; Recovery Manager complete. $ exit 6. As the root user, copy the content from /u03 (which you have been using for backup storage) to /u05: # cp -R /u03/* /u05/ 7. Unmount the /u05 and /u03 mount points: # umount /u05/ # umount /u03/ Note: The Linux unmount command is umount (with no n). 8. Mount the partition of new storage volume you just created to /u03, which Oracle Database Cloud - Database as a Service uses for backups. For example: # mount /dev/xvdg1 /u03 9. Look at the results: # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT xvdb 202: G 0 disk xvdb1 202: M 0 part /boot xvdb2 202: G 0 part / xvdb3 202:19 0 4G 0 part [SWAP] xvdc 202: G 0 disk xvdc1 202: G 0 part /u04 xvdd 202:48 0 7G 0 disk xvdd1 202:49 0 7G 0 part xvde 202: G 0 disk xvde1 202: G 0 part /u01 xvdf 202: G 0 disk xvdf1 202: G 0 part /u02 xvdg 202: G 0 disk xvdg1 202: G 0 part /u03 Backing Up and Restoring a Database as a Service Instance 6-17

96 Changing the Backup Configuration to a Different Backup Destination The old 7 GB partition xvdd1, which was previously mounted to /u03, is no longer mounted at all. The new 17 GB partition xvdg1 is now mounted to /u03 and will therefore be used for backups. Note that the space used for xvdd1 is now no longer available for any use. 10. Set the ownership and permissions of the mount-point directory /u03. For example: # chown -R oracle:oinstall /u03 # chmod 755 /u As the oracle user, start SQL*Plus, connect to the database as SYSDBA, and start it. For example: $ sqlplus /nolog SQL*Plus: Release Production on Sat Feb 21 13:19: Copyright (c) 1982, 2014, Oracle. All rights reserved. SQL> connect sys/password as sysdba Connected to an idle instance. SQL> startup ORACLE instance started. Total System Global Area bytes Fixed Size bytes Variable Size bytes Database Buffers bytes Redo Buffers bytes Database mounted. Database opened. 12. If you want to see the current setting for the limit on the total space to be used by target database recovery files, show the values of the parameter DB_RECOVERY_FILE_DEST, for example: SQL> show parameter db_recovery_file_dest NAME TYPE VALUE db_recovery_file_dest string /u03/app/oracle/fast_recovery_ area db_recovery_file_dest_size big integer 7G 13. Increase the parameter DB_RECOVERY_FILE_DEST_SIZE to use the new extra space in /u03, for example: SQL> alter system set db_recovery_file_dest_size=17g; System altered. 14. Show the new value: SQL> show parameter db_recovery_file_dest; NAME TYPE VALUE db_recovery_file_dest string /u03/app/oracle/fast_recovery_ area db_recovery_file_dest_size big integer 17G 15. Quit SQL*Plus and log out: 6-18 Using Oracle Database Cloud - Database as a Service

97 Disabling and Re-enabling Scheduled Backups SQL> quit; Disconnected from Oracle Database 12c Enterprise Edition Release bit Production $ exit Disabling and Re-enabling Scheduled Backups If some activity you want to perform requires you to temporarily disable regularly scheduled backups, you can do so by removing the scheduling information from the crontab file. Note: Currently, disabling and re-enabling scheduled backups is not supported for Database as a Service instances that use Oracle Real Application Clusters (RAC). Disabling Scheduled Backups To disable scheduled backups: 1. Connect to the compute node as the opc user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. Make a copy of the crontab file to preserve the configuration, for example: # cp /etc/crontab /etc/crontab.bak 4. Use the crontab -e command to remove this line from the original crontab file: * * * root /var/opt/oracle/bkup_api/bkup_api bkup_start Note: You cannot comment out the line, you must delete it. 5. Save the file and exit from the editor. 6. Exit the root-user command shell: # exit $ Re-Enabling Scheduled Backups To re-enable scheduled backups: 1. Connect to the compute node as the opc user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: Backing Up and Restoring a Database as a Service Instance 6-19

98 Restoring a Database as a Service Instance from a Backup $ sudo -s # 3. Copy the crontab.bak file you created when disabling scheduled backups to its original name, crontab: # cp /etc/crontab.bak /etc/crontab 4. Exit the root-user command shell: # exit $ Restoring a Database as a Service Instance from a Backup How you restore from a backup and perform recovery on an Oracle Database Cloud - Database as a Service instance depends on the type of database running on the service instance. Topics Restoring from a Backup on Service Instances Hosting Single-Instance Databases Restoring from a Backup on Service Instances Hosting Oracle RAC Databases Restoring from a Backup on Service Instances Hosting Single-Instance Databases To restore from a backup and perform recovery on an Oracle Database Cloud - Database as a Service instance hosting a single-instance database, you use the orec subcommand of the dbaascli utility, which is available on the service instance s compute node. Note: The orec subcommand must be run with root access. Therefore, you need to connect to the compute node as the opc user to perform recovery operations. The full syntax for the orec subcommand is as follows. Line breaks have been added for clarity, but are not used when entering a command: dbaascli orec --args { -duplicate [-dbrole db_role] -help -keep { -list -tag backup_tag } -latest [ -cfgfiles -data ] -list -pitr backup_tag [ -cfgfiles -data ] -scn SCN_number -timestamp="date_and_time" } 6-20 Using Oracle Database Cloud - Database as a Service

99 Restoring from a Backup on Service Instances Hosting Single-Instance Databases Note: You can also run orec subcommands from within the dbaascli utility; for example: # dbaascli... DBAAS> orec --args -list... DBAAS> quit # The following table describes options for the orec subcommand. Option -help -keep -list -keep -tag backup_tag -latest -latest - cfgfiles -latest -data -list -pitr backup_tag -pitr backup_tag -cfgfiles -pitr backup_tag -data -scn SCN_number - timestamp="date_ and_time" Description Displays the orec command syntax. Lists long-term backups available. Restores the long-term backup specified by backup_tag. Restores the latest backup. Restores the configuration files from the latest backup, but not the data. Restores the data from the latest backup, but not the configuration files. Lists available backups. Restores the specific backup identified by backup_tag. Restores the configuration files from the specific backup identified by backup_tag, but not the data. Restores the data from the specific backup identified by backup_tag, but not the configuration files. Restores the specific backup identified by the system change number, SCN number. Restores the specific backup identified by the given date and time in the format DD-MON-YYYY hh24:mi:ss. For general information about restoring Oracle Databases from backup, see the Oracle Database Backup and Recovery User's Guide. Topics Restoring from the Most Recent Backup Restoring from a Specific Backup Backing Up and Restoring a Database as a Service Instance 6-21

100 Restoring from a Backup on Service Instances Hosting Single-Instance Databases Restoring from a Specific Long-Term Backup Restoring an Instance Using the mrec Utility Restoring from the Most Recent Backup To restore the most recent backup on a service instance hosting a single-instance database: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. Restore the most recent backup using the orec subcommand of the dbaascli utility: # dbaascli orec --args -latest The restore process performs these steps: Shuts down the database Extracts and restores configuration files Prepares for recovery Performs the recovery Restarts the database instance after recovery 4. Exit the root-user command shell: # exit $ Restoring from a Specific Backup To restore a specific backup on a service instance hosting a single-instance database: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. List the available backups using the orec subcommand of the dbaascli utility. # dbaascli orec --args -list A list of available backups displays; for example: 6-22 Using Oracle Database Cloud - Database as a Service

101 Restoring from a Backup on Service Instances Hosting Single-Instance Databases Backup Tag Completion Tag Config File Location TAG T /26/ :16:45 TAG T /26/ :51:18.../ORCL/oscfgfiles/2014_06_26/ oscfgfiles_ _1951.tar.gz.../orcl/ohcfgfiles/2014_06_26/ ohcfgfiles_ _1951.tar.gz Config files relative path to: /u03/app/oracle/fast_recovery_area 4. Restore the specific backup you want using the orec subcommand: # dbaascli orec --args -pitr backup-tag where backup-tag is the tag of the backup you want to restore. The restore process performs these steps: Shuts down the database Extracts and restores configuration files Prepares for recovery Performs the recovery Restarts the database instance after recovery 5. Exit the root-user command shell: # exit $ Restoring from a Specific Long-Term Backup To restore from a specific long-term backup on a service instance hosting a singleinstance database: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. List the available long-term backups using the orec subcommand of the dbaascli utility. # dbaascli orec --args -keep -list A list of available long-term backups displays; for example: TAG T TAG T TAG T Restore the specific long-term backup you want using the orec subcommand. Backing Up and Restoring a Database as a Service Instance 6-23

102 Restoring from a Backup on Service Instances Hosting Single-Instance Databases # dbaascli orec --args -keep -tag backup-tag where backup-tag is the tag of the long-term backup you want to restore. The restore process performs these steps: Shuts down the database Prepares for recovery Performs the recovery Restarts the database instance after recovery 5. Exit the root-user command shell: # exit $ Restoring an Instance Using the mrec Utility For an Oracle Database Cloud - Database as a Service instance hosting a singleinstance database, you can use the Media Recovery (mrec) utility to restore the service instance if cannot be restored using the orec command or RMAN. This situation could occur if you've deleted critical configuration files or data files (such as the database redo log files, for example), or if something else has happened that caused the instance to be lost. The mrec utility restores the instance to the point of the last backup. This is equivalent to restoring the database and configuration from a tape device external to the instance. The mrec utility should be considered a last resource and used only when an instance cannot be restored in any other way. Before You Begin To restore an instance using the mrec utility, the following conditions must be met: The instance that you want to restore (referred to as the original instance) must have been created using the Oracle Database Cloud Service service level, not the Oracle Database Cloud Service - Virtual Image service level. A backup of the original instance, including configuration files, must exist in cloud storage. The instance will be restored up to the latest backup available in cloud storage (data files and configuration files). If such a backup doesn t exist, you can't use mrec to restore the instance. You must also know the following: The settings used to create the original instance. The credentials and URL of the Oracle Storage Cloud Service instance to which the original instance is backed up. The database system identifier (SID) associated with the original instance. Procedure To restore an instance using mrec: 6-24 Using Oracle Database Cloud - Database as a Service

103 Restoring from a Backup on Service Instances Hosting Single-Instance Databases 1. Use the Create Database Cloud Service Instance wizard to create a new instance. See Creating a Database as a Service Instance. The backup of the original instance will be restored to this new instance. Make sure you specify the following: The Oracle Database Cloud Service service level. The same Oracle Database version and software edition as the original instance. On the Service Details page, the same settings as the original instance. At a minimum, the compute shape, storage capacity, and backup and recovery configuration settings must be identical to those of the original instance. If the compute node associated with the original instance still exists, a different instance name can be used. 2. Connect as the opc user to the compute node associated with the newly created service instance. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 3. Start a root-user command shell: $ sudo -s # 4. Prepare the new compute node so mrec can be used (the compute node must have minimal configuration): a. Run the deinstall script to remove everything in the attached storage volumes: # /home/oracle/deinstall.pl b. Run the ocde script to execute the prep or sda assistant and configure the compute node with the requirements for mrec: # /var/opt/oracle/ocde/ocde -alist='prep sda' This configuration will take some time. When it's done, the compute node is ready for mrec. 5. Create a new oss.cfg configuration file with the exact same parameters and values as those in the oss.cfg file of the original instance: a. Connect to the original instance as opc user and start a root-user command shell. b. Locate the oss.cfg file and view its contents. For example: # cd /home/oracle/bkup # cat oss.cfg Copy the parameters in the file. The same parameters and values must be used in the oss.cfg file for the new instance. If you can t access the oss.cfg file for the original instance, these are the parameters you ll need to specify: oss_tid=storage-service-identity-domain oss_sname=storage-service-name Backing Up and Restoring a Database as a Service Instance 6-25

104 Restoring from a Backup on Service Instances Hosting Oracle RAC Databases oss_user=storage-service-admin-user-name oss_passwd=storage-service-admin-user-password oss_url=storage-service-container-url oss_auth_url=storage-service-authentication-url For example: oss_tid=usoracle04791 oss_sname=dbaasoss oss_user=admin-user-name oss_passwd=admin-user-password oss_url=" mycontainer" oss_auth_url=" c. Switch back to your connection to the new instance. d. Create an oss.cfg file that contains the parameters used in the oss.cfg file of the original instance: # cd /var/opt/oracle/mrec # vim oss.cfg e. Change ownership of the new oss.cfg file from the root user to the oracle user. Also change permissions: # chown oracle:oinstall oss.cfg # chmod 0600 oss.cfg 6. While still in the root-user command shell connection to the new instance, run the mrec utility: # cd /var/opt/oracle/mrec #./mrec -oss_cfgfile./oss.cfg -old_hostname hostname-of-node-to-restore -sid SID-of-instance-to-restore where: hostname-of-node-to-restore is the simple name of the compute node to restore (doesn't need to be fully qualified). For example, prod01. SID-of-instance-to-restore is the database system identifier (SID) of the database instance to restore. For example, orcl. The mrec utility pulls files over from the original instance, installs the module used for cloud backups, and attempts recovery. Information about progress and status is displayed in the terminal window as the utility runs. If recovery is successful, you ll see a message indicating that the instance has been recovered and is in an open state. The amount of time this takes depends on the size of the instance that you re recovering. Restoring from a Backup on Service Instances Hosting Oracle RAC Databases To restore from a backup and perform recovery on an Oracle Database Cloud - Database as a Service instance hosting an Oracle Real Application Clusters (RAC) database, you use the raccli create recovery command, which is available on the compute nodes associated with the service instance Using Oracle Database Cloud - Database as a Service

105 Restoring from a Backup on Service Instances Hosting Oracle RAC Databases Topics Restoring from the Most Recent Backup Restoring to a Specific Point in Time Restoring from the Most Recent Backup To restore from the most recent backup and perform complete recovery on a service instance hosting an Oracle Real Application Clusters (RAC) database: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Restore the most recent backup and perform complete recovery using the create recovery subcommand of the raccli utility: $ raccli create recovery -latest The restore and recover process performs these steps: Shuts down the database Extracts and restores configuration files Prepares for recovery Performs the recovery Restarts the database instance after recovery Restoring to a Specific Point in Time To restore from a backup and perform recovery to a specific point in time on a service instance hosting an Oracle Real Application Clusters (RAC) database: 1. Connect as the opc user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Perform recovery to a specific point in time using the create recovery subcommand of the raccli utility: $ raccli create recovery -pitr -scn SCN or $ raccli create recovery -pitr -timestamp time where SCN is the system change number (SCN) for the end point of the recovery and time is time (in the format MM/DD/YYYY HH24:MI:SS) for the end point of the recovery. The restore and recover process performs these steps: Shuts down the database Backing Up and Restoring a Database as a Service Instance 6-27

106 Restoring from a Backup on Service Instances Hosting Oracle RAC Databases Extracts and restores configuration files Prepares for recovery Performs the recovery Restarts the database instance after recovery 6-28 Using Oracle Database Cloud - Database as a Service

107 7 Patching Database as a Service This section explains how to apply a patch to Oracle Database Cloud - Database as a Service, and roll back the patch as necessary. Note: This section does not apply to instances created at the Database Cloud Service - Virtual Image service level. Such instances do not include the cloud tooling described in this section. Patching is not supported by Oracle at the Database Cloud Service - Virtual Image service level. Topics Checking Prerequisites Before Applying a Patch Applying a Patch Rolling Back a Patch or Failed Patch Applying a Patch to a Test Instance The dbpatchm Subcommand The dbpatchm.cfg Configuration File For general information about patching Oracle Database, see Patch Set Updates and Requirements for Upgrading Oracle Database in the Oracle Database 12c Upgrade Guide or the Oracle Database 11g Upgrade Guide. Checking Prerequisites Before Applying a Patch Before you apply a patch, you can check its prerequisites to make sure that it can be successfully applied. Note: Currently, checking patch prerequisites is not supported for Database as a Service instances that use Oracle Real Application Clusters (RAC). The prerequisites-checking operation: Confirms that the patch is available for download. Verifies that there is enough space in the /u01 directory to apply the patch. Patching Database as a Service 7-1

108 Checking Prerequisites Before Applying a Patch Compares the patch s prerequisites to the service instance by running opatch prereq commands. You can perform the prerequisites-checking operation using either the Oracle Database Cloud Service Console or the dbpatchm subcommand. For detailed instructions, see: Checking Prerequisites by Using the Oracle Database Cloud Service Console Checking Prerequisites by Using the dbpatchm Subcommand Checking Prerequisites by Using the Oracle Database Cloud Service Console You can use the Oracle Database Cloud Service Instance Administration page to check the prerequisites of a patch before you apply it to an Oracle Database Cloud - Database as a Service instance. Note: Currently, checking patch prerequisites by using the Oracle Database Cloud Service console is not supported for Database as a Service instances that use Oracle Real Application Clusters (RAC). To check the prerequisites of a patch by using the Oracle Database Cloud Service Console: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. Click the service instance to which you want to apply a patch. The Oracle Database Cloud Service Instance Overview page is displayed. 3. Click the Administration tile. The Oracle Database Cloud Service Instance Administration page is displayed. A list of patches you can apply appears in the Available Patches section. 4. In the entry for the patch whose prerequisites you want to check, click the menu and then select Precheck. If you have previously checked prerequisites on the selected patch, the Patch Precheck Service window displays, showing the results of the previous check and asking you to confirm another precheck. In this case, click Precheck to continue. The Instance Administration page redisplays, showing a status message that your request has been submitted. 5. Refresh the Instance Administration page occasionally to update the status message. Note that the checking operation can take several minutes to complete. When the checking operation completes, the status message displays the results of the prerequisite checking. 7-2 Using Oracle Database Cloud - Database as a Service

109 Applying a Patch Checking Prerequisites by Using the dbpatchm Subcommand You can use the dbpatchm subcommand of the dbaascli command to the check the prerequisites of a patch before you apply it to an Oracle Database Cloud - Database as a Service instance. To check the prerequisites of a patch by using the dbpatchm subcommand: 1. Connect to the compute node as the opc user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. Edit the /var/opt/oracle/patch/dbpatchm.cfg patching configuration file, setting the keys to apply the desired patch. For more information about this file and its keys, see The dbpatchm.cfg Configuration File. 4. Check the the prerequisites of a patch: # dbaascli dbpatchm --run -prereq The prerequisites report displays. 5. Exit the root-user command shell: # exit $ Applying a Patch You can apply a patch to a service instance by using the Oracle Database Cloud Service console or by using a command-line utility. Topics Applying a Patch by Using the Oracle Database Cloud Service Console Applying a Patch on Service Instances Hosting Single-Instance Databases Applying a Patch on Service Instances Hosting Oracle RAC Databases Applying a Patch by Using the Oracle Database Cloud Service Console You can apply a patch to an Oracle Database Cloud - Database as a Service instance from the Oracle Database Cloud Service Instance Administration page. Note: Currently, applying a patch by using the Oracle Database Cloud Service console is not supported for Database as a Service instances that use Oracle Real Application Clusters (RAC). Patching Database as a Service 7-3

110 Applying a Patch Before you begin Before you apply a patch, make sure you have the latest cloud tooling on the service instance. For more information, see Updating the Cloud Tooling on a Database as a Service Instance. Note: Before applying a patch to an Oracle Database Cloud - Database as a Service instance, you should back up the instance. For instructions, see Creating an On-Demand Backup of a Database as a Service Instance. Procedure To apply a patch to a service instance: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. Click the service instance to which you want to apply a patch. The Oracle Database Cloud Service Instance Overview page is displayed. 3. Click the Administration tile. The Oracle Database Cloud Service Instance Administration page is displayed. A list of patches you can apply appears in the Available Patches section. 4. In the entry for the patch you want to apply, click the menu and then select Patch. The Patch Service window displays. 5. If you want errors to be ignored during the patching operation, select the Force apply patch option. Then, click Patch. If the Force apply patch option is not selected, patch conflicts or errors discovered during the precheck stage of the patching operation are ignored and the patch will be applied (space permitting). If the option is not selected and conflicts or errors are discovered, the patch will not be applied. The Patch Service window closes and the patching operation begins. The Administration tile shows the starting time of the patching operation and a Patching... message replaces the Patch button. When the patching operation completes, the Instance Administration page shows the completion time of the patching operation, and a log of the operation s activities appears in the Details of Last Patching Activity section. If the operation was successful, the patch is removed from the list of patches in the Available Patches. If the operation failed, the patch remains in the list. In this case, check the Details of Last Patching Activity section for information about the failure. 7-4 Using Oracle Database Cloud - Database as a Service

111 Applying a Patch Note: Patching operations are performed with a minimum of impact on the functioning of the service instance. However, during part of the operation the database is shut down for a period of time, thus making the database inaccessible. Applying a Patch on Service Instances Hosting Single-Instance Databases You can use the dbpatchm subcommand of the dbaascli utility to apply a patch to a service instance. Before you begin Before you apply a patch, make sure you have the latest cloud tooling on the service instance. For more information, see Updating the Cloud Tooling on a Database as a Service Instance. Note: Before applying a patch to an Oracle Database Cloud - Database as a Service instance, you should back up the instance. For instructions, see Creating an On-Demand Backup of a Database as a Service Instance. Procedure To apply a patch to a service instance by using the dbpatchm subcommand: 1. Connect to the compute node as the opc user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. If you have not already done so, edit the /var/opt/oracle/patch/ dbpatchm.cfg patching configuration file, setting the keys to apply the desired patch. For more information about this file and its keys, see The dbpatchm.cfg Configuration File. 4. Apply the patch to the instance using the dbpatchm subcommand of dbaascli: # dbaascli dbpatchm --run -apply The dbpatchm subcommand displays progress as the patch is applied. Note: Patching operations are performed with a minimum of impact on the functioning of the service instance. However, during part of the operation the database is shut down for a period of time, thus making the database inaccessible. Patching Database as a Service 7-5

112 Applying a Patch 5. Exit the root-user command shell: # exit $ Applying a Patch on Service Instances Hosting Oracle RAC Databases You can use the apply patch subcommand of the raccli utility to apply a patch to a service instance. Before you begin Before you apply a patch, make sure you have the latest cloud tooling on the service instance. For more information, see Updating the Cloud Tooling on a Database as a Service Instance. Note: Before applying a patch to an Oracle Database Cloud - Database as a Service instance, you should back up the instance. For instructions, see Creating an On-Demand Backup of a Database as a Service Instance. Procedure To apply a patch to a service instance by using the apply patch subcommand: 1. Connect to the compute node as the opc user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Apply a patch to the Oracle Database home using the apply patch subcommand with the -db option: $ raccli apply patch -db -tag tag-name -local Where tag-name is the name of the patch. If you do not specify a specific patch, the latest patch is applied. The local option causes raccli to update the Oracle Database home only on the current (local) compute node. If this option is omitted, the Oracle Database home is updated on all compute nodes of the Database as a Service instance. Note: Patching operations are performed with a minimum of impact on the functioning of the service instance. However, during part of the operation the database is shut down for a period of time, thus making the database inaccessible. 3. Apply a patch to the Grid Infrastructure home using the apply patch subcommand of raccli: $ raccli apply patch -gi -tag tag-name -local Where tag-name is the name of the patch. If you do not specify a specific patch, the latest patch is applied. 7-6 Using Oracle Database Cloud - Database as a Service

113 Rolling Back a Patch or Failed Patch The local option causes raccli to update the Grid Infrastructure home only on the current (local) compute node. If this option is omitted, the Grid Infrastructure home is updated on all compute nodes of the Database as a Service instance. Note: Patching operations are performed with a minimum of impact on the functioning of the service instance. However, during part of the operation the database is shut down for a period of time, thus making the database inaccessible. Rolling Back a Patch or Failed Patch You can roll back a patch or failed patch attempt on a service instance by using the Oracle Database Cloud Service console or by using the dbpatchm subcommand of the dbaascli utility. Note: Currently, rolling back a patch is not supported for Database as a Service instances that use Oracle Real Application Clusters (RAC). Note: Oracle strongly recommends against performing the rollback operation on a service instance that has never had patches applied to it. You should only use the rollback operation on patches that you have applied to a service instance. Note: Beginning with the April 2015 Patch Set Update (Apr 2015 PSU), Oracle has adopted a composite approach to patch set updates. With this composite approach, a rollback operation restores the software release level to the previous patch set level instead of to the base software release level. For example, if you roll back the April 2015 Patch Set Update, the software is restored to the January 2015 Patch Set Update release level, not the base release level. Topics Rolling Back a Patch or Failed Patch by Using the Service Console Rolling Back a Patch or Failed Patch by Using the dbpatchm Subcommand Patching Database as a Service 7-7

114 Rolling Back a Patch or Failed Patch Rolling Back a Patch or Failed Patch by Using the Oracle Database Cloud Service Console You can roll back the last patch or failed patch attempt to an Oracle Database Cloud - Database as a Service instance from the Oracle Database Cloud Service Instance Administration page. Note: Currently, rolling back a patch by using the Oracle Database Cloud Service console is not supported for Database as a Service instances that use Oracle Real Application Clusters (RAC). 7-8 Using Oracle Database Cloud - Database as a Service

115 Rolling Back a Patch or Failed Patch Note: If you are rolling back the April 2015 Patch Set Update (Apr 2015 PSU) or the January 2015 Patch Set Update (Jan 2015 PSU), you need to include the update s overlay patch numbers in the rollback operation. To do so, you must add the overlay patch numbers to the rollbackpatches.txt file before rolling back the patch: 1. Connect as the oracle user to the compute node. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Navigate to the /var/opt/oracle/patch directory: $ cd /var/opt/oracle/patch 3. Change permissions on the rollbackpatches.txt file to make it editable: $ chmod +w rollbackpatches.txt 4. Use an editor such as vim to add the following lines to the end of the rollbackpatches.txt file, making sure to include the colon at the end of each line: For the Apr 2015 PSU on Oracle Database : : :datapatch For the Apr 2015 PSU on Oracle Database , Standard Edition: : :../../sqlpatch/ /postdeinstall.sql For the Apr 2015 PSU on Oracle Database , all Enterprise Editions: : :../../sqlpatch/ /postdeinstall.sql :../../sqlpatch/ /postdeinstall.sql For the Jan 2015 PSU on Oracle Database : : :datapatch For the Jan 2015 PSU on Oracle Database : : :../../sqlpatch/ /postdeinstall.sql To roll back the last patch or failed patch attempt to a service instance by using the Oracle Database Cloud Service console: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. Click the service instance on which you want to roll back a patch. Patching Database as a Service 7-9

116 Rolling Back a Patch or Failed Patch The Oracle Database Cloud Service Instance Overview page is displayed. 3. Click the Administration tile. The Oracle Database Cloud Service Instance Administration page is displayed. 4. Click Rollback. The Instance Administration page redisplays, showing a status message that your request has been submitted, the Administration tile shows the starting time of the rollback operation, and a Rolling back... message replaces the Rollback button. Note: Rollback operations are performed with a minimum of impact on the functioning of the service instance. However, during part of the operation the database is shut down for a period of time, thus making the database inaccessible. 5. Refresh the Instance Administration page occasionally to update the status message. Note that the rollback operation can take several minutes to complete. When the rollback operation completes, the Administration page shows the completion time of the operation, and a log of the operation s activities appears in the Details of Last Patching Activity section. Rolling Back a Patch or Failed Patch by Using the dbpatchm Subcommand You can use the dbpatchm subcommand of the dbaascli utility to roll back the last patch or failed patch attempt to a service instance. To roll back the last patch or failed patch attempt to a service instance by using the dbpatchm subcommand: 1. Connect as the opc user to the service instance's virtual machine (VM). For detailed instructions, see Connecting to a Virtual Machine Through Secure Shell (SSH). 2. Start a root-user command shell: $ sudo -s # 3. If you are rolling back the April 2015 Patch Set Update (Apr 2015 PSU) or the January 2015 Patch Set Update (Jan 2015 PSU), you need to include the update s overlay patch numbers in the rollback operation. To do so, you must add the overlay patch numbers to the rollbackpatches.txt file before rolling back the patch: a. Change to the oracle user: # su - oracle $ b. Navigate to the /var/opt/oracle/patch directory: 7-10 Using Oracle Database Cloud - Database as a Service

117 Rolling Back a Patch or Failed Patch $ cd /var/opt/oracle/patch c. Change permissions on the rollbackpatches.txt file to make it editable: $ chmod +w rollbackpatches.txt d. Use an editor such as vim to add the following lines to the end of the rollbackpatches.txt file, making sure to include the colon at the end of each line: For the Apr 2015 PSU on Oracle Database : : :datapatch For the Apr 2015 PSU on Oracle Database , Standard Edition: : :../../sqlpatch/ /postdeinstall.sql For the Apr 2015 PSU on Oracle Database , all Enterprise Editions: : :../../sqlpatch/ /postdeinstall.sql :../../sqlpatch/ /postdeinstall.sql For the Jan 2015 PSU on Oracle Database : : :datapatch For the Jan 2015 PSU on Oracle Database : : :../../sqlpatch/ /postdeinstall.sql e. Return to being the root user: $ exit # 4. Roll back the last patch in the instance using the dbpatchm subcommand of dbaascli: # dbaascli dbpatchm --run -rollback The patch is removed and database instance reverts to its previous state. Note: Rollback operations are performed with a minimum of impact on the functioning of the service instance. However, during part of the operation the database instance hosted on the service instance is shut down, thus making the database inaccessible. 5. Exit the root-user command shell: # exit $ Patching Database as a Service 7-11

118 Applying a Patch to a Test Instance Applying a Patch to a Test Instance You can use the clonedb option of the dbpatchm subcommand to apply a patch to a test instance of Oracle Database Cloud - Database as a Service before you apply it to a live, production instance. Note: Currently, applying a patch to a test instance is not supported for Database as a Service instances that use Oracle Real Application Clusters (RAC). To apply a patch to a test instance: 1. Using the Create Database Cloud Service Instance wizard, create a test Database as a Service instance, providing the same information as you did when creating the live instance. 2. Connect as the opc user to the test instance and then perform these steps: a. Start a root-user command shell: $ sudo -s # b. Run the following commands: # cd /home/oracle #./deinstall.pl... # /var/opt/oracle/ocde/ocde -dump -alist=prep sda... # c. Exit the root-user command shell and disconnect from the test instance. 3. Copy the SSH private key file for the SSH key used when creating the test instance to the live instance. 4. Connect as the opc user to the live instance and then start a root-user command shell: $ sudo -s # 5. Edit the /var/opt/oracle/patch/dbpatchm.cfg patching configuration file, setting the normal keys to perform a patching operation. In addition, set the following keys: cloning: set this key to yes remotenode: set this key to the IP address of the test instance sshkey_fl: set this key to value of the SSH private key file you copied to the live instance upg: set this key to upg 7-12 Using Oracle Database Cloud - Database as a Service

119 The dbpatchm Subcommand 6. Apply the patch to the test instance using the dbpatchm subcommand of dbaascli: # dbaascli dbpatchm --run -clonedb The dbpatchm subcommand displays progress as it copies information from the live instance to the test instance and then applies the patch to the test instance. 7. Exit the root-user command shell and disconnect from the test instance. After applying the patch to the test instance, confirm appropriate application of the patch on the test instance. When satisfied, you can delete the test instance and apply the patch to the live instance. The dbpatchm Subcommand Use the dbpatchm subcommand of the dbaascli utility to perform patching operations on an Oracle Database Cloud - Database as a Service instance. The dbaascli utility is available on a compute node associated with the service instance. Note: The dbpatchm subcommand must be run with root access. Therefore, you need to connect to the compute node as the opc user to perform patching operations. The full syntax for the dbpatchm subcommand is: dbaascli dbpatchm --run [ -list_patches -apply -prereq -setup -config -cleanup -reset -rollback -clonedb ] To perform a patching operation, the dbpatchm subcommand reads and acts on the content of the dbpatchm.cfg patching configuration file. For information about this file, see The dbpatchm.cfg Configuration File. When you run the dbpatchm subcommand, it records its activity in the log file /var/opt/oracle/log/dbpatchm/dbpatchm.log. The following table describes the options shown in the syntax for the dbpatchm subcommand. Option list_patches apply Description Display a list of available patches. Run prereq, setup, config and cleanup in order. You should use this option to patch a database instance because it performs the required steps in order for you. Patching Database as a Service 7-13

120 The dbpatchm.cfg Configuration File Option prereq setup config cleanup reset rollback clonedb Description Test the database instance for patch readiness. In addition to performing conflict and readiness checking, the apply option detects whether one-off patches have been applied to the instance and warns you that they could be overwritten as part of the patching process. You can run this option any number of times. If prereq reports an error, check the log file, fix the error, and rerun the check. For more information, see Checking Prerequisites Before Applying a Patch. Set up the database for the patch. If setup fails, check the log file to determine what caused the failure. Correct the problem and then use the cleanup and reset options before attempting to use setup again. Apply the patch. This option should only be used after prereq and setup have been used successfully. After the patch is applied, config checks whether any one-off patches discovered by prereq were included in the patch that was applied and reports any that were not so that you can manually apply them again. When config is run, the database instance is shut down. Upon its completion, the database instance is restarted. Removes temporary files and storage volumes after the patch has been applied. You can run this option any number of times after a patch has been applied. Undo a partial patching operation and reset dbpatchm status information so that a new patching operation can be performed. You can use this option before starting a new patching operation to ensure that the new operation s status will be reported accurately. Remove the patch just applied. Before using this option, set the psunum key in the dbpatchm.cfg file to the PSU s bug id. In some cases, you may need to use this option to clean up a patching operation that failed during the config step. Apply the patch to a test instance, prior to applying the patch to the live instance. To use this option, see Applying a Patch to a Test Instance. The dbpatchm.cfg Configuration File To perform a patching operation, the dbpatchm subcommand reads and acts on the content of the /var/opt/oracle/patch/dbpatchm.cfg patching configuration file. This file, which is created when the service instance is created, provides information about the locations of various files that may be used in patching operations Using Oracle Database Cloud - Database as a Service

121 The dbpatchm.cfg Configuration File Before using dbpatchm to perform a patching operation, set the value of the psunum key in the dbpatchm.cfg file to the patch ID of the patch to apply. To find out what patches are available, use the list_patches option of the dbpatchm subcommand, as described in The dbpatchm Subcommand. The dbpatchm.cfg file contains additional keys you can edit to customize the patching operation, and comment lines describing the purpose of each key and how to set its value. Here is a sample dbpatchm.cfg file showing these keys and comments. # sample config file # oss storage container url with public access, normally should not be changed # there is a default for this now, that is set to production container oss_container_url="" # change this following golden image zip/psu zip file to be used in patching # this will be used only if you run dbaascli/dbpatchm directly # keep these files in different location from temporary_space given below & /u01/psu gold_img_loc="</tmp/db _ee_psu.tar.gz>" psu_zip_loc="</tmp/p _112040_linux-x86-64.zip>" # location where the temporary files will be kept - should have 15GB space minimum # change this location if needed but do not use /u01/psu - used for conflict check temporary_space="/u01/download"; # turn this ignore_patch_conflict to 1 to let patching ignore conflicts ignore_patch_conflict=0 # turn this ignore_space_less_than_15g to 1 to let patching proceed if discspace < 15g ignore_space_less_than_15g=0 # change the gf_home and app_base if needed app_base="/u01/app/oracle" gf_home="/u01/app/oracle/product/glassfish3/glassfish" # create /var/opt/oracle/patch/files_to_save.ora with full path of directory or # files to preserve any special files you may have in your /u01/app directory. # set this to yes, if you have files_to_save.ora special_files="no" # type could be "psu", "upg" type="psu" # psunum is the bugid for PSU's - needed to rollback the psu patches psunum= # patching method could be cloning (for temporary instance validation) or psu way # when cloning is yes, remote node IP needs to be provided and also sys password cloning="no" remotenode="" syspasswd="" # ssh private key needed for cloning that needs a 2nd VM connectivity # "/root/.ssh/pat.key" sshkey_fl="" # oracle recovery manager catalog connect string - if configured rcatconnect="" # data guard patching - need to provide primary and standby ip's and # private sshkeys to connect to the same Patching Database as a Service 7-15

122 The dbpatchm.cfg Configuration File # if dg_inst="yes", then all dg_ parameters need to be provided dg_inst="no" dg_primary="" dg_primary_sshkey_fl="" dg_standby="" dg_standby_sshkey_fl="" 7-16 Using Oracle Database Cloud - Database as a Service

123 8 Configuring Database Features, Database Options, and Companion Products Oracle Database Cloud - Database as a Service provides special capabilities for certain Oracle Database features and options and for certain companion products. Topics Using Oracle Real Application Clusters (RAC) in Database as a Service Using Hybrid Columnar Compression (HCC) in Database as a Service Using Tablespace Encryption in Database as a Service Using Oracle Application Express in Database as a Service Using Oracle Enterprise Manager Cloud Control with Database as a Service Using the Oracle Pluggable Database Self-Service Provisioning Application Using Oracle Real Application Clusters (RAC) in Database as a Service When creating an Oracle Database Cloud - Database as a Service instance at the Oracle Database Cloud Service service level, you can create an Oracle RAC database. Oracle RAC enhances Oracle Database capabilities so that you can use multiple database instances on different compute nodes in a Database as a Service instance concurrently. This allows you to scale workload across multiple database instances in order to efficiently store, update, and retrieve data. Oracle RAC provides the software that manages multiple servers and database instances as a single set of servers, called a cluster. The data files that comprise the database reside on shared storage that is accessible from all servers that are part of the cluster. Each server in the cluster runs the Oracle RAC software. Unlike a single-instance Oracle database, which has a one-to-one relationship between data files and the database instance, Oracle RAC databases have a one-to-many relationship between data files and database instances. This means that in an Oracle RAC database multiple database instances access a single set of database files concurrently, allowing you to access the data from any database instance in the database cluster. This allows you to use horizontal scalability beyond the scope of one compute node, in case this compute node is insufficient to run the desired workload. It also increases availability of the database and the data in case a database instance or compute node fails. The remaining database instance can be used to continue operations while the failed database instance or compute node is being restarted. Having more than one database instance also allows you to perform rolling patch upgrades. Configuring Database Features, Database Options, and Companion Products 8-1

124 Using Oracle Real Application Clusters (RAC) in Database as a Service To create an Oracle RAC database in Database as a Service, make the following choices in the Create Database Cloud Service Instance wizard: For Service Level, choose Oracle Database Cloud Service. For Software Edition, choose Enterprise Edition - Extreme Performance. For Shape (on the Service Details page), choose a shape with two OCPUs for trial accounts or a shape with four or more OCPUs for subscription accounts. For RAC Database (on the Service Details page), choose Yes, set up RAC. When you make these choices, Database as a Service creates a two-node Oracle RAC database, hosting the database on two independent compute nodes that share data, fast recovery area, and redo log storage. It creates these compute nodes using computing, storage and networking resources provided by Oracle Compute Cloud service. Managing a Service Instance that Uses Oracle RAC Compared to a Service Instance that Doesn t Because a Database as a Service instance that uses Oracle RAC comprises two compute nodes that each host a RAC database instance, you manage the service instance in slightly different ways: Cloud tooling: you use raccli instead of bkup_api or dbaascli. For more information, see The raccli Utility. You can stop and start the database instances and even the compute nodes independently of each other. Thus, the database can remain available even when you need to perform maintenance that requires you to stop a database instance or compute node. More About the Oracle RAC Configuration on a Service Instance Cluster size: currently, the Oracle RAC database on a Database as a Service instance is limited to a two-node cluster. Cloud tooling: Oracle Cloud tooling is provided for the common administrative tasks of scaling, backing up and recovering, and patching. For more information, see Scaling a Database as a Service Instance and The raccli Utility. Network access: on the service instance s compute nodes, access to all ports except port 22 is disabled. Port 22 is open for passwordless, key-based SSH access by the opc user. To enable access to other ports, see Enabling Access to a Compute Node Port. Networking for client access: to make client connections to the Oracle RAC database, you include particular options in the connection s entry in the client s tnsnames.ora file. For more information, see Connecting Remotely to the Database by Using Oracle Net Services. Database file storage: storage for database data files, the fast recovery area, and the redo logs is created and managed using Oracle Automatic Storage Management (ASM) and Oracle Automatic Storage Management Cluster File System (ACFS) instead of Linux LVM. 8-2 Using Oracle Database Cloud - Database as a Service

125 Using Hybrid Columnar Compression (HCC) in Database as a Service Included software: Oracle Grid Infrastructure, Oracle ASM and Oracle ACFS are included; Oracle Application Express, Oracle REST Data Services, Oracle DBaaS Monitor and Oracle GlassFish Server are not currently included. Using Hybrid Columnar Compression (HCC) in Database as a Service Hybrid Columnar Compression (HCC) is a storage-related Oracle Database feature that causes the database to store the same column for a group of rows together. Storing column data together in this way can dramatically increase the storage savings achieved from compression. Because database operations work transparently against compressed objects, no application changes are required. The HCC feature is available on Oracle Database Cloud - Database as a Service instances created using the Oracle Database Cloud Service service level. For more information about HCC, see: Hybrid Columnar Compression in Oracle Database Concepts Consider Using Table Compression in Oracle Database Administrator's Guide table_compression under CREATE TABLE in Oracle Database SQL Language Reference Using Tablespace Encryption in Database as a Service In Oracle Database Cloud - Database as a Service databases, user-created tablespaces are encrypted by default. All new tablespaces you create in a Database as a Service database are encrypted by default. The tablespaces that were created when you created the service instance are not encrypted. In an Oracle Database 11g database, none of the tablespaces created when the database was created are encrypted. In an Oracle Database 12c database, this includes the tablespaces in the root (CDB$ROOT), the seed (PDB$SEED), and the PDB that is created when the database is created. Topics Creating Encrypted Tablespaces Managing Tablespace Encryption Creating Encrypted Tablespaces User-created tablespaces are encrypted by default. By default any new tablespaces you create by using the SQL CREATE TABLESPACE command or any tool executing the CREATE TABLESPACE command will be encrypted with the AES128 encryption algorithm. You do not need to include the USING 'encrypt_algorithm' clause to use the default encryption. You can specify another supported algorithm by including the USING 'encrypt_algorithm' clause on the CREATE TABLESPACE command. Supported algorithms for Oracle Database 11g and Oracle Database 12c are: AES256, AES192, AES128 and 3DES168. Configuring Database Features, Database Options, and Companion Products 8-3

126 Using Tablespace Encryption in Database as a Service Managing Tablespace Encryption You can manage the software keystore (known as an Oracle wallet in Oracle Database 11g), the master encryption key, and control whether encryption is enabled by default. Managing the Software Keystore and Master Encryption Key Tablespace encryption uses a two-tiered, key-based architecture to transparently encrypt (and decrypt) tablespaces. The master encryption key is stored in an external security module (software keystore). This master encryption key is used to encrypt the tablespace encryption key, which in turn is used to encrypt and decrypt data in the tablespace. When the Database as a Service instance is created, a local auto-login software keystore is created. The keystore is local to the compute node and is protected by a system-generated password. The auto-login software keystore is automatically opened when accessed. You can change (rotate) the master encryption key by using the tde rotate masterkey subcommand of the dbaascli utility. When you execute this subcommand you will be prompted for the keystore password. Enter the password specified when the service instance was created. For more information about changing the master encryption key, see Managing the TDE Master Encryption Key in Oracle Database 12c Advanced Security Guide or Setting and Resetting the Master Encryption Key in Oracle Database 11g Advanced Security Administrator's Guide. Controlling Default Tablespace Encryption The ENCRYPT_NEW_TABLESPACES initialization parameter controls default encryption of new tablespaces. In Database as a Service databases, this parameter is set to CLOUD_ONLY. Values of this parameter are as follows. Value ALWAYS CLOUD_ONLY DDL Description Any tablespace created will be transparently encrypted with the AES128 algorithm unless a different algorithm is specified on the ENCRYPTION clause. Tablespaces created in a Database Cloud Service database will be transparently encrypted with the AES128 algorithm unless a different algorithm is specified on the ENCRYPTION clause. For non-database Cloud Service databases, tablespaces will only be encrypted if the ENCRYPTION clause is specified. This is the default value. Tablespaces are not transparently encrypted and are only encrypted if the ENCRYPTION clause is specified. 8-4 Using Oracle Database Cloud - Database as a Service

127 Using Oracle Application Express in Database as a Service Using Oracle Application Express in Database as a Service Oracle Database Cloud - Database as a Service instances include Oracle Application Express. Note: This section does not apply to service instances that use Oracle Real Application Clusters. Such instances do not currently include Oracle Application Express. Oracle Application Express enables you to design, develop and deploy beautiful, responsive, database-driven applications using only your web browser. If you are new to Oracle Application Express, see its Overview and Getting Started pages on Oracle Technology Network to learn about its features and get started using it. This section provides guidance on how to navigate to Oracle Application Express from Oracle Database Cloud - Database as a Service, how to upgrade Oracle Application Express releases residing in Database as a Service and instructions on migrating Oracle Application Express applications between Database as a Service and Database Schema Service. Topics Accessing the Oracle Application Express Administration Console Accessing the Oracle Application Express Home Page Upgrading from Oracle Application Express 4.2 to 5.0 in Database as a Service Migrating Applications from Database as a Service to Database Schema Service Migrating Applications from Database Schema Service to Database as a Service Accessing the Oracle Application Express Administration Console Oracle Database Cloud - Database as a Service instances include Oracle Application Express, which you manage using the Oracle Application Express administration console. You access this administration console by going to the Oracle Application Express home page and then clicking the Administration link. If you are new to Oracle Application Express, see its Overview and Getting Started pages on Oracle Technology Network to learn about its features and get started using it. How you access the administration console depends on whether the HTTPS port (443) has been unblocked. When a Database as a Service instance is first created, the HTTPS port is blocked to ensure network security. For information about unblocking a port, see Enabling Access to a Compute Node Port. Accessing the Administration Console When the HTTPS Port Is Unblocked To access the administration console when the HTTPS port is unblocked: 1. Direct your browser to the appropriate URL, based on which release of Oracle Database is in use: Configuring Database Features, Database Options, and Companion Products 8-5

128 Using Oracle Application Express in Database as a Service For the CDB in an Oracle Database 12c Release 1 database: For a PDB in an Oracle Database 12c Release 1 database: For an Oracle Database 11g Release 2 database: where node-ip-address is the public IP address of the compute node hosting the administration console and lowercase-pdb-name is the name of the PDB, with all letters in lowercase. Obtain these values by viewing details as described in Viewing Detailed Information for a Database as a Service Instance. After directing your browser to the appropriate URL, the Oracle Application Express Login page is displayed. 2. Enter the following information to log in as the administrator. Then, click Login to Application Express. In the Workspace box, enter INTERNAL. In the Username box, enter ADMIN. In the Password box, enter the password specified when the Database as a Service instance was created. The Oracle Application Express administration home page is displayed. Note: If this it the first login to the Oracle Application Express administration console, you will be required to change your password before you can access the administration home page. Accessing the Administration Console When the HTTPS Port Is Blocked To access the administration console when the HTTPS port is blocked, you must create an SSH tunnel to port 443 on the compute node hosting the administration console. For information about creating an SSH tunnel, see Creating an SSH Tunnel to a Compute Node Port. After creating an SSH tunnel to port 443, you can access the administration console as follows: 1. Direct your browser to the appropriate URL, based on which release of Oracle Database is in use: For the CDB in an Oracle Database 12c Release 1 database: localhost/apex/ For a PDB in an Oracle Database 12c Release 1 database: localhost/apex/lowercase-pdb-name/ For an Oracle Database 11g Release 2 database: where lowercase-pdb-name is the name of the PDB, with all letters in lowercase. 8-6 Using Oracle Database Cloud - Database as a Service

129 Using Oracle Application Express in Database as a Service After directing your browser to the appropriate URL, the Oracle Application Express Login page is displayed. 2. Enter the following information to log in as the administrator. Then, click Login to Application Express. In the Workspace box, enter INTERNAL. In the Username box, enter ADMIN. In the Password box, enter the password specified when the Database as a Service instance was created. The Oracle Application Express administration home page is displayed. Note: If this it the first login to the Oracle Application Express administration console, you will be required to change your password before you can access the administration home page. Accessing the Oracle Application Express Home Page Oracle Database Cloud - Database as a Service instances include Oracle Application Express, which you access on the Oracle Application Express home page. If you are new to Oracle Application Express, see its Overview and Getting Started pages on Oracle Technology Network to learn about its features and get started using it. How you access the home page depends on whether the HTTPS port (443) has been unblocked. When a Database as a Service instance is first created, the HTTPS port is blocked to ensure network security. For information about unblocking a port, see Enabling Access to a Compute Node Port. Accessing the Home Page When the HTTPS Port Is Unblocked To access the home page when the HTTPS port is unblocked, direct your browser to the appropriate URL, based on which release of Oracle Database is in use: For the CDB in an Oracle Database 12c Release 1 database: For a PDB in an Oracle Database 12c Release 1 database: For an Oracle Database 11g Release 2 database: apex/ where node-ip-address is the public IP address of the compute node hosting Oracle Application Express and lowercase-pdb-name is the name of the PDB, with all letters in lowercase. Obtain these values by viewing details as described in Viewing Detailed Information for a Database as a Service Instance. After the home page is displayed, enter INTERNAL as the workspace, enter ADMIN as the username, enter the password specified when the service instance was created, and then click Login to Application Express. Note that the initial password (that is, Configuring Database Features, Database Options, and Companion Products 8-7

130 Using Oracle Application Express in Database as a Service the password specified when the service instance was created) must be changed the first time you log in as the ADMIN user. Accessing the Home Page When the HTTPS Port Is Blocked To access the home page when the HTTPS port is blocked, you must create an SSH tunnel to port 443 on the on the compute node hosting Oracle Application Express. For information about creating an SSH tunnel, see Creating an SSH Tunnel to a Compute Node Port. After creating an SSH tunnel to port 443, you can access the home page by directing your browser to the appropriate URL, based on which release of Oracle Database is in use: For the CDB in an Oracle Database 12c Release 1 database: apex/ For a PDB in an Oracle Database 12c Release 1 database: apex/lowercase-pdb-name/ For an Oracle Database 11g Release 2 database: where lowercase-pdb-name is the name of the PDB, with all letters in lowercase. After the home page is displayed, enter INTERNAL as the workspace, enter ADMIN as the username, enter the password specified when the service instance was created, and then click Login to Application Express. Note that the initial password (that is, the password specified when the service instance was created) must be changed the first time you log in as the ADMIN user. Upgrading from Oracle Application Express 4.2 to 5.0 in Database as a Service These instructions are for those of you who have Oracle Application Express 4.2 installed on your 12c Oracle Database Cloud - Database as a Service instance and want to upgrade to Oracle Application Express 5.0. To upgrade from Oracle Application Express 4.2 to 5.0 in Database as a Service: 1. Upload Oracle Application Express and patch files to Database as a Service. a. Download Oracle Application Express from the Oracle Technical Network. b. Download patch # for Oracle Database c. Log in as an oracle user. d. Use scp/sftp to upload the Oracle Application Express zip file and patch file to your /tmp directory in your Database as a Service instance. e. Unzip the patch file by entering this command: unzip p _121020_linux-x86 64.zip f. Navigate to the new patch directory by running this command: cd Now you re ready to shutdown the database and listeners and apply the patch. 8-8 Using Oracle Database Cloud - Database as a Service

131 Using Oracle Application Express in Database as a Service a. Before applying this patch, you need to shutdown the database and its listeners. There are multiple ways to do this, so perform the shutdown whichever way is best for you. b. To check for patch conflicts, after the database and its listeners are shutdown, run the following: $ORACLE_HOME/OPatch/opatch prereqcheckconflictagainstohwithdetail -ph./ If there are no conflicts you will get this result: Prereq "checkconflictagainstohwithdetail" passed. OPatch succeeded. Note: If you did not get the above result, stop the upgrade immediately. Proceeding will most likely cause serious damage to your database. c. To start patching, run the following: opatch apply 3. If the patch applied successfully, start up the database and listeners. 4. You are ready to upgrade to Oracle Application Express 5.0. a. Upgrade all PDBs with the new patch you applied. This is done with a utility called datapatch. To execute this utility, run the following command: datapatch b. Unzip the uploaded Oracle Application Express zip file. This results in an apex directory. c. Next perform some maintenance by moving the old apex directory and replacing it with the new directory. Change the Linux directory to the Oracle Home by running this command: $ORACLE_HOME d. Now rename the Oracle Application Express 4.2 home to apex_old: mv apex apex_old e. Move the Oracle Application Express 5.0 home to the oracle home: mv /tmp/apex $ORACLE_HOME f. Move to the new apex directory: cd $ORACLE_HOME/apex g. Start up sqlplus as sys: sqlplus / as sysdba h. More than likely, your SSH session is going to time out during the following upgrade steps. To avoid this, change the timeout parameters on the VM. See Extending Your SSH Session Timeout for instructions on how to do this. Configuring Database Features, Database Options, and Companion Products 8-9

132 Using Oracle Application Express in Database as a Service i. Start the SYSAUX SYSAUX TEMP /i/ j. After the upgrade finishes, check the log files for errors by issuing the following commands at the Linux prompt: grep ORA- *.log grep PLS- *.log If you don t find any errors, you are ready to proceed to the next step and replace the image directory. 5. After successfully upgrading, it s time to move the image directory. a. Change directory to the glassfish docroot: cd /u01/app/oracle/product/glassfish3/glassfish/domains/ domain1 b. Move the old images directory to i_old: mv i i_old c. Create an i directory: mkdir i d. Move into the i directory: cd i e. Copy the images from the apex directory to here: cp -rf $ORACLE_HOME/apex/images/*. Upgrade complete! Go to your apex URL to bring up the new Oracle Application Express 5.0 Home page. Extending Your SSH Session Timeout To extend your SSH timeout values: 1. Log into your Oracle Cloud VM as opc, then change directory to the ssh directory. cd /etc/ssh 2. Make a copy of the ssh configuration file. sudo cp sshd_config sshd_config.save 3. Edit the file as root. sudo vi sshd_config 4. Change the parameters at the end of the file or replace them with the following: TCPKeepAlive yes ClientAliveCountMax Using Oracle Database Cloud - Database as a Service

133 Using Oracle Application Express in Database as a Service ClientAliveInterval 30 TCPKeepAlive yes 5. Save the file and restart ssh. sudo service sshd restart Migrating from Oracle Database Cloud - Database as a Service to Oracle Database Cloud - Database Schema Service Oracle Application Express applications and data can be migrated from Oracle Database Cloud - Database as a Service to Oracle Database Cloud - Database Schema Service. To migrate from Database as a Service to Database Schema Service: 1. Use Oracle SQL Developer to move data: a. Install SQL Developer if not already installed. See Installing Oracle SQL Developer in Using Oracle Database Cloud - Database Schema Service. b. From SQL Developer, create a connection to Database as a Service. See Database Connections in Oracle SQL Developer User s Guide. c. From SQL Developer, create a cloud connection to Database Schema Service. See Configuring Oracle SQL Developer Cloud Connection in Using Oracle Database Cloud - Database Schema Service. d. Use the cart to move data from one service to the other. See Creating and Deploying a Cart of Objects in Using Oracle Database Cloud - Database Schema Service. When the SQL Developer cart deployment status is PROCESSED, the data and tables have been successfully migrated from Database as a Service to Database Schema Service. See Checking Deployment Status in Using Oracle Database Cloud - Database Schema Service. 2. Use Oracle Application Express to migrate the application: a. Access Oracle Application Express Application Builder home page from Database as a Service. See Accessing the Oracle Application Express Administration Console and Accessing the Oracle Application Express Home Page. b. Create an application export. See Understanding the Deployment Process in Oracle Application Express Application Builder User s Guide. c. Save the application export file locally. d. Access Oracle Application Express Application Builder home page from the destination Database Schema Service. See Accessing Oracle Database Cloud - Database Schema Service in Using Oracle Database Cloud - Database Schema Service. e. Import the locally saved application export file. See Importing Export Files in Oracle Application Express Application Builder User s Guide. Configuring Database Features, Database Options, and Companion Products 8-11

134 Using Oracle Application Express in Database as a Service The application has now been migrated from Database as a Service to Database Schema Service. Migrating from Oracle Database Cloud - Database Schema Service to Oracle Database Cloud - Database as a Service Oracle Application Express applications and data can be migrated from Oracle Database Cloud - Database Schema Service to Oracle Database Cloud - Database as a Service To migrate from Database Schema Service to Database as a Service: 1. Use Database Schema Service Data Export to move data: a. Access the My Services console for Database Schema Service. See Steps to Sign In to the My Services Applicationin Managing and Monitoring Oracle Cloud. b. Create a data Export of the service. For further information on creating a data Export in Database Schema Service, see Creating an Oracle Data Pump Export in Using Oracle Database Cloud - Database Schema Service. c. Download and save the data Export file locally. For further information on downloading an Database Schema Service data Export, see Downloading a Data Export in Using Oracle Database Cloud - Database Schema Service. d. Access Oracle Application Express Application Builder home page from Database as a Service. See Accessing the Oracle Application Express Administration Console and Accessing the Oracle Application Express Home Page. e. Import the locally saved data Export file. See Importing Export Files in Oracle Application Express Application Builder User s Guide. The data has now been migrated from Database Schema Service to Database as a Service. 2. Use Oracle Application Express to migrate the application: a. Access Oracle Application Express Application Builder home page from Database Schema Service. See Accessing Oracle Database Cloud - Database Schema Service in Using Oracle Database Cloud - Database Schema Service. b. Create an application export file. See Understanding the Deployment Process in Oracle Application Express Application Builder User s Guide. c. Save the application export file locally. d. Access Oracle Application Express Application Builder home page from the destination Database as a Service. See Accessing the Oracle Application Express Administration Console and Accessing the Oracle Application Express Home Page. e. Import the locally saved application export file. See Importing Export Files in Oracle Application Express Application Builder User s Guide. The application has now been migrated from Database Schema Service to Database as a Service Using Oracle Database Cloud - Database as a Service

135 Using Oracle Enterprise Manager Cloud Control with Database as a Service Using Oracle Enterprise Manager Cloud Control with Database as a Service Oracle Enterprise Manager Cloud Control 12c Release 5 ( ) includes Hybrid Cloud Management, which you can use to manage the Oracle Databases on Oracle Database Cloud - Database as a Service instances from the same management console that you use for your on-premises databases. Oracle Enterprise Manager is Oracle s integrated enterprise IT management product line, which provides the industry s only complete, integrated and business-driven enterprise cloud management solution. Oracle Enterprise Manager 12c delivers comprehensive capabilities to manage, migrate, test, and deploy applications and workloads across hybrid clouds. See EM Hybrid Cloud Management for information about its hybrid cloud features. To use the Hybrid Cloud Management feature to manage the Oracle Databases on Database as a Service instances, you perform these high-level tasks: 1. Ensure that your on-premises Enterprise Manager Cloud Control Oracle Management Service (OMS) is of version , and that at least one Management Agent exists in your enterprise. 2. Configure one or more version Management Agents within your enterprise to act as Hybrid Cloud Gateway Agents, which provide an SSH-based communication channel between Database as a Service compute nodes and the on-premises OMS. 3. Ensure that the Hybrid Cloud Gateway Agents and the on-premises OMS can communicate with the Database as a Service compute nodes. 4. Deploy Management Agents to Database as a Service compute nodes using the Add Host Targets Wizard or Enterprise Manager Command Line Interface. For the detailed steps to perform these tasks, see Enabling Hybrid Cloud Management in Oracle Enterprise Manager Cloud Control Administrator's Guide, 12c Release 5 ( ). Preserving the Hybrid Cloud Agent Home When Patching a Database as a Service Instance If you installed the Oracle Enterprise Manager Cloud Control agent under /u01/app/oracle (the Oracle Base directory) the agent home will be moved to /u01/app.org/oracle when a database patch is applied to the Database as a Service instance using the cloud tooling. If the agent home has already been moved to /u01/app.org/oracle, you can copy it back to /u01/app/oracle to restore it. Perform the following steps to configure the patching tools so that they do not move the agent home to /u01/app.org/oracle: 1. Connect to the compute node as the oracle user. For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH). 2. Create a file named /var/opt/oracle/patch/files_to_save.ora. 3. Add the full path of the agent directory to the /var/opt/oracle/patch/ files_to_save.ora file. Configuring Database Features, Database Options, and Companion Products 8-13

136 Using the Oracle Pluggable Database Self-Service Provisioning Application 4. Disconnect from the compute node, and then reconnect as the opc user. 5. Start a root-user command shell: $ sudo -s # 6. Edit the patching configuration file, /var/opt/oracle/patch/ dbpatchm.cfg, and search for the following lines: # create /var/opt/oracle/patch/files_to_save.ora with full path of directory or # files to preserve any special files you may have in your /u01/app directory. # set this to yes, if you have files_to_save.ora special_files="no" 7. Change special_files="no" to special_files="yes". 8. Save and close the file. 9. Exit the root-user command shell and disconnect from the compute node. After performing these steps, the agent home will be preserved in its original location whenever the service instance is patched. Using the Oracle Pluggable Database Self-Service Provisioning Application The Oracle Pluggable Database Self-Service Provisioning application provides an interface to Oracle Database 12c Multitenant option and allows for the provisioning of Pluggable Databases (PDBs). You can perform PDB operations including create, clone, open/close, plug/unplug, and drop. Additionally, you can grant others access to the application, giving them rights to create and manage their own PDBs within the quota limits you set. Note: This section does not apply to service instances that use Oracle Real Application Clusters. Such instances do not currently include the Oracle Pluggable Database Self-Service Provisioning application. Note: Before you begin using the Pluggable Database Self-Service Provisioning application, you need to configure its properties. See Configuring for the Pluggable Database Self-Service Provisioning Application. Topics Accessing the Pluggable Database Self-Service Provisioning Application Configuring for the Pluggable Database Self-Service Provisioning Application Setting the Password for a New User 8-14 Using Oracle Database Cloud - Database as a Service

137 Using the Oracle Pluggable Database Self-Service Provisioning Application Accessing the Pluggable Database Self-Service Provisioning Application How you access the Pluggable Database Self-Service Provisioning application depends on whether the HTTP port (80) has been unblocked. When an Oracle Database Cloud - Database as a Service instance is first created, the HTTP port is blocked to ensure network security. For information about unblocking a port, see Enabling Access to a Compute Node Port. When the HTTP port is unblocked: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. From the menu for the service instance, select Open PDB Provisioning Console. The Oracle Pluggable Database Self-Service Provisioning login page is displayed. 3. Enter admin as the user name and the password specified when the instance was created as the password, and then click Login. This option is also available from the Service Instance Overview page. menu on the Oracle Database Cloud Alternatively, you can access the Oracle Pluggable Database Self-Service Provisioning login page by directing your browser to the URL where node-ip-address is the public IP address of the compute node hosting the application. When the HTTP port is blocked: When the HTTP port on the instance is blocked, you must create an SSH tunnel to port 80 on the compute node hosting the application. For information about creating an SSH tunnel, see Creating an SSH Tunnel to a Compute Node Port. After the SSH tunnel is created, you can access the Pluggable Database Self-Service Provisioning application by directing your browser to the URL localhost/apex/f?p=pdbss. After the Oracle Pluggable Database Self-Service Provisioning login page is displayed, enter admin as the user name, enter the password specified when the service instance was created, and then click Login. Configuring for the Pluggable Database Self-Service Provisioning Application The Pluggable Database Self-Service Provisioning application sends messages to users of the application on occasion, such as when requesting an account. However, as a security measure, Oracle Cloud prohibits outgoing from service instances. Thus, these messages are blocked when using the application on an Oracle Database Cloud - Database as a Service instance. Despite the fact that outgoing messages are blocked, you must set the application s sender of to a valid address in order for the application to work correctly. To do so, you set the application s sender to an address that is local the service instance: Configuring Database Features, Database Options, and Companion Products 8-15

138 Using the Oracle Pluggable Database Self-Service Provisioning Application 1. Log into the Pluggable Database Self-Service Provisioning application. For instructions, see Accessing the Pluggable Database Self-Service Provisioning Application. 2. Click the Administration link. The Self-Service Administration page displays. 3. Locate and click the Self-Service System Configuration item. The Self-Service System Configuration page displays. 4. Locate the row labeled s From and click the edit icon in the row. The Update Self-Service System Setting page displays, providing a box where you can enter a value for the s From setting. 5. In the box, enter the local address of the oracle user: oracle@instance.compute-domain.oraclecloud.internal where instance is the name of the service instance and domain is the name of the service domain. 6. Click Save Changes. Your change is saved and the Self-Service System Configuration page displays, showing the changed value. Setting the Password for a New User As a security measure, Oracle Cloud prohibits outgoing from service instances. As a result, the messages providing new PDBSS users with their usernames and temporary passwords are blocked. You, as the PDBSS administrator, must therefore set an initial password for new users and them their account login information. You must perform this task whether you create the user manually or approve a user s request for an account. When to perform this procedure You must perform this task: After you have approved a request for access to the PDBSS application. After you have manually added a user to the PDBSS application. Procedure 1. Log in to the Oracle Application Express administration console on the Oracle Database Cloud - Database as a Service instance. For detailed instructions, see Accessing the Oracle Application Express Administration Console. Note: If your service instance is running Oracle Database 12c Release 1, make sure you log into the administration console for the CDB. 2. On the home page, click Manage Workspaces Using Oracle Database Cloud - Database as a Service

139 Using the Oracle Pluggable Database Self-Service Provisioning Application The Manage Workspaces page displays. 3. In the Workspace Actions group, click Manage Developers and Users. The Manage Developers and Users page displays. 4. In the table of users, locate the row for new PDBSS user. The user s name will have the form of an address and a workspace value of ORACLE_PDB_SELF_SERVICE. 5. Edit the new PDBSS user s information by clicking the Pencil icon in the new user s row. The Create / Edit User page displays. 6. Edit the new PDBSS user s information as follows: In the Account Privileges section, set Default Schema to C##PDBMGR. In the Password section, enter an initial password for the user in the Password box and then reenter that password in the Confirm Password box In the Password section, set Require Change of Password on First Use to Yes. In the Password section, make sure the Expire Password box is not selected. 7. Click Apply Changes. Your changes are saved and the Manage Developer and Users page is displayed with a message indicating that the user was updated. 8. Log out of the Oracle Application Express administration console. 9. Send a message to the new PDBSS user, providing the following information: A link to the PDBSS application on the Database as a Service instance. Their user name Their initial password, with a note indicating that they will be required to change their password when they login the first time. (As a security measure, you may want to send the password separately.) Configuring Database Features, Database Options, and Companion Products 8-17

140 Using the Oracle Pluggable Database Self-Service Provisioning Application 8-18 Using Oracle Database Cloud - Database as a Service

141 9 Migrating an On-Premises Oracle Database to Oracle Database Cloud You can migrate your on-premises Oracle Database database to an Oracle Database Cloud database using a number of different methods that use several different tools. Topics Choosing a Migration Method Migrating from Oracle Database 11g to Oracle Database 11g in the Cloud Migrating from Oracle Database 11g to Oracle Database 12c in the Cloud Migrating from Oracle Database 12c CDB to Oracle Database 12c in the Cloud Migrating from Oracle Database 12c Non-CDB to Oracle Database 12c in the Cloud Migration Methods Choosing a Migration Method You can migrate your on-premises Oracle Database database to an Oracle Database Cloud database using a number of different methods that use several different tools. Not all migration methods apply to all migration scenarios. Many of the migration methods apply only if specific characteristics of the source and destination databases match or are compatible. Moreover, additional factors can affect which method you choose for your migration from among the methods that are technically applicable to your migration scenario. Some of the characteristics and factors to consider when choosing a migration method are: On-premises database version Oracle Database Cloud database version On-premises host operating system and version On-premises database character set Quantity of data, including indexes Data types used in the on-premises database Storage for data staging Acceptable length of system outage Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-1

142 Migrating from Oracle Database 11g to Oracle Database 11g in the Cloud Network bandwidth To determine which migration methods are applicable to your migration scenario, gather the following information. 1. Database version of your on-premises database: Oracle Database 11g Release 2 version lower than Oracle Database 11g Release 2 version or higher Oracle Database 12c Release 1 version lower than Oracle Database 12c Release 1 version or higher 2. For on-premises Oracle Database 12c Release 1 databases, the architecture of the database: CDB (single-tenant or multitenant) Non-CDB 3. Endian format of your on-premises database s host platform Some platforms are little endian and others are big endian. Query V $TRANSPORTABLE_PLATFORM to identify the endian format, and to determine whether cross-platform tablespace transport is supported. Oracle Database Cloud uses the Linux platform, which is little endian. 4. Database character set of your on-premises database Databases on Oracle Database Cloud use the AL32UTF8 database character set. 5. Database version of the Oracle Database Cloud database you are migrating to Oracle Database 11g Release 2 Oracle Database 12c Release 1 Oracle Database 12c Release 1 databases created on Oracle Database Cloud use CDB architecture. Databases created using the Enterprise Edition option are single-tenant, and databases created using the Enterprise Edition - High Performance or Enterprise Edition - Extreme Performance option are multitenant. After gathering this information, use the source and destination database versions as your guide to see which migration methods apply to your migration scenario: Migrating from Oracle Database 11g to Oracle Database 11g in the Cloud Migrating from Oracle Database 11g to Oracle Database 12c in the Cloud Migrating from Oracle Database 12c CDB to Oracle Database 12c in the Cloud Migrating from Oracle Database 12c Non-CDB to Oracle Database 12c in the Cloud Migrating from Oracle Database 11g to Oracle Database 11g in the Cloud You can migrate Oracle Database 11g databases from on-premises to Oracle Database 11g databases in Oracle Database Cloud using several different methods. The applicability of some of the migration methods depends on the on-premises database s database character set and platform endian format. 9-2 Using Oracle Database Cloud - Database as a Service

143 Migrating from Oracle Database 11g to Oracle Database 12c in the Cloud If you have not already done so, determine the database character set of your onpremises database, and determine the endian format of the platform your on-premises database resides on. Use this information to help you choose an appropriate method. Data Pump Conventional Export/Import This method can be used regardless of the endian format and database character set of the on-premises database. For the steps this method entails, see Data Pump Conventional Export/Import. Data Pump Transportable Tablespace This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. For the steps this method entails, see Data Pump Transportable Tablespace. RMAN Transportable Tablespace with Data Pump This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. For the steps this method entails, see RMAN Transportable Tablespace with Data Pump. RMAN CONVERT Transportable Tablespace with Data Pump This method can be used only if the on-premises database character set is AL32UTF8. This method is similar to the Data Pump Transportable Tablespace method, with the addition of the RMAN CONVERT command to enable transport between platforms with different endianness. Query V$TRANSPORTABLE_PLATFORM to determine if the on-premises database platform supports cross-platform tablespace transport and to determine the endian format of the platform. The Oracle Database Cloud platform is little-endian format. For the steps this method entails, see RMAN CONVERT Transportable Tablespace with Data Pump. Migrating from Oracle Database 11g to Oracle Database 12c in the Cloud You can migrate Oracle Database 11g databases from on-premises to Oracle Database 12c databases in Oracle Database Cloud using several different methods. The applicability of some of the migration methods depends on the on-premises database s database version, database character set and platform endian format. If you have not already done so, determine the database version and database character set of your on-premises database, and determine the endian format of the platform your on-premises database resides on. Use this information to help you choose an appropriate method. Data Pump Conventional Export/Import This method can be used regardless of the endian format and database character set of the on-premises database. For the steps this method entails, see Data Pump Conventional Export/Import. Data Pump Transportable Tablespace Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-3

144 Migrating from Oracle Database 12c CDB to Oracle Database 12c in the Cloud This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. For the steps this method entails, see Data Pump Transportable Tablespace. RMAN Transportable Tablespace with Data Pump This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. For the steps this method entails, see RMAN Transportable Tablespace with Data Pump. RMAN CONVERT Transportable Tablespace with Data Pump This method can be used only if the on-premises database character set is AL32UTF8. This method is similar to the Data Pump Transportable Tablespace method, with the addition of the RMAN CONVERT command to enable transport between platforms with different endianness. Query V$TRANSPORTABLE_PLATFORM to determine if the on-premises database platform supports cross-platform tablespace transport and to determine the endian format of the platform. The Oracle Database Cloud platform is little-endian format. For the steps this method entails, see RMAN CONVERT Transportable Tablespace with Data Pump. Data Pump Full Transportable This method can be used only if the source database release version is or later and the database character set is AL32UTF8. For the steps this method entails, see Data Pump Full Transportable. Migrating from Oracle Database 12c CDB to Oracle Database 12c in the Cloud You can migrate Oracle Database 12c CDB databases from on-premises to Oracle Database 12c databases in Oracle Database Cloud using several different methods. The applicability of some of the migration methods depends on the on-premises database s database character set and platform endian format. If you have not already done so, determine the database character set of your onpremises database, and determine the endian format of the platform your on-premises database resides on. Use this information to help you choose an appropriate method. Data Pump Conventional Export/Import This method can be used regardless of the endian format and database character set of the on-premises database. For the steps this method entails, see Data Pump Conventional Export/Import. Data Pump Transportable Tablespace This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. For the steps this method entails, see Data Pump Transportable Tablespace. RMAN Transportable Tablespace with Data Pump 9-4 Using Oracle Database Cloud - Database as a Service

145 Migrating from Oracle Database 12c CDB to Oracle Database 12c in the Cloud This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. For the steps this method entails, see RMAN Transportable Tablespace with Data Pump. RMAN CONVERT Transportable Tablespace with Data Pump This method can be used only if the on-premises database character set is AL32UTF8. This method is similar to the Data Pump Transportable Tablespace method, with the addition of the RMAN CONVERT command to enable transport between platforms with different endianness. Query V$TRANSPORTABLE_PLATFORM to determine if the on-premises database platform supports cross-platform tablespace transport and to determine the endian format of the platform. The Oracle Database Cloud platform is little-endian format. For the steps this method entails, see RMAN CONVERT Transportable Tablespace with Data Pump. RMAN Cross-Platform Transportable Tablespace Backup Sets This method can be used only if the on-premises database character set is AL32UTF8. For the steps this method entails, see RMAN Cross-Platform Transportable Tablespace Backup Sets. Data Pump Full Transportable This method can be used only if the source database character set is AL32UTF8. For the steps this method entails, see Data Pump Full Transportable. Unplugging/Plugging (CDB) This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. For the steps this method entails, see Unplugging/Plugging a PDB. Remote Cloning (CDB) This method can be used only if the on-premises platform is little endian, the onpremises database release is or higher, and the database character set is AL32UTF8. For the steps this method entails, see Remote Cloning a PDB. RMAN Cross-Platform Transportable PDB This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. For the steps this method entails, see RMAN Cross-Platform Transportable PDB. SQL Developer and SQL*Loader to Migrate Selected Objects You can use SQL Developer to create a cart into which you add selected objects to be loaded into your Oracle Database 12c database on the cloud. In this method, you use SQL*Loader to load the data into your cloud database. For the steps this method entails, see SQL Developer and SQL*Loader to Migrate Selected Objects. Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-5

146 Migrating from Oracle Database 12c Non-CDB to Oracle Database 12c in the Cloud SQL Developer and INSERT Statements to Migrate Selected Objects You can use SQL Developer to create a cart into which you add selected objects to be loaded into your Oracle Database 12c database on the cloud. In this method, you use SQL INSERT statements to load the data into your cloud database. For the steps this method entails, see SQL Developer and INSERT Statements to Migrate Selected Objects. Migrating from Oracle Database 12c Non-CDB to Oracle Database 12c in the Cloud You can migrate Oracle Database 12c non-cdb databases from on-premises to Oracle Database 12c databases in Oracle Database Cloud using several different methods. The applicability of some of the migration methods depends on the on-premises database s database character set and platform endian format. If you have not already done so, determine the database character set of your onpremises database, and determine the endian format of the platform your on-premises database resides on. Use this information to help you choose an appropriate method. Data Pump Conventional Export/Import This method can be used regardless of the endian format and database character set of the on-premises database. For the steps this method entails, see Data Pump Conventional Export/Import. Data Pump Transportable Tablespace This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. For the steps this method entails, see Data Pump Transportable Tablespace. RMAN Transportable Tablespace with Data Pump This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. For the steps this method entails, see RMAN Transportable Tablespace with Data Pump. RMAN CONVERT Transportable Tablespace with Data Pump This method can be used only if the on-premises database character set is AL32UTF8. This method is similar to the Data Pump Transportable Tablespace method, with the addition of the RMAN CONVERT command to enable transport between platforms with different endianness. Query V$TRANSPORTABLE_PLATFORM to determine if the on-premises database platform supports cross-platform tablespace transport and to determine the endian format of the platform. The Oracle Database Cloud platform is little-endian format. For the steps this method entails, see RMAN CONVERT Transportable Tablespace with Data Pump. RMAN Cross-Platform Transportable Tablespace Backup Sets This method can be used only if the on-premises database character set is AL32UTF Using Oracle Database Cloud - Database as a Service

147 Migration Methods For the steps this method entails, see RMAN Cross-Platform Transportable Tablespace Backup Sets. Data Pump Full Transportable This method can be used only if the source database character set is AL32UTF8. For the steps this method entails, see Data Pump Full Transportable. Unplugging/Plugging (non-cdb) This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. You can use the unplug/plug method to migrate an Oracle Database 12c non-cdb database to Oracle Database 12c in the cloud. This method provides a way to consolidate several non-cdb databases into a single Oracle Database 12c CDB on the cloud. For the steps this method entails, see Unplugging/Plugging Non-CDB. Remote Cloning (non-cdb) This method can be used only if the on-premises platform is little endian, the onpremises database release is or higher, and the database character set is AL32UTF8. You can use the remote cloning method to copy an Oracle Database 12c non-cdb on-premises database to your Oracle Database 12c database in the cloud. For the steps this method entails, see Remote Cloning Non-CDB. SQL Developer and SQL*Loader to Migrate Selected Objects You can use SQL Developer to create a cart into which you add selected objects to be loaded into your Oracle Database 12c database on the cloud. In this method, you use SQL*Loader to load the data into your cloud database. For the steps this method entails, see SQL Developer and SQL*Loader to Migrate Selected Objects. SQL Developer and INSERT Statements to Migrate Selected Objects You can use SQL Developer to create a cart into which you add selected objects to be loaded into your Oracle Database 12c database on the cloud. In this method, you use SQL INSERT statements to load the data into your cloud database. For the steps this method entails, see SQL Developer and INSERT Statements to Migrate Selected Objects. Migration Methods Many methods exist to migrate Oracle Database databases to Oracle Database Cloud. Which of these many methods apply to a given migration scenario depends on several factors, including the version, character set, and platform endian format of the source and destination databases. Topics Data Pump Conventional Export/Import Data Pump Full Transportable Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-7

148 Migration Methods Data Pump Transportable Tablespace Remote Cloning a PDB Remote Cloning Non-CDB RMAN Cross-Platform Transportable PDB RMAN Cross-Platform Transportable Tablespace Backup Sets RMAN Transportable Tablespace with Data Pump RMAN CONVERT Transportable Tablespace with Data Pump SQL Developer and INSERT Statements to Migrate Selected Objects SQL Developer and SQL*Loader to Migrate Selected Objects Unplugging/Plugging a PDB Unplugging/Plugging Non-CDB Data Pump Conventional Export/Import You can use this method regardless of the endian format and database character set of the on-premises database. To migrate an on-premises source database, tablespace, schema, or table to the database on an Oracle Database Cloud - Database as a Service instance using Data Pump Export and Import, you perform these tasks: 1. On the on-premises database host, invoke Data Pump Export and export the onpremises database. 2. Use a secure copy utility to transfer the dump file to the Database as a Service compute node. 3. On the Database as a Service compute node, invoke Data Pump Import and import the data into the database. 4. After verifying that the data has been imported successfully, you can delete the dump file. For information about Data Pump Import and Export, see these topics: In Oracle Database Utilities for 12c Release 1: Data Pump Export Modes and Data Pump Import Modes In Oracle Database Utilities for 11g Release 2: Data Pump Export Modes and Data Pump Import Modes Data Pump Conventional Export/Import: Example This example provides a step-by-step demonstration of the tasks required to migrate a schema from an on-premises Oracle database to an Oracle Database Cloud - Database as a Service database. This example illustrates a schema mode export and import. The same general procedure applies for a full database, tablespace, or table export and import. In this example, the on-premises database is on a Linux host. 9-8 Using Oracle Database Cloud - Database as a Service

149 Migration Methods 1. On the on-premises database host, invoke Data Pump Export to export the schemas. a. On the on-premises database host, create an operating system directory to use for the on-premises database export files. $ mkdir /u01/app/oracle/admin/orcl/dpdump/for_cloud b. On the on-premises database host, invoke SQL*Plus and log in to the onpremises database as the SYSTEM user. $ sqlplus system Enter password: <enter the password for the SYSTEM user> c. Create a directory object in the on-premises database to reference the operating system directory. SQL> CREATE DIRECTORY dp_for_cloud AS '/u01/app/oracle/admin/orcl/dpdump/ for_cloud'; d. Exit from SQL*Plus. e. On the on-premises database host, invoke Data Pump Export as the SYSTEM user or another user with the DATAPUMP_EXP_FULL_DATABASE role and export the on-premises schemas. Provide the password for the user when prompted. $ expdp system SCHEMAS=fsowner DIRECTORY=dp_for_cloud 2. Use a secure copy utility to transfer the dump file to the Database as a Service compute node. In this example the dump file is copied to the /u01 directory. Choose the appropriate location based on the size of the file that will be transferred. a. On the Database as a Service compute node, create a directory for the dump file. $ mkdir /u01/app/oracle/admin/orcl/dpdump/from_onprem b. Before using the scp command to copy the export dump file, make sure the SSH private key that provides access to the Database as a Service compute node is available on your on-premises host. For more information about SSH keys, see About Network Access to a Database as a Service Instance. c. On the on-premises database host, use the SCP utility to transfer the dump file to the Database as a Service compute node. $ scp i private_key_file \ /u01/app/oracle/admin/orcl/dpdump/for_cloud/expdat.dmp \ oracle@ip_address_dbaas_vm:/u01/app/oracle/admin/orcl/dpdump/from_onprem 3. On the Database as a Service compute node, invoke Data Pump Import and import the data into the database. a. On the Database as a Service compute node, invoke SQL*Plus and log in to the database as the SYSTEM user. $ sqlplus system Enter password: <enter the password for the SYSTEM user> b. Create a directory object in the Database as a Service database. Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-9

150 Migration Methods SQL> CREATE DIRECTORY dp_from_onprem AS '/u01/app/oracle/admin/orcl/dpdump/ from_onprem'; c. If they do not exist, create the tablespace(s) for the objects that will be imported. d. Exit from SQL*Plus. e. On the Database as a Service compute node, invoke Data Pump Import and connect to the database. Import the data into the database. $ impdp system SCHEMAS=fsowner DIRECTORY=dp_from_onprem 4. After verifying that the data has been imported successfully, you can delete the expdat.dmp file. Data Pump Full Transportable You can use this method only if the source database release version is or later and the database character set is AL32UTF8. You can use the Data Pump full transportable method to copy an entire database from your on-premises host to the database on an Oracle Database Cloud - Database as a Service instance. To migrate an Oracle Database 11g on-premises database to the Oracle Database 12c database on a Database as a Service instance using the Data Pump full transportable method, you perform these tasks: 1. On the on-premises database host, prepare the database for the Data Pump full transportable export by placing the user-defined tablespaces in READ ONLY mode. 2. On the on-premises database host, invoke Data Pump Export to perform the full transportable export. 3. Use a secure copy utility to transfer the Data Pump Export dump file and the datafiles for all of the user-defined tablespaces to the Database as a Service compute node. 4. Set the on-premises tablespaces back to READ WRITE. 5. On the Database as a Service compute node, prepare the database for the tablespace import. 6. On the Database as a Service compute node, invoke Data Pump Import and connect to the database. 7. After verifying that the data has been imported successfully, you can delete the dump file. Data Pump Transportable Tablespace You can use this method only if the on-premises platform is little endian and the database character set is AL32UTF8. The Transportable Tablespace method is generally much faster than a conventional export/import of the same data because the data files containing all of the actual data are simply copied to the destination location. You use Data Pump to transfer only the metadata of the tablespace objects to the new database Using Oracle Database Cloud - Database as a Service

151 Migration Methods To migrate an on-premises source database to the database on an Oracle Database Cloud - Database as a Service instance using the Data Pump Transportable Tablespace method, you perform these tasks: 1. On the on-premises database host, prepare the database for the Data Pump transportable tablespace export. 2. On the on-premises database host, invoke Data Pump Export to perform the transportable tablespace export. 3. Use a secure copy utility to transfer the Data Pump Export dump file and the tablespace datafiles to the Database as a Service compute node. 4. Set the on-premises tablespaces back to READ WRITE. 5. On the Database as a Service compute node, prepare the database for the tablespace import. 6. On the Database as a Service compute node, invoke Data Pump Import and connect to the database. 7. Set the tablespaces on the Database as a Service database to READ WRITE mode. 8. After verifying that the data has been imported successfully, you can delete the dump file. Data Pump Transportable Tablespace: Example This example provides a step-by-step demonstration of the tasks required to migrate tablespaces in an on-premises Oracle database to an Oracle Database Cloud - Database as a Service database. This example performs a migration of the FSDATA and FSINDEX tablespaces. In this example, the on-premises database is on a Linux host. 1. On the on-premises database host, prepare the database for the Data Pump transportable tablespace export. a. On the on-premises database host, create a directory in the operating system to use for the on-premises export. $ mkdir /u01/app/oracle/admin/orcl/dpdump/for_cloud b. On the on-premises database host, invoke SQL*Plus and log in to the onpremises database as the SYSTEM user. $ sqlplus system Enter password: <enter the password for the SYSTEM user> c. Create a directory object in the on-premises database to reference the operating system directory. SQL> CREATE DIRECTORY dp_for_cloud AS '/u01/app/oracle/admin/orcl/dpdump/ for_cloud'; d. Determine the name(s) of the datafiles that belong to the FSDATA and FSINDEX tablespaces by querying DBA_DATA_FILES. These files will also be listed in the export output. SQL> SELECT file_name FROM dba_data_files 2 WHERE tablespace_name = 'FSDATA'; Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-11

152 Migration Methods FILE_NAME /u01/app/oracle/oradata/orcl/fsdata01.dbf SQL> SELECT file_name FROM dba_data_files 2 WHERE tablespace_name = 'FSINDEX'; FILE_NAME /u01/app/oracle/oradata/orcl/fsindex01.dbf e. On the on-premises database host, set all tablespaces that will be transported (the transportable set) to READ ONLY mode. SQL> ALTER TABLESPACE fsindex READ ONLY; Tablespace altered. SQL> ALTER TABLESPACE fsdata READ ONLY; Tablespace altered. f. Exit from SQL*Plus. 2. On the on-premises database host, invoke Data Pump Export to perform the transportable tablespace export. On the on-premises database host, invoke Data Pump Export and connect to the on-premises database. Export the on-premises tablespaces using the TRANSPORT_TABLESPACES option. Provide the password for the SYSTEM user when prompted. $ expdp system TRANSPORT_TABLESPACES=fsdata,fsindex TRANSPORT_FULL_CHECK=YES DIRECTORY=dp_for_cloud 3. Use a secure copy utility to transfer the Data Pump Export dump file and the tablespace datafiles to the Database as a Service compute node. In this example the dump file is copied to the /u01 directory. Choose the appropriate location based on the size of the file that will be transferred. a. On the Database as a Service compute node, create a directory for the dump file. $ mkdir /u01/app/oracle/admin/orcl/dpdump/from_onprem b. Before using the scp utility to copy files, make sure the SSH private key that provides access to the Database as a Service compute node is available on your on-premises host. For more information about SSH keys, see About Network Access to a Database as a Service Instance. c. On the on-premises database host, use the scp utility to transfer the dump file and all datafiles of the transportable set to the Database as a Service compute node. $ scp -i private_key_file \ /u01/app/oracle/admin/orcl/dpdump/for_cloud/expdat.dmp \ oracle@ip_address_dbaas_vm:/u01/app/oracle/admin/orcl/dpdump/from_onprem $ scp -i private_key_file \ /u01/app/oracle/oradata/orcl/fsdata01.dbf \ oracle@ip_address_dbaas_vm:/u02/app/oracle/oradata/orcl $ scp -i private_key_file \ 9-12 Using Oracle Database Cloud - Database as a Service

153 Migration Methods /u01/app/oracle/oradata/orcl/fsindex01.dbf \ oracle@ip_address_dbaas_vm:/u02/app/oracle/oradata/orcl 4. Set the on-premises tablespaces back to READ WRITE. a. Invoke SQL*Plus and log in as the SYSTEM user. b. Set the FSDATA and FSINDEX tablespaces back to READ WRITE mode. SQL> ALTER TABLESPACE fsdata READ WRITE; Tablespace altered. SQL> ALTER TABLESPACE fsindex READ WRITE; Tablespace altered. c. Exit from SQL*Plus. 5. On the Database as a Service compute node, prepare the database for the tablespace import. a. On the Database as a Service compute node, invoke SQL*Plus and log in to the database as the SYSTEM user. b. Create a directory object in the Database as a Service database. SQL> CREATE DIRECTORY dp_from_onprem AS '/u01/app/oracle/admin/orcl/dpdump/ from_onprem'; c. If the owners of the objects that will be imported do not exist in the database, create them before performing the import. The transportable tablespace mode of import does not create the users. SQL> CREATE USER fsowner 2 PROFILE default 3 IDENTIFIED BY fspass 4 TEMPORARY TABLESPACE temp 5 ACCOUNT UNLOCK; 6. On the Database as a Service compute node, invoke Data Pump Import and connect to the database. Import the data into the database using the TRANSPORT_DATAFILES option. $ impdp system DIRECTORY=dp_from_onprem \ TRANSPORT_DATAFILES='/u02/app/oracle/oradata/ORCL/fsdata01.dbf', \ '/u02/app/oracle/oradata/orcl/fsindex01.dbf' 7. Set the tablespaces on the Database as a Service database to READ WRITE mode. a. Invoke SQL*Plus and log in as the SYSTEM user. b. Set the FSDATA and FSINDEX tablespaces to READ WRITE mode. SQL> ALTER TABLESPACE fsdata READ WRITE; Tablespace altered. SQL> ALTER TABLESPACE fsindex READ WRITE; Tablespace altered. c. Exit from SQL*Plus. 8. After verifying that the data has been imported successfully, you can delete the expdat.dmp dump file. Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-13

154 Migration Methods Remote Cloning a PDB Remote Cloning Non-CDB You can use this method only if the on-premises platform is little endian, the onpremises database release is or higher, and the database character set is AL32UTF8. You can use the remote cloning method to copy a PDB from your on-premises Oracle Database 12c database to a PDB in an Oracle Database 12c database on an Oracle Database Cloud - Database as a Service instance. To migrate an Oracle Database 12c PDB to a PDB in the Oracle Database 12c database on a Database as a Service instance using the remote cloning method, you perform these tasks: 1. On the on-premises database host, invoke SQL*Plus and close the on-premises PDB and then reopen it in READ ONLY mode. 2. On the Database as a Service compute node, invoke SQL*Plus and create a database link that enables a connection to the on-premises database. 3. On the Database as a Service compute node, execute the CREATE PLUGGABLE DATABASE command to clone the on-premises PDB. 4. On the Database as a Service compute node, open the new PDB by executing the ALTER PLUGGABLE DATABASE OPEN command. 5. Optionally, on the on-premises database host invoke SQL*Plus and set the onpremises PDB back to READ WRITE mode. For more information, see Cloning a Remote PDB or Non-CDB in Oracle Database Administrator's Guide. You can use this method only if the on-premises platform is little endian, the onpremises database release is or higher, and the database character set is AL32UTF8. You can use the remote cloning method to copy an Oracle Database 12c non-cdb onpremises database to a PDB in an Oracle Database 12c database on an Oracle Database Cloud - Database as a Service instance. To migrate an Oracle Database 12c non-cdb database to the Oracle Database 12c database on a Database as a Service instance using the remote cloning method, you perform these tasks: 1. On the on-premises database host, invoke SQL*Plus and set the on-premises database to READ ONLY mode. 2. On the Database as a Service compute node, invoke SQL*Plus and create a database link that enables a connection to the on-premises database. 3. On the Database as a Service compute node, execute the CREATE PLUGGABLE DATABASE command to clone the on-premises non-cdb database. 4. On the Database as a Service compute node, execute the $ORACLE_HOME/rdbms/ admin/noncdb_to_pdb.sql script Using Oracle Database Cloud - Database as a Service

155 Migration Methods 5. On the Database as a Service compute node, open the new PDB by executing the ALTER PLUGGABLE DATABASE OPEN command. 6. Optionally, on the on-premises database host invoke SQL*Plus and set the onpremises database back to READ WRITE mode. For more information, see Cloning a Remote PDB or Non-CDB in Oracle Database Administrator's Guide. RMAN Cross-Platform Transportable PDB This method can be used only if the on-premises platform is little endian and the database character set is AL32UTF8. To migrate an Oracle Database 12c PDB to a PDB in an Oracle Database 12c database on an Oracle Database Cloud - Database as a Service instance using the RMAN crossplatform transportable PDB method, you perform these tasks: 1. On the on-premises database host, invoke SQL*Plus and close the on-premises PDB. 2. On the on-premises database host, execute the ALTER PLUGGABLE DATABASE UNPLUG command to generate an XML file containing the list of datafiles that will be plugged in on the cloud database. 3. On the on-premises database host, invoke RMAN and connect to the root. Execute the BACKUP FOR TRANSPORT PLUGGABLE DATABASE command. 4. Use a secure copy utility to transfer the XML file and the backup set to the Database as a Service compute node. 5. On the Database as a Service compute node, invoke RMAN and connect to the root. Execute the RESTORE ALL FOREIGN DATAFILES command. 6. the Database as a Service compute node, invoke SQL*Plus and connect to the root. Execute the CREATE PLUGGABLE DATABASE command. 7. the Database as a Service compute node, execute the ALTER PLUGGABLE DATABASE OPEN command. For more information, see Performing Cross-Platform Transport of PDBs in Oracle Database Backup and Recovery User's Guide. RMAN Cross-Platform Transportable Tablespace Backup Sets You can use this method only if the on-premises database character set is AL32UTF8. Note: See Oracle Database Backup and Recovery User's Guide for detailed information on a similar method that enables you to perform a cross-platform transport of an entire database. When you transport an entire database to a different platform, the source platform and the destination platform must use the same endian format. To migrate Oracle Database 12c non-cdb on-premises tablespaces to an Oracle Database 12c database on an Oracle Database Cloud - Database as a Service instance Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-15

156 Migration Methods using the RMAN cross-platform transportable backup sets method, you perform these tasks: 1. On the on-premises database host, prepare the database by placing the userdefined tablespaces that you intend to transport in READ ONLY mode. 2. On the on-premises database host, invoke RMAN and use the BACKUP command with the TO PLATFORM or FOR TRANSPORT clause and the DATAPUMP clause to create a backup set for cross-platform transport. See in BACKUP in Oracle Database Backup and Recovery Reference for more information on the BACKUP command. 3. Use a secure copy utility to transfer the backup sets, including the Data Pump export dump file, to the Database as a Service compute node. 4. Set the on-premises tablespaces back to READ WRITE. 5. On the Database as a Service compute node, prepare the database by creating the required schemas. 6. On the Database as a Service compute node, invoke RMAN and use the RESTORE command with the foreignfilespec subclause to restore the cross-platform backup. 7. On the Database as a Service compute node, set the tablespaces on the database to READ WRITE mode. For more information, see Overview of Cross-Platform Data Transport Using Backup Sets in Oracle Database Backup and Recovery User s Guide. RMAN Transportable Tablespace with Data Pump You can use this method only if the on-premises platform is little endian and the database character set is AL32UTF8. You can use this method to eliminate placing the tablespaces in READ ONLY mode, as required by the Data Pump Transportable Tablespace method. To migrate an on-premises source database to the database on an Oracle Database Cloud - Database as a Service instance using the RMAN Transportable Tablespace with Data Pump method, you perform these tasks: 1. On the on-premises database host, invoke RMAN and create the transportable tablespace set. 2. Use a secure copy utility to transfer the Data Pump Export dump file and the tablespace datafiles to the Database as a Service compute node. 3. On the Database as a Service compute node, prepare the database for the tablespace import. 4. On the Database as a Service compute node, invoke Data Pump Import and connect to the database. Import the data into the database using the TRANSPORT_DATAFILES option. 5. After verifying that the data has been imported successfully, you can delete the dump file Using Oracle Database Cloud - Database as a Service

157 Migration Methods RMAN Transportable Tablespace with Data Pump: Example This example provides a step-by-step demonstration of the tasks required to migrate tablespaces in an on-premises Oracle database to an Oracle Database Cloud - Database as a Service database. This example performs a migration of the FSDATA and FSINDEX tablespaces. In this example, the on-premises database is on a Linux host. 1. On the on-premises database host, invoke RMAN and create the transportable tablespace set. a. On the on-premises database host, create an operating system directory for the datafiles. $ mkdir /u01/app/oracle/admin/orcl/rman_transdest b. On the on-premises data host, create an operating system directory for the RMAN auxiliary instance files. $ mkdir /u01/app/oracle/admin/orcl/rman_auxdest c. Invoke RMAN and log in as the SYSTEM user. Enter the password for the SYSTEM user when prompted. $ rman target system d. Execute the TRANSPORT TABLESPACE command. RMAN> TRANSPORT TABLESPACE fsdata, fsindex 2> TABLESPACE DESTINATION '/u01/app/oracle/admin/orcl/rman_transdest' 3> AUXILIARY DESTINATION '/u01/app/oracle/admin/orcl/rman_auxdest'; e. Log out of RMAN. f. Optionally, navigate to the directory you specified for the TABLESPACE DESTINATION and view the files that were created by the TRANSPORT TABLESPACE operation. $ cd /u01/app/oracle/admin/orcl/rman_transdest $ ls dmpfile.dmp fsdata01.dbf fsindex01.dbf impscrpt.sql 2. Use a secure copy utility to transfer the Data Pump Export dump file and the tablespace datafiles to the Database as a Service compute node. In this example the dump file is copied to the /u01 directory. Choose the appropriate location based on the size of the file that will be transferred. a. On the Database as a Service compute node, create a directory for the dump file. $ mkdir /u01/app/oracle/admin/orcl/dpdump/from_onprem b. Before using the scp command to copy files, make sure the SSH private key that provides access to the Database as a Service compute node is available on your on-premises host. For more information about SSH keys, see About Network Access to a Database as a Service Instance. Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-17

158 Migration Methods c. On the on-premises database host, use the SCP utility to transfer the dump file and all datafiles of the transportable set to the Database as a Service compute node. $ scp -i private_key_file \ /u01/app/oracle/admin/orcl/rman_transdest/dmpfile.dmp \ oracle@ip_address_dbaas_vm:/u01/app/oracle/admin/orcl/dpdump/from_onprem $ scp -i private_key_file \ /u01/app/oracle/admin/orcl/rman_transdest/fsdata01.dbf \ oracle@ip_address_dbaas_vm:/u02/app/oracle/oradata/orcl $ scp -i private_key_file \ /u01/app/oracle/admin/orcl/rman_transdest/fsindex01.dbf \ oracle@ip_address_dbaas_vm:/u02/app/oracle/oradata/orcl 3. On the Database as a Service compute node, prepare the database for the tablespace import. a. On the Database as a Service compute node, invoke SQL*Plus and log in to the database as the SYSTEM user. b. Create a directory object in the Database as a Service database. SQL> CREATE DIRECTORY dp_from_onprem AS '/u01/app/oracle/admin/orcl/dpdump/ from_onprem'; c. If the owners of the objects that will be imported do not exist in the database, create them before performing the import. The transportable tablespace mode of import does not create the users. SQL> CREATE USER fsowner 2 PROFILE default 3 IDENTIFIED BY fspass 4 TEMPORARY TABLESPACE temp 5 ACCOUNT UNLOCK; 4. On the Database as a Service compute node, invoke Data Pump Import and connect to the database. Import the data into the database using the TRANSPORT_DATAFILES option. $ impdp system DIRECTORY=dp_from_onprem DUMPFILE='dmpfile.dmp' \ TRANSPORT_DATAFILES='/u02/app/oracle/oradata/ORCL/fsdata01.dbf', \ '/u02/app/oracle/oradata/orcl/fsindex01.dbf' 5. After verifying that the data has been imported successfully, you can delete the dmpfile.dmp dump file. RMAN CONVERT Transportable Tablespace with Data Pump You can use this method only if the on-premises database character set is AL32UTF8. This method is similar to the Data Pump Transportable Tablespace method, with the addition of the RMAN CONVERT command to enable transport between platforms with different endianness. Query V$TRANSPORTABLE_PLATFORM to determine if the on-premises database platform supports cross-platform tablespace transport and to determine the endian format of the platform. The Oracle Database Cloud - Database as a Service platform is little-endian format. To migrate tablespaces from your on-premises Oracle database to the database on a Database as a Service instance using RMAN, you perform these tasks: 9-18 Using Oracle Database Cloud - Database as a Service

159 Migration Methods 1. On the on-premises database host, prepare the database for the Data Pump transportable tablespace export. 2. On the on-premises database host, invoke Data Pump Export to perform the transportable tablespace export. 3. On the on-premises database host, invoke RMAN and use the CONVERT TABLESPACE command to convert the tablespace datafile to the Oracle Database Cloud platform format. Refer to the Oracle Database Backup and Recovery Reference for more information on the CONVERT command. 4. Use a secure copy utility to transfer the Data Pump Export dump file and the converted tablespace datafiles to the Database as a Service compute node. 5. Set the on-premises tablespaces back to READ WRITE. 6. On the Database as a Service compute node, prepare the database for the tablespace import. 7. On the Database as a Service compute node, invoke Data Pump Import and connect to the database. 8. On the Database as a Service compute node, set the tablespaces in the database to READ WRITE mode. 9. After verifying that the data has been imported successfully, you can delete the dump file. RMAN CONVERT Transportable Tablespace with Data Pump: Example This example provides a step-by-step demonstration of the tasks required to migrate tablespaces in an on-premises Oracle database to an Oracle Database Cloud - Database as a Service database. In this example, the on-premises database is on a Linux host. 1. On the on-premises database host, prepare the database for the Data Pump transportable tablespace export. a. On the on-premises database host, create a directory in the operating system to use for the on-premises export. $ mkdir /u01/app/oracle/admin/orcl/dpdump/for_cloud b. On the on-premises database host, invoke SQL*Plus and log in to the onpremises database as the SYSTEM user. $ sqlplus system Enter password: <enter the password for the SYSTEM user> c. Create a directory object in the on-premises database to reference the operating system directory. SQL> CREATE DIRECTORY dp_for_cloud AS '/u01/app/oracle/admin/orcl/dpdump/ for_cloud'; d. On the on-premises database host, set all tablespaces that will be transported (the transportable set) to READ ONLY mode. SQL> ALTER TABLESPACE fsindex READ ONLY; Tablespace altered. Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-19

160 Migration Methods SQL> ALTER TABLESPACE fsdata READ ONLY; Tablespace altered. e. Exit from SQL*Plus. 2. On the on-premises database host, invoke Data Pump Export to perform the transportable tablespace export. On the on-premises database host, invoke Data Pump Export and connect to the on-premises database. Export the on-premises tablespaces using the TRANSPORT_TABLESPACES option. Provide the password for the SYSTEM user when prompted. $ expdp system TRANSPORT_TABLESPACES=fsdata,fsindex TRANSPORT_FULL_CHECK=YES DIRECTORY=dp_for_cloud 3. On the on-premises database host, invoke RMAN and use the CONVERT TABLESPACE command to convert the tablespace datafile to the Oracle Database Cloud platform format. a. Invoke RMAN. $ rman target / b. Execute the RMAN CONVERT TABLESPACE command to convert the datafiles and store the converted files in a temporary location on the onpremises database host. RMAN> CONVERT TABLESPACE fsdata, fsindex 2> TO PLATFORM 'Linux x86 64-bit' 3> FORMAT '/tmp/%u '; input datafile file number=00006 name=/u01/app/oracle/oradata/orcl/ fsdata01.dbf converted datafile=/tmp/data_d-orcl_i _ts-fsdata_fno-6_0aqc9un3 input datafile file number=00007 name=/u01/app/oracle/oradata/orcl/ fsindex01.dbf converted datafile=/tmp/data_d-orcl_i _ts-fsindex_fno-7_0bqc9un6 c. Take note of the names of the converted files. You will copy these files to the Database as a Service compute node in the next step. d. Exit RMAN. 4. Use a secure copy utility to transfer the Data Pump Export dump file and the converted tablespace datafiles to the Database as a Service compute node. In this example the dump file is copied to the /u01 directory. Choose the appropriate location based on the size of the file that will be transferred. a. On the Database as a Service compute node, create a directory for the dump file. $ mkdir /u01/app/oracle/admin/orcl/dpdump/from_onprem b. Before using the scp command to copy files, make sure the SSH private key that provides access to the Database as a Service compute node is available on your on-premises host. For more information about SSH keys, see About Network Access to a Database as a Service Instance Using Oracle Database Cloud - Database as a Service

161 Migration Methods c. On the on-premises database host, use the scp utility to transfer the dump file and all datafiles of the transportable set to the Database as a Service compute node. $ scp -i private_key_file \ /u01/app/oracle/admin/orcl/dpdump/for_cloud/expdat.dmp \ oracle@ip_address_dbaas_vm:/u01/app/oracle/admin/orcl/dpdump/from_onprem $ scp -i private_key_file \ /tmp/data_d-orcl_i _ts-fsdata_fno-6_0aqc9un3 \ oracle@ip_address_dbaas_vm:/u02/app/oracle/oradata/orcl/fsdata01.dbf $ scp -i private_key_file \ /tmp/data_d-orcl_i _ts-fsindex_fno-7_0bqc9un6 \ oracle@ip_address_dbaas_vm:/u02/app/oracle/oradata/orcl/fsindex01.dbf 5. Set the on-premises tablespaces back to READ WRITE. a. Invoke SQL*Plus and log in as the SYSTEM user. b. Set the FSDATA and FSINDEX tablespaces back to READ WRITE mode. SQL> ALTER TABLESPACE fsdata READ WRITE; Tablespace altered. SQL> ALTER TABLESPACE fsindex READ WRITE; Tablespace altered. c. Exit from SQL*Plus. 6. On the Database as a Service compute node, prepare the database for the tablespace import. a. On the Database as a Service compute node, invoke SQL*Plus and log in to the database as the SYSTEM user. b. Create a directory object in the Database as a Service database. SQL> CREATE DIRECTORY dp_from_onprem AS '/u01/app/oracle/admin/orcl/dpdump/ from_onprem'; c. If the owners of the objects that will be imported do not exist in the database, create them before performing the import. The transportable tablespace mode of import does not create the users. SQL> CREATE USER fsowner 2 PROFILE default 3 IDENTIFIED BY fspass 4 TEMPORARY TABLESPACE temp 5 ACCOUNT UNLOCK; 7. On the Database as a Service compute node, invoke Data Pump Import and connect to the database. Import the data into the DBaaS database using the TRANSPORT_DATAFILES option $ impdp system DIRECTORY=dp_from_onprem \ TRANSPORT_DATAFILES='/u02/app/oracle/oradata/ORCL/fsdata01.dbf', \ '/u02/app/oracle/oradata/orcl/fsindex01.dbf' 8. On the Database as a Service compute node, set the tablespaces in the database to READ WRITE mode. Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-21

162 Migration Methods a. Invoke SQL*Plus and log in as the SYSTEM user. b. Set the FSDATA and FSINDEX tablespaces to READ WRITE mode. SQL> ALTER TABLESPACE fsdata READ WRITE; Tablespace altered. SQL> ALTER TABLESPACE fsindex READ WRITE; Tablespace altered. c. Exit from SQL*Plus. 9. After verifying that the data has been imported successfully, you can delete the expdat.dmp dump file. SQL Developer and INSERT Statements to Migrate Selected Objects You can use SQL Developer to create a cart into which you add selected objects to be loaded into an Oracle Database 12c database on an Oracle Database Cloud - Database as a Service instance. In this method, you use SQL INSERT statements to load the data into your cloud database. To migrate selected objects to an Oracle Database 12c database on a Database as a Service instance using SQL Developer and INSERT statements, you perform these tasks: 1. Launch SQL Developer, connect to your on-premises database and create a cart containing the objects you want to migrate. 2. In SQL Developer, click the Export Cart icon and select Insert in the Format menu. 3. In SQL Developer, open a connection to the Oracle Database 12c database on Database as a Service and execute the generated script to create the database objects. 4. In SQL Developer, open a connection to the Oracle Database 12c database on Database as a Service and run the generated script to create the objects and load the data. SQL Developer and SQL*Loader to Migrate Selected Objects You can use SQL Developer to create a cart into which you add selected objects to be loaded into an Oracle Database 12c database on an Oracle Database Cloud - Database as a Service instance. In this method, you use SQL*Loader to load the data into your cloud database. To migrate selected objects to an Oracle Database 12c database on a Database as a Service instance using SQL Developer and SQL*Loader, you perform these tasks: 1. Launch SQL Developer, connect to your on-premises database and create a cart containing the objects you want to load into your cloud database. 2. In SQL Developer, click the Export Cart icon and select loader in the Format menu Using Oracle Database Cloud - Database as a Service

163 Migration Methods Unplugging/Plugging a PDB 3. In SQL Developer, open a connection to the Oracle Database 12c database on Database as a Service and execute the generated script to create the database objects. 4. Use a secure copy utility to transfer the SQL*Loader control files and the SQL*Loader data files to the Database as a Service compute node. 5. On the Database as a Service compute node, invoke SQL*Loader to load the data using the SQL*Loader control files and data files for each object. You can use this method only if the on-premises platform is little endian and the database character set is AL32UTF8. You can use the unplug/plug method to migrate an Oracle Database 12c PDB to a PDB in an Oracle Database 12c database on an Oracle Database Cloud - Database as a Service instance. To migrate an Oracle Database 12c PDB to a PDB in the Oracle Database 12c database on a Database as a Service instance using the plug/unplug method, you perform these tasks: 1. On the on-premises database host, invoke SQL*Plus and close the on-premises PDB. 2. On the on-premises database host, ALTER PLUGGABLE DATABASE UNPLUG command to generate an XML file containing the list of datafiles that will be plugged in to the database on Database as a Service. 3. Use a secure copy utility to transfer the XML file and the datafiles to the Database as a Service compute node. 4. On the Database as a Service compute node, invoke SQL*Plus and execute the CREATE PLUGGABLE DATABASE command to plug the database into the CDB. 5. On the Database as a Service compute node, open the new PDB by executing the ALTER PLUGGABLE DATABASE OPEN command. For more information, see Creating a PDB by Plugging an Unplugged PDB into a CDB in Oracle Database Administrator's Guide. Unplugging/Plugging Non-CDB You can use this method only if the on-premises platform is little endian and the database character set is AL32UTF8. You can use the unplug/plug method to migrate an Oracle Database 12c non-cdb database to a PDB in an Oracle Database 12c database on an Oracle Database Cloud - Database as a Service instance. This method provides a way to consolidate several non-cdb databases into a single Oracle Database 12c multitenant database on Database as a Service. To migrate an Oracle Database 12c non-cdb database the Oracle Database 12c database on a Database as a Service instance using the plug/unplug method, you perform these tasks: 1. On the on-premises database host, invoke SQL*Plus and set the on-premises database to READ ONLY mode. Migrating an On-Premises Oracle Database to Oracle Database Cloud 9-23

164 Migration Methods 2. On the on-premises database host, execute the DBMS_PDB.DESCRIBE procedure to generate an XML file containing the list of datafiles that will be plugged in on the cloud database. 3. Use a secure copy utility to transfer the XML file and the datafiles to the Database as a Service compute node. 4. On the Database as a Service compute node, invoke SQL*Plus and execute the CREATE PLUGGABLE DATABASE command to plug the database into the CDB. 5. On the Database as a Service compute node, execute the $ORACLE_HOME/rdbms/ admin/noncdb_to_pdb.sql script to delete unnecessary metadata from the SYSTEM tablespace of the new PDB. 6. On the Database as a Service compute node, open the new PDB by executing the ALTER PLUGGABLE DATABASE OPEN command. 7. Optionally, on the on-premises database host invoke SQL*Plus and set the onpremises database back to READ WRITE mode. For more information, see Creating a PDB Using a Non-CDB in Oracle Database Administrator's Guide Using Oracle Database Cloud - Database as a Service

165 10 Using Oracle DBaaS Monitor Oracle DBaaS Monitor provides monitoring and management of the Oracle Database RDBMS and listener on an Oracle Database Cloud - Database as a Service instance. Note: This section does not apply to service instances that use Oracle Real Application Clusters. Such instances do not currently include Oracle DBaaS Monitor. Topics About Oracle DBaaS Monitor Accessing Oracle DBaaS Monitor Filtering the Display on DBaaS Monitor Pages Starting and Stopping the Database Instance Viewing and Modifying Initialization Parameters Viewing Alert Log Entries and Checking for Errors Viewing Tablespace and Segment Space Usage Administering the Listener About Oracle DBaaS Monitor Oracle DBaaS Monitor provides monitoring and management of the Oracle Database RDBMS and listener on an Oracle Database Cloud - Database as a Service instance. DBaaS Monitor provides quick and easy access to a variety of information about the database instance running on a service instance: Overall, how much storage is allocated to tablespaces, and how much of that storage is used For each tablespace, how much storage is allocated and how much of that storage is used, with additional drill-down capabilities to view segments A real-time graph showing wait events across several selectable categories The alert log, with log searching capabilities A list of open user sessions, with drill-down capabilities to view session details such as the last SQL statement, explain plan, waits, contention, and so on Using Oracle DBaaS Monitor 10-1

166 Accessing Oracle DBaaS Monitor A list of initialization parameters, with the ability to change parameter values, both in memory and in the SPFILE. Indication of whether certain database options are enabled Monitoring of current and past SQL Developer PDB uploads You can use DBaaS Monitor to view information about the service instance virtual machine: CPU utilization information in an interactive table format, with automatic refresh intervals OS process information, with filtering and automatic refresh capabilities DBaaS Monitor also provides the following management capabilities: Start up and shut down the database instance Start and stop the listener Access the GlassFish Administration Console Accessing Oracle DBaaS Monitor Oracle Database Cloud - Database as a Service instances include Oracle DBaaS Monitor, an on-instance monitor that provides a wide spectrum of information about Oracle Database status and resource usage. How you access Oracle DBaaS Monitor depends on whether the HTTPS port (443) has been unblocked. When a Database as a Service instance is first created, the HTTPS port is blocked to ensure network security. For information about unblocking a port, see Enabling Access to a Compute Node Port. Accessing Oracle DBaaS Monitor When the HTTPS Port Is Unblocked To access Oracle DBaaS Monitor when the HTTPS port is unblocked: 1. Open the Oracle Database Cloud Service console. For detailed instructions, see Accessing the Oracle Database Cloud Service Console. 2. From the menu for the instance, select Open DBaaS Monitor Console. A window prompting you for your user name and password is displayed. 3. Enter dbaas_monitor as the user name and the password specified when the instance was created as the password, and then click OK. Accessing the On-Instance Monitor When the HTTPS Port Is Blocked To access Oracle DBaaS Monitor when the HTTPS port on the instance is blocked, you must create an SSH tunnel to port 443 on the compute node hosting the DBaaS Monitor. For information about creating an SSH tunnel, see Creating an SSH Tunnel to a Compute Node Port. After creating an SSH tunnel to port 443, you can access the on-instance monitor by directing your browser to the URL Using Oracle Database Cloud - Database as a Service

167 Filtering the Display on DBaaS Monitor Pages When prompted for a user name and password, enter dbaas_monitor as the user name and the password specified when the instance was created as the password, and then click OK. Filtering the Display on DBaaS Monitor Pages On DBaaS Monitor pages that show tabular lists, you can filter what items the table displays. 1. Expand the first drop-down menu and select the column you want to use as the filter. 2. In the second drop-down menu, select the operator. 3. In the box, enter the value and click the search icon. Starting and Stopping the Database Instance You can use DBaaS Monitor to start up and shut down your database instance. Topics Starting the Database Instance Using Oracle DBaaS Monitor 10-3