...
- kiwi701 – Primary Database Server
- kiwi702 – Standby Database Server (first standby)
- kiwi703 – Cascading Standby Database Server (second standby)
- kiwi704 – Dbvisit Standby Version 8 9 Central Console
- Oracle Database 12.2 installed and configured on kiwi701, kiwi702, kiwi703
- Oracle 12c Database DEV running on kiwi701
- Standby Database DEV running on kiwi702 (with kiwi701 as primary)
- Dbvisit Standby DDC file for Primary (kiwi701) to Standby (kiwi702) called DEV
- Dbvisit Standby Version 9 installed on all systems into /usr/dbvisit. This includes Dbvnet, Dbvagent and Standby Core on kiwi701, kiwi702 and kiwi703. The Central Console (dbvserver) is installed on kiwi704.
- In this example, the secondary standby server kiwi703 is using the exact same directory structure as the first standby – which is also the same directory structure that is used on the primary. This is the recommended approach – a primary and standby database environment should match.
...
Updating the new secondary standby database
Once the new secondary standby database is created, we can start the process of shipping logs to the standby database. But at this stage, it is important to note that the secondary standby database now running on kiwi703, is reliant on the archive logs that are available on the first standby database running on kiwi702. To ensure we have logs available on the first standby database, we first run the process to ship and apply logs from primary (kiwi701)(2) to the first standby (kiwi702)(3). Then once we have successfully sent and applied logs between these, we can now send logs from the first standby database running on kiwi702(4) to the secondary standby on kiwi703(5). The arrows and numbers in the image below show the order of the steps to be performed.
...