lab updates (#68)

Co-authored-by: Seth-Miller <[email protected]>

exadata-features/exascale_clone/exascale_clone.md

@@ -90,6 +90,15 @@ This lab assumes:
     </copy>
     ```
 
+9. Exit the sqlplus session before starting the next lab.
+
+    ```text
+    <copy>
+    exit
+    </copy>
+    ```
+
+
 You may now **proceed to the next lab**.
 
 ## Acknowledgements

exadata-features/flash_cache/flash_cache.md

@@ -67,31 +67,40 @@ This lab assumes:
 
 ## Task 2: Query With Flash Cache
 
-1. Disconnect and reconnect your session. Repeat the statistics query using the SQL script `lab_flash_cache_01.sql` and verify that the statistics are again at or near zero values. If any statistics are significantly greater than zero then reconnect again and retry.
+1. Disconnect and reconnect your sqlplus session.
+
+    ```text
+    <copy>
+    exit
+    sqlp
+    </copy>
+    ```
+
+2. Repeat the statistics query using the SQL script `lab_flash_cache_01.sql` and verify that the statistics are again at or near zero values. If any statistics are significantly greater than zero then reconnect again and retry.
 
     ```text
     <copy>
     @lab_flash_cache_01.sql
     </copy>
     ```
 
-2. Again, flush the buffer cache to ensure that the queries in the next step must retrieve the required data from the Exadata cells.
+3. Again, flush the buffer cache to ensure that the queries in the next step must retrieve the required data from the Exadata cells.
 
     ```text
     <copy>
     EXECUTE sys.flush_buffer_cache;
     </copy>
     ```
 
-3. Re-execute the query in the SQL script `lab_flash_cache_02.sql`.
+4. Re-execute the query in the SQL script `lab_flash_cache_02.sql`.
 
     ```text
     <copy>
     @lab_flash_cache_02.sql
     </copy>
     ```
 
-4. Repeat the statistics query using the SQL script `lab_flash_cache_01.sql`. Compare the values for `cell flash cache read hits` and `physical read total IO requests`. They should be closer together, indicating that most of the I/Os were satisfied by Exadata Smart Flash Cache.
+5. Repeat the statistics query using the SQL script `lab_flash_cache_01.sql`. Compare the values for `cell flash cache read hits` and `physical read total IO requests`. They should be closer together, indicating that most of the I/Os were satisfied by Exadata Smart Flash Cache.
 
     ```text
     <copy>
@@ -101,6 +110,15 @@ This lab assumes:
 
     > Note: If `cell flash cache read hits` is showing zero, you may be running this lab on a system with Extreme Flash storage cells. Since the flash cache on EF systems prior to X10M is on the storage disks and is not used for standard queries, `cell flash cache read hits` shows zero.
 
+
+6. Exit the sqlplus session before starting the next lab.
+
+    ```text
+    <copy>
+    exit
+    </copy>
+    ```
+
 You may now **proceed to the next lab**.
 
 ## Acknowledgements

exadata-features/hcc/hcc.md

@@ -94,6 +94,15 @@ This lab assumes:
     </copy>
     ```
 
+
+3. Exit the sqlplus session before starting the next lab.
+
+    ```text
+    <copy>
+    exit
+    </copy>
+    ```
+
 You may now **proceed to the next lab**.
 
 ## Acknowledgements

exadata-features/smart_scan/smart_scan.md

@@ -57,30 +57,47 @@ This lab assumes:
 
 ## Task 2: Query With Smart Scan
 
-1. Disconnect and reconnect your session. Repeat the statistics query from the SQL script `lab_smart_scan_01.sql` and verify that the statistics are again at or near zero values. If any statistics are significantly greater than zero then reconnect again and retry.
+1. Disconnect and reconnect your sqlplus session.
+
+    ```text
+    <copy>
+    exit
+    sqlp
+    </copy>
+    ```
+
+2. Repeat the statistics query from the SQL script `lab_smart_scan_01.sql` and verify that the statistics are again at or near zero values. If any statistics are significantly greater than zero then reconnect again and retry.
 
     ```text
     <copy>
     @lab_smart_scan_01.sql
     </copy>
     ```
 
-2. Execute the SQL script `lab_smart_scan_03.sql`. This is the same query, but this time there is no optimizer hint to disable Smart Scan.
+3. Execute the SQL script `lab_smart_scan_03.sql`. This is the same query, but this time there is no optimizer hint to disable Smart Scan.
 
     ```text
     <copy>
     @lab_smart_scan_03.sql
     </copy>
     ```
 
-3. Repeat the statistics query from the SQL script `lab_smart_scan_01.sql`. Note that the query still performs physical I/O (`physical read total bytes`). However, this time only a fraction of that is actually returned to the database server (`cell physical IO interconnect bytes`). This is Smart Scan in action. Also note that in this case, Smart Scan is acting on all of the I/O associated with the query. This is the case because `cell physical IO bytes eligible for predicate offload` equals `physical read total bytes`, and `cell physical IO interconnect bytes returned by smart scan` equals `cell physical IO interconnect bytes`.
+4. Repeat the statistics query from the SQL script `lab_smart_scan_01.sql`. Note that the query still performs physical I/O (`physical read total bytes`). However, this time only a fraction of that is actually returned to the database server (`cell physical IO interconnect bytes`). This is Smart Scan in action. Also note that in this case, Smart Scan is acting on all of the I/O associated with the query. This is the case because `cell physical IO bytes eligible for predicate offload` equals `physical read total bytes`, and `cell physical IO interconnect bytes returned by smart scan` equals `cell physical IO interconnect bytes`.
 
     ```text
     <copy>
     @lab_smart_scan_01.sql
     </copy>
     ```
 
+5. Exit the sqlplus session before starting the next lab.
+
+    ```text
+    <copy>
+    exit
+    </copy>
+    ```
+
 You may now **proceed to the next lab**.
 
 ## Acknowledgements