Moneycontrol Brokerage Recos

Sunday, September 22, 2019

Cloning an Autonomous Transaction Processing Database



So far we have seen how to create an Autonomous Transaction Processing Database(click here) and seen how to login to its service console to monitor the database activities and do some administration work.

In this article, I would demonstrate the process to Clone an Autonomous Transaction Processing database as and when required. Purpose of the cloning is to get a full copy of the production database to do the development or testing works.


There are two options to clone an Autonomous Transaction Processing Database:

1 - Full Clone

2 - Metadata Clone


Let's now see how easily we can clone an ATP(Autonomous Transaction Processing) database using its Details page.


Login to the ATP instance you want to clone via its direct link or you can navigate through the Oracle Cloud Infrastructure Console.

Source DB Name = DB201909201730

Target Clone DB Name = CLONEDB


I have the direct link for my ATP database named DB201909201730 , so I login with that as below.




Having logged in to the ATP instance, Autonomous Database Details page opens, Click on the "Action" drop down menu and then Click "Create Clone" to clone this database.






"Create Autonomous Database Clone" page opens where you specify the target clone database name and its details.


Here I want a Full clone (default option) to clone my source DB(DB201909201730). Select the Compartment in which you want to place this resource and provide the target DB name and Database Display Name.



Since I am using the "Always Free" credentials so I just turn this option on that makes CPU core count and Storage limits gets populated automatically. Provide Admin password.



Further, "License Included" option is selected by default, if a customer already has appropriate licensing then he/she can select the BYOL option as needed. Provide the Tag Key and its Value and finally click on "Create Autonomous Database Clone" to start the cloning job.



Cloning job has been started now.





You can monitor the progress of the cloning job > click on the "Work Request" under the "Resources" in left side at Database Details page. Here you can see the job progress in terms of % Complete, job stared date timestamp.



To go further in monitoring the cloning job, click on the Work Request > Operation and you get to "Create Autonomous Database" page and see more logs.




In few mins, your ATP clone created.




Autonomous Database > has list of clone ATP now.



I am now able to login to the CLONEDB ATP instance as below.










Cloning Limitation for Autonomous Transaction Processing Database:

1 > Oracle Machine Learning workspaces, projects, and notebooks of the source database are not cloned to the new database.
2 > If there is an ongoing clone operation on a source database, you cannot initiate a new clone operation on the database being cloned until the ongoing operation completes.
3 > You can only clone an Autonomous Transaction Processing instance to the same tenancy and the same region as the source database.
4 > If you define a network Access Control List (ACL) on the source database, the network ACL is cloned to the new database.



Optimizer Statistics for a Cloned Database:

During the provisioning for either a Full Clone or a Metadata Clone, the optimizer statistics are copied from the source database to the cloned database.

The following applies for optimizer statistics for tables in a cloned database:

Full Clone : loads into tables behave the same as loading into a table with statistics already in place.


Metadata Clone : the first load into a table after the clone clears the statistics for that table and updates the statistics with the new load.



Resource Management Rules and Performance Data for a Cloned Database:

The following applies for resource management rules and performance data in a
cloned database:

>  During the provisioning for either a Full Clone or a Metadata Clone, any resource management rule changed by the user in the source database is carried over to the cloned database.

>  Performance data for the time before the clone operation is not visible on the service console of the cloned database.



Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Autonomous Transaction Processing Cloud Services and new articles.


Twitter : https://twitter.com/rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

No comments:

Post a Comment