You might try creating a High Availability setup with a brand-new secondary database created via unload/reload. Once the HA setup is running, and the slim secondary is up-to-date with respect to the bloated primary, stop the bloated primary database and let the slim secondary database become the primary.
↧