Oracle 19c Restore Point Replication From Primary To Standby
Description:-
- Oracle Database Release 19c New Features.
- The process of flashing back a physical standby to a point in time that was captured on the primary is
simplified by automatically replicating restore points from primary to the standby. - These restore points are called replicated restore points.
- Irrespective of whether a restore point on the primary database is a guaranteed restore point or a normal restore point, the corresponding replicated restore point is
always a normal restore point.
Automatically replicates restore points from a primary database to the standby database Conditions:-
- COMPATIBLE initialization parameter for both the primary database and the standby database is set to 19.0.0 or higher
- Primary database is open
- A restore point that is created on a primary database when the primary is in mount mode is not replicated. This restriction is because the restore point information is replicated though the redo.
SQL> show parameter compatible
NAME TYPE VALUE
———————————— ———– ——————————
compatible string 19.0.0
SQL> select status,instance_name,database_role,protection_mode ,flashback_on from v$database,v$instance;
STATUS INSTANCE_NAME DATABASE_ROLE PROTECTION_MODE FLASHBACK_ON
———— —————- ————- ————— ——————
OPEN chennai PRIMARY MAXIMUM AVAILABILITY YES
- When you delete a restore point on the primary, the corresponding replicated restore point on the
standby is also deleted. - The managed redo process (MRP) manages the creation and maintenance of replicated restore
points. If restore points are created on the primary database when MRP is not running, then these
restore points are replicated to the standby database after MRP is started.
DEMO:-
Primary Side:-
SQL> SELECT database_role, open_mode FROM v$database;
DATABASE_ROLE OPEN_MODE
—————- ——————–
PRIMARY READ WRITE
SQL> create restore point Oracle_test guarantee flashback database;
Restore point created.
SQL> select SCN, GUARANTEE_FLASHBACK_DATABASE, TIME, NAME, REPLICATED from v$restore_point;
SCN GUARANTEE_FLASHBACK_DATABASE TIME NAME REPLICATED
———- —————————— —————————————- ————————-
2443446 YES 20-OCT-19 04.15.22.000000000 PM ORACLE_TEST NO
Alertlog
2019-10-20T16:15:22.184171+05:30
Created guaranteed restore point ORACLEDBWR_TEST
Standby Side
SQL> SELECT database_role, open_mode FROM v$database;
DATABASE_ROLE OPEN_MODE
—————- ——————–
PHYSICAL STANDBY READ ONLY WITH APPLY
SQL> select SCN, GUARANTEE_FLASHBACK_DATABASE, TIME, NAME, REPLICATED from v$restore_point;
SCN GUARANTEE_FLASHBACK_DATABASE TIME NAME REPLICATED
———- —————————— —————————————- ————————-
2443446 NO 20-OCT-19 04.15.22.000000000 PM ORACLEDBWR_TEST_PRIMARY YES
SQL> select status,instance_name,database_role,protection_mode ,flashback_on from v$database,v$instance;
STATUS INSTANCE_NAME DATABASE_ROLE PROTECTION_MODE FLASHBACK_ON
———— —————- —————- —————————————————————————-
OPEN delhi PHYSICAL STANDBY MAXIMUM AVAILABILITY YES
The naming convention for a replicated restore point uses the name of the restore point on the primary database suffixed with _PRIMARY. If a replicated restore point with the same name exists on the standby database, then a replicated restore point is not created. For example, when you create a restore point named PRE_MYTBS on the primary database, the replicated restore point is named oracledbwr_test_PRIMARY. When you delete a restore point on the primary, the corresponding replicated restore point on the standby is also deleted.
Connect to me:-
Telegram App: https://t.me/oracledbwr
LinkedIn: https://www.linkedin.com/in/hariprasathdba
LinkedIN Page: https://www.linkedin.com/company/orcldbwr/
Facebook: https://www.facebook.com/HariPrasathdba
FB Group: https://www.facebook.com/groups/oracledbwr/
FB Page : https://www.facebook.com/dbahariprasath/
Twitter : https://twitter.com/hariprasathdba
