Now automatically refresh Refreshable Clones on Autonomous Database

March 27, 2024 | 3 minute read
Nilay Panchal
Principal Product Manager
Text Size 100%:

I’m always thrilled to announce features that make our customers lives easier and today’s feature is just that – Automatic Refresh for Refreshable Clones. This new feature enables users to set up an automatic refresh schedule in a few clicks, to refresh a clone at a desired cadence. This avoids the need to stand up your own server or scheduler to call the refresh API on a clone.

If you’re new here, to catch you up – Refreshable Clones are read-only clones of your database that stay attached to its source and can be refreshed as needed (ie. pull in new data from the source). These are very useful in keeping an updated copy of the database; simply refreshing the clone to the desired timestamp of the source is much quicker than creating a full clone of the database. This type of clone is perfect for scenarios where you need to offload query workloads or create billing separation from your production database.

Before today, users could manually refresh a refreshable clone on the UI or by automating an API call. With the new Automatic Refresh feature, Autonomous Database will automatically refresh your local or cross-region refreshable clones, at specified time intervals, to ensure your clone always stays as up-to-date as you need it to be!


How to Enable Automatic Refresh on a Refreshable Clones

Enabling Automatic Refresh is straightforward and can be done so either at the time of creating your refreshable clone or after creation, by updating the refreshable clone. You will notice a new Automatic Refresh checkbox – Once checked, you will be prompted to make two selections:

  • Frequency of refresh: Select how frequently you want the clone to refresh (eg. Refresh the clone every 24 hours)
  • Data lag: Select the lag, which is the amount of time behind the source’s data the clone’s data will be when it refreshes (eg. Each time the clone refreshes, you may want it to lag behind the sources data by 12 hours, leaving time for incoming data’s cleansing on the source). If you simply want the clone to refresh the latest current timestamp of the source, enter a 0 lag.

Note here that a refreshable clone has a limit to only fall behind its source upto 7 days (the longer time between refreshes, the longer the refresh would take). So the total of your selections above for frequency of refresh + data lag must be less than a maximum 7 days. Of course, as simple as it is to enable automatic refreshes, you may also edit your refresh schedule or disable automatic refresh at any point if required. You may also still call a manual refresh as before, any time between your scheduled automatic refreshes, if the need arises.

Enable automatic refresh


Once you have automatic refresh enabled, you may view or edit the refresh schedule on the database console. You may also view the timestamp of the upcoming refresh, as well as the refresh point of the source database that the clone has been most recently refresh to.

Automatic Refresh clone information


I expect this simplifies the refreshable clone process for many of you, and if you’re looking for what to do with all the spare time on your hands - Check out more Autonomous Database learning and walkthrough content on our Oracle’s LiveLabs platform. If you would also like to read all of the details about refreshable clones, including automatic refreshes, see the ADB documentation here. See you in the next one!



Like what I write? Follow me on the Twitter!



Nilay Panchal

Principal Product Manager

Nilay is a principal product manager at Oracle, responsible for adoption and feature development of Oracle's flagship converged cloud database - Autonomous Database. He was previously a developer and data scientist, and has a decade worth of experience in data warehousing, dimensional modeling, search engines and machine learning. A global Carnegie Mellon graduate, he has had the opportunity to work, travel and study in several different countries in various fields. His avocation is music; in his downtime he enjoys playing guitar or piano with a strong cup of chai nearby.

Nilay blogs regularly, and often speaks at cloud and database events. Follow his work on the Twitter @theproductlad

Show more

Previous Post

Iceberg Tables: A New Data Source for Oracle Autonomous Database

Alexey Filanovskiy | 5 min read

Next Post

Essbase Release Update Revision (RUR) is Available

Tanya Heise | 2 min read
Everything you need to know about data warehousing with the world's leading cloud solution provider