𝐀𝐮𝐭𝐨𝐧𝐨𝐦𝐨𝐮𝐬 𝐃𝐚𝐭𝐚𝐛𝐚𝐬𝐞𝐬 𝐂𝐥𝐨𝐧𝐢𝐧𝐠 𝐌𝐞𝐭𝐡𝐨𝐝𝐬

 

v   Autonomous Database Cloning

 

Use cases: 

·       Business requirements: Testing, Development or Analytics.

·       Database upgrade when a new version is available.

 

 

       Types of Clone:

·        Full clone: A full copy of the source database.

·        Refreshable clone: Changes on applied on the clone based on requests.

·        Metadata clone: A copy of the source database without user-data.

OCI CLI Clone Commands

Command	Description
ocidbautonomous-database create-from-clone	Creates a new full or metadata clone Autonomous Database.
ocidbautonomous-database create-refreshable-clone	Creates a new refreshable clone Autonomous Database.
ocidbautonomous-database list-clones	Lists the Autonomous Database clones for the specified Autonomous Database
ocidbautonomous-database manual-refresh	Initiates a data refresh for an Autonomous Database refreshable clone.

𝐎𝐫𝐚𝐜𝐥𝐞 𝐑𝐀𝐂 𝐏𝐥𝐚𝐧𝐧𝐞𝐝 𝐌𝐚𝐢𝐧𝐭𝐞𝐧𝐚𝐧𝐜𝐞 𝐀𝐜𝐭𝐢𝐯𝐢𝐭𝐲 𝐒𝐭𝐞𝐩𝐬 (𝐇𝐢𝐠𝐡-𝐀𝐯𝐚𝐢𝐥𝐚𝐛𝐢𝐥𝐢𝐭𝐲 𝐁𝐞𝐬𝐭 𝐏𝐫𝐚𝐜𝐭𝐢𝐜𝐞𝐬)

                                                      [̲̅O][̲̅R][̲̅A][̲̅C][̲̅L][̲̅E] [̲̅R][̲̅A][̲̅C]

Ø  First take “RMAN FULL Backup” of PRODUCTION RAC database.

 

Shutdown NODE-2 of ORACLE RAC Cluster   Step 1) IN NODE-2, Disable auto start of CRS in order to be able to perform server-OS Patching. So that CRS is not restarted after a reboot of the server.   Ø   crsctl disable crs

Step 2) Shutdown the instance running on NODE-2.   Ø   srvctl stop instance -d RACDB -i RACDB2 -o immediate

Step 3) Shutdown oracle cluster ware.   Ø  crsctl stop crs

Step 4) Check cluster ware and database instance status.   Ø   crsctl check crs Ø  srvctl status database –d RACDB

Handover NODE-2 to IT team for OS patching.

After OS Patching:

Startup NODE-2 of ORACLE RAC Cluster   Step 1) IN NODE-2, enable auto start of CRS.   Ø   crsctl enable crs

Step 2) Start oracle cluster ware.   Ø  crsctl start crs

Step 3) Startup the RACDB2 instance on NODE-2.   Ø  srvctl start instance -d RACDB -i RACDB2

Step 4) Check cluster ware and database instance status.   Ø  crsctl check crs Ø  srvctl status database –d RACDB

Handover NODE-2 to  Apps team to check it functionality.

Note:-  After confirmation from Apps team that everything running smoothly then only we will go for NODE-1.   Otherwise IT team will have to Rollback OS Patch in NODE-2 !!

 

 

☑ Again we will follow the same steps as all mentioned above for Node 1  

Shutdown NODE-1 of ORACLE RAC Cluster   Step 1) IN NODE-1, Disable auto start of CRS in order to be able to perform server-OS Patching. So that CRS is not restarted after a reboot of the server.   Ø  crsctl disable crs

Step 2) Shutdown the instance running on NODE-1.   Ø  srvctl stop instance -d RACDB -i RACDB1 -o immediate

Step 3) Shutdown oracle cluster ware.   Ø  crsctl stop crs

Step 4) Check cluster ware and database instance status.   Ø  crsctl check crs Ø  srvctl status database –d RACDB

Handover NODE-1 to IT team for OS patching.

After OS Patching:

Startup NODE-1 of ORACLE RAC Cluster   Step 1) IN NODE-1, enable auto start of CRS.   Ø  crsctl enable crs

Step 2) Start oracle cluster ware.   Ø crsctl start crs

Step 3) Startup the RACDB1 instance on NODE-1.   Ø  srvctl start instance -d RACDB -i RACDB1

Step 4) Check cluster ware and database instance status.   Ø  crsctl check crs Ø  srvctl status database –d RACDB

Handover NODE-1 to  Apps team to check it functionality.

Apps team will need to confirm that everything running smoothly from their end..!!

 ROLLBACK: If anything goes wrong then IT team will have to rollback OS patch in Node- 1 & Node- 2 accordingly. 

Else even after rollback of OS patch if it doesn't work then we can restore RAC database from latest backup which we have taken just before the activity.