\noracle@exacc-cl01n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 14:46:17 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ WRITE NO\n 4 SWTET_TMR_001T READ ONLY NO\nSQL>\n<\/pre>\n<\/br>\n\n\n\n On the standby side, this looks like:<\/p>\n\n\n\n
\noracle@exacc-cl02n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 14:46:48 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ ONLY NO\n 4 SWTET_TMR_001T MOUNTED\nSQL>\n<\/pre>\n<\/br>\n\n\n\nWhich is correct as the Master Read Only SWTET_TMR_001T was created with STANDBYS=NONE option.<\/p>\n\n\n\n
Sparse clone creation<\/h3>\n\n\n\n
The command used to create the sparse clone on the primary CDB was:<\/p>\n\n\n\n
SQL> CREATE PLUGGABLE DATABASE SWTET_APP_002T FROM SWTET_TMR_001T\n KEYSTORE IDENTIFIED BY \"...\" INCLUDING SHARED KEY\n PARALLEL 8\n CREATE_FILE_DEST='+SPRC2'\n SERVICE_NAME_CONVERT=('SWTET_TMR_001T','SWTET_APP_002T','SWTET_APP_001T','SWTET_APP_002T')\n SNAPSHOT COPY\n STANDBYS=NONE;\n\nSQL> ALTER PLUGGABLE DATABASE SWTET_APP_002T OPEN INSTANCES=ALL;<\/code><\/pre>\n\n\n\nOn the primary side, this looks like:<\/p>\n\n\n\n
\noracle@exacc-cl01n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 15:03:18 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ WRITE NO\n 4 SWTET_TMR_001T READ ONLY NO\n 5 SWTET_APP_002T READ WRITE NO\nSQL>\n<\/pre>\n<\/br>\n\n\n\nThe sparse clone PDB is opened as expected in READ\/WRITE mode.<\/p>\n\n\n\n
On the standby side, this looks like:<\/p>\n\n\n\n
\noracle@exacc-cl02n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 15:37:11 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ ONLY NO\n 4 SWTET_TMR_001T MOUNTED\n 5 SWTET_APP_002T MOUNTED\nSQL>\n<\/pre>\n<\/br>\n\n\n\nWhich is correct as we used the standby=no option to create the sparse clone and in any case the snapshot is only locally as storage dependant.<\/p>\n\n\n\n
Create some data in the spare clone<\/h3>\n\n\n\n
Let’s create some data into the spare clone.<\/p>\n\n\n\n
\noracle@exacc-cl01n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 15:28:39 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ WRITE NO\n 4 SWTET_TMR_001T READ ONLY NO\n 5 SWTET_APP_002T READ WRITE NO\n\nSQL> alter session set container=SWTET_APP_002T;\n\nSession altered.\n\nSQL> alter session set nls_date_format='DD\/MM\/YYYY HH24:MI:SS';\n\nSession altered.\n\nSQL> set lines 300\n\nSQL> create table TEST_SWITCH (id int, name varchar(100), run_exec date);\n\nTable created.\n\nSQL> insert into TEST_SWITCH values (0, 'Before switch', sysdate);\n\n1 row created.\n\nSQL> commit;\n\nCommit complete.\n\nSQL> select * from TEST_SWITCH;\n\n ID NAME RUN_EXEC\n---------- ---------------------------------------------------------------------------------------------------- -------------------\n 0 Before switch 06\/06\/2025 15:33:32\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nSwitchover to CHZ3<\/h3>\n\n\n\n
Let’s switchover from CHZ2 to CHZ3.<\/p>\n\n\n\n
\noracle@exacc-cl01n1:~\/ [SWIT001T1 (CDB$ROOT)] dgh\nDGMGRL for Linux: Release 19.0.0.0.0 - Production on Fri Jun 6 15:36:06 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2019, Oracle and\/or its affiliates. All rights reserved.\n\nWelcome to DGMGRL, type \"help\" for information.\n\nDGMGRL> connect sys@SWIT001T_CHZ2\nPassword:\nConnected to \"SWIT001T_CHZ2\"\nConnected as SYSDBA.\n\nDGMGRL> show configuration lag\n\nConfiguration - swit001t_dgconf\n\n Protection Mode: MaxPerformance\n Members:\n SWIT001T_CHZ2 - Primary database\n SWIT001T_CHZ3 - Physical standby database\n Transport Lag: 0 seconds (computed 0 seconds ago)\n Apply Lag: 0 seconds (computed 0 seconds ago)\n\nFast-Start Failover: Disabled\n\nConfiguration Status:\nSUCCESS (status updated 46 seconds ago)\n\nDGMGRL> validate database SWIT001T_CHZ3\n\n Database Role: Physical standby database\n Primary Database: SWIT001T_CHZ2\n\n Ready for Switchover: Yes\n Ready for Failover: Yes (Primary Running)\n\n Managed by Clusterware:\n SWIT001T_CHZ2: YES\n SWIT001T_CHZ3: YES\n\n Temporary Tablespace File Information:\n SWIT001T_CHZ2 TEMP Files: 5\n SWIT001T_CHZ3 TEMP Files: 3\n\nDGMGRL> switchover to SWIT001T_CHZ3;\nPerforming switchover NOW, please wait...\nOperation requires a connection to database \"SWIT001T_CHZ3\"\nConnecting ...\nConnected to \"SWIT001T_CHZ3\"\nConnected as SYSDBA.\nNew primary database \"SWIT001T_CHZ3\" is opening...\nOracle Clusterware is restarting database \"SWIT001T_CHZ2\" ...\nConnected to \"SWIT001T_CHZ2\"\nSwitchover succeeded, new primary is \"swit001t_chz3\"\nDGMGRL>\n\nDGMGRL> show configuration lag\n\nConfiguration - swit001t_dgconf\n\n Protection Mode: MaxPerformance\n Members:\n SWIT001T_CHZ3 - Primary database\n SWIT001T_CHZ2 - Physical standby database\n Transport Lag: 0 seconds (computed 1 second ago)\n Apply Lag: 0 seconds (computed 1 second ago)\n\nFast-Start Failover: Disabled\n\nConfiguration Status:\nSUCCESS (status updated 7 seconds ago)\n<\/pre>\n<\/br>\n\n\n\nCreate table in source pdb in new primary cl02<\/h3>\n\n\n\n
To check on the sparse clone database would react after the switchover, let’s add some data in the source PDB on the new primary (CHZ3).<\/p>\n\n\n\n
\noracle@exacc-cl02n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 15:40:16 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ WRITE NO\n 4 SWTET_TMR_001T MOUNTED\n 5 SWTET_APP_002T MOUNTED\n\nSQL> alter session set container=SWTET_APP_001T;\n\nSession altered.\n\nSQL> alter session set nls_date_format='DD\/MM\/YYYY HH24:MI:SS';\n\nSession altered.\n\nSQL> set lines 300\n\nSQL> create table TEST_ON_STDBY (id int, name varchar(100), run_exec date);\n\nTable created.\n\nSQL> insert into TEST_ON_STDBY values (0, 'Cl08 is primary', sysdate);\n\n1 row created.\n\nSQL> commit;\n\nCommit complete.\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 3 SWTET_APP_001T READ WRITE NO\n\t\t \nSQL> select instance_name, host_name from v$instance;\n\nINSTANCE_NAME HOST_NAME\n---------------- ----------------------------------------------------------------\nSWIT001T1 exacc-cl02n1\n\nSQL> select * from TEST_ON_STDBY;\n\n ID NAME RUN_EXEC\n---------- ---------------------------------------------------------------------------------------------------- -------------------\n 0 Cl08 is primary 06\/06\/2025 15:43:19\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nCheck table on new standby side cl01<\/h3>\n\n\n\n
We can check data on the standby side PDB on the cluster cl01.<\/p>\n\n\n\n
\noracle@exacc-cl01n1:~\/ [grinf19] SWIT001T1\n\n ********************************************\n INSTANCE_NAME : SWIT001T1\n DB_NAME : SWIT001T\n DB_UNIQUE_NAME : SWIT001T_CHZ2\n STATUS : OPEN READ ONLY WITH APPLY\n LOG_MODE : ARCHIVELOG\n USERS\/SESSIONS : 4\/19\n DATABASE_ROLE : PHYSICAL STANDBY\n FLASHBACK_ON : YES\n FORCE_LOGGING : YES\n VERSION : 19.26.0.0.0\n CDB_ENABLED : YES\n PDBs : PDB$SEED SWTET_APP_001T SWTET_APP_002T SWTET_TMR_001T\n ********************************************\n\n PDB color: pdbname=mount, pdbname=open read-write, pdbname=open read-only\n Statustime: 2025-06-06 15:45:25\n\noracle@exacc-cl01n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 15:45:27 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ ONLY NO\n 4 SWTET_TMR_001T MOUNTED\n 5 SWTET_APP_002T READ ONLY NO\n<\/pre>\n<\/br>\n\n\n\nThe Master Read Only PDB is in MOUNT status, opening it in READ ONLY mode would not be possible. This would make sense as it is the reference for the sparse clone and we created it with the no standby option.<\/p>\n\n\n\n
\nSQL> alter pluggable database SWTET_TMR_001T open read only instances=all;\nalter pluggable database SWTET_TMR_001T open read only instances=all\n*\nERROR at line 1:\nORA-01173: data dictionary indicates missing data file from system tablespace\n<\/pre>\n<\/br>\n\n\n\nLet’s check if the source PDB is having the new created data on the new standby side cl01.<\/p>\n\n\n\n
\nSQL> alter session set container=SWTET_APP_001T;\n\nSession altered.\n\nSQL> alter session set nls_date_format='DD\/MM\/YYYY HH24:MI:SS';\n\nSession altered.\n\nSQL> set lines 300\n\nSQL> select instance_name, host_name from v$instance;\n\nINSTANCE_NAME HOST_NAME\n---------------- ----------------------------------------------------------------\nSWIT001T1 exacc-cl01n1\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 3 SWTET_APP_001T READ ONLY NO\n\nSQL> select * from TEST_ON_STDBY;\n\n ID NAME RUN_EXEC\n---------- ---------------------------------------------------------------------------------------------------- -------------------\n 0 Cl08 is primary 06\/06\/2025 15:43:19\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nYes, we have the new data.<\/p>\n\n\n\n
Run switchover back<\/h3>\n\n\n\n
Let’s switch back to cl01.<\/p>\n\n\n\n
\nDGMGRL> show configuration lag\n\nConfiguration - swit001t_dgconf\n\n Protection Mode: MaxPerformance\n Members:\n SWIT001T_CHZ3 - Primary database\n SWIT001T_CHZ2 - Physical standby database\n Transport Lag: 0 seconds (computed 0 seconds ago)\n Apply Lag: 0 seconds (computed 0 seconds ago)\n\nFast-Start Failover: Disabled\n\nConfiguration Status:\nSUCCESS (status updated 11 seconds ago)\n\nDGMGRL> validate database SWIT001T_CHZ2;\n\n Database Role: Physical standby database\n Primary Database: SWIT001T_CHZ3\n\n Ready for Switchover: Yes\n Ready for Failover: Yes (Primary Running)\n\n Managed by Clusterware:\n SWIT001T_CHZ3: YES\n SWIT001T_CHZ2: YES\n\n Temporary Tablespace File Information:\n SWIT001T_CHZ3 TEMP Files: 3\n SWIT001T_CHZ2 TEMP Files: 5\n\nDGMGRL> switchover to SWIT001T_CHZ2;\nPerforming switchover NOW, please wait...\nOperation requires a connection to database \"SWIT001T_CHZ2\"\nConnecting ...\nConnected to \"SWIT001T_CHZ2\"\nConnected as SYSDBA.\nNew primary database \"SWIT001T_CHZ2\" is opening...\nOracle Clusterware is restarting database \"SWIT001T_CHZ3\" ...\nConnected to \"SWIT001T_CHZ3\"\nSwitchover succeeded, new primary is \"swit001t_chz2\"\n\nDGMGRL> show configuration lag\n\nConfiguration - swit001t_dgconf\n\n Protection Mode: MaxPerformance\n Members:\n SWIT001T_CHZ2 - Primary database\n SWIT001T_CHZ3 - Physical standby database\n Transport Lag: 0 seconds (computed 5 seconds ago)\n Apply Lag: 0 seconds (computed 5 seconds ago)\n\nFast-Start Failover: Disabled\n\nConfiguration Status:\nSUCCESS (status updated 20 seconds ago)\n<\/pre>\n<\/br>\n\n\n\nOn the standby side, this would look like:<\/p>\n\n\n\n
\noracle@exacc-cl02n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 15:51:33 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ ONLY NO\n 4 SWTET_TMR_001T MOUNTED\n 5 SWTET_APP_002T MOUNTED\nSQL>\n<\/pre>\n<\/br>\n\n\n\nOn the primary side, this would look like:<\/p>\n\n\n\n
\noracle@exacc-cl01n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 15:52:24 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ WRITE NO\n 4 SWTET_TMR_001T MOUNTED\n 5 SWTET_APP_002T READ WRITE NO\n<\/pre>\n<\/br>\n\n\n\nReopening the Master Read Only would fail.<\/p>\n\n\n\n
\nSQL> alter pluggable database SWTET_TMR_001T open read only instances=all;\nalter pluggable database SWTET_TMR_001T open read only instances=all\n*\nERROR at line 1:\nORA-01173: data dictionary indicates missing data file from system tablespace\n<\/pre>\n<\/br>\n\n\n\nAdd data in source PDB<\/h3>\n\n\n\n
Adding new data in source PDB would be of course successful.<\/p>\n\n\n\n
\nSQL> alter session set container=SWTET_APP_001T;\n\nSession altered.\n\nSQL> alter session set nls_date_format='DD\/MM\/YYYY HH24:MI:SS';\n\nSession altered.\n\nSQL> set lines 300\n\nSQL> select instance_name, host_name from v$instance;\n\nINSTANCE_NAME HOST_NAME\n---------------- ----------------------------------------------------------------\nSWIT001T1 exacc-cl01n1\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 3 SWTET_APP_001T READ WRITE NO\n\nSQL> insert into TEST_ON_STDBY values (1,'primary back to cl07',sysdate);\n\n1 row created.\n\nSQL> commit;\n\nCommit complete.\n\nSQL> select * from TEST_ON_STDBY;\n\n ID NAME RUN_EXEC\n---------- ---------------------------------------------------------------------------------------------------- -------------------\n 0 Cl08 is primary 06\/06\/2025 15:43:19\n 1 primary back to cl07 06\/06\/2025 15:54:54\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nAnd data would be also available in the source PDB on the standby side.<\/p>\n\n\n\n
\noracle@exacc-cl02n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 15:56:00 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ ONLY NO\n 4 SWTET_TMR_001T MOUNTED\n 5 SWTET_APP_002T MOUNTED\n\nSQL> alter session set container=SWTET_APP_001T;\n\nSession altered.\n\nSQL> alter session set nls_date_format='DD\/MM\/YYYY HH24:MI:SS';\n\nSession altered.\n\nSQL> set lines 300\n\nSQL> select instance_name, host_name from v$instance;\n\nINSTANCE_NAME HOST_NAME\n---------------- ----------------------------------------------------------------\nSWIT001T1 exacc-cl02n1\n\nSQL> select * from TEST_ON_STDBY;\n\n ID NAME RUN_EXEC\n---------- ---------------------------------------------------------------------------------------------------- -------------------\n 0 Cl08 is primary 06\/06\/2025 15:43:19\n 1 primary back to cl07 06\/06\/2025 15:54:54\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\n<h3>Add new data in spare clone<\/h3><\/p>\n\n\n\n
Let’s add new data in the sparse clone.<\/p>\n\n\n\n
\noracle@exacc-cl01n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 15:57:00 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ WRITE NO\n 4 SWTET_TMR_001T MOUNTED\n 5 SWTET_APP_002T READ WRITE NO\n\nSQL> alter session set container=SWTET_APP_002T;\n\nSession altered.\n\nSQL> alter session set nls_date_format='DD\/MM\/YYYY HH24:MI:SS';\n\nSession altered.\n\nSQL> set lines 300\n\nSQL> select instance_name, host_name from v$instance;\n\nINSTANCE_NAME HOST_NAME\n---------------- ----------------------------------------------------------------\nSWIT001T1 exacc-cl01n1\n\nSQL> select * from TEST_SWITCH;\n\n ID NAME RUN_EXEC\n---------- ---------------------------------------------------------------------------------------------------- -------------------\n 0 Before switch 06\/06\/2025 15:33:32\n\nSQL> insert into TEST_SWITCH values (1,'After switchover and back cl07', sysdate);\n\n1 row created.\n\nSQL> commit;\n\nCommit complete.\n\nSQL> select * from TEST_SWITCH;\n\n ID NAME RUN_EXEC\n---------- ---------------------------------------------------------------------------------------------------- -------------------\n 0 Before switch 06\/06\/2025 15:33:32\n 1 After switchover and back cl07 06\/06\/2025 15:59:01\n\nSQL>\n<\/pre>\n<\/br>\n\n\n\nAdding new data into the sparse clone is possible.<\/p>\n\n\n\n
Drop the sparse clone<\/h3>\n\n\n\n
Command to drop the sparse clone would be:<\/p>\n\n\n\n
SQL> ALTER PLUGGABLE DATABASE SWTET_APP_002T CLOSE IMMEDIATE INSTANCES=ALL;\n\nSQL> DROP PLUGGABLE DATABASE SWTET_APP_002T INCLUDING DATAFILES;<\/code><\/pre>\n\n\n\nOn the primary side, this would now look like:<\/p>\n\n\n\n
\noracle@exacc-cl01n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 17:25:32 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ WRITE NO\n 4 SWTET_TMR_001T MOUNTED\nSQL>\n<\/pre>\n<\/br>\n\n\n\nOn the standby side, this would now look like:<\/p>\n\n\n\n
\noracle@exacc-cl02n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 17:26:03 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ ONLY NO\n 4 SWTET_TMR_001T MOUNTED\nSQL>\n<\/pre>\n<\/br>\n\n\n\nRefresh Master Read Only<\/h3>\n\n\n\n
We can refresh the Master Read Only with following command.<\/p>\n\n\n\n
SQL> drop pluggable database SWTET_TMR_001T including datafiles;\n\nSQL> CREATE PUBLIC DATABASE LINK SWIT001T_e9085be389a239c888e5c0baf4f50405@SWIT001T_CHZ2 CONNECT TO C##USER IDENTIFIED BY \"..................\" USING 'SWIT001T_CHZ2';\n\nSQL> CREATE PLUGGABLE DATABASE SWTET_TMR_001T FROM SWTET_APP_001T@\"SWIT001T_e9085be389a239c888e5c0baf4f50405@SWIT001T_CHZ2\"\n KEYSTORE IDENTIFIED BY \"...\" INCLUDING SHARED KEY\n PARALLEL 8\n SERVICE_NAME_CONVERT=('SWTET_APP_001T','SWTET_TMR_001T')\n REFRESH MODE MANUAL\n STANDBYS=NONE;\n\nSQL> ALTER PLUGGABLE DATABASE SWTET_TMR_001T OPEN READ ONLY INSTANCES=ALL;\n\nSQL> DROP PUBLIC DATABASE LINK SWIT001T_e9085be389a239c888e5c0baf4f50405@SWIT001T_CHZ2;<\/code><\/pre>\n\n\n\nCreate spare clone again<\/h3>\n\n\n\n
And we can create the sparse clone again with the same command.<\/p>\n\n\n\n
SQL> CREATE PLUGGABLE DATABASE SWTET_APP_002T FROM SWTET_TMR_001T\n KEYSTORE IDENTIFIED BY \"...\" INCLUDING SHARED KEY\n PARALLEL 8\n CREATE_FILE_DEST='+SPRC2'\n SERVICE_NAME_CONVERT=('SWTET_TMR_001T','SWTET_APP_002T','SWTET_APP_001T','SWTET_APP_002T')\n SNAPSHOT COPY\n STANDBYS=NONE;\n\nSQL> ALTER PLUGGABLE DATABASE SWTET_APP_002T OPEN INSTANCES=ALL;<\/code><\/pre>\n\n\n\nOn the primary side, this looks like:<\/p>\n\n\n\n
\noracle@exacc-cl01n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 17:38:12 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ WRITE NO\n 4 SWTET_APP_002T READ WRITE NO\n 5 SWTET_TMR_001T READ ONLY NO\nSQL>\n<\/pre>\n<\/br>\n\n\n\nAnd on the standby side:<\/p>\n\n\n\n
\noracle@exacc-cl02n1:~\/ [SWIT001T1 (CDB$ROOT)] sqh\n\nSQL*Plus: Release 19.0.0.0.0 - Production on Fri Jun 6 17:38:38 2025\nVersion 19.26.0.0.0\n\nCopyright (c) 1982, 2024, Oracle. All rights reserved.\n\n\nConnected to:\nOracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production\nVersion 19.26.0.0.0\n\nSQL> show pdbs\n\n CON_ID CON_NAME OPEN MODE RESTRICTED\n---------- ------------------------------ ---------- ----------\n 2 PDB$SEED READ ONLY NO\n 3 SWTET_APP_001T READ ONLY NO\n 4 SWTET_APP_002T MOUNTED\n 5 SWTET_TMR_001T MOUNTED\nSQL>\n<\/pre>\n<\/br>\n\n\n\nTo wrap up…<\/h3>\n\n\n\n
Sparse clone works successfully in Data Guard environment. Sparse clone are only available locally, and so available only when the CDB hosting initially the sparse clone PDB has the primary role. Switching to the other site is not a problem. The sparse clone would be available again once switching back. At last, we can then easily refresh the master read only and create again the spare clone.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
As you might know, on ExaCC, it is possible to create spare clones. This is based on snapshot technology. There is no physical copy and the modified blocks will be written to the sparse clone, and in our case these blocks will be part of the ASM spare disk group. And of course, the sparse […]<\/p>\n","protected":false},"author":48,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[3624,59],"tags":[2742,2598,3646],"type_dbi":[],"class_list":["post-39722","post","type-post","status-publish","format-standard","hentry","category-exacc-oracle","category-oracle","tag-data-guard-2","tag-exacc-3","tag-sparse"],"acf":[],"yoast_head":"\n
What will happen to your spare clones during a switchover on ExaCC? - dbi Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"What will happen to your spare clones during a switchover on ExaCC?\" \/>\n<meta property=\"og:description\" content=\"As you might know, on ExaCC, it is possible to create spare clones. This is based on snapshot technology. There is no physical copy and the modified blocks will be written to the sparse clone, and in our case these blocks will be part of the ASM spare disk group. And of course, the sparse […]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/\" \/>\n<meta property=\"og:site_name\" content=\"dbi Blog\" \/>\n<meta property=\"article:published_time\" content=\"2025-07-29T14:57:36+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-07-29T14:57:38+00:00\" \/>\n<meta name=\"author\" content=\"Marc Wagner\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Marc Wagner\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/\"},\"author\":{\"name\":\"Marc Wagner\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"headline\":\"What will happen to your spare clones during a switchover on ExaCC?\",\"datePublished\":\"2025-07-29T14:57:36+00:00\",\"dateModified\":\"2025-07-29T14:57:38+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/\"},\"wordCount\":785,\"commentCount\":0,\"keywords\":[\"Data Guard\",\"exacc\",\"sparse\"],\"articleSection\":[\"ExaCC\",\"Oracle\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/\",\"name\":\"What will happen to your spare clones during a switchover on ExaCC? - dbi Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\"},\"datePublished\":\"2025-07-29T14:57:36+00:00\",\"dateModified\":\"2025-07-29T14:57:38+00:00\",\"author\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Accueil\",\"item\":\"https:\/\/www.dbi-services.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"What will happen to your spare clones during a switchover on ExaCC?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#website\",\"url\":\"https:\/\/www.dbi-services.com\/blog\/\",\"name\":\"dbi Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628\",\"name\":\"Marc Wagner\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g\",\"caption\":\"Marc Wagner\"},\"url\":\"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"What will happen to your spare clones during a switchover on ExaCC? - dbi Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/","og_locale":"en_US","og_type":"article","og_title":"What will happen to your spare clones during a switchover on ExaCC?","og_description":"As you might know, on ExaCC, it is possible to create spare clones. This is based on snapshot technology. There is no physical copy and the modified blocks will be written to the sparse clone, and in our case these blocks will be part of the ASM spare disk group. And of course, the sparse […]","og_url":"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/","og_site_name":"dbi Blog","article_published_time":"2025-07-29T14:57:36+00:00","article_modified_time":"2025-07-29T14:57:38+00:00","author":"Marc Wagner","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Marc Wagner","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/#article","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/"},"author":{"name":"Marc Wagner","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"headline":"What will happen to your spare clones during a switchover on ExaCC?","datePublished":"2025-07-29T14:57:36+00:00","dateModified":"2025-07-29T14:57:38+00:00","mainEntityOfPage":{"@id":"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/"},"wordCount":785,"commentCount":0,"keywords":["Data Guard","exacc","sparse"],"articleSection":["ExaCC","Oracle"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/","url":"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/","name":"What will happen to your spare clones during a switchover on ExaCC? - dbi Blog","isPartOf":{"@id":"https:\/\/www.dbi-services.com\/blog\/#website"},"datePublished":"2025-07-29T14:57:36+00:00","dateModified":"2025-07-29T14:57:38+00:00","author":{"@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628"},"breadcrumb":{"@id":"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.dbi-services.com\/blog\/what-will-happen-to-your-spare-clones-during-a-switchover-on-exacc\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Accueil","item":"https:\/\/www.dbi-services.com\/blog\/"},{"@type":"ListItem","position":2,"name":"What will happen to your spare clones during a switchover on ExaCC?"}]},{"@type":"WebSite","@id":"https:\/\/www.dbi-services.com\/blog\/#website","url":"https:\/\/www.dbi-services.com\/blog\/","name":"dbi Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.dbi-services.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.dbi-services.com\/blog\/#\/schema\/person\/225d9884b8467ead9a872823acb14628","name":"Marc Wagner","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/a873cc6e7fbdbbcbdbcaf5dbded14ad9a77b2ec2c3e03b4d724ed33d35d5f328?s=96&d=mm&r=g","caption":"Marc Wagner"},"url":"https:\/\/www.dbi-services.com\/blog\/author\/marc-wagner\/"}]}},"_links":{"self":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/39722","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/users\/48"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/comments?post=39722"}],"version-history":[{"count":28,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/39722\/revisions"}],"predecessor-version":[{"id":39758,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/posts\/39722\/revisions\/39758"}],"wp:attachment":[{"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/media?parent=39722"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/categories?post=39722"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/tags?post=39722"},{"taxonomy":"type","embeddable":true,"href":"https:\/\/www.dbi-services.com\/blog\/wp-json\/wp\/v2\/type_dbi?post=39722"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}