SkyBase for Oracle on AWS: Maintenance Tasks


Rebooting SkyBase system

To reboot the SkyBase system:

  1. Stop all running databases.

  2. Reboot the SkyBase system. The following command will gracefully stop HAS, FlashGrid services and restarts the AWS instance.

    # flashgrid-node reboot
  3. Wait until ASM is started:

    [grid@skybase ~]$ srvctl status asm
    ASM is running on skybase
  4. Start the databases stopped at step 1.

Powering off SkyBase system

  1. Stop all running databases.

  2. Stop the SkyBase system. The following command will gracefully stop HAS, FlashGrid services and the AWS instance.
    # flashgrid-node poweroff

Resizing AWS instance

Resizing the AWS instance may be needed for performance or cost reasons. Resizing requires database downtime.

  1. Update SGA and PGA sizing parameters for the databases according to the new AWS instance memory size

  2. Skip this step unless you have vm.nr_hugepages parameter in /etc/sysctl.conf manually configured. If you have it manually configured then update the parameters according to the new AWS instance size.

  3. Stop all running databases.

  4. Stop the SkyBase system. The following command will gracefully stop HAS, FlashGrid services and the AWS instance.

    # flashgrid-node poweroff
  5. Resize the AWS instance using AWS console.

  6. Start the AWS instance.

  7. Wait until ASM is started:

    [grid@skybase ~]$ srvctl status asm
    ASM is running on skybase
  8. Start the databases stopped previously.

Adding EBS volumes for use in ASM

When adding new disks make sure that each disk group has disks of the same size.

  1. Create and attach new volumes to the AWS instance. Attach the volumes using disk names xvdba through xvdbz - these disks will be automatically available for use in ASM.

  2. Confirm FlashGrid names of the new disks, e.g. myhostname.xvdbb

    [fg@skybase ~] $ flashgrid-node

    If the new disks are not listed then check that the corresponding devices (e.g. /dev/xvdbb) are visible in the OS. If they are visible in the OS then run # flashgrid-node reload-config and check output of flashgrid-cluster drives again. If they are not visible in the OS then double-check that you have attached them with correct device names.

  3. Add the new disks to an existing disk group (or create a new disk group). Example:

    [fg@skybase ~] $ flashgrid-dg add-disks -G MYDG -d /dev/flashgrid/myhostname.xvdb[a-c]

Removing EBS volumes

  1. Determine FlashGrid names of the disks to be removed, e.g. myhostname.xvdbb or myhostname.xvdbc:

    [fg@skybase ~] $ flashgrid-node
  2. If the disks are members of an ASM disk group then drop the disks from the disk group. Example:

    SQL> alter diskgroup MYDG
    drop disk SKYBASE$XVDBB
    drop disk SKYBASE$XVDBC
    rebalance wait;
  3. Prepare the disks for removal. Example:

    [fg@skybase ~] $ flashgrid-node stop-target /dev/flashgrid/myhostname.xvdbb
    [fg@skybase ~] $ flashgrid-node stop-target /dev/flashgrid/myhostname.xvdbc
  4. Detach the EBS volumes from the AWS instance.

Updating FlashGrid software and Linux kernel using SkyBase Update package

SkyBase Update package is a single self-extracting bash script file that allows updating the following components:

  • FlashGrid Storage Fabric RPM
  • FlashGrid Diagnostics RPM
  • FlashGrid Cloud Area Network RPM
  • FlashGrid Health Checker RPM
  • Linux kernel (can be skipped)

Using this package makes it easier to have the update performed to the latest validated set of software components and helps avoid accidental installation of incompatible software versions.

Note: Please review corresponding release notes and check with FlashGrid support before performing any major version update. A major version consists of the first two numbers. The third number represents a revision (hotfix). For example, update from version 19.02.x to 19.05.x is major, but from 19.05.100 to 19.05.200 is a hotfix revision.

To update software using SkyBase Update package, perform the following steps

  1. Create backup snapshot of the OS disk

    a. Flush OS buffers:

    # sync

    b. Create snapshot of the OS disk /dev/sda1 using AWS console or CLI

  2. Stop all running databases.

  3. Stop Oracle High Availability Services:

    # crsctl stop has
  4. Stop the FlashGrid Diagnostics monitoring service:

    # systemctl stop flashgrid-node-monitor
  5. Stop the FlashGrid Storage Fabric services:

    # flashgrid-node stop
  6. Stop the FlashGrid Cloud Area Network service:

    # systemctl stop flashgrid-clan
  7. Run the update script as root.

    Example with kernel update:

    # bash skybase_update-19.5.17.85011.sh

    Example without kernel update:

    # bash skybase_update-19.5.17.85011.sh skip-kernel-update
  8. Reboot the server:

    # reboot

Updating FlashGrid software RPMs

Note: In most cases using SkyBase Update package is recommended for updating FlashGrid software and OS kernel.

Note: Please review corresponding release notes and check with FlashGrid support before performing any major version update. A major version consists of the first two numbers. The third number represents a revision (hotfix). For example, update from version 19.02.x to 19.05.x is major, but from 19.05.100 to 19.05.200 is a hotfix revision.

To update flashgrid-sf and/or flashgrid-clan RPM perform the following steps

  1. Stop all running databases.

  2. Stop Oracle High Availability Services:

    # crsctl stop has
  3. Stop the FlashGrid Storage Fabric services:

    # flashgrid-node stop
  4. Stop the FlashGrid Cloud Area Network service:

    # systemctl stop flashgrid-clan
  5. Update the flashgrid-sf and/or flashgrid-clan RPM on the server using yum or rpm tool.
  6. Reboot the server:

    # reboot

To update flashgrid-diags RPM

  1. Update the flashgrid-diags RPM using yum or rpm tool

  2. Restart the flashgrid-node-monitor service (this can be done without stopping any Oracle services):
    # systemctl restart flashgrid-node-monitor

Updating OS

Note: Running yum update without first stopping Oracle and FlashGrid services may result in the services restarting non-gracefully during the update.

To update OS on a running server perform the following steps

  1. Create backup snapshot of the OS disk

    a. Flush OS buffers:

    # sync

    b. Create snapshot of the OS disk /dev/sda1 using AWS console or CLI

  2. Stop all running databases.

  3. Stop Oracle High Availability Services:

    # crsctl stop has
  4. Stop FlashGrid Storage Fabric services:

    # flashgrid-node stop
  5. Install OS updates:

    # yum update
  6. Reboot the server
    # reboot

Applying Grid Infrastructure and Database patches

For applying single patches or Release Updates / Patch Set Updates to Grid Infrastructure or Database homes follow standard procedures documented by Oracle.

Note: Before applying the latest Release Update from Oracle, we recommend to request confirmation from FlashGrid support . FlashGrid performs validation of every Release Update to minimize risk of compatibility or reliability issues. Typical time to complete the validation is 3 weeks after the Release Update is publicly available.