ADW / ATP How to clone a Autonomous Database instance from UI console.
(Doc ID 2523837.1)
Last updated on JUNE 13, 2024
Applies to:
Autonomous Database on Shared Infrastructure - Version N/A to N/AAutonomous Transaction Processing - Version NA to NA [Release NA]
Information in this document applies to any platform.
Goal
The purpose is to demonstrate how to Clone a Autonomous Database instance (ADW or ATP) using UI Console
Available options:
-Full clone
The full clone option creates a new database that includes all of the source database's metadata and data.
- Metadata clone
The metadata clone option creates a new database that includes the source database's metadata, but not the source database's data.
(i.e. the new ADW/ATP clone will only contain the definitions of our existing database objects such as tables, views etc)
Why do we need cloning :
====================
++ For Development instance
++ For test instance
++ For training instance
What works ,what not :
==================
++ You can change compartments
++ You can change Storage size (Note : for Full Clone you must specify storage size at least the amount of source ADW / ATP ,else it will fail)
++ You can change CPU
++ Cannot clone across regions.You can only clone the instance to the same tenancy and the same region as the source database.
++ Oracle Machine Learning workspaces, projects, and notebooks are NOT cloned to the new database.
++ Backups associated with the source database are not cloned for either the full clone or the metadata clone option.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |