Resynchronizing Both the Primary and Replicate Databases from the Same Dump

Coordinate resynchronization to reload both the primary database and replicate database from the same dump or copy of data. No dump database marker is needed, since you are not obtaining a dump from the primary database.

Stop replication processing by Replication Agent. Do not alter the truncation point. In Replication Agent, execute:
```
suspend
```
Suspend the Replication Server DSI connection to the replicate database:
```
suspend connection to data_server.database
```
Instruct Replication Server to remove data from the replicate database outbound queue and wait for a resync marker from the primary database Replication Agent:
```
resume connection to data_server.database skip to 
resync marker
```
Apply the dump of the data from the external source to the primary database.
Move the truncation point to the end of the transaction log for the primary database. In Replication Agent, execute:
```
pdb_xlog move_truncpt
go
```
Reinitialize Replication Agent repository based on the latest system data from the primary database:
```
ra_init force
go
```
Instruct Replication Agent to start in resync mode with the init option. In Replication Agent, execute:.
```
resume resync, init
```
Verify that DSI has received and accepted the resync marker from the Replication Agent by looking for this message in the Replication Server system log:
```
DSI for data_server.database received and processed
Resync Database Marker. DSI is now suspended. Resume 
after database has been reloaded.
```
When Replication Server receives and processes the resync database with init marker, the DSI connection suspends.
Apply the dump of the data from the external source to the replicate database.
If the maintenance and DDL users do not exist in the primary database, add these users to the replicate database after you apply the dump from the primary database.
Run the hds_oracle_new_setup_for_replicate.sql script on the replicate database to add the rs_info and rs_lastcommit tables to the replicate database.
The script also inserts relevant values and grants the required permissions in the replicate database.
After you apply the dump to the replicate database, resume DSI to the replicate database to allow Replication Server to apply transactions from the primary database:
```
resume connection to data_server.database
```