The steps in this article apply when you want to re-create the standby database. Make sure the process is followed before initiating CSD (Create Standby Database) again.
Problem Details
Problem Statement
What is the correct process of re-creating standby database?
Applicable Error Code
N/A
Affected Versions
v7, v8, v9 & v10
Affected Platforms
All
Description
When rebuilding standby database, please make sure the following are done:
Solution
Version 7
- Shutdown standby database
- Delete datafiles and FRA folder (if using FRA) related to standby database
- Make sure Dbvisit schedules are stopped (both primary & standby) - Note: this could either be CRON (for Linux), Windows Task Scheduler (for Windows), or Dbvserver GUI scheduler
- Re-run CSD on primary server. You can do this either via CLI or GUI. If you are using Dbvisit Standby version 7, follow this guide - https://dbvisit.atlassian.net/wiki/pages/viewpage.action?pageId=19005583
- Run Dbvisit manually to test if everything is configured correctly
- Schedule Dbvisit process to automatically ship & apply logs - Ref: https://dbvisit.atlassian.net/wiki/display/UGDS7/Dbvisit+Standby+Scheduling
Version 8,9 & v10
- Shutdown standby database
- Delete datafiles and FRA folder (if using FRA) related to standby database
- Make sure Dbvisit schedules are stopped (both primary & standby) - Note: this could either be CRON (for Linux), Windows Task Scheduler (for Windows), or Dbvisit daemon
- Re-run CSD on primary server. You can do this either via CLI or GUI.
- Run Dbvisit manually to test if everything is configured correctly
- Schedule Dbvisit process to automatically ship & apply logs, reference
v8 https://dbvisit.atlassian.net/wiki/display/DS8QSG/Dbvisit+Standby+Scheduling
v9 https://dbvisit.atlassian.net/wiki/spaces/DS9QSG/pages/1244990162/Dbvisit+Standby+Scheduling
This note only discusses deleting files for a file system. It doesn't address ASM.