WMSID:11640 - Changes after review from development. (#53)

* WMSID:11640 - Added walkthrough videos and included feedback from developers

* WMSID:11640 - Fixed typo

data-guard/active-data-guard-23ai/awr-snapshots/awr-snapshots.md

@@ -7,6 +7,8 @@ Before Oracle Database 23ai, creating a snapshot on the standby database was imp
 
 Estimated Lab Time: 5 Minutes
 
+[Oracle Active Data Guard 23ai](videohub:1_7rghvu1t)
+
 ### Requirements
 To try this lab, you must have completed the following labs:
 * [Prepare the database hosts](../prepare-host/prepare-host.md)

data-guard/active-data-guard-23ai/configure-dg/configure-dg.md

@@ -10,6 +10,8 @@ For more information about the Data Guard broker, refer to the [broker documenta
 
 Estimated Lab Time: 5 Minutes
 
+[Oracle Active Data Guard 23ai](videohub:1_eucevsm7)
+
 ### Requirements
 To try this lab, you must have completed:
 * Lab 1: Prepare the database hosts

data-guard/active-data-guard-23ai/create-services/create-services.md

@@ -19,6 +19,8 @@ In this lab, we will create the services for the primary, physical standby, and
 
 Estimated Lab Time: 5 Minutes
 
+[Oracle Active Data Guard 23ai](videohub:1_zluu0czz)
+
 ### Requirements
 To try this lab, you must have successfully completed:
 * Lab 1: Prepare the database hosts

data-guard/active-data-guard-23ai/prepare-db/prepare-db.md

@@ -7,6 +7,8 @@ This lab uses a manual Data Guard configuration on top of two OCI Base Database
 
 Estimated Lab Time: 15 Minutes
 
+[Oracle Active Data Guard 23ai](videohub:1_6i8cq28y)
+
 ### Requirements
 To try this lab, you must have completed **Lab 1: Prepare the database hosts**
 
@@ -176,8 +178,9 @@ Oracle recommends using `RESTORE FROM SERVICE` to instantiate the standby databa
 
     ```
     <copy>
-    select * from v$standby_log;
+    select * from v$log;
     alter database clear logfile group 1, group 2, group 3;
+    select * from v$standby_log;
     alter database clear logfile group 4, group 5, group 6;
     </copy>
     ```

data-guard/active-data-guard-23ai/prepare-host/prepare-host-ocw.md

@@ -5,6 +5,8 @@ In this lab, we connect to the database hosts and do some preliminary preparatio
 
 Estimated Lab Time: 15 Minutes
 
+[Oracle Active Data Guard 23ai](videohub:1_1cq91vn7)
+
 ### Objectives
 - Prepare the connection to the database hosts
 - Prepare the primary database host

data-guard/active-data-guard-23ai/prepare-host/prepare-host.md

@@ -5,6 +5,8 @@ In this lab, we connect to the database hosts and do some preliminary preparatio
 
 Estimated Lab Time: 15 Minutes
 
+[Oracle Active Data Guard 23ai](videohub:1_1cq91vn7)
+
 ### Objectives
 - Prepare the connection to the database hosts
 - Prepare the primary database host

data-guard/active-data-guard-23ai/real-time-query-dml/real-time-query-dml.md

@@ -11,6 +11,8 @@ This functionality broadens the use cases for the physical standby, including ru
 
 Estimated Lab Time: 15 Minutes
 
+[Oracle Active Data Guard 23ai](videohub:1_fzrzvek5)
+
 ### Requirements
 To try this lab, you must have completed the following labs:
 * [Prepare the database hosts](../prepare-host/prepare-host.md)

data-guard/active-data-guard-23ai/snapshot-standby/snapshot-standby.md

@@ -13,6 +13,8 @@ This functionality can be helpful in testing:
 
 Estimated Lab Time: 5 Minutes
 
+[Oracle Active Data Guard 23ai](videohub:1_w5u4zktb)
+
 ### Requirements
 To try this lab, you must have completed the following labs:
 * [Prepare the database hosts](../prepare-host/prepare-host.md)

data-guard/active-data-guard-23ai/tac/tac.md

@@ -10,6 +10,8 @@ Transparent Application Continuity brilliantly solves this problem. Once the ses
 
 Estimated Lab Time: 10 Minutes
 
+[Oracle Active Data Guard 23ai](videohub:1_83rxr9ae)
+
 ### Requirements
 To try this lab, you must have completed the following labs:
 * [Prepare the database hosts](../prepare-host/prepare-host.md)
@@ -141,6 +143,24 @@ Remember to switch back before continuing with the next labs. The labs expect `A
     </copy>
     ```
 
+## Task 6 (optional): List the recent switchovers
+
+1. From a terminal (**the host is irrelevant for this lab**), connect to the read-write service on the primary:
+    
+    ```
+    <copy>
+    sql sys/WElcome123##@mypdb_rw as sysdba
+    </copy>
+    ```
+
+2. Query the view `v$dg_broker_role_change` to get the recent role changes:
+    
+    ```
+    <copy>
+    select * from v$dg_broker_role_change;
+    </copy>
+    ```
+
 You have successfully tested Transparent Application Continuity.
 
 - **Author** - Ludovico Caldara, Product Manager Data Guard, Active Data Guard and Flashback Technologies

data-guard/active-data-guard-23ai/verify-dg/verify-dg.md

@@ -6,6 +6,8 @@ In this lab, we will check the configuration and gain a basic knowledge of contr
 
 Estimated Lab Time: 15 Minutes
 
+[Oracle Active Data Guard 23ai](videohub:1_esvtn3k8)
+
 ### Requirements
 To try this lab, you must have completed:
 * Lab 1: Prepare the database hosts
@@ -37,14 +39,13 @@ The SQLcl integration does not yet support `VALIDATE` commands. Therefore, we wi
 
     ![Show configuration verbose shows a healthy status](images/show-configuration-verbose.png)
 
-3. The command `validate static connect identifier for all` checks that all members' static connect identifiers are reachable by each other.
+3. The command `validate static connect identifier for all` checks that the specified service is statically registered with the listener:
 
     ```
     <copy>validate static connect identifier for all;</copy>
     ```
 
-4. Similarly, the command `validate network configuration for all` checks the network configuration is healthy.
-
+4. Similarly, the command `validate network configuration for all` checks that all member's instances are reachable by each other.
     ```
     <copy>validate network configuration for all;</copy>
     ```
@@ -75,7 +76,7 @@ The SQLcl integration does not yet support `VALIDATE` commands. Therefore, we wi
 
     ![Output of VALIDATE DATABASE STRICT ALL](images/validate-strict.png)
 
-    In this case, you can see that the configuration **is not ready for the switchover**. The output shows that the Flashback logging is not enabled on the standby database. It won't prevent the switchover from working but might give unexpected problems later, for example, the inability to reinstate the new primary in case of failover.
+    In this case, you can see that the configuration **is not ready for the switchover**. The output shows that the Flashback logging is not enabled on the standby database. It won't prevent the switchover from working but might give unexpected problems later, for example, the inability to reinstate the database after a failover.
 
     Don't worry; we will fix that later.
 
@@ -184,17 +185,17 @@ Oracle Data Guard exposes many fixed views that help observe and monitor the Dat
     </copy>
     ```
      
-2. Query `v$dataguard_config`:
+2. Query `v$dg_broker_config`:
 
     ```
     <copy>
-    select * from v$dataguard_config;
+    select * from v$dg_broker_config;
     </copy>
     ```
 
     ![Content of the v$dataguard_config view](images/v-dataguard-config-primary.png)
 
-    The view `v$dataguard_config` contains the configuration members. The content is the same on the primary and standby databases, and it's helpful to understand the topology.
+    The view `v$dg_broker_config` contains the configuration members. The content is the same on the primary and standby databases, and it's helpful to understand the topology.
 
 3. Query the broker properties from `v$dg_broker_property`:
 
@@ -236,7 +237,7 @@ Oracle Data Guard exposes many fixed views that help observe and monitor the Dat
 
     ```
     <copy>
-    select * from v$dataguard_config;
+    select * from v$dg_broker_config;
     </copy>
     ```