below are the restore points
SCN DATABASE_INCARNATION# GUA STORAGE_SIZE TIME RESTORE_POINT_TIME PRE
---------- --------------------- --- ------------ --------------------------------------------------------------------------- --------------------------------------------------------------------------- ---
NAME PDB CLE PDB_INCARNATION# REP CON_ID
-------------------------------------------------------------------------------------------------------------------------------- --- --- ---------------- --- ----------
1.7593E+13 2 YES 3.2415E+10 29-JUN-21 11.02.54.000000000 AM YES
AFTER_REFRESH NO NO 0 NO 0
1.7593E+13 3 YES 6.5498E+10 30-JUN-21 06.11.21.000000000 AM YES
BEFORE_UPGRD NO NO 0 NO 0
1.7593E+13 3 YES 5.1540E+10 01-JUL-21 07.11.08.000000000 AM YES
AFTER_UPGRADE NO NO 0 NO 0
we want to flashback database to restore point AFTER_UPRADE
flashback database to restore point AFTER_UPGRADE;
alter database open resetlogs;but we want to apply all trails since upgrade started so giving time of replicat start as of BEFORE_UPGRD
GGSCI (oel-rac01) 4> dblogin UserID ggadmin@TROY, Password ggadmin
Successfully logged into database.
GGSCI (oel-rac01 as ggadmin@TROY_4) 5> ALTER REPLICAT R_CL1, BEGIN 2021-06-30 06:11:21
2021-07-01 15:37:59 INFO OGG-06594 Replicat R_CL1 has been altered. Even the start up position might be updated, duplicate suppression remains active in next startup. To override duplicate suppression, start R_CL1 with NOFILTERDUPTRANSACTIONS option.
REPLICAT altered.
GGSCI (oel-rac01 as ggadmin@TROY_4) 6> ALTER REPLICAT R_CL2, BEGIN 2021-06-30 06:11:21
2021-07-01 15:38:06 INFO OGG-06594 Replicat R_CL2 has been altered. Even the start up position might be updated, duplicate suppression remains active in next startup. To override duplicate suppression, start R_CL2 with NOFILTERDUPTRANSACTIONS option.
REPLICAT altered.
GGSCI (oel-rac01 as ggadmin@TROY_4) 7> info all
Program Status Group Lag at Chkpt Time Since Chkpt
MANAGER RUNNING
EXTRACT ABENDED E1_ICG01 00:00:04 02:22:04
EXTRACT ABENDED E_ICG01 00:00:04 02:22:05
REPLICAT STOPPED R_CL1 33:26:38 00:00:09
REPLICAT STOPPED R_CL2 00:00:00 00:00:02
check the time in replicat it is moved now to restore point time
GGSCI (oel-rac01 as ggadmin@TROY_4) 8> info R_CL1
REPLICAT R_CL1 Initialized 2021-07-01 15:37 Status STOPPED
Parallel
Checkpoint Lag 33:26:38 (updated 00:00:13 ago)
Log Read Checkpoint File /u01/acfs/ogg/EXTRACT/TROY/RA000000000
2021-06-30 06:11:21.000000
GGSCI (oel-rac01 as ggadmin@TROY_4) 9> info R_CL2
REPLICAT R_CL2 Initialized 2021-07-01 15:38 Status STOPPED
Parallel
Checkpoint Lag 00:00:00 (updated 00:00:11 ago)
Log Read Checkpoint File /u01/acfs/ogg/EXTRACT/TROY/RB000000000
2021-06-30 06:11:21.000000
start the replicat
GGSCI (oel-rac01 as ggadmin@TROY_4) 10> start replicat R_CL1 NOFILTERDUPTRANSACTIONS
Sending START request to MANAGER ...
REPLICAT R_CL1 starting
GGSCI (oel-rac01 as ggadmin@TROY_4) 10> start replicat R_CL2 NOFILTERDUPTRANSACTIONS
Sending START request to MANAGER ...
REPLICAT R_CL2 starting
DBATracker 
Question:
In integrated replicat we refer dba_gg_inbound_progress view column APPLIED_LOW_POSITION column to track the transactional progress get use that scn value in case we have to rebuild the replicat so that we can start the replicat aftercn from that APPLIED_LOW_POSITION value. How do we get the SCN value to be used in case it is a parallel replict? Parallel replicat does not put entry in dba_gg_inbound_progress view, instead it uses checkpoint table but that checkpoint table has multiple rows for each of the applier process with different scns for different parallel appliers. Could you please provide the steps if we have to rebuild the parallel replicat, where do we get the SCN value to be used for start replicat aftercsn?
LikeLike