Answer
This is a TEMP tablespace sizing issue — the fix is increasing the TEMP tablespace's temp file size (a jump to around 20GB has resolved this in practice), and if the underlying disk doesn't have room for that, increasing the drive's free space first. Since this is typically an infrastructure-level change, it usually needs to go through whichever team manages the database server's storage (e.g. a hosting/infrastructure support ticket) rather than something changed from within the application itself.