Update to EXASuite 5.0

Synopsis This article guides you through the update procedure from EXASuite version 4.2.10 to the EXASuite version 5.0.0. Please note that The update requires a maintenance window of at least one hour The tasks performed in EXAoperation require a user with at least "Administrator" privileges It is vital to wait for uploads and reboots to finish completely It's recommended to perform a REORGANIZE on database instances after the update (see SOL-95 for details) The Backup format has changed in 5.0.x. A new full backup must be created after the upgrade. Prerequisites Please download the following packages from the EXASOL customer portal : Package Description Size (GiB) MD5 Checksum EXAClusterOS-5.0.0_LS-Update.pkg EXASuite LS update package 1.2 7213c0917a2b087d350df228ace4f1b3 Applicability The EXASuite 5.0.0 LS update package can be applied to: EXACluster OS 5.0.rc1 EXACluster OS 5.0.rc2 EXACluster OS 5.0.rc3 EXACluster OS 4.2.10 EXACluster OS 4.2.9 EXACluster OS 4.2.7 EXACluster OS 4.2.6 EXACluster OS 4.2.5 EXACluster OS 4.2.3 EXACluster OS 4.2.2 EXACluster OS 4.2.1 EXASuite version 5 upwards requires the use of EXAStorage. The legacy filesystem is no longer supported as database backend. Please contact the EXASOL support for details and assistanc on the migration from filesystem to EXAStorage. 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 5.0.0 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. To check: 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 the button "Move to specified Node" Return to the Configuration > Network page and examine if the license server is now the EXAoperation master 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 5.0.0 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-5.0.0_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 a messages similar to: Start update process to EXAClusterOS version 5.0.0. Software update requires kernel update from 2.6.32-358.0.1.el6.centos.plus.x86_64 to 2.6.32-431.el6.centos.plus.x86_64. Successfully installed kernel version 2.6.32-431.el6.centos.plus.x86_64. First part of update process succeeded. Please shutdown databases and nodes and restart license server. 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. When the storage service is down, it looks like: 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 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 "5.0.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.0' 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'). Successfully unpacked package on client node: EXAClusterOS-5.0.0_CentOS-6.5_x86_64.tar.gz Successfully unpacked package on client node: EXARuntime-5.0.0_x86_64.tar.gz Successfully updated kernel packages. Successfully synchronized EXAoperation. Successfully updated EXAStorage metadata. Successfully unpacked package on client node: EXASolution-5.0.0_x86_64.tar.gz Successfully unpacked package on client node: EXASolution-4.2.11-COS-5.0.0_x86_64.tar.gz Successfully unpacked package on client node: Oracle-InstantClient-10.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 unpacked package on client node: Plugin.RAID.tw_cli-10.1.tar.gz Successfully initialized thresholds for node monitoring Start boot process stage 3. Doing CentOS update from version 6.4 to 6.5. CentOS update succeeded. 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 (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 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 "5.0.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 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. 13. Start EXAoperation plugins If required, you may now start services delivered through EXAoperaton plugins.