Changes for Oracle Database 23.5.0 (#624)

* Initial changes * Acknowledgements * Lab 10 - first edition * Start lab 11 plus lab 10 fixes * Lab 11, final changes * Lab 11 minor text changes * Lab 11 - restart source post-migration * Lab 12 * Small stuff * Lab 12 * Missing ``` * Lab 13 * Labs 3-5 update * Update autoupgrade.md * Labs 3-9 * Lab 15 downgrade * Lab 14 glitches * Changed release dates * Lab 14 - part 1 * Changing contributors * Trim spaces * Page changes * Update awr-compare.md * Update spa.md * Lab 14 * Update encrypted-db-upg-conv.md * Minor corrections * Lab 02 errors * Changes * Error fixing * Get rid of EXPORT and use env script * Lab 7 * More fixes * Missing exit in lab 14 * Image pptx * Fixing underscores * underscores * Small * Lab 8 finalize * Lab 9 * Lab 00 * Dummy change * Test change * Squashed commit of the following: commit 1d6978d Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 12:07:30 2024 -0300 Update migrate-using-ftex.md commit b71c67d Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 11:48:31 2024 -0300 Update upg-cdb-flashback.md commit 12a96a5 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 11:27:52 2024 -0300 Fix some details commit 637d577 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 10:32:57 2024 -0300 Update spm.md commit a1e191a Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 10:32:45 2024 -0300 Update spm.md commit 3e3cb76 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 10:16:14 2024 -0300 Update spm.md commit 8493933 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:54:26 2024 -0300 Update awr-compare.md commit 11c13cd Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:54:23 2024 -0300 Update explore-multitenant.md commit a891039 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:31:52 2024 -0300 Update awr-snapshot.md commit 6e3e57a Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:31:49 2024 -0300 Update explore-multitenant.md commit b4ee666 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:00:26 2024 -0300 Update explore-multitenant.md commit 8828c2b Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:00:23 2024 -0300 Update initialize-environment.md commit 3d94b33 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 08:53:52 2024 -0300 Update initialize-environment.md commit 5047abb Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 08:53:46 2024 -0300 Update introduction.md * Update explore-multitenant.md * Update upg-cdb-flashback.md * More stuff * f * Update initialize-environment.md * Delete ~$images.pptx * Squashed commit of the following: commit 87452a1 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Thu Jun 6 12:13:44 2024 -0300 Update migrate-using-ftex.md commit 2f89859 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Thu Jun 6 09:44:06 2024 -0300 Update upg-cdb-flashback.md commit e3da2b9 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Wed Jun 5 14:37:07 2024 -0300 Update explore-multitenant.md commit cfaa942 Merge: c1b40df f5ca582 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Wed Jun 5 11:40:22 2024 -0300 Merge branch 'main' into hammerdb-changes-doc commit c1b40df Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 16:07:15 2024 -0300 Fix typos commit 1d6978d Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 12:07:30 2024 -0300 Update migrate-using-ftex.md commit b71c67d Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 11:48:31 2024 -0300 Update upg-cdb-flashback.md commit 12a96a5 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 11:27:52 2024 -0300 Fix some details commit 637d577 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 10:32:57 2024 -0300 Update spm.md commit a1e191a Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 10:32:45 2024 -0300 Update spm.md commit 3e3cb76 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 10:16:14 2024 -0300 Update spm.md commit 8493933 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:54:26 2024 -0300 Update awr-compare.md commit 11c13cd Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:54:23 2024 -0300 Update explore-multitenant.md commit a891039 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:31:52 2024 -0300 Update awr-snapshot.md commit 6e3e57a Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:31:49 2024 -0300 Update explore-multitenant.md commit b4ee666 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:00:26 2024 -0300 Update explore-multitenant.md commit 8828c2b Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 09:00:23 2024 -0300 Update initialize-environment.md commit 3d94b33 Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 08:53:52 2024 -0300 Update initialize-environment.md commit 5047abb Author: Rodrigo Jorge <rodrigoaraujorge@hotmail.com> Date: Mon Jun 3 08:53:46 2024 -0300 Update introduction.md * Changes from Klaus + Alex * Klaus changes * Image error * Delete ~$images.pptx * New workshops * Mikes changes * Small change * Fix issue with UPGR starting too fast and failing to register at listener * A few more changes * First run * Lab 2 * Lab 3 * Start lab 5 * Next push * Next lab * Labs 4-6 * Lab 8 complete * Final labs - first draft * Test changes * Next round * Lab 10 * More stuff * More stuff * Update post-migration-tasks.md * Grammarly changes * Final test / Daniel * Timing * Typo * Updating contributors * Grammerly changes * Changes from Alex * Updating manifest files * Old lab instructions - replaced by "hitchhikers-guide-upgrade-to-19c-2-0" * Moving to Oracle home 23.4.1 * Use desktop shortcut to start a terminal * dd * Minor stuff * aaa * Mike's changes * Adjust to 23.5.0 * XTTS migration - minor changes * Banner change for 19c * Updating labs to use yellow/blue terminals * Final changes * No longer necessary to check UPGR database * Testing changes * Using color codes for the terminals. * More color coded terminals * A few more checks * Testing performance stability prescription on 23.5.0 * pptx with graphics --------- Co-authored-by: Rodrigo Jorge <rodrigoaraujorge@hotmail.com>
oracle-livelabs · Aug 13, 2024 · 8332f84 · 8332f84
1 parent 2d0cee9
commit 8332f84
Show file tree

Hide file tree

Showing 27 changed files with 357 additions and 419 deletions.
diff --git a/datapump-xtts-migration/01-initialize-environment/initialize-environment.md b/datapump-xtts-migration/01-initialize-environment/initialize-environment.md
@@ -19,29 +19,29 @@ In this lab, you will:
 
 2. Before copy/pasting, take notice of the commands that you execute; it is important to understand what the commands will do.
 
-3. You can use any terminal to run the lab. The lab sets the environment when appropriate.
-
-4. Double-click on the *Terminal* shortcut on the desktop. 
+3. Double-click on the *Terminal* shortcut on the desktop. 
 
 ![Click shortcut to start a terminal](./images/initialize-environment-desktop-click-terminal.jpeg " ")
 
-5. The terminal has two tabs, *Yellow* and *Blue*. You can use any of them to perform the labs. All labs start by setting the appropriate environment.
+4. The terminal has two tabs, *yellow* and *blue*. *Yellow* 🟨 is for the source database. *Blue* 🟦 is for the target database.
+
+5. The instructions will tell you which terminal to use.
 
 6. Optionally, in the terminal, you can zoom in to make the text larger. 
 
 ![Zoom in to make the text larger in the terminal](./images/initialize-environment-terminal-zoom-in.png)    
 
 ## Task 2: Initialize the workshop environment
 
-1. Open a terminal or use an existing one. When you start the lab, the following components should be started.
+1. When you start the lab, the following components should be started.
 
     - Database Listener
         - LISTENER
     - Database Server Instances
         - FTEX
         - CDB23
 
-2. Ensure the listener is started.
+2. Use the *yellow* terminal 🟨. Ensure the listener is started.
 
     ```
     <copy>
@@ -83,4 +83,4 @@ You may now *proceed to the next lab*.
 
 * **Author** - Daniel Overby Hansen
 * **Contributors** - Rodrigo Jorge, Mike Dietrich, Klaus Gronau, Alex Zaballa
-* **Last Updated By/Date** - Daniel Overby Hansen, July 2024
+* **Last Updated By/Date** - Daniel Overby Hansen, August 2024
diff --git a/datapump-xtts-migration/02-check-source/check-source.md b/datapump-xtts-migration/02-check-source/check-source.md
@@ -17,7 +17,7 @@ In this lab, you will:
 
 The M5 script has a set of minimum requirements.
 
-1. Set the environment to the source database, *FTEX*.
+1. Use the *yellow* terminal 🟨 and set the environment to the source database, *FTEX*.
 
     ```
     <copy>
@@ -304,4 +304,4 @@ You may now *proceed to the next lab*.
 
 * **Author** - Daniel Overby Hansen
 * **Contributors** - Rodrigo Jorge, Mike Dietrich, Klaus Gronau, Alex Zaballa
-* **Last Updated By/Date** - Daniel Overby Hansen, July 2024
+* **Last Updated By/Date** - Daniel Overby Hansen, August 2024
diff --git a/datapump-xtts-migration/03-create-target/create-target.md b/datapump-xtts-migration/03-create-target/create-target.md
@@ -19,7 +19,7 @@ In this lab, you will:
 
 In contrast to the source database, the target CDB is on Oracle Database 23ai. This means there are no minimum requirements for the Release Update. Nor is there a requirement for the Data Pump Bundle Patch. However, Oracle recommends that you install the latest Release Update in the target database prior to the migration.
 
-1. Set the environment to the target CDB, *CDB23*, and connect.
+1. Use the *blue* terminal 🟦. Set the environment to the target CDB, *CDB23*, and connect.
 
     ```
     <copy>
@@ -251,7 +251,26 @@ In contrast to the source database, the target CDB is on Oracle Database 23ai. T
 
 A few more changes are needed on the target database. Plus, Oracle has a few recommendations that help ensuring a smooth migration.
 
-1. Create a directory object that points to the file system directory you created in a previous lab. Data Pump needs this directory for the import.
+1. Ensure you are still in *VIOLET*.
+
+    ```
+    <copy>
+    show con_name
+    </copy>
+    ```
+
+    <details>
+    <summary>*click to see the output*</summary>
+    ``` text
+    SQL> show con_name
+
+    CON_NAME
+    ------------------------------
+    VIOLET
+    ```
+    </details>
+
+2. Create a directory object that points to the file system directory you created in a previous lab. Data Pump needs this directory for the import.
 
     ```
     <copy>
@@ -310,4 +329,4 @@ Oracle recommends migrating to the same database character set. In some situatio
 
 * **Author** - Daniel Overby Hansen
 * **Contributors** - Rodrigo Jorge, Mike Dietrich, Klaus Gronau, Alex Zaballa
-* **Last Updated By/Date** - Daniel Overby Hansen, July 2024
+* **Last Updated By/Date** - Daniel Overby Hansen, August 2024
diff --git a/datapump-xtts-migration/04-prepare-m5/prepare-m5.md b/datapump-xtts-migration/04-prepare-m5/prepare-m5.md
@@ -19,7 +19,7 @@ In this lab, you will:
 
 In this lab, the source and target database are on the same host. Both hosts access the same directory with the M5 script via a shared NFS drive.
 
-1. Go to *M5* directory and get the M5 migration script. The directory acts as your script base. You have created the directory already in a previous exercise when you created the database directory. Instead of downloading from My Oracle Support, you copy the script to the script base.
+1. Use the *yellow* terminal 🟨. Go to *M5* directory and get the M5 migration script. The directory acts as your script base. You have created the directory already in a previous exercise when you created the database directory. Instead of downloading from My Oracle Support, you copy the script to the script base.
 
     ```
     <copy>
@@ -289,4 +289,4 @@ You may now *proceed to the next lab*.
 
 * **Author** - Daniel Overby Hansen
 * **Contributors** - Rodrigo Jorge, Mike Dietrich, Klaus Gronau, Alex Zaballa
-* **Last Updated By/Date** - Daniel Overby Hansen, July 2024
+* **Last Updated By/Date** - Daniel Overby Hansen, August 2024
diff --git a/datapump-xtts-migration/05-initial-backup-restore/initial-backup-restore.md b/datapump-xtts-migration/05-initial-backup-restore/initial-backup-restore.md
@@ -18,7 +18,7 @@ In this lab, you will:
 
 ## Task 1: Start initial backup
 
-1. Set the environment to the source database and switch to the script base.
+1. Use the *yellow* terminal 🟨. Set the environment to the source database and change to the script base.
 
     ```
     <copy>
@@ -179,7 +179,7 @@ In this lab, you will:
 
 ## Task 2: Perform initial restore
 
-1. The backup also generated a restore script that you can use on the target database. Find the restore script. 
+1. Switch to the *blue* terminal 🟦. The backup also generated a restore script that you can use on the target database. Find the restore script. 
 
     ```
     <copy>
@@ -310,4 +310,4 @@ In a real migration, if you are worried about the load on the source database, a
 
 * **Author** - Daniel Overby Hansen
 * **Contributors** - Rodrigo Jorge, Mike Dietrich, Klaus Gronau, Alex Zaballa
-* **Last Updated By/Date** - Daniel Overby Hansen, July 2024
+* **Last Updated By/Date** - Daniel Overby Hansen, August 2024
diff --git a/...pump-xtts-migration/06-incremental-backup-restore/incremental-backup-restore.md b/...pump-xtts-migration/06-incremental-backup-restore/incremental-backup-restore.md
@@ -18,7 +18,7 @@ In this lab, you will:
 
 ## Task 1: Perform incremental backup and restore it
 
-1. Set the environment to the source database and start a level 1 backup.
+1. Use the *yellow* terminal 🟨. Set the environment to the source database and start a level 1 backup.
 
     ```
     <copy>
@@ -116,10 +116,13 @@ In this lab, you will:
     ```
     </details>
 
-4. Examine the corresponding restore script. The backup also produced a restore script you can use on the target database.
+4. Switch to the *blue* terminal 🟦. 
+
+5. Examine the corresponding restore script. The backup also produced a restore script you can use on the target database.
 
     ```
     <copy>
+    cd /home/oracle/m5/cmd
     ll restore_L1*cmd
     </copy>
     ```
@@ -131,7 +134,7 @@ In this lab, you will:
     ```
     </details>
 
-5. Examine the restore script. 
+6. Examine the restore script. 
 
     ```
     <copy>
@@ -164,10 +167,11 @@ In this lab, you will:
     ```
     </details>
 
-6. *Restore* the level 1 backup. 
+7. *Restore* the level 1 backup. 
 
     ```
     <copy>
+    cd /home/oracle/m5/cmd
     export L1SCRIPT=$(ls -tr restore_L1_* | tail -1) 
     cd /home/oracle/m5
     . cdb23
@@ -207,7 +211,7 @@ In this lab, you will:
     ```
     </details>
 
-7. Search the log file for any warnings or errors. 
+8. Search the log file for any warnings or errors. 
 
     ```
     <copy>
@@ -224,7 +228,7 @@ In this lab, you will:
 
 Let's simulate changes to the source database and see how they affect the backup and restore phase.
 
-1. Set the environment to the source database and connect.
+1. Use the *yellow* terminal 🟨. Set the environment to the source database and connect.
 
     ```
     <copy>
@@ -299,11 +303,11 @@ Let's simulate changes to the source database and see how they affect the backup
     ```
     </details>
 
-2. Restore the backup.
+2. Switch to the *blue* terminal 🟦. Restore the backup.
 
     ```
     <copy>
-    cd cmd
+    cd /home/oracle/m5/cmd
     export L1SCRIPT=$(ls -tr restore_L1_* | tail -1) 
     cd /home/oracle/m5
     . cdb23
@@ -366,4 +370,4 @@ In a real migration, you would run incremental backup/restore cycles at regular
 
 * **Author** - Daniel Overby Hansen
 * **Contributors** - Rodrigo Jorge, Mike Dietrich, Klaus Gronau, Alex Zaballa
-* **Last Updated By/Date** - Daniel Overby Hansen, July 2024
+* **Last Updated By/Date** - Daniel Overby Hansen, August 2024
diff --git a/datapump-xtts-migration/07-test-migration/test-migration.md b/datapump-xtts-migration/07-test-migration/test-migration.md
@@ -30,7 +30,7 @@ You will test the migration by performing the final steps of the migration. Howe
 
 1. Outage starts on the source database.
 
-2. Set the environment to the source database.
+2. Use the *yellow* terminal 🟨. Set the environment to the source database.
 
     ```
     <copy>
@@ -270,11 +270,11 @@ You will test the migration by performing the final steps of the migration. Howe
     </copy>
     ```
 
-6. Restore the test backup.
+6. Switch to the *blue* terminal 🟦. Restore the test backup.
 
     ```
     <copy>
-    cd cmd
+    cd /home/oracle/m5/cmd
     export L1FSCRIPT=$(ls -tr restore_L1F* | tail -1) 
     . cdb23
     cd /home/oracle/m5
@@ -287,7 +287,7 @@ You will test the migration by performing the final steps of the migration. Howe
     <details>
     <summary>*click to see the output*</summary>
     ``` text
-    $ cd cmd
+    $ cd /home/oracle/m5/cmd
     $ export L1FSCRIPT=$(ls -tr restore_L1F* | tail -1)
     $ . cdb23
     $ cd /home/oracle/m5
@@ -326,7 +326,7 @@ You will test the migration by performing the final steps of the migration. Howe
     export L1FLOGFILE=$(ls -tr restore_L1F*log | tail -1)
     cd /home/oracle/m5/m5dir
     export DMPFILE=$(ls -tr exp_FTEX*dmp | tail -1)
-    cd ..
+    cd /home/oracle/m5
     . cdb23
     ./impdp.sh $DMPFILE log/$L1FLOGFILE run-readonly N
     </copy>
@@ -805,7 +805,7 @@ You will test the migration by performing the final steps of the migration. Howe
 
 You just finished the test migration. You can connect to the target database and see the data.
 
-1. Connect to the target database, *CDB23*. 
+1. Still in the *blue* terminal 🟦. Connect to the target database, *CDB23*. 
 
     ```
     <copy>
@@ -883,7 +883,7 @@ You just finished the test migration. You can connect to the target database and
 
 Now that you are done testing, you use `FLASHBACK DATABASE` to undo the test import.
 
-1. Switch to the root container and restart the database in mount mode.
+1. Still in the *blue* terminal 🟦. Switch to the root container and restart the database in mount mode.
 
     ```
     <copy>
@@ -1016,7 +1016,7 @@ Now that you are done testing, you use `FLASHBACK DATABASE` to undo the test imp
 
 When the test completes and you reverted the changes, you can resume the backup/restore cycle.
 
-1. Set the environment to the source database and connect.
+1. Use the *yellow* terminal 🟨. Set the environment to the source database and connect.
 
     ```
     <copy>
@@ -1089,11 +1089,11 @@ When the test completes and you reverted the changes, you can resume the backup/
     ```
     </details>
 
-5. Restore the backup.
+5. Switch to the *blue* terminal 🟦. Restore the backup.
 
     ```
     <copy>
-    cd cmd
+    cd /home/oracle/m5/cmd
     export L1SCRIPT=$(ls -tr restore_L1_* | tail -1) 
     cd /home/oracle/m5
     . cdb23
@@ -1106,7 +1106,7 @@ When the test completes and you reverted the changes, you can resume the backup/
     <details>
     <summary>*click to see the output*</summary>
     ``` text
-    $ cd cmd
+    $ cd /home/oracle/m5/cmd
     $ export L1SCRIPT=$(ls -tr restore_L1_* | tail -1)
     $ cd /home/oracle/m5
     $ . cdb23
@@ -1161,4 +1161,4 @@ During the test, you introduced a short outage on the source database. You chang
 
 * **Author** - Daniel Overby Hansen
 * **Contributors** - Rodrigo Jorge, Mike Dietrich, Klaus Gronau, Alex Zaballa
-* **Last Updated By/Date** - Daniel Overby Hansen, July 2024
+* **Last Updated By/Date** - Daniel Overby Hansen, August 2024
diff --git a/datapump-xtts-migration/08-final-preparations/final-preparations.md b/datapump-xtts-migration/08-final-preparations/final-preparations.md
@@ -19,7 +19,7 @@ Although Data Pump can transfer statistics as part of a full transportable expor
 
 You can export statistics before the maintenance window begins. Most likely, the statistics will not change from now on, and even if they do, such changes shouldn't make a huge difference for the optimizer.
 
-1. Set the environment to the source database and connect.
+1. Use the *yellow* terminal 🟨. Set the environment to the source database and connect.
 
     ```
     <copy>
@@ -130,7 +130,7 @@ You can export statistics before the maintenance window begins. Most likely, the
 
 While executing an export or import job, Data Pump is querying the data dictionary heavily. To avoid any performance issues caused by inaccurate statistics, Oracle recommends gathering dictionary statistics close to the maintenance window.
 
-1. Gather dictionary statistics.
+1. Still in the *yellow* terminal 🟨. Gather dictionary statistics.
 
     ```
     <copy>
@@ -179,4 +179,4 @@ There are other means of dealing with the statistics than using `DBMS_STATS`. Al
 
 * **Author** - Daniel Overby Hansen
 * **Contributors** - Rodrigo Jorge, Mike Dietrich, Klaus Gronau, Alex Zaballa
-* **Last Updated By/Date** - Daniel Overby Hansen, July 2024
+* **Last Updated By/Date** - Daniel Overby Hansen, August 2024