Reloading data is recommended in the following cases:
After resizing the cluster by adding or removing nodes. Reloading data distributes the data among all nodes of the resized cluster.
After a maintenance window. Maintenance involves a DB System restart, which requires that you reload data into HeatWave. On OCI, consider setting up a MySQL HeatWave Service event notification or Service Connector Hub notification to let you know when an update has occurred. For information about MySQL DB System maintenance:
For MySQL HeatWave on OCI, see Maintenance in the MySQL HeatWave on OCI Service Guide.
For MySQL HeatWave on AWS, see Maintenance, in the MySQL HeatWave on AWS Service Guide.
For HeatWave in Oracle Database Service for Azure (ODSA), see the Oracle Database Service for Azure documentation.
For information about MySQL HeatWave Service events, see MySQL HeatWave Service Events.
For information about Service Connector Hub, see Service Connector Hub.
For table load instructions, see Section 2.2, “Loading Data to HeatWave”.Tip
Instead of loading data into HeatWave manually, consider using the Auto Parallel Load utility, which prepares and loads data for you using an optimized number of parallel load threads. See Section 2.2.3, “Loading Data Using Auto Parallel Load”.
When the HeatWave Cluster is restarted due to a DB System restart. Data in the HeatWave Cluster is lost in this case, requiring reload.