Skip to content

Lab3.md

Latest commit

 

History

History
52 lines (30 loc) · 2.09 KB

Lab3.md

File metadata and controls

52 lines (30 loc) · 2.09 KB
![](images/obe_tag.png)

November 08, 2018

 # Lab 3: Scaling an ATP instance

Introduction

Autonomous Transaction Processing provides all of the performance of the market-leading Oracle Database in an environment that is tuned and optimized for transaction processing workloads. Oracle Autonomous Transaction Processing (or ATP) service provisions in a few minutes and requires very little manual ongoing administration.

Scaling in the context of an ATP database means increasing or decreasing the amount of CPU or storage resources allocated to the service. Scaling an ATP instance is easy, flexible and can be done without any downtime so your application can continue to run unaffected while the scaling operation is in progress.

To log issues, click here to go to the github oracle repository issue submission form.

Objectives

  • Learn how to scale an ATP instance

Required Artifacts

  • Please ensure you are connected to your cloud account and have provisioned an ATP instance. ReferLabGuide1.md

Steps

STEP 1: Log into your cloud account and navigate to ATP console

  • Log into your cloud account and navigate to ATP console

  • On the instance details page, select Scale Up/Down button at the top

  • Enter the CPU or storage you need to change to.

NOTE: The service does not limit you to any rigid shapes ( 2,4, 8, 16 etc). You can choose any size from 1 – 128 for both CPU and storage in TB.

  • The service details page would indicate that the scaling operation is in progress. Once it completes, the status changes to ‘Available’.

NOTE: Regardless to the change in CPU or storage, your database is always available to your application and your workload can run uninterrupted during the scaling process.

  • You are now ready to move to the next lab.
[![](images/obe_tag.png)](#) ## Great Work - All Done!