Process RSM0, PID = 23456, will be killed

Standby database DG log:

11/09/2022 11:53:34
Creating process RSM0
11/09/2022 11:53:37
Process RSM0 re-created with PID = 20918
11/09/2022 11:59:37
Process RSM0, PID = 20918, will be killed
11/09/2022 11:59:51

Primary database DG log:

Data Guard Broker Status Summary:
Type Name Severity Status
Configuration DG_CDRDB Warning ORA-16607
Primary Database PCDRDB Error ORA-16778
Physical Standby database SCDRDB Error ORA-16810

SOLUTION

  1. Check and resolve network issues between primary db server and standby server.
  2. Increase the OperationTimeout property value :
DGMGRL> show configuration OperationTimeout;
  OperationTimeout = '30'
 
DGMGRL> EDIT CONFIGURATION SET PROPERTY OperationTimeout=90;
Property "operationtimeout" updated

DGMGRL>  show configuration OperationTimeout;
  OperationTimeout = '90'

Oracle Goldengate : start replicat ATCSN or AFTERCSN ?

There is a following question on the web with different answers:

You must synchronize the starting point for Replicat with the restore point of the target database. How should you accomplish this?

A. Use the command option AFTERCSN.
B. Use the command option ATCSN.
C. Use the command option UNTIL CANCEL.
D. Use the command option RESUME.

There are more than one correct answer, i think.

A is correct, if datapump has been used to instantiate the target database. expdp performed consistency as of FLASHBACK_SCN included.

B is correct, if RMAN has been used to instantiate the target database. Oracle RMAN restore or recovery using UNTIL SCN which specifies an SCN as an upper limit  but not including the specified SCN.

For Oracle GoldenGate 12.2 and above, neither AFTERCSN nor ATCSN is required anymore, if “DBOPTIONS ENABLE_INSTANTIATION_FILTERING” is enabled in replicat parameter file.

Reference : Oracle GoldenGate Best Practices: Instantiation from an Oracle Source Database
Version 12c
Document ID 1276058.1