Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-89

Update EXASuite 4.2.6 to EXASolution 4.2.8 + OS Patchlevel 2

    Details

    • Solution:
      Hide

      Synopsis

      This article guides you through the update procedure from EXASuite version 4.2.6 (plain, without OS patchlevels) to EXASolution 4.2.8 and OS patchlevel 2.

      The update requires a maintenance window of about two hours and will be performed in four steps:

      1. Update to EXASuite version 4.2.7 (~ 45 minutes)
      2. Update to OS Patchlevel 1 (~ 45 minutes)
      3. Update to OS Patchlevel 2 (~ 10 minutes)
      4. Update to EXASolution 4.2.8 (~ 10 minutes)

      Please note that

      1. the the tasks performed in EXAoperation require a user with at least "Administrator" privileges and
      2. it is vital to wait for uploads and reboots to finish completely!


      Prereqesites

      Please download the following packages from the EXASOL customer portal:

      Package Description Size (MiB) MD5 Checksum
      EXAClusterOS-4.2.7_LS-Update.pkg EXASuite LS update package 104.5 110afeaa6802fc2e04706e987a1bcfe5
      EXAClusterOS-CentOS-6.4_Patchlevel-1.pkg EXASuite security updates 294.3 efc3b46a717b293560d27cf3ecd99b92
      EXAClusterOS-CentOS-6.4_Patchlevel-2.pkg EXASuite security updates 50.5 b5fe3f427cd7a48e50e8873c3d4aaef3
      EXASolution-4.2.8_x86_64.pkg EXASolution package 44.7 6f4d8ad26b59a93333d914373b3b4b4f


      Installation instructions

      1. Check Software Versions
      • Open Configuration > Software in EXAoperation and click on the tab "Versions"
      • EXAClusterOS 4.2.1 is required as minimum version for the update to EXASuite 4.2.7
      2. EXAoperation master node
      • The update must be applied to the license server since it is the only node that boots from the local hard drive.
        • In EXAoperation, please navigate to Configuration > Network
        • Open the tab "System"
        • Ensure that the license server (usually node n0010) is listed as "License Server Node"
      • Move EXAoperation if the license server is not the master node:
        • Open the Page Services > EXAoperation
        • Select "n0010" from dropdown list
        • Confirm with click on th button "Move to specified Node"
      3. Check database operaton
      • Navigate to the EXAoperation page Services > EXASolution
      • Review the database list and check if the column "Background Restore" indicates "None" on all instances
      4. Upload EXASuite 4.2.7
      • Open the Configuration > Software page in EXAoperation
      • In the tab "Versions" please find the input box labelled "Software Update File:"
      • Click on the button "Browse" (label depends on browser, language and operating system)
      • Choose "EXAClusterOS-4.2.7_LS-Update.pkg" in the newly opened file manager view
      • Confirm with click on the button "Submit" and wait until EXAoperation displays the message:

      First part of update process succeeded. Please shutdown databases, Storage and nodes and restart license server.

      • In the EXAoperation Services > Monitoring page you may open an appropriately defined logservice that will present the messages:

      Software update First part of update process succeeded. Please shutdown databases and nodes and restart license server.
      Software update No need to update kernel 2.6.32-358.0.1.el6.centos.plus.x86_64.
      Software update Start update process to EXAClusterOS version 4.2.7.

      5. Shutdown all databases
      • Open the Services > EXASolution page
      • Select all (running) EXASolution instances
      • Click on the button "Shutdown"
      • Reload the page until all instances change their status from "Running" to "Created"
      • Again, you may follow the procedure in an appropriate logservice:

      System marked as stopped.
      Successfully send retry shutdown event to system partition 64.
      EXASolution DEMO is rejecting connections
      controller-st(0.0): Shutdown called.
      User 0 requests shutdown of system.

      6. Shutdown EXAStorage
      • Navigate to the EXAoperation page Services > EXAStorage
      • Click on the button "Shutdown Storage Service" and confirm your choice when prompted.
      7. Suspend Nodes
      • Open the Configuration > Nodes page in EXAoperation
      • In the tab "Cluster Nodes", please select all nodes
      • Select "Stop cluster services" from actions dropdown menu
      • Confirm with click on the button "Execute"
      • Reload the page and until all nodes indicate the State/Op. "Suspended"
      8. Reboot the license server
      • Open the Configuration > Nodes page in EXAoperation
      • Navigate down to the fieldset "License Nodes"
      • Click on the button "Reboot" next to the license server (usually node n0010)
      • If reboot is not possible, you may open the license server console (e.g. in iDRAC or vSphere) and send the key sequence CTRL + ALT + DEL.

      • Wait for the license server to finish it's startup procedure (about 10 minutes) and log into EXAoperation again
      9. Check Software Versions
      • Open Configuration > Software in EXAoperation and click on the tab "Versions"
      • The field labelled EXAClusterOS must now present version "4.2.7"
      10. Reboot the database nodes
      • Navigate to the Configuration > Nodes page
      • Select all nodes in the tab "Cluster Nodes"
      • Choose "Reboot" from actions dropdown menu and confirm with click on button "Execute"
      • Wait for the nodes to finish reboot (about 5 to 10 minutes)
      • Reload the nodes page until the State/Op. column changes from "booting" to "running" for all nodes
      • You may watch the boot process (of node n11 in this example) in an appropriately configured logservice:

      n11 Boot process finished after 259 seconds
      n11 Boot process stage 3 finished.
      n11 Start boot process stage 3.
      n11 successfully initialized thresholds for node monitoring
      n11 successfully unpacked package on client node: JDBC_Drivers-2013-04-24.tar.gz
      n11 successfully unpacked package on client node: Oracle-InstantClient-10.2_x86_64.tar.gz
      n11 successfully unpacked package on client node: EXASolution-4.1.14-COS-4.2.7_x86_64.tar.gz
      n11 successfully unpacked package on client node: EXASolution-4.2.7_x86_64.tar.gz
      n11 successfully updated EXAStorage metadata.
      n11 successfully synchronized EXAoperation.
      n11 successfully unpacked package on client node: EXARuntime-4.2.1_x86_64.tar.gz
      n11 successfully unpacked package on client node: EXAClusterOS-4.2.7_CentOS-6.4_x86_64.tar.gz
      n11 Node does not support CPU power management (requested 'performance').
      n11 Prepare boot process stage 3.
      n11 Hard drives mounted.
      n11 Mount hard drives.
      n11 client mac address of eth1 matches the expected value (08:00:27:1F:64:0D)
      n11 client mac address of eth0 matches the expected value (08:00:27:6F:75:C3)
      n11 Initialize boot process.
      n11 client mac adress is '08:00:27:6F:75:C3'
      n11 client version is '4.2.7'
      n11 client ID is '27.1.0.11'
      Booting Start boot process stage 2 for '27.1.0.11'.

      Do not start the EXAStorage service or any EXASolution instance at this time!

      11. Suspend all database nodes
      • Open the Configuration > Nodes page in EXAoperation
      • In the tab "Cluster Nodes", please select all nodes
      • Select "Stop cluster services" from actions dropdown menu
      • Confirm with click on the button "Execute"
      • Reload the page and until all nodes indicate the State/Op. "Suspended"
      12. Upload CentOS 6.4 Patchlevel 1
      • Open the Configuration > Software page in EXAoperation
      • In the tab "Versions" please find the input box labelled "Software Update File:"
      • Click on the button "Browse" (label depends on browser, language and operating system)
      • Choose "EXAClusterOS-CentOS-6.4_Patchlevel-1.pkg" in the newly opened file manager view
      • Confirm with click on the button "Submit"
      • After upload and installation (which takes about 15 minutes), the EXAClusterOS Version changes to "4.2.7 (+ OS patchlevel 1)" and EXAoperation will display displays the message:

        Kernel has been updated. Please shutdown databases, Storage, nodes and restart license server to finish update.

      13. Reboot the license server
      • Open the Configuration > Nodes page in EXAoperation
      • Navigate down to the fieldset "License Nodes"
      • Click on the button "Reboot" next to the license server (usually node n0010)
      • If reboot is not possible, you may open the license server console (e.g. in iDRAC or vSphere) and send the key sequence CTRL + ALT + DEL.
      • Wait for the license server to finish it's startup procedure (about 15 minutes) and log into EXAoperation again
      14. Reboot the database nodes
      • Navigate to the Configuration > Nodes page
      • Select all nodes in the tab "Cluster Nodes"
      • Choose "Reboot" from actions dropdown menu and confirm with click on button "Execute"
      • Wait for the nodes to finish reboot (about 5 to 10 minutes)
      • Reload the nodes page until the State/Op. column changes from "booting" to "running" for all nodes (takes about 10 minutes)
      • Again, you may watch the boot process in an appropriately configured logservice (Please ignore the error message "failed to install kernel package on client node." if you encounter it during the first boot after the update)

      Keep the database nodes running now but do not start EXAStorage or any EXASolution instance yet!

      15. Upload CentOS 6.4 Patchlevel 2
      • Open the Configuration > Software page in EXAoperation
      • In the tab "Versions" please find the input box labelled "Software Update File:"
      • Click on the button "Browse" (label depends on browser, language and operating system)
      • Choose "EXAClusterOS-CentOS-6.4_Patchlevel-2.pkg" in the newly opened file manager view
      • Confirm with click on the button "Submit"
      • After upload and installation (which takes about 5 minutes), the EXAClusterOS Version changes to "4.2.7 (+ OS patchlevel 2)"
      16. Upload EXASolution Version 4.2.8
      • Open the Configuration > Software page in EXAoperation
      • In the tab "Versions" please find the input box labelled "Software Update File:"
      • Click on the button "Browse" (label depends on browser, language and operating system)
      • Choose "EXASolution-4.2.8_x86_64.pkg" in the newly opened file manager view
      • Confirm with click on the button "Submit"
      • After upload, the EXASolution Versions will list "4.2.8"
      17. Review the installation history
      • Open the Configuration > Software page in EXAoperation
      • In the tab "Versions" please click on the button "Show Installation History"
      • The following items will appear:
      Installed EXASolution 4.2.8
      Updated to operating system patchlevel 2
      Updated to operating system patchlevel 1
      Updated to EXAClusterOS 4.2.7
      18. Startup EXAStorage
      • Navigate to the EXAoperation page Services > EXAStorage
      • Ensure that all database nodes (n11 upwards) indicate the State "Running"
      • Click on the button "Startup Storage Service" and confirm your choice when prompted
      • After the EXAStorage page reloaded, check the status of all nodes, disks and volumes
      19. Update and start the databases
      • Open the Services > EXASolution page and repeat the following steps for all instances:
      • Click on an EXASolution instance name to open the properties page
      • Click on the button "Edit" on the bottom of the page to open the "Edit Database" form
      • Select "4.2.8" from the dropdown menu labelled "Version" and confirm with click on the button "Apply"
      • You will be redirected to the EXASolution instance properties page
      • From the "Actions" dropdown menu please select "Startup" and confirm with click on the button "Submit"
      • Navigate back to the Services > EXASolution page and reload until the database indicates the status "Running"
      • You may follow the procedure in an appropriate logservice:

      EXASolution DEMO is accepting connections
      System is ready to receive client connections.
      System started successfully in partition 44.
      User 0 requests startup of system.
      User 0 requests new system setup.

      20. Start EXAoperation plugins

      If required, you may now start services delivered through EXAoperaton plugins.

      Show
      Synopsis This article guides you through the update procedure from EXASuite version 4.2.6 (plain, without OS patchlevels) to EXASolution 4.2.8 and OS patchlevel 2. The update requires a maintenance window of about two hours and will be performed in four steps: Update to EXASuite version 4.2.7 (~ 45 minutes) Update to OS Patchlevel 1 (~ 45 minutes) Update to OS Patchlevel 2 (~ 10 minutes) Update to EXASolution 4.2.8 (~ 10 minutes) Please note that the the tasks performed in EXAoperation require a user with at least "Administrator" privileges and it is vital to wait for uploads and reboots to finish completely! Prereqesites Please download the following packages from the EXASOL customer portal : Package Description Size (MiB) MD5 Checksum EXAClusterOS-4.2.7_LS-Update.pkg EXASuite LS update package 104.5 110afeaa6802fc2e04706e987a1bcfe5 EXAClusterOS-CentOS-6.4_Patchlevel-1.pkg EXASuite security updates 294.3 efc3b46a717b293560d27cf3ecd99b92 EXAClusterOS-CentOS-6.4_Patchlevel-2.pkg EXASuite security updates 50.5 b5fe3f427cd7a48e50e8873c3d4aaef3 EXASolution-4.2.8_x86_64.pkg EXASolution package 44.7 6f4d8ad26b59a93333d914373b3b4b4f Installation instructions 1. Check Software Versions Open Configuration > Software in EXAoperation and click on the tab "Versions" EXAClusterOS 4.2.1 is required as minimum version for the update to EXASuite 4.2.7 2. EXAoperation master node The update must be applied to the license server since it is the only node that boots from the local hard drive. In EXAoperation, please navigate to Configuration > Network Open the tab "System" Ensure that the license server (usually node n0010) is listed as "License Server Node" Move EXAoperation if the license server is not the master node: Open the Page Services > EXAoperation Select "n0010" from dropdown list Confirm with click on th button "Move to specified Node" 3. Check database operaton Navigate to the EXAoperation page Services > EXASolution Review the database list and check if the column "Background Restore" indicates "None" on all instances 4. Upload EXASuite 4.2.7 Open the Configuration > Software page in EXAoperation In the tab "Versions" please find the input box labelled "Software Update File:" Click on the button "Browse" (label depends on browser, language and operating system) Choose "EXAClusterOS-4.2.7_LS-Update.pkg" in the newly opened file manager view Confirm with click on the button "Submit" and wait until EXAoperation displays the message: First part of update process succeeded. Please shutdown databases, Storage and nodes and restart license server. In the EXAoperation Services > Monitoring page you may open an appropriately defined logservice that will present the messages: Software update First part of update process succeeded. Please shutdown databases and nodes and restart license server. Software update No need to update kernel 2.6.32-358.0.1.el6.centos.plus.x86_64. Software update Start update process to EXAClusterOS version 4.2.7. 5. Shutdown all databases Open the Services > EXASolution page Select all (running) EXASolution instances Click on the button "Shutdown" Reload the page until all instances change their status from "Running" to "Created" Again, you may follow the procedure in an appropriate logservice: System marked as stopped. Successfully send retry shutdown event to system partition 64. EXASolution DEMO is rejecting connections controller-st(0.0): Shutdown called. User 0 requests shutdown of system. 6. Shutdown EXAStorage Navigate to the EXAoperation page Services > EXAStorage Click on the button "Shutdown Storage Service" and confirm your choice when prompted. 7. Suspend Nodes Open the Configuration > Nodes page in EXAoperation In the tab "Cluster Nodes", please select all nodes Select "Stop cluster services" from actions dropdown menu Confirm with click on the button "Execute" Reload the page and until all nodes indicate the State/Op. "Suspended" 8. Reboot the license server Open the Configuration > Nodes page in EXAoperation Navigate down to the fieldset "License Nodes" Click on the button "Reboot" next to the license server (usually node n0010) If reboot is not possible, you may open the license server console (e.g. in iDRAC or vSphere) and send the key sequence CTRL + ALT + DEL. Wait for the license server to finish it's startup procedure (about 10 minutes) and log into EXAoperation again 9. Check Software Versions Open Configuration > Software in EXAoperation and click on the tab "Versions" The field labelled EXAClusterOS must now present version "4.2.7" 10. Reboot the database nodes Navigate to the Configuration > Nodes page Select all nodes in the tab "Cluster Nodes" Choose "Reboot" from actions dropdown menu and confirm with click on button "Execute" Wait for the nodes to finish reboot (about 5 to 10 minutes) Reload the nodes page until the State/Op. column changes from "booting" to "running" for all nodes You may watch the boot process (of node n11 in this example) in an appropriately configured logservice: n11 Boot process finished after 259 seconds n11 Boot process stage 3 finished. n11 Start boot process stage 3. n11 successfully initialized thresholds for node monitoring n11 successfully unpacked package on client node: JDBC_Drivers-2013-04-24.tar.gz n11 successfully unpacked package on client node: Oracle-InstantClient-10.2_x86_64.tar.gz n11 successfully unpacked package on client node: EXASolution-4.1.14-COS-4.2.7_x86_64.tar.gz n11 successfully unpacked package on client node: EXASolution-4.2.7_x86_64.tar.gz n11 successfully updated EXAStorage metadata. n11 successfully synchronized EXAoperation. n11 successfully unpacked package on client node: EXARuntime-4.2.1_x86_64.tar.gz n11 successfully unpacked package on client node: EXAClusterOS-4.2.7_CentOS-6.4_x86_64.tar.gz n11 Node does not support CPU power management (requested 'performance'). n11 Prepare boot process stage 3. n11 Hard drives mounted. n11 Mount hard drives. n11 client mac address of eth1 matches the expected value (08:00:27:1F:64:0D) n11 client mac address of eth0 matches the expected value (08:00:27:6F:75:C3) n11 Initialize boot process. n11 client mac adress is '08:00:27:6F:75:C3' n11 client version is '4.2.7' n11 client ID is '27.1.0.11' Booting Start boot process stage 2 for '27.1.0.11'. Do not start the EXAStorage service or any EXASolution instance at this time! 11. Suspend all database nodes Open the Configuration > Nodes page in EXAoperation In the tab "Cluster Nodes", please select all nodes Select "Stop cluster services" from actions dropdown menu Confirm with click on the button "Execute" Reload the page and until all nodes indicate the State/Op. "Suspended" 12. Upload CentOS 6.4 Patchlevel 1 Open the Configuration > Software page in EXAoperation In the tab "Versions" please find the input box labelled "Software Update File:" Click on the button "Browse" (label depends on browser, language and operating system) Choose "EXAClusterOS-CentOS-6.4_Patchlevel-1.pkg" in the newly opened file manager view Confirm with click on the button "Submit" After upload and installation (which takes about 15 minutes), the EXAClusterOS Version changes to "4.2.7 (+ OS patchlevel 1)" and EXAoperation will display displays the message: Kernel has been updated. Please shutdown databases, Storage, nodes and restart license server to finish update. 13. Reboot the license server Open the Configuration > Nodes page in EXAoperation Navigate down to the fieldset "License Nodes" Click on the button "Reboot" next to the license server (usually node n0010) If reboot is not possible, you may open the license server console (e.g. in iDRAC or vSphere) and send the key sequence CTRL + ALT + DEL. Wait for the license server to finish it's startup procedure (about 15 minutes) and log into EXAoperation again 14. Reboot the database nodes Navigate to the Configuration > Nodes page Select all nodes in the tab "Cluster Nodes" Choose "Reboot" from actions dropdown menu and confirm with click on button "Execute" Wait for the nodes to finish reboot (about 5 to 10 minutes) Reload the nodes page until the State/Op. column changes from "booting" to "running" for all nodes (takes about 10 minutes) Again, you may watch the boot process in an appropriately configured logservice (Please ignore the error message "failed to install kernel package on client node." if you encounter it during the first boot after the update) Keep the database nodes running now but do not start EXAStorage or any EXASolution instance yet! 15. Upload CentOS 6.4 Patchlevel 2 Open the Configuration > Software page in EXAoperation In the tab "Versions" please find the input box labelled "Software Update File:" Click on the button "Browse" (label depends on browser, language and operating system) Choose "EXAClusterOS-CentOS-6.4_Patchlevel-2.pkg" in the newly opened file manager view Confirm with click on the button "Submit" After upload and installation (which takes about 5 minutes), the EXAClusterOS Version changes to "4.2.7 (+ OS patchlevel 2)" 16. Upload EXASolution Version 4.2.8 Open the Configuration > Software page in EXAoperation In the tab "Versions" please find the input box labelled "Software Update File:" Click on the button "Browse" (label depends on browser, language and operating system) Choose "EXASolution-4.2.8_x86_64.pkg" in the newly opened file manager view Confirm with click on the button "Submit" After upload, the EXASolution Versions will list "4.2.8" 17. Review the installation history Open the Configuration > Software page in EXAoperation In the tab "Versions" please click on the button "Show Installation History" The following items will appear: Installed EXASolution 4.2.8 Updated to operating system patchlevel 2 Updated to operating system patchlevel 1 Updated to EXAClusterOS 4.2.7 18. Startup EXAStorage Navigate to the EXAoperation page Services > EXAStorage Ensure that all database nodes (n11 upwards) indicate the State "Running" Click on the button "Startup Storage Service" and confirm your choice when prompted After the EXAStorage page reloaded, check the status of all nodes, disks and volumes 19. Update and start the databases Open the Services > EXASolution page and repeat the following steps for all instances: Click on an EXASolution instance name to open the properties page Click on the button "Edit" on the bottom of the page to open the "Edit Database" form Select "4.2.8" from the dropdown menu labelled "Version" and confirm with click on the button "Apply" You will be redirected to the EXASolution instance properties page From the "Actions" dropdown menu please select "Startup" and confirm with click on the button "Submit" Navigate back to the Services > EXASolution page and reload until the database indicates the status "Running" You may follow the procedure in an appropriate logservice: EXASolution DEMO is accepting connections System is ready to receive client connections. System started successfully in partition 44. User 0 requests startup of system. User 0 requests new system setup. 20. Start EXAoperation plugins If required, you may now start services delivered through EXAoperaton plugins.
    • Category 1:
      Cluster Administration - Update

      Attachments

        Issue Links

          Activity

            People

            • Assignee:
              CaptainEXA Captain EXASOL
              Reporter:
              CaptainEXA Captain EXASOL
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: