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

How to upgrade from version 5 to version 6

    Details

    • Type: How To
    • Status: Published
    • Affects Version/s: EXASolution 5.0.0
    • Fix Version/s: None
    • Component/s: EXAoperation, EXASolution
    • Labels:
      None
    • Solution:
      Hide

      This article guides you through the update procedure from EXASuite version 5.0.0+ to EXASuite version 6.0.

      Before you start

      Before proceeding with the upgrade, ensure you have read and understood SOL-450.

      Please note that

      1. The update requires a maintenance window of at least one hour
      2. The tasks performed in EXAoperation require a user with at least "Administrator" privileges
      3. It is vital to wait for uploads and reboots to finish completely
      4. It is strongly recommended that you have a recent backup available, stored remotely, in case of errors during the update
      5. In case, of using public bond interfaces, please either (A) upgrade to version 5.0.21 beforehand or (B) remove these public bond interface before starting the update process and reinsert those interface after the update process finished.

      Prerequisites

      Please download the following packages from the EXASOL customer portal:

      Package Description Size (MiB) MD5 Checksum
      EXAClusterOS-6.0_LS-Update.pkg EXASuite LS update package 383
      Applicability

      The EXASuite 6.0 LS update package can be applied to:

      EXAClusterOS 5.0.0+

      Installation instructions

      1. Check Software Versions

      Open Configuration > Software in EXAoperation and click on the tab "Versions"
      EXAClusterOS 5.0.0+ is required as minimum version for the update to EXASuite 6.0

      2. EXAoperation master node
      • The update must be applied to a real license server since it is the only node that boots from the local hard drive.
      • Check the following things:
      • In EXAoperation, navigate to Configuration > Network
      • Open the tab "System"
      • Ensure that the license server (usually node n0010) is listed as "License Server Node"

      • if the license server is not the "License Server Node", then move EXAoperation :
        • Open the Page Services > EXAoperation
        • Select "n0010" from dropdown list
        • Confirm with click on the button "Move to specified Node"

      • Return to the Configuration > Network page and check if the license server is now the EXAoperation master
      3. Check database operation

      Navigate to the EXAoperation page Services > EXASolution
      Review the database list and check if the column "Background Restore" indicates "None" on all instances

      4. 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.

      5. Shutdown EXAStorage
      • Navigate to the EXAoperation page Services > EXAStorage

      • Click on the button "Shutdown Storage Service" and confirm your choice when prompted. When the storage service is down, it looks as follows:

      6. Suspend Nodes
      • Open the Configuration > Nodes page in EXAoperation
      • Select all nodes in the tab "Cluster 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"

      Important

      (!)The 2nd state of every node must be "Active"! Restarting a node which is on "To Install" state will lead into an unrecoverable data loss!

      7. Upload EXASuite 6.0
      • Open the Configuration > Software page in EXAoperation
      • In the tab "Versions" please find the input box labeled "Software Update File:"
      • Click on the button "Browse" (label depends on browser, language and operating system)
      • Choose "EXAClusterOS-6.0_LS-Update.pkg" in the newly opened file selector

      • Confirm by clicking 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.

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

      Start update process to EXAClusterOS version 6.0.
      Current kernel is more recent than required kernel. Do not install required kernel.
      First part of update process succeeded. Please shutdown databases and nodes and restart license server.

      8. Reboot the license server
      • Open the Configuration > Nodes page in EXAoperation
      • Navigate down to the section "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 to 25 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 "6.0"
      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 15 to 25 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:
          client ID is '27.1.0.16'
          Client version is '5.0.15'
          Client mac adress is '00:11:22:33:44:55'
          Initialize boot process.
          Client mac address of eth0 matches the expected value (00:11:22:33:44:55)
          Client mac address of eth1 matches the expected value (00:12:34:56:78:9A)
          Mount hard drives.
          Hard drives mounted.
          Prepare boot process stage 3.
          Node does not support CPU power management (requested 'performance').
          unpacked package on client node: EXAClusterOS-6.0_CentOS-6.5_x86_64.tar.gz
          Successfully unpacked package on client node: EXARuntime-6.0_x86_64.tar.gz
          Successfully synchronized EXAoperation.
          Successfully updated EXAStorage metadata.
          Successfully unpacked package on client node: EXASolution-6.0_x86_64.tar.gz
          Successfully unpacked package on client node: EXASolution-4.2.16-COS-6.0_x86_64.tar.gz
          Successfully unpacked package on client node: Oracle-InstantClient-11.2_x86_64.tar.gz
          Successfully unpacked package on client node: JDBC_Drivers-2014-03-05.tar.gz
          Successfully unpacked package on client node: java-package-2014-04-29.tar.gz
          Successfully initialized thresholds for node monitoring
          Start boot process stage 3.
          Boot process stage 3 finished.
          Boot process stages 1 to 3 took 833 seconds.
      
      11. Startup EXAStorage
      • Navigate to the EXAoperation page Services > EXAStorage
      • Ensure that all database nodes indicates the state "Running"
      • Click on the button "Startup Storage Service" and confirm your choice when prompted
      • After the EXAStorage page has been reloaded, check the status of all nodes, disks and volumes
      12. 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 "6.0" 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 exa_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.
      
      Show
      This article guides you through the update procedure from EXASuite version 5.0.0+ to EXASuite version 6.0. Before you start Before proceeding with the upgrade, ensure you have read and understood SOL-450 . Please note that 1. The update requires a maintenance window of at least one hour 2. The tasks performed in EXAoperation require a user with at least "Administrator" privileges 3. It is vital to wait for uploads and reboots to finish completely 4. It is strongly recommended that you have a recent backup available, stored remotely, in case of errors during the update 5. In case, of using public bond interfaces, please either (A) upgrade to version 5.0.21 beforehand or (B) remove these public bond interface before starting the update process and reinsert those interface after the update process finished. Prerequisites Please download the following packages from the EXASOL customer portal: Package Description Size (MiB) MD5 Checksum EXAClusterOS-6.0_LS-Update.pkg EXASuite LS update package 383 Applicability The EXASuite 6.0 LS update package can be applied to: EXAClusterOS 5.0.0+ Installation instructions 1. Check Software Versions Open Configuration > Software in EXAoperation and click on the tab "Versions" EXAClusterOS 5.0.0+ is required as minimum version for the update to EXASuite 6.0 2. EXAoperation master node The update must be applied to a real license server since it is the only node that boots from the local hard drive. Check the following things: In EXAoperation, navigate to Configuration > Network Open the tab "System" Ensure that the license server (usually node n0010) is listed as "License Server Node" if the license server is not the "License Server Node", then move EXAoperation : Open the Page Services > EXAoperation Select "n0010" from dropdown list Confirm with click on the button "Move to specified Node" Return to the Configuration > Network page and check if the license server is now the EXAoperation master 3. Check database operation Navigate to the EXAoperation page Services > EXASolution Review the database list and check if the column "Background Restore" indicates "None" on all instances 4. 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. 5. Shutdown EXAStorage Navigate to the EXAoperation page Services > EXAStorage Click on the button "Shutdown Storage Service" and confirm your choice when prompted. When the storage service is down, it looks as follows: 6. Suspend Nodes Open the Configuration > Nodes page in EXAoperation Select all nodes in the tab "Cluster 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" Important (!)The 2nd state of every node must be "Active"! Restarting a node which is on "To Install" state will lead into an unrecoverable data loss! 7. Upload EXASuite 6.0 Open the Configuration > Software page in EXAoperation In the tab "Versions" please find the input box labeled "Software Update File:" Click on the button "Browse" (label depends on browser, language and operating system) Choose "EXAClusterOS-6.0_LS-Update.pkg" in the newly opened file selector Confirm by clicking 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. On the EXAoperation Services > Monitoring page you may open an appropriately defined logservice that will present messages similar to: Start update process to EXAClusterOS version 6.0. Current kernel is more recent than required kernel. Do not install required kernel. First part of update process succeeded. Please shutdown databases and nodes and restart license server. 8. Reboot the license server Open the Configuration > Nodes page in EXAoperation Navigate down to the section "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 to 25 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 "6.0" 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 15 to 25 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: client ID is '27.1.0.16' Client version is '5.0.15' Client mac adress is '00:11:22:33:44:55' Initialize boot process. Client mac address of eth0 matches the expected value (00:11:22:33:44:55) Client mac address of eth1 matches the expected value (00:12:34:56:78:9A) Mount hard drives. Hard drives mounted. Prepare boot process stage 3. Node does not support CPU power management (requested 'performance'). unpacked package on client node: EXAClusterOS-6.0_CentOS-6.5_x86_64.tar.gz Successfully unpacked package on client node: EXARuntime-6.0_x86_64.tar.gz Successfully synchronized EXAoperation. Successfully updated EXAStorage metadata. Successfully unpacked package on client node: EXASolution-6.0_x86_64.tar.gz Successfully unpacked package on client node: EXASolution-4.2.16-COS-6.0_x86_64.tar.gz Successfully unpacked package on client node: Oracle-InstantClient-11.2_x86_64.tar.gz Successfully unpacked package on client node: JDBC_Drivers-2014-03-05.tar.gz Successfully unpacked package on client node: java-package-2014-04-29.tar.gz Successfully initialized thresholds for node monitoring Start boot process stage 3. Boot process stage 3 finished. Boot process stages 1 to 3 took 833 seconds. 11. Startup EXAStorage Navigate to the EXAoperation page Services > EXAStorage Ensure that all database nodes indicates the state "Running" Click on the button "Startup Storage Service" and confirm your choice when prompted After the EXAStorage page has been reloaded, check the status of all nodes, disks and volumes 12. 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 "6.0" 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 exa_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.
    • Category 1:
      Cluster Administration - Update

      Attachments

        Issue Links

        1. 001 DBstatus.png
          001 DBstatus.png
          22 kB
        2. 002 shutdown_all_databases-1.png
          002 shutdown_all_databases-1.png
          59 kB
        3. 003 all_databases-shutdown-2.png
          003 all_databases-shutdown-2.png
          51 kB
        4. 004 ShutdownExaStorage.png
          004 ShutdownExaStorage.png
          101 kB
        5. 005 exastoragedown.png
          005 exastoragedown.png
          58 kB
        6. 006 suspend_nodes.png
          006 suspend_nodes.png
          107 kB
        7. 007 6_suspend_nodes-2.png
          007 6_suspend_nodes-2.png
          125 kB
        8. 008 softwareVersion.png
          008 softwareVersion.png
          40 kB
        9. 009 upload.png
          009 upload.png
          16 kB
        10. 011 8_reboot_licenseserver_exaoperation.png
          011 8_reboot_licenseserver_exaoperation.png
          77 kB
        11. 012 reboot_database_nodes.png
          012 reboot_database_nodes.png
          122 kB
        12. 014 update_and_start_database-1.png
          014 update_and_start_database-1.png
          50 kB
        13. 017_update_and_start_database-3.png
          017_update_and_start_database-3.png
          41 kB
        14. license_server_master_node.png
          license_server_master_node.png
          37 kB
        15. move_to_specified_node.png
          move_to_specified_node.png
          38 kB

          Activity

            People

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

              Dates

              • Created:
                Updated: