Skip to main content
FlashGrid.io

Resizing database server (FlashGrid Server on AWS)

  • Updated
  • Products: FlashGrid Server on AWS

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 FlashGrid server 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@myhostname ~]$ srvctl status asm
ASM is running on flashgrid server

  8. Start the databases stopped previously.