QuickSight SPICE Ingestion Failure – SQL_EXCEPTION Error

Hello AWS QuickSight Support Team,

I am a Data Analyst, I am experiencing an issue while ingesting data from MySQL into SPICE in AWS QuickSight. The ingestion fails with the following error:

  • Ingestion ID: 5683a7dc-a176-4918-87c5-b3a0d09a91cf
  • Error Type: SQL_EXCEPTION
  • Error Details: "Internal error: Required history data has been purged, please retry transaction."

Context:

  • My data source is MySQL, and I am using SPICE for ingestion.
  • A temporary workaround that works is restarting the MySQL instance, but I need a permanent solution.
  • I suspect it might be related to binlog retention or transaction history purging, but I need confirmation.

Hello @humairooh , welcome to the QuikSight community!

Do you have a manual or incremental refresh set up for this dataset or are you manually refreshing this dataset every time?

hi duncan, I set up scheduled refresh hourly.

1 Like

Hey @humairooh

To troubleshoot this on the QuickSight side, I would try using an incremental refresh with a look back window that only grabs what you need instead of refreshing all rows of your dataset.